How we work - Prove the opportunity. Then build.
Many of the early-stage founders we meet are working on something technically interesting. Fewer of them have tested whether the problem they are solving is one that enough people care about enough to pay someone to fix.
That gap — between technical ambition and validated opportunity — is where most early ventures go wrong. Not because founders are incapable, but because the support structures around them rarely pressure-test the problem before pushing toward a product.
We do things differently.
The Forward Method - Test the problem before committing to the solution.
The Forward Method is the methodology framework we apply across all our work with founders. It scales in depth depending on the engagement — from a 3-day bootcamp to a multi-week accelerator to open-ended incubation — but the core logic stays the same. The method draws on established frameworks like Customer Development (Steve Blank), Jobs-to-be-Done (Clayton Christensen), and Disciplined Entrepreneurship (Bill Aulet).
-
Value Proposition Design. Adapted for mapping founder assumptions against real customer needs, not just articulating a pitch.
-
Assumption Mapping Framework. For identifying and prioritizing the riskiest assumptions in a business model, so founders test what matters most.
-
Value Creation & Capture Mapping. For understanding how economic value actually flows between a startup and its stakeholders.
-
Financial Opportunity Assessment. For evaluating whether the size and shape of an opportunity justifies the investment required to pursue it.
What this looks like in practice
Regardless of format, the work follows the same progression:
-
Frame the problem. Move from a vague idea or technology to a clearly articulated problem worth solving and an opportunity worth pursuing.
-
Map the assumptions. Identify what the business model depends on being true — and rank those assumptions by risk and testability.
-
Run discovery. Structured conversations with real potential users and buyers. Not surveys. Not desk research. Direct, well-designed interviews that surface what people actually do, not what they say they might do.
-
Design experiments. Build the smallest possible test for the most important assumption. Interpret the results honestly.
-
Form or revise the model. Translate validated insights into a coherent model of value creation, delivery, and capture that can withstand scrutiny.
A deliberate way of engaging
We choose depth over scale. We take on fewer engagements because real involvement takes time, and we are not willing to do the work superficially.
This means we are selective about who we work with. It also means that when we commit, we commit — with attention, responsibility, and honest challenge at every stage.
We do not optimize for pitch readiness or investor narratives. We optimize for learning velocity and execution quality. The founders who benefit most from working with us are the ones who want to know what the evidence actually says, even when it complicates the plan.
