MVP Development

Your first release, built and launched. One team, one fixed quote.

We own the whole first release: scope, design, engineering, testing and launch. The core journey your users need works in a deployed product you own. Most focused first releases cost $8,000–$20,000, fixed in writing after scoping.

  • Fixed quote after scoping
  • 60% paid only on reviewed delivery
  • 30 days of defect fixes after launch

A first release does one journey well

We agree the one journey that must work end to end. Everything else waits for version two.

  1. Customer portal

    1. 1Customer signs in
    2. 2Submits a request
    3. 3Sees its status
  2. SaaS tool

    1. 1User creates an account
    2. 2Does the main task
    3. 3Saves the result
  3. AI application

    1. 1User submits information
    2. 2Gets a checked AI output
    3. 3Reviews and keeps it
  4. Booking product

    1. 1Customer picks a time
    2. 2Books it
    3. 3Gets a confirmation

Example scopeIllustrative, not a client project

Customer portal, first release

The kind of first release that fits the published range.

Primary journey
A customer signs in, submits a service request and sees its status
Supporting workflows
  • Staff see and update requests in an admin view
  • An email when a request changes status
  • Google or email sign-in
Left for later
  • Payments
  • Native mobile app
  • Importing old requests

Every build includes

  • One primary user journey, with its supporting workflows listed in the scope
  • UX for the core journey
  • Frontend, backend and the data storage it needs
  • Sign-in and permissions where the product needs them
  • The integrations listed in the scope
  • Tests on the agreed critical paths
  • Deployed in accounts you own
  • Error monitoring and handover documentation
  • 30 days of defect fixes after launch

Priced by scope

Included when the scope lists them, and quoted for.

  • Payments and billing
  • AI features
  • Native mobile apps
  • Data migration
  • Complex or custom integrations

Before you reach out

Is this right for you?

MVP Build is for a new product with a clear first job to do, and someone on your side who can make decisions.

Yes, this is for you

  • Founders and teams who need the whole first release delivered, not individual developers to manage
  • A customer portal, SaaS tool, web app or AI application with one core journey
  • A pilot, launch or customer date the release has to meet
  • Someone on your side who can make product decisions within a few days

Not this. Go here instead

Scope → Design → Build → Verify → Launch

One delivery contact throughout, regular demos, and a decision point before each payment.

  1. 011–2 weeks

    Scope

    We fix the core journey, features, exclusions, dependencies, acceptance criteria, build plan and schedule in writing.

  2. 02Early build

    Design

    UX for the core journey, reviewed with you before the screens are engineered.

  3. 03Most of the timeline

    Build

    Frontend, backend and integrations, demoed regularly. The core journey is shown working on staging.

  4. 04Before launch

    Verify

    We test the agreed critical paths, then you review against the written acceptance criteria.

  5. 05+30 days

    Launch

    Deployed in your accounts with monitoring and handover. We fix defects for 30 days after launch.

Fixed quote, milestone payments

Most focused first releases cost $8,000–$20,000. The fixed quote is confirmed in writing after scoping.

Fit call

Free

Is a first release the right next step?

  • 30-minute callYour product, users and deadline
  • Straightforward productsGet a written scope and fixed quote at no cost

Scope stage

Fixed feecredited in full

For products that need deeper discovery first.

  • Core journey, scope and exclusionsYours to keep whether or not you continue
  • Acceptance criteria and build planWhat “done” means, before money is committed
  • A decision pointGo ahead, change the scope, or stop with the documents
  • Fee agreed before we startCredited against the build if you go ahead

First release build

$8,000–$20,000

Typical for a focused first release, fixed after scoping. What moves the price:

  • Core workflowsHow many the release covers
  • IntegrationsEach external system the product must talk to
  • AI featuresWhether AI is central, and how it is checked
  • Web only, or web and mobileNative apps add a second delivery track
  • 40% on the approved scope, before the build starts
  • 30% when the core journey is demonstrated on staging
  • 30% on acceptance against the written criteria, before production launch
  • Production deployment and handover stay our obligation after the final payment
  • The schedule is confirmed in the approved scope; it assumes your decisions within agreed review times and third parties on time
  • The acceptance review window is agreed in the scope, so sign-off has a clear date
  • New features, changed requirements and third-party changes are scoped and quoted separately
  • A paid Scope stage is credited once, in full, against the total build price

What happens next

  1. 01We reply within 4 working hoursAnd book a free 30-minute fit call.
  2. 02Fit callYour users, core journey, budget and launch date.
  3. 03Written scope and quoteDirectly for straightforward products, or a Scope stage proposal first.

Work we’ve delivered

Real projects, on screen.

Described as they happened.

01
Chess Rocket screens: Lichess play, Stockfish analysis and the puzzle rankingsChess Rocket screens: Lichess play, Stockfish analysis and the puzzle rankingsChess Rocket screens: Lichess play, Stockfish analysis and the puzzle rankings

EdTech · web and mobile

Chess Rocket

Six engineers working as the product’s engineering team for five months

Our team owned delivery across web, iOS/Android, admin and backend, working in weekly rounds set by the client’s feedback. We shipped every feature across all four codebases at once and moved releases to gated dev, pre-prod and production environments on Azure.

“Took Chess Rocket from idea to live product, building puzzles, real-time play and community features that just work. Highly recommended.” 
Kenny Campbell · Chess Rocket

Before

  • Every feature had to land in four separate codebases
  • Store purchases did not unlock premium on Android or show on iOS
  • No separate environments; changes went straight to users

After

  • Weekly feature rounds shipped across web, mobile, admin and backend
  • Store subscriptions fixed end to end
  • Gated dev → pre-prod → production releases, with an onboarding handover
02
LadyLight screens: guided AI assistants, team access and the admin dashboardLadyLight screens: guided AI assistants, team access and the admin dashboardLadyLight screens: guided AI assistants, team access and the admin dashboard

AI platform · coaching and marketing

LadyLight

AI engineers who grew into the platform team

Our team owned the backend and AI features alongside the client, first as a build and then on retainer. We moved a browser extension’s model calls behind a secure per-team backend, shipped new GPT-builder features, and added server-side roles and error monitoring.

“Really happy with LadyLight. It looks great, works smoothly and you can tell a lot of care went into it. Great job!” 
LadyLight · Client review

Before

  • Model calls made straight from the browser
  • Prompt edits not reaching production

After

  • A per-team backend for every model call
  • Prompt changes live again, with monitoring in place

Who you’ll work with

A delivery team in Lahore, Pakistan, working remotely in your tools, on hours set to overlap yours.

Delivered remotely from our team in Lahore. We join your Slack or Teams, your repository and your tracker.

Flexible hours, set to overlap your working day (US, UK or Gulf) and agreed in writing. We don’t promise 24/7.

Work under NDA, in your accounts, with least-privilege access you can revoke.

New enquiry
Reply within 4 working hours
Fit call
Free, 30 minutes
Delivery contact
One person for the whole build
After launch
30 days of defect fixes

MVP Build

Questions, answered

The things buyers ask us before they start.

Still have a question?

Ask us directly. We reply within 4 working hours.

  1. A deployed first release in accounts you own, where the agreed core journey works end to end: for example, a customer signs in, submits a request and sees its status. It comes with the code, tests on the critical paths, error monitoring, handover documentation and 30 days of defect fixes after launch.

Already have a team, and need more engineers?

If you can lead the product yourself, add engineers by the month instead, with the first week free.

See Engineering Capacity
Start here

Tell us what your first release has to do

Bring your launch or pilot date. On a free 30-minute call we tell you whether it fits, what the core journey is, and whether we can quote directly or need a Scope stage first.

Or book a free fit call