The Founder's Decision Framework

Seven questions, asked at every stage, with a different right answer each time.

Three case studies in this series looked at three companies solving three problems on three clouds. Underneath all of it, the same seven questions did the work of deciding what to build. Making them explicit means they can be asked directly instead of re-derived at the next stage, the next company, or the next architectural decision this series didn't cover.

What changes between stages

The questions stay the same; what counts as a good answer changes. A company optimizing for learning gives a different answer to “what should we buy as a managed service” than a company optimizing for global regulatory compliance, even though the question is identical. Five stages recur throughout this series:

Stage	Optimizing for	Illustrated by
Pre-seed	Learning whether the problem is real	Casewell: an AI legal-research assistant for small law firms
Seed	Product-market fit
Series A	Repeatable growth	Sentrio: AI-assisted cybersecurity analysis for SOC teams
Series B/C	Scalable execution	No case study in this series
Late stage	Reliability, governance, cost, security, and global scale	Virelane AI: an enterprise AI platform for regulated customers

1. What problem are we solving now?

The current bottleneck standing between where the company is and its next milestone, which is a narrower thing than the company's mission.

Stage	The current problem
Pre-seed	Nobody has confirmed the problem is real. Casewell's founders talked to law firms with a rough prototype.
Seed	Early users exist; usage and retention are the open question, ahead of feature breadth.
Series A	Sentrio: proving last quarter's deal wasn't a fluke, that the sales motion and the product both repeat.
Series B/C	Scaling a proven model without the organization or architecture fragmenting.
Late stage	Virelane: operating at a scale where a single failure reaches a regulator before a support queue, while holding latency commitments and gross margin.

2. What milestone must the company reach next?

Stage	The next milestone
Pre-seed	A working prototype and candid reactions from a handful of prospective users.
Seed	Evidence of product-market fit strong enough to raise a Series A on.
Series A	Sentrio: a growth engine that produces the same result every quarter, for reasons the team understands.
Series B/C	Efficient scaling: growing revenue without growing headcount and cost at the same rate.
Late stage	Virelane: an IPO or a further growth round, which puts financial and operational controls under outside scrutiny.

3. What failure would be fatal?

Stage	The fatal failure mode
Pre-seed	Building a polished solution to a problem nobody has.
Seed	Mistaking interested conversations for product-market fit and scaling too early.
Series A	A growth engine that worked once by luck, and can't be repeated on purpose.
Series B/C	Headcount outpacing the systems that support it, and coherence breaking down.
Late stage	Virelane: a serious breach or a failed audit at a top account. A slower threat: infrastructure cost growing in step with revenue, which undermines the IPO's margin story.

4. What complexity can we avoid?

Stage	Complexity worth avoiding
Pre-seed	Casewell: almost everything beyond the prototype, such as multi-region infrastructure.
Seed	Premature scale: building for load that hasn't been asked for yet.
Series A	Sentrio: operating its own Kubernetes cluster; a managed container platform met its scheduling needs.
Series B/C	Building bespoke platform tooling before enough teams exist to make it worth the investment.
Late stage	Virelane: complexity that maps to no requirement, such as an extra cloud no contract calls for or a bespoke database where a managed one fits.

5. What should we buy as a managed service?

Stage	What gets bought instead of built
Pre-seed	Everything that isn't the product itself: auth, hosting, the database, the model API.
Seed	Still nearly everything; the product is the only thing worth custom-building.
Series A	Sentrio: SSO, audit logging, and compliance tooling; none of it differentiates the product.
Series B/C	Managed databases and observability, plus managed Kubernetes once enough teams share a platform.
Late stage	Virelane: Kubernetes control planes, key management, multi-region databases, and the SIEM.

6. What is strategically differentiating enough to build ourselves?

Stage	What's worth building in-house
Pre-seed	The core product experience, the thing being tested for demand.
Seed	The specific workflow and retrieval logic that makes the product useful.
Series A	Sentrio: its own detection and analysis models, the part customers pay for.
Series B/C	An internal developer platform, once enough teams exist for it to pay for itself.
Late stage	Virelane: fine-tuned models and a routing layer for the most sensitive workloads, plus compliance and audit tooling for its regulatory footprint.

7. What would force us to revisit this architecture?

Stage	The trigger that forces a revisit
Pre-seed	Finding out the problem isn't real; the architecture rarely survives a pivot.
Seed	Signs of product-market fit, the point at which avoiding scale stops being the safe choice.
Series A	Sentrio: enterprise demand outpacing a single-region, lightly governed deployment.
Series B/C	Growth outpacing the platform team and tooling, so every team builds its own version.
Late stage	Virelane: a new jurisdiction requiring data residency the region footprint doesn't cover, or a regulatory change.

Same seven questions, different answers. Casewell, Sentrio, and Virelane arrived at three different architectures by asking them at three different points on the stage table above. Asking them again at each stage also shows when an earlier answer has stopped being true.

The other half of this framework

This series has covered the technology side of that table: what to build, buy, or leave alone at each stage. A parallel set of decisions governs the capital side of the same company: how much to raise, from whom, and on what terms, at each of these same five stages. The founder's funding checklist closes that series' lesson on ownership and investor rights. Capital decisions without architectural discipline burn the runway that capital bought, and architectural decisions made without knowing the company's stage produce the over-engineering this framework exists to prevent.

Previous ← Virelane AI