MVP Build, for non-technical founders

A first working product for your idea.

We scope it, design it and build the first version your users can touch, usually in 4 to 6 weeks. The code and the designs are yours from the first commit, in your own repositories.

A product manager replies and books a free 30 minute call. No pitch deck needed; a sketch from a chat with an AI is enough.

We reply from hello@programmx.com. NDA on request before you share more. Privacy notice.

What you get.

A first version is not a prototype. It is a product you can put in front of users and investors, and keep building on.

  • A written scope and roadmapPlain English. What the first version does, what it leaves out, and what comes next.
  • A clickable design before any codeFigma screens you can walk through with users, often within days of the first call.
  • A working build, demoed weeklyWeb, mobile or both. Every week you see what changed; your feedback goes into the next demo.
  • Deployment to your own accountsHosting, domains and keys in your name. You are never locked into ours.
  • Handover documentationHow it runs, how to deploy it, how to extend it. Written so another team could pick it up.
  • 14 days of free fixesBugs in what we delivered are fixed at no cost. Most founders then move to the Co-build Retainer.

Six weeks, in the usual shape.

Every product is different, so the scope call sets the real dates. This is how most MVP builds run.

  1. Week 1

    Scope and design

    The written scope, then clickable screens you review with us.

  2. Weeks 2 to 5

    Build, with a demo every week

    The team builds against the agreed scope. At the end of each week you get a working demo and a short note on what changed and what is next. Feedback goes in; the next demo shows it landed. Anything outside the scope is written down for version two, not squeezed in.

  3. Week 6

    Launch and handover

    Deployed to your accounts, documented, and yours.

Work behind this offer.

Client names are withheld by agreement. Every number can be walked through on a call.

A maritime recruitment startup in the Gulf. Product build.

A job-matching product for seafarers, live with paying users.

A Telegram bot and Mini App that matches seafarers to vacancies, writes cover letters with AI, builds CVs and sends applications by email. Every cover letter passes rule checks and is previewed by the seafarer before anything is sent.

Python, Telegram Mini App, LLM applications

What the product does, in order

  1. Builds the CVFrom the seafarer's details, inside Telegram.
  2. Matches vacanciesOpen positions that fit the profile.
  3. Writes the cover letterDrafted with AI, then run through rule checks.
  4. Shows a previewThe seafarer reads and approves. Nothing goes out unread.
  5. Sends the applicationCV and letter by email to the employer.
Product screenshots are shared on the call, with the client's permission.

A US physician and founder. Co-build retainer since 2017.

Days to a first mock-up. Weeks to a working demo.

The rhythm has not changed in nine years. He brings an idea and we show him what it could be rather than describe it. About a dozen products so far, across AI, blockchain and the web, the latest a full platform shipped in twelve weeks.

  • 9 yearsone relationship
  • About 12products shipped
  • 50+builds, APIs and services
  • 12 weeksfor the latest platform
Day 0

An idea arrives, often as a chat transcript with an AI. We read it and say what is buildable and what is not.

Days

A clickable mock-up in Figma, so the idea can be argued with before anything is coded.

Weeks

A working demo of the real thing, then a demo every week until it ships.

Nine years

The same rhythm, about a dozen times, across AI, blockchain and web products.

Our own product. Built the same way.

latetrains.pk, from scope to launch, in public.

A live delay tracker for Pakistan Railways, launched in August 2026. We ran it through the same scope, design, build and launch shape we use for founders, so you can see the finished article before you talk to us.

Try latetrains.pk

latetrains.pk home page
What you are looking atThe latetrains.pk home page as it is live today.
What we didScope, design, build and launch, August 2026.
Where it standsLive. Try it before you talk to us.

How the engagement works.

The questions founders ask on the first call, answered before it.

Who works on it
A product manager, a designer and one or two engineers, chosen for your stack. The founder reviews every scope and joins when the project needs it.
What we need from you
About an hour a week: the weekly demo and your decisions on it. Any domain knowledge only you have.
How you see progress
A weekly demo and a short written note. Your own repository, updated as we work, not at the end.
After launch
14 days of free fixes. Then version two as another fixed build, or the Co-build Retainer for a team that keeps going.

How it's priced

A fixed price for the agreed scope
Quoted after the first call. No surprises in week five.

You own the work

Code and designs are yours from the first commit, in your own repositories.

Online through your morning

The team works through the UK morning. US founders book calls with the founder.

After delivery

Bugs in what we delivered are fixed free for 14 days.

Confidential by default

NDA on request before you share anything beyond the first message.

Before you send the brief.

I only have an idea. Is that enough to start?

Yes. Most first messages are a paragraph. The 30 minute call is where we work out what the first version should be, and you leave it with an honest read on whether it is buildable now.

How is 4 to 6 weeks possible?

By leaving things out. The scope names what the first version does and what it does not, and anything outside it goes on the list for version two. Ambition in the idea, discipline in the scope.

Can I keep building after the MVP?

Yes, and most founders do. The Co-build Retainer is the same team on a monthly basis, which is how our longest client has worked with us for nine years.

What if I already have a developer or a codebase?

We review what exists before quoting. Sometimes the right first version builds on it; sometimes a clean start is cheaper. We tell you which, with reasons.

Do you sign an NDA?

On request, before you share anything beyond the first message.

Tell us about your idea.

A sentence or two is enough. A product manager reads it and books a free 30 minute call.

Prefer to book straight away? Pick a time for the call. Or write to hello@programmx.com.

We reply from hello@programmx.com. Privacy notice.