MVP in two weeks. Real client. Here is the day-by-day playbook we use to take a new service from idea to live in 14 days, including the mistakes.
MVP in two weeks. real client. here's the day-by-day.
In March 2026 we had an idea for a new service on a Tuesday. By the following Monday we had a paying client. Fourteen days from concept to live.
This is not about moving fast for its own sake. It is about learning faster. The only real feedback is a paying client using your thing. Everything before that is a guess.
This post is the exact playbook — day by day — for how we go from idea to first client in 14 days. We've done this four times now. The playbook is the same each time.
The constraint is not arbitrary.
Two weeks is long enough to build something real. It is short enough that you cannot hide behind preparation. If you have not shipped in 14 days, you are overthinking it.
We learned this from the indie maker community. Pieter Levels built nomad.list in one week. Most productiized services that successful indie agencies run were built over a long weekend. The pressure of a tight deadline forces the one decision that most agency founders avoid: what is the actual minimum version of this thing?
Long timelines encourage scope creep. You add a client portal. Then reporting. Then a Slack integration. Then you're six weeks in and you have a complex product nobody has validated. The 14-day constraint forces you to pick one deliverable, build only that, and find a client who wants only that.
Y Combinator's advice to founders applies directly: do things that don't scale first, talk to users early, and ship something imperfect that works (per Y Combinator, 2024). The 14-day sprint is the agency version of that advice.
| Day | Activity | Output |
|---|---|---|
| 1 | Define the single deliverable | One-sentence description |
| 2 | Define the single client type | ICP + 3 qualifying questions |
| 3 | Price it and write the offer | Pricing doc + 1-page PDF offer |
| 4 | Build the minimum version | Working v0 (rough is fine) |
| 5 | Internal test and fix critical bugs | Bug-free enough to show |
| 6 | Write the pitch (one paragraph) | Outreach template |
| 7 | List 20 specific potential clients | Named list with contact info |
| 8 | Reach out to the top 5 on the list | 5 personalized messages sent |
| 9 | Follow up + reach out to next 5 | 5 more messages |
| 10 | Handle replies, book calls | Calls scheduled |
| 11 | Run discovery calls | Notes + real feedback |
| 12 | Send proposals | 2-3 proposals out |
| 13 | Follow up on proposals | Answers collected |
| 14 | Close first client or course-correct | Signed or revised plan |
This is the exact sequence we run. Not aspirational. Literal.
Day 1: Define the single deliverable. One sentence. Not a paragraph.
Bad: "A service where we help companies improve their SEO strategy and content and build a system for long-term organic growth."
Good: "A 5-day SEO technical audit of an existing website with a prioritized fix list."
The bad version is three services and a philosophy. The good version is one thing with a clear timeline and a clear output. If you cannot say what the client receives in one sentence, the product is not defined yet.
Day 2: Define the single client type. Three qualifying questions that determine if a prospect is a good fit for this specific thing. Not general discovery questions. The specific three things that tell you this will work.
For our technical SEO audit: "Do you have a site with more than 50 pages? Have you invested in content in the last 12 months? Are you not currently working with an SEO agency?" If yes to all three, they're a fit.
Day 3: Price it and write the offer. Price first, then write the offer. If you write the offer first you will undercharge to match the work you described. Pricing should reflect the outcome value, not the hours involved.
For the audit: we priced at $2,400. That is less than one month of most SEO retainers. The value: a clear prioritized fix list that the client's existing developer can implement. We solve the diagnosis problem, not the implementation problem.
For service agencies, "building" means building the delivery system, not a software product.
Day 4 build for a new service:
That's it. The service itself — the actual work — is what you already know how to do. The build is the scaffolding around the delivery.
For services with a software component: build only what is required to show the output to a real client. If the output is a report, build the report template. If the output is a dashboard, build one hard-coded version first. Make it work for one client before making it general.
We built our first version of the SEO audit on a spreadsheet template. We moved it to a web-based report only after the third client. The spreadsheet worked fine. The clients didn't care that it wasn't a custom app.
Day 6-9 is where most agency founders stall. They write a pitch that is too long or too vague and then send it to people they don't actually know.
Our one-paragraph pitch structure:
Example: "I was looking at your site and noticed you've published 40+ blog posts in the last year but the technical SEO foundation has some fixable issues — particularly around structured data and canonical tags. We do a 5-day technical SEO audit with a prioritized fix list your developer can implement. It costs $2,400 flat. Would a quick call this week make sense to see if it's a fit?"
That is 72 words. It is specific. It names a real problem. It has a clear price. It asks for one thing.
The mistake most agencies make: they send a capabilities overview and ask for a discovery call to "learn more about your goals." Nobody wants that. People want to know what you do, what it costs, and what they get.
We've run this four times. Three times we had a paying client by day 14. Once we did not.
The one miss: we built a service that we thought clients wanted based on a problem we had seen. When we got on calls, the clients we talked to did not see it as a problem. They framed the same situation differently. We were solving the wrong version of the problem.
On day 14, we had a decision: kill the service or adjust and try again. We adjusted the framing, repriced from $3,200 to $1,800, and changed the deliverable from a "strategy" to a concrete tool they could use immediately. We closed a client on day 22.
The lesson: when you miss in 14 days, do not assume the idea is wrong. Assume the framing or price is wrong. Talk to the people who said no and ask what would have to be different. That conversation is worth more than any market research.
Running a 14-day launch requires that your delivery infrastructure already exists. If you are building delivery tools from scratch each time, you cannot move this fast.
We built once:
Each new service slots into existing infrastructure. The only new thing we build is the specific deliverable template for that service. The scaffolding is reusable.
This is why your first stack matters: if the first service you build forces you to build unique infrastructure, you cannot launch fast later. Build general infrastructure first, specific products second.
Pick one service you have been thinking about building. Give yourself 14 days.
Day 1: Write one sentence describing the deliverable.
If you cannot write that sentence clearly, spend day 1 only on that. Do not move to day 2 until the sentence is clear.
Then follow the playbook. Do not add features. Do not wait for a better client. Do not do more market research. Ship the minimum thing to the most obvious buyer as fast as possible.
The 14-day playbook is not about cutting corners. It is about learning what the corners are. You will not know what to build until a real client uses version 1 and tells you what is missing.
Ship v1. Then ship v2.
A clearly defined single-deliverable service can be productized and launched in 14 days. The key constraint is scope: one deliverable, one client type, one price. Most agencies take longer because they try to build a comprehensive service with multiple tiers before getting any client feedback. The indie approach is to ship a minimum version to one real client first and iterate from that.
An agency MVP is the minimum version of a service that delivers real value to one specific client type. It is not a full-service offering. It is one deliverable with a clear format, a fixed price, and a defined timeline. For Striveloom, the first MVP of its SEO audit service was a spreadsheet-based report. It became a web app only after the third client validated demand.
List 20 specific potential clients by name. Write a one-paragraph pitch with a specific observation about each one, a clear description of the deliverable, a stated price, and one yes/no question. Send it to the top 5 first. Follow up once. Then send to the next 5. A targeted specific pitch to 20 known contacts outperforms a general pitch to 200 cold emails every time.
Four things: a specific observation about this particular prospect, a one-sentence description of the deliverable, the price, and one question. Total length under 100 words. The most common mistake is writing a capabilities overview instead of a specific offer. Clients respond to specific offers with clear prices because it removes the risk of a long discovery process before knowing if they can afford it.
Reusable infrastructure is the answer. If your delivery scaffolding — templates, project management, client communication, report formats — already exists, the only thing you build per new service is the specific deliverable template. Striveloom reuses its Next.js report template, Supabase client schema, and Resend email sequences across every new service. New service launch time: 14 days. Delivery quality: same as existing services.
Founder & CEO of Striveloom. Software engineer and Harvard graduate student researching software engineering, e-commerce platforms, and customer experience. Builds the agency that ships like software — one team, one pipeline, one platform. Writes on AI agencies, web development, paid advertising, and conversion optimization.
Every tool Striveloom uses to run a 7-person digital agency in 2026, with actual monthly costs. $1,847/month total. Here is the full bill and why we chose each one.
Six AI agents run across all Striveloom client work. Here is what each agent does, what it costs, what it replaces, and where it still fails.
Everything a startup founder needs to know about building a website in 2026 — tech stack choices, realistic budgets, timelines, and the mistakes that kill product launches.
Book a free 30-minute call to scope your project. Fixed pricing, transparent timelines.
