Skip to content

I build MVPs end to end — data model, roles, dashboards, integrations and the interface — in weekly slices you can click through. You talk to the engineer who writes the code, and you own every repository and account from day one.

Who it's for

  • Founders launching a marketplace, booking platform, SaaS or online store
  • Teams that validated an idea and now need it built properly
  • Businesses replacing spreadsheets and manual work with their own software

Problems I solve

  • Agencies quote months

    A focused MVP needs the core flow, roles and admin — not every feature on the wish list.

  • Prototypes don't survive users

    No access rules, no tests, no data model that can grow.

  • Hand-offs lose context

    Designer, frontend, backend and PM in a chain; nobody owns the whole flow.

What you get

  • Scope and milestones after a short brief, with an honest range
  • A data model and core flows designed for what breaks: retries, duplicates, edge cases
  • A working preview every week, from database to screen
  • Roles, dashboards and an admin panel your team can actually use
  • Fast pages (Lighthouse 90+), basic SEO and analytics from the start

How it works

  1. 01

    Brief

    The business, the users and what success looks like in numbers. I say plainly if something isn't worth building yet.

  2. 02

    Architecture

    Tables, constraints, API contracts and failure modes, written down before the code.

  3. 03

    Weekly slices

    Each slice lands on a preview URL; you can reprioritise at any point.

  4. 04

    Launch and support

    Monitoring, fixes and improvements after launch, on a retainer or hourly.

Related work

Read on the blog

Questions

How much does an MVP cost?

From $6,000. The final price depends on roles, integrations and the logic behind the screens; after a short brief you get a scope and a fixed price split into weekly milestones.

How long does an MVP take?

It depends on roles, integrations and how much logic sits behind the screens. After the brief you get milestones in weekly slices and a range, not a single optimistic date.

Which stack do you use?

Usually Next.js, TypeScript and PostgreSQL, deployed on Vercel or similar. I'll adapt to your existing stack if there is one.

Who owns the code?

You do. Repositories, hosting, databases and third-party accounts are created under your name from the start.

Can you work with my designer?

Yes. I've built products with a designer's Figma files, and I can also design simple interfaces myself.