Validating a Vertical SaaS Idea in 14 Days

Most vertical SaaS ideas die for one of two reasons: the founder spent six months building before talking to customers, or the founder talked to customers but only heard what they wanted to hear. Both are avoidable. Both cost a six-figure bill that didn't need to happen.

We've worked with enough early-stage founders to know that 14 days — two focused weeks — is enough to decide whether an idea has real signal. Not to prove a market exists (that takes months of real usage data). Just enough to decide, honestly, whether to keep going or save yourself the next $150K. This is the sequence we run.

Before Day 1 — the scoping conversation

A two-week sprint is only useful if the idea is concrete enough to validate. Before the clock starts, you need to be able to answer:

• Who specifically. Not "small businesses." Not "contractors." Something like "independent insurance brokers in Florida with 2–6 employees who handle their own renewals."
• What specifically. Not "make their lives easier." One workflow, one pain point, one measurable outcome.
• Why now. What changed in the last 12–24 months that made this worth building? If nothing changed, be suspicious.

If any of those three are fuzzy, spend another week sharpening them before starting the 14-day clock. Vertical SaaS is won by specificity. A founder who can't name the exact customer is going to spend the next year failing to find them.

Days 1–2 — build the pitch, not the product

The goal of the first two days is a single artifact: a landing page that describes the product as if it already existed. Not a fantasy version — a minimum viable promise. What it does, who it's for, what it costs, and a way to express interest.

The page is built on anything that ships fast — a no-code site builder, a simple Next.js page, a single-page template. It should include:

1. A headline that names the customer and the outcome.
2. A subheadline that names the specific pain.
3. Three product-like screenshots or mockups (designed, not implemented).
4. A plausible price.
5. A call to action — "join the early access list," "book a 20-minute call," or "reserve a pilot spot."
6. A basic privacy-respecting analytics setup.

One of the most useful things you can do here: include a price. Not a placeholder, a real number you'd actually charge. Pricing in the first conversation forces every subsequent conversation to be about value, not features. Leave pricing off and every interview becomes a design critique of your mockups.

Two days is enough for this. If it takes five, you're overbuilding.

Days 3–8 — the interview sprint

This is the core of the exercise. Fifteen interviews with real prospects in six business days. Not 15 friends who say "yeah that sounds cool." Fifteen people who currently have the pain you claim to solve, who don't know you, and who owe you nothing.

How to get the interviews

• Cold outreach on LinkedIn. A specific message to a specific person about their specific work beats a generic note by an order of magnitude.
• Industry communities. Subreddits, Discord servers, Slack communities for the vertical. Introduce yourself, be useful first, ask for 20 minutes.
• Paid leads. A small budget on a targeted ad or a list pull can fill the pipeline quickly. Cheaper than six months of shadow-boxing.
• Warm-to-cold chain. Warm intros are gold but slow. Use them to learn the vocabulary, then turn that vocabulary into better cold outreach.

Aim for 3–5 conversations booked in the first 48 hours. If you can't fill the calendar in 48 hours, that is itself a signal about how reachable the customer is — a problem that will compound after launch.

What to ask

Interview scripts matter less than discipline. The most important rule: ask about what they already do, not about what they'd want. "Walk me through the last time you did X" gives you data. "Would you use a tool that did X?" gives you politeness.

A structure that works:

1. Context. What's your role, what does the business do, what does your week look like?
2. The workflow. Walk me through the last time you [the specific pain]. What tools? Who was involved? How long did it take? Where did it go wrong?
3. The workarounds. What do you do today to make this less painful? What have you tried that didn't work?
4. The spend. What does this problem cost you, in hours or dollars? (Even rough numbers.)
5. Only at the end: Here's what we're thinking of building. What's your reaction?

The first four questions are about reality. The fifth is the pitch. Do the fifth too early and you contaminate the first four.

What to listen for

Green signals: They describe the exact pain you predicted, in their own words, before you prompt them. They've already built janky workarounds (spreadsheets, duct-taped Zapier flows, an unpaid intern). They give you a specific dollar figure when you ask about cost. They ask when they can buy it.

Yellow signals: They say "yeah that sounds useful" without describing their own pain. They're polite but vague. They can't name a competitor they've considered.

Red signals: They tell you about a different, bigger problem. They've tried to solve this before and stopped because it wasn't actually that painful. The workarounds are already fine. Price brings out a long silence.

Days 9–10 — the pricing probe

By now you have 10–15 conversations, a landing page with traffic, and some early-access signups. Days 9 and 10 are for a pricing probe: take the three or four most engaged prospects and have a second conversation specifically about money.

Structure:

• "Based on our first conversation, here's what we're planning to build."
• "It will cost $X per month per [seat / location / unit]."
• "If that works for your business, I'd like to put you on the pilot list for $Y% off the first [3 / 6] months."

You are looking for three specific reactions:

1. A flat no on the price. Useful data — either the price is wrong or the value is perceived as lower than you thought.
2. A hesitant yes. Also useful, but less than it looks. Hesitation often means "I'm being polite."
3. A "when can I start" yes, with a card or a signed LOI. This is the only reaction that counts as validation.

Five serious "when can I start" replies out of 15 interviews is a strong signal. One or two is a weak signal that might still be worth pursuing on a tighter scope. Zero is an answer.

Days 11–12 — pressure-test the economics

Two days to build a simple spreadsheet, not a pitch deck. Five inputs, no more:

1. Target price per customer per month.
2. Realistic time-to-close and sales cycle (from the interviews — not from a startup Twitter post).
3. Realistic churn for the vertical (look at comparable verticals if no data exists).
4. Build cost to get to an MVP that delivers the promised value.
5. Ongoing engineering and support cost per month.

Run the numbers. Is there a plausible path to the business covering its own costs inside 18–24 months? If yes, the 14-day sprint is a green light. If no, you don't have a business — you have a project that will need outside funding or a bigger price. Both are survivable, but only if you see them now.

Days 13–14 — the decision

Two days to write the memo and decide. The memo is two to four pages. It contains:

• What you learned about the customer you didn't know before.
• The strongest green signals and the strongest red signals, in the words of the actual people you talked to.
• The pricing reality (what they said they'd pay vs. what you need to charge).
• The economic model on one page.
• The decision: build, pivot, or stop.

The temptation at the end of two weeks is always to build. The founder is energized, prospects exist, the mockups look great. Build anyway only if the green signals are specific, the pricing held, and the economics work. If the signals are vague or the pricing softened — pivot or stop. The 14 days weren't wasted; they saved you a year.

What comes after a "build" decision

If the sprint said build, the next step is an MVP that honors the promise. We typically scope a 30–60 day build targeting the three or four early-access customers who paid or committed in the pricing probe. The scope is brutal: only the workflow the interviews validated, only the screens the landing page promised, only the integrations the first customers actually asked for.

Everything else — teams, permissions, fancy dashboards, mobile, integrations — waits. You are building a product for four customers, not four hundred. The shape of the product for four hundred customers isn't clear yet, and pretending it is wastes months.

If you want help running the sprint, or going from validation into a tight first build, that's what we do — you can see our approach to SaaS development and how we work with founders at the early stages, or reach out directly to talk through your specific idea.

Closing

Fourteen days won't tell you whether you're going to build a great company. It will tell you whether the next six months of your life are worth committing to this idea. That's the only question the sprint needs to answer — and it answers it for the price of two weeks of focus instead of a year of building into silence.