Internal dashboards
Operational data a small team already has, made legible. Filters, exceptions surfaced, actions one click away instead of one spreadsheet away.
Next.jsPostgresCharts
Fixed scope · Fixed price · 14 days
Ship the product, not the pitch deck.
We design and build the front end of your MVP in two weeks. Fixed scope, fixed price, deployed on your own infrastructure — so you can put something real in front of users and investors instead of describing it.
- 14days
- From kickoff to a live URL
- 1price
- Quoted upfront, never revised
- 100%
- Of the source code is yours
How it works
Three steps, and you know the price after the first one.
Most of what makes a build slip happens before anyone writes code. So the scope is settled, in writing, before the clock starts.
Scoping call
30 minutes
We map what your MVP actually has to prove, then cut everything that does not serve it. You get a written scope and a fixed quote within 24 hours. No charge, no obligation.
Build
10 working days
You get a live preview URL on day one and watch it fill in. Written updates every morning, and one revision round is built into the schedule rather than billed on top of it.
Handoff
Day 14
We deploy to your repo, your Vercel, your domain. Full documented source, no lock-in. Take it in-house from there, or keep us on retainer for the next iteration.
Scope
What a fixed price actually buys.
A studio that will not tell you what it does not do has not thought hard enough about what it does.
Every engagement includes
- Product design and UI, made for your actual flows
- Responsive down to mobile, tested on real devices
- Auth, database and one third-party integration
- Deployed to production on your own accounts
- Analytics wired up so you can read the first week
- The repository, documented, transferred to you
What we do not do
- Native iOS or Android apps
- Migrating or rescuing a legacy codebase
- Design files with nobody to build them
- 24/7 on-call support or an SLA
What we build
Small teams, real software, shipped in under two weeks.
The three shapes of project we are set up for. Case studies will replace this section as engagements complete.
Booking and intake
Scheduling, forms and reminders for teams still running on a phone line and a shared inbox. Confirmation and no-show reminders included.
Next.jsSupabaseNotifications
Quoting and billing tools
Line items, margin preview, a document out the other end. Built for the phone, because that is where the work actually gets quoted.
Next.jsPrismaPDF
Pricing
One number, agreed before anyone writes code.
Every engagement is a fixed price against a written scope. No hourly billing, no change orders, no surprise at the end.
We are still finalising packages and pricing. The shape of each engagement is settled — the figures will be published here shortly.
Prototype
For pitching and user interviews.
5 working days
Price to be published
- Up to 6 screens
- Clickable, realistic front end
- Mock data, no backend
- Deployed to a shareable URL
Core package
MVP
For putting it in front of real users.
10 working days
Price to be published
- Up to 14 screens
- Auth and database, working
- One third-party integration
- Production deploy on your infra
- One revision round included
MVP+
For more surface area than two weeks holds.
4 weeks
Price to be published
- Multiple roles and permissions
- Payments and billing flows
- Admin and internal tooling
- Scope agreed in writing first
Continuation retainer
A standing block of build time each month for iterating after launch. Same team, no re-onboarding, cancel any time.
FAQ
The things people ask on the call.
You say front end — do you do the backend too?
Yes, as far as an MVP needs one. Auth, a database, server routes and one integration are part of the MVP package. What we do not do is build infrastructure your traffic does not justify yet. If you outgrow it, that is a good problem and a different project.
Who owns the code?
You do, entirely, from day one. We build in your repository under your account. There is no license, no hosted component you rent from us, and nothing that stops you handing it to another team the day after launch.
What happens if we go over scope?
The quote does not move. If something new comes up mid-build, we park it in writing and it becomes the first thing in the next block — either a retainer month or a second engagement. The fixed price is only meaningful if the scope is genuinely fixed, so we spend real effort on the scope up front.
What stack do you use?
Next.js on Vercel, TypeScript, Postgres, Tailwind. Deliberately boring and widely known, so any developer you hire later can pick it up without a handover from us. We will use something else if you have a good reason, but we will ask what it is.
What do you need from me during the two weeks?
Roughly thirty minutes a day. You review the preview URL, answer questions in a shared thread, and make decisions when we hit a fork. The one thing that reliably slows a build down is a founder who goes quiet for four days.
Do you take equity instead of cash?
No. Fixed-price work and equity pull in opposite directions, and the arrangement tends to sour the moment priorities diverge. If cash is the blocker, the Prototype package exists for exactly that reason.
Two weeks from now, you could be watching someone use it.
We are putting the final pieces in place before opening for enquiries. Packages, pricing and availability will be published on this page.
Read how we work