A working version of your product. Built in four weeks.
Not a Figma prototype. Not a production app. A real, deployed product — with real interactions and real data — that you can test with users and demo to investors.
From $8,000 · Fixed scope · Fixed timeline
Right for you if…
You know what you want to build. You just don't have anything to show yet
You tried building with Lovable, Replit, or Cursor and the result isn't good enough to show anyone
You need something real in front of users or investors before committing to a full development team
You're fundraising and need more than a deck — investors need to click something
You want to find out what's wrong with your idea before you spend six months building it
Four weeks. One focused build.
Week 1
Scope & Flows
- Scope and flow mapping: what we're building and what we're leaving out
- Core user journey definition: 3–5 key flows end to end
- UX decisions made upfront — patterns, structure, information hierarchy
Weeks 2–3
Build & Iterate
- Build using Claude and Codex for AI-assisted development
- Every screen reviewed. We catch what AI gets wrong
- Real data wired up via Supabase — sign-up, persistence, interactions
- Iterative design passes as the product takes shape
Week 4
Polish & Deploy
- Final design polish. Not AI defaults, not generic components
- The product holds up when things don't go as planned
- Deployment to Vercel — accessible via URL
- Handoff document: what's working, what's mocked, what to build next
What you walk away with
- The output looks like it was designed, not generated. Not AI defaults, not generic components
- A step up from Figma in every way that matters: real data flows, real interactions, real error states
- A deployed, working product accessible via URL. Hand it to a user and watch them use it
- Core flows working end to end, with real data persisting via Supabase
- Handoff document: what worked, what to rebuild for production, what to build next
Built on tools your dev team will recognise.
We use the same modern stack that most product teams end up on. If you decide to continue building after this, you're not starting from scratch.
Next.js
Frontend framework
Supabase
Database & auth
Sanity
Content management
Vercel
Deployment
Claude / Codex
Development backbone
What this is. And what it isn't.
What you're testing is whether the product is worth building, before you spend six months and $80–150k building it for real. You'll end four weeks knowing which flows work, which assumptions were wrong, and exactly what your development team needs to build next.
This is not your production codebase. It's built to test, not to scale. The code works for a controlled audience, not thousands of concurrent users. Complex business logic is mocked or simplified. Real payments, compliance layers, and deep third-party integrations are out of scope. That's intentional. You're not ready to build those yet, and neither is your idea.
After the sprint
Most clients use the prototype to validate with users, close a round, or scope their first engineering hire. Some come back for an embedded design retainer to take the product to production. At handoff, we'll give you a specific recommendation on what to do next: not a generic proposal, but a view based on what we learned about your product and where it's headed.
Pricing
Fixed scope, fixed timeline, fixed price. We can typically start within one week of a signed contract.
Test before you build.
Tell us what you're building and how far you've got. We'll scope it and get back to you within 48 hours.
Book a scoping call