MVP build / Fixed scope / 21 days
You have an idea.
In 21 days you will have a product.
I am a software engineer. I build the first real version of your product in 21 days for a fixed $2,000, then hand you the code and the keys. No agency, no hourly billing, no invoice you did not expect.
Price
$2,000 fixed
Timeline
21 days
Code
Yours from day one
Capacity
2 builds a month
Here is the whole schedule, before you pay anything.
Most founders have been burned by a developer who went quiet for a month. So this is the actual plan: what happens, in what order, and the days you will see something working.
- Day 01Kickoff call
- Day 04Scope locked and signed
- Day 10First working link
- Day 16Beta ready for your users
- Day 21Live on your domain
- Scope and design
- We cut the idea down to the smallest thing a real user would pay for. You approve the screen designs before a line of code is written.
- Core build
- Accounts, database, the one thing your product is actually for. You get a working link on day 10 and can click through it yourself.
- The rest of the product
- Payments, admin, emails, the supporting screens. A demo call every few days so nothing drifts away from what you asked for.
- Test, fix, polish
- You and a few of your users break it, I fix it. Speed, mobile layouts, error states, the parts that make it feel finished.
- Launch and handover
- Live on your domain. Repo transferred to your GitHub account, recorded walkthrough, and a written map of how everything fits together.
Eight things land in your hands on day 21.
Not "a codebase". Things you can log into, show people, and sell with.
- A working product, live on the internet
- Not a clickable mockup or a slide deck. A real application on your own domain that a stranger can sign up for on day 21.
- A design made for your product
- Screens built around what your users actually need to do, drawn and approved by you in the first four days before any code exists.
- Accounts and payments
- People can sign up, log in, and pay you. Stripe handles the money, so you are never holding card details.
- An admin view
- See your users, your data, and your sales yourself, without messaging me to run a query.
- The code, in your name
- A private GitHub repository transferred to your account. No licence, no lock-in. You can hire anyone to take over tomorrow.
- Hosting set up and running
- Deployed, secured with HTTPS, backed up, and monitored. I show you exactly what it costs to run before we start.
- A recorded handover
- A walkthrough of how everything works, plus a written map of the codebase so the next developer is not starting cold.
- Two weeks of free fixes
- Anything broken in the first 14 days after launch, I fix at no charge. Bugs are my problem, not yours.
What I will not build in 21 days.
A fixed timeline has edges. Here are mine, in writing, so neither of us discovers them in the last week.
- Native iOS and Android apps
- Your product works well on a phone, through the browser. App store builds are a different project.
- Anything that needs a team
- If your idea honestly needs six months and three engineers, I will tell you on the call instead of taking your money.
- Custom AI models
- I can connect your product to existing AI APIs. Training a model of your own is not a 21 day job.
- Enterprise system integrations
- Anything that needs a third party vendor's approval, paperwork, or sandbox access sits outside a fixed timeline.
- A full brand identity
- I work with the brand you already have, or a clean neutral one. Logos and naming are not part of the build.
- New features after day 21
- The build ends when it ships. Continuing to build is what the monthly plan below is for.
Two numbers. That is the entire price list.
The build
$2,000once
Your product designed, built, tested, and live inside 21 days.
- Everything on the 21 day plan, start to finish
- Fixed price and fixed scope, agreed by day four
- The code and every account in your name
- 14 days of free fixes after launch
- Half up front, half on the day it goes live
After launch, if you want it
$1,000a month
Keep building once real users are in. Optional, and never a condition of the build.
- Around 20 hours of build time a month
- A weekly call to decide what ships next
- Bugs fixed within one business day
- Hosting, updates, and security patches handled
- Month to month, cancel with two weeks notice
Note
Why this is $2,000 and not $20,000.
Agency quotes carry account managers, project managers, sales commission, and an office. You pay for all of it. Here there is one engineer, a scope small enough to actually finish, and nobody in between. The saving is overhead, not quality. What gets cut is scope, and it gets cut with you on day four, not quietly in the last week.
Navaneeth CT
I am a software engineer with 6 years of shipping production software. OnePointO Labs is the part of that work I like most: taking a founder who cannot build it themselves from an idea to something real, fast enough that the idea is still worth testing.
You are not handed to an account manager. The person on the call is the person writing the code, which is the only reason a 21 day timeline works at all. When you ask why something is taking longer, you get an answer from the person it is taking longer for.
I take two builds a month. That limit is not scarcity marketing, it is arithmetic. It is how a fixed 21 days stays a fixed 21 days.
Elsewhere
Built with
Next.js, TypeScript, Postgres, Stripe, deployed on Vercel. Boring on purpose. These are standard tools any developer can pick up, so you are never stuck with me.
The things founders ask before they say yes.
What actually counts as an MVP?
The smallest version of your product that a real person would use and pay for. One core thing done properly, not ten things done halfway. If your idea is a marketplace, that means listings, search, and checkout, not ratings, messaging, referrals, and an affiliate program. We decide together in the first four days exactly where that line sits, and it goes in writing.
Why is this $2,000 when agencies quote $30,000?
Agency quotes carry account managers, project managers, sales commission, and an office. You pay for all of it. Here there is one engineer, a scope small enough to actually finish, and nobody in between. The saving is overhead, not quality. What gets cut is scope, and it gets cut with you on day four rather than quietly in the last week.
What if it takes longer than 21 days?
The price does not move. If a delay is on my side, I keep working until it ships and you pay nothing extra. If a delay is on your side, usually feedback or an account I need access to, the clock pauses until I have what I need. Scope is what protects the deadline, which is why the first four days are spent locking it.
Who owns the code?
You do, from the first commit. The repository is transferred to your GitHub account at handover, along with every account and service in your name. Nothing is licensed to you and nothing depends on me staying involved.
I am not technical. How much of my time does this take?
Around two hours a week. A short call every few days to review progress, and the rest is answering questions over email or Slack. You never need to read code, write a specification, or understand the stack. Describing what your users need is your job. Everything else is mine.
What if I do not like what you build?
You will have seen it long before day 21. Designs are approved by you in the first four days, there is a working link you can click on day 10, and a demo call every few days after that. Course corrections happen in hours, not at the end. If we get to day four and the scope we agree on is not what you want, you can stop and only owe the deposit.
What happens after day 21?
Most founders take the code and run with it, and that is a completely fine outcome. If you want me to keep building, the monthly plan is $1,000 per month and starts whenever you want it to. There is no obligation either way.
Can you sign an NDA?
Yes, before the first call if you prefer. Send yours over, or I can send a standard mutual one.
How many builds do you take at once?
Two a month. That limit is the whole reason a fixed 21 days is possible. When both slots are full, I will tell you the next start date rather than squeeze you in.
Next step
Tell me what you want to build.
Twenty minutes. You describe the idea, I tell you honestly whether it fits in 21 days and what I would cut to make it fit. If it does not fit, I will say so on the call and point you somewhere better.
2 build slots a month. No pitch deck, no follow up sequence.