The email says launch in two weeks. The list still has two audiences and a rebuild of Stripe. How long does a first version of a web product take? Weeks, once you name the job. Months if the brief is still a platform.
What belongs in a first version and what that cut costs are other posts. This one is the date. I build this as SaaS and web products. The weeks start after the brief I write before I quote, not after the first Slack message. If you haven't named whether it's a website or a web product, stop. I can't give you a week for the wrong thing.
What people mean by how long a first version takes
They mean a date they can put in a deck. A funding round. A trade show. Or nothing, just anxiety with a number on it. A date with a person attached to it changes what I cut. A date with nothing behind it doesn't. I want the week someone actually uses it, not the week the slide says launch.
Two weeks is a demo. I can make screens that look like the product in two weeks. Nobody finishes a job in those screens unless the job was already tiny and named. A quarter is often a platform wearing an MVP label. The first version that is actually a product sits in the middle. It only exists once you can say who opens it and what they finish.
How long a first version of a web product actually takes
These are weeks from jobs I quote. An agency on the same job often quotes a quarter because four people have to see the screens. You might still not have someone who owns it after launch. If you meant five pages and a form, this date is the wrong one. That work is how much a custom website costs, and it is usually a few weeks, not a product quarter.
| What they asked for | Weeks | What you actually get |
|---|---|---|
| A demo sold as a first version | 1 to 3 | A click-through. You are still on the call when someone tries to finish the job. Put it in a deck as a rehearsal. Not as launch. |
| An internal tool for one job | 4 to 8 | Staff finish something they already do in a spreadsheet. Faster, because the first user is in the building. Still a login and a URL that stays up. Still not two weeks. |
| A first version people pay for | 6 to 12 | Someone can finish the job without you on the call. Login, records, a URL that stays up. That is the date I write down. |
| The platform they asked for | A quarter, often two | Every role, every market. I still see this labeled as a first version. Cut until a person can finish a job in twelve weeks, or hire a team and stop calling it v1. |
Six to twelve weeks is a real first version for one job, on a URL that stays up. It sits next to the first-version price. I have quoted eight weeks on that row and watched it become eleven when a second login showed up in week three. Shorter than six, I'm suspicious you bought a demo. Longer than a quarter before anyone can finish the job, cut again. I want the date attached to a person using it. Work that already shipped started that way more often than it started as a platform with a launch month.
What makes a first version take months
I would rather give you a six-week date on one job than a Q1 date on a platform that never ships. The extra weeks are rarely the screens. It's Slack, and a second login in week three. That's what I own on this kind of job. I don't hide a second product inside the first and call it the same date.
| What happens | What it does to the date |
|---|---|
| The job still isn't named | The weeks don't start. I quoted two weeks once on a simple MVP. The job was still the platform. Four months of Slack later, nobody had finished anything. |
| A second audience in week three | Six weeks becomes three months. Someone forwards a new persona. Pick who pays. The other login waits. Building both is how neither ships. |
| Starting in the App Store | Add six to ten weeks after a web product that already works. Signing, listings, a review queue. I won't start the store date first. |
| Four people have to agree on a button | Roughly twice as long. I have priced a label at a week because four people had to see it. The screens aren't slow. The inbox is. |
The store queue is do you need a mobile app, or is the website enough. Chat in week one is the same delay unless chat is the job. Ask when AI belongs in a product before you add a chatbot to the six-week plan.
When a first version calendar is the wrong answer
Sometimes the honest date is not a first-version date. I'd rather say you needed a site, or that checkout is already live, than take a six-week deposit and stall.
You needed a website
A stranger acts once. Nobody comes back. Five pages shouldn't take two months. If nobody logs in, you wanted a website date. A custom websiteis often a few weeks after the brief. Don't buy a product quarter for a contact form.
The product already exists
People already pay you inside it, and there's a repo. Don't start a six-week first-version date next to that checkout. A takeover starts from the live URL. A blank six weeks while money still has to move is a rewrite. Call it v1 if you want. The live product still has to run.
I put a week on the calendar when one named person can finish the job without emailing me. If that week is months away, the first version is still too big.
If the date feels fake, send it with the list. Tell me what you're building. I'll tell you if those weeks are a first version, or if you still have a platform.
