The Vertical SaaS Financial Model Investors Actually Want to See

← All posts

Most financial models for early-stage SaaS companies are built wrong. Not because founders don't understand math — because they're using horizontal SaaS assumptions for a vertical SaaS business. Wrong pricing structure, wrong cohort behavior, wrong expansion mechanics.

Operators have a specific advantage here: if you've spent a decade running a business in your target vertical, you already know what the revenue model should look like. You've paid software contracts. You know whether customers in your space pay per seat, per location, per transaction, or on a flat annual basis. The vertical SaaS financial model's job is to translate that knowledge into a structure investors can evaluate.

Why Vertical SaaS Models Are Different

Horizontal SaaS — a CRM or project management tool — serves a broad market with variable use cases. The financial model reflects that: wide top of funnel, low ACV, expansion through seat adds, high churn expectations in early cohorts.

Vertical SaaS is structurally different on every dimension. The addressable market is smaller and more concentrated. Average contract values are higher because you're solving a mission-critical workflow, not a nice-to-have productivity tool. Gross revenue retention is higher because switching costs are real — once a pest control company has 18 months of job history in your system, migration is a project, not a decision.

Your financial model should make those structural differences visible. If it looks like a horizontal SaaS model with a vertical label on it, investors who know the space will notice.

The Metrics That Matter

Annual Contract Value (ACV). In vertical markets, pricing is usually location- or business-based, not seat-based. A multi-location HVAC company pays a different number than a single-truck operation. Model your ACV at the business level, segmented by size tier.

Gross Revenue Retention (GRR). This is the number that tells investors whether your product is sticky. Best-in-class vertical SaaS runs at 95%+ GRR. If you're projecting 85%, you need to explain why. Operators often have GRR intuition from the vendor side — if you've never seen a competitor lose a customer after two years of clean implementation, that's data worth citing.

Net Revenue Retention (NRR). How much does revenue grow within the existing customer base? For vertical SaaS with expansion paths — more locations, more modules, more users as the business grows — NRR above 110% is achievable. Model the realistic expansion scenario, not the optimistic one.

CAC and Payback Period. Early CAC for operator-founded companies is low because the first customers come through direct relationships. The mistake is modeling all future CAC based on that initial cohort. By year 2, you're paying for customers who don't know you personally — model that realistic cost.

Your domain knowledge is your edge. Make it explicit in the model — put assumptions in the notes, show the research behind your ACV and GRR projections.

What to Project and How Far Out

A seed-stage investor wants 18-24 months of operating projections with enough granularity to evaluate assumptions, and a 3-year view that shows the path to sustainability. Series A investors want 36 months with clear cohort data.

The model should show: monthly customer adds by channel (operator-led vs. marketing vs. referral), revenue per cohort over time to show retention and expansion, burn and runway under base and conservative scenarios, and the headcount build that matches the revenue plan.

What it should not show: revenue in year 3 that relies on a distribution channel you haven't built yet, or a CAC assumption that only holds if you're exclusively selling through your personal network forever.

What Investors Focus On

When a venture studio or early-stage investor looks at a vertical SaaS model, they spend their time on three things:

The retention assumption. GRR is the most scrutinized number in any vertical SaaS model. If you project 95% retention and your market has no data to support it, investors will push back. If you've spoken to 20 customers in your vertical and they all told you their current vendor has near-zero churn, document that and defend it.

The TAM-to-customer-count math. Investors check whether your projected customer count in year 3 is realistic given your target market size. If you're targeting independent veterinary clinics and there are 28,000 in the US, a model showing 800 customers in year 3 is 2.9% penetration — achievable. A model showing 8,000 customers is 28% penetration at seed stage — not plausible.

The payback period. For vertical SaaS with high ACV and low churn, the payback period on CAC should be 12-18 months. If your model shows 36 months, investors will want to know what changes to make it viable.

The Common Operator Mistake

Operators make one consistent financial modeling error: they build models with baked-in assumptions that aren't visible to the reader. Your knowledge of how customers use and pay for software in your vertical is your edge. Make it explicit in the model. Put your assumptions in the notes. Show the research behind your ACV assumption and your GRR projection.

Investors backing operator-founders are backing the thesis that domain knowledge produces better assumptions. Prove that thesis in the model itself — and the diligence conversation becomes very different.

Want to talk through your vertical SaaS model? Pitch us your idea — we'll dig into the numbers with you.

Related reading

You know the numbers. Let's model it.

Your operator knowledge is the edge in the model. Two paragraphs on the vertical you're building for — we'll look at the unit economics together.

Pitch us