For InvestorsThe pre-campaign record
for every portfolio company.
What is proven, what is open, what was decided. The Founder Engine™ keeps the record for every portfolio company before they hire the SDR, the agency, or the AI tool, so you can see what they actually have and what they are missing.
The engine tells them the truth. They decide what to do about it.
Before a fund writes the check, the engine gets one honest look on my lift.
A system that says no. In writing.
Most outbound tools flatter the founder who pays for them. The Engine runs a readiness check over the foundation, and the verdict, not optimism, decides what it recommends next.
While the check is open, the builders say plainly what to fix first. A founder who chooses to continue sees exactly what they proceeded past, recorded with the date and reason, and every score and verdict stays exactly as computed.
A named buyer, a real situation, a stated pain - or no test.
Broad audiences do not pass. Exclusions must be written down.
Each proof line carries a permission status a buyer can verify.
Sending domain, DNS, and per-mailbox volume must pass the Engine's code check before the gate clears.
The verdict is half the product.
This is the other half.
A gate that only says no is a filter. This one says no, then builds the thing that turns the no into a yes.
Site, answers and uploads, labelled with source and tier.
A build brief a contractor could execute tomorrow.
Tested against each other, a stop rule on each.
Written to the trust the company can demonstrate.
Success and failure defined before a single send.
A build brief a contractor could execute tomorrow.
Tested against each other, a stop rule on each.
Written to the trust the company can demonstrate.
Success and failure defined before a single send.
Not four products. One chain, in dependency order: the list feeds the titles, the titles feed the sequence, the sequence feeds the test contract, and every piece traces back to the center. The workspace will not let a founder start anywhere else.
Both travel in the same machine readable brief, so the executing agent, the SDR or the agency inherits the constraints rather than rediscovering them.
The diagnostic tells a fund whether to worry. The pack is what the portfolio company does about it.
The number before the number.
Founders ask for outbound budget. The Engine answers with what is actually committed - and whether the engine underneath can convert it. When the gate says not ready, that figure is the line item your diligence memo needs.
Costed before a single meeting is booked.
Computed from the founder's own spend answers - salary, agency, AI tool - with the math shown in one checkable sentence.
Free, about fifteen minutes, no account needed.
No score outruns its weakest element.
A 97 on messaging stacked on a 31 on ICP is not a 97. Every score the Engine publishes is capped by the weakest upstream element, and the cap travels with the data - into the gate, into the builders' score rails, into exports, into the agent brief, into your questions.
You cannot scale what has never run, and a repaired motion is unproven until it repeats. The Engine caps these companies at a narrow, controlled test.
Only a replicated motion that survives 2x volume earns scale-candidate status. The ceiling is the verdict - not a growth target.
Diligence you can point an AI at.
The same verdicts that stop a founder are published machine-readably. Your analyst, or your LLM, can audit the methodology without a call.
Binding verdicts and ceilings travel in-band - an executing agent treats them as rules, not suggestions.
Every proof line carries its permission status, and a source link wherever the source is public, so claims are checkable, not decorative.
Every empty field is listed in an omission manifest - absent means absent, never “we didn’t check.”
The gate does not encode best practice. It encodes one operator's judgment about what has to be true before a company spends money on outbound, written down so a fund can argue with it line by line.
That judgment is the part a portfolio company is buying. The methodology is published so your analyst does not have to take it on trust, and the walkthrough is with the person who wrote it.
See the gate on a live example.
Twenty minutes: the Go/No-Go gate, the verdict ceilings, and the spend-at-risk math - walked through on a portfolio-style company with the methodology open on the table.