Dossier 044 · anonymised with permission · €39 tier

Rotterdam contract, or keep building my own product?

Intake summary: solo founder, two years' runway, a team of three whose pay depends on the product working. A six‑month enterprise contract appeared at double his usual rate — in another country, on‑site. His instinct: refuse, protect the dream. He paid for the room because he suspected the instinct was doing the deciding.

Lens 01 · Means Inventorywhat you actually have

Runway is not two years. It is fourteen months after the team's fixed costs and the landlord get their share — and the number decays while the product's market window does not. You have one underpriced asset nobody counts: the contract client is in your exact vertical. Six months inside their operation is a paid research fellowship in the problem you claim to solve.

Lens 07 · Commitment Costwhat this choice kills

Say yes to Rotterdam and something dies: the version of the story where you never "sold out." Name it, mourn it in the intake, and stop letting an unnamed grief steer the company. Stories don't make payroll; they're also not free — the price is what you tell yourself at 2am.

Lens 16 · Collapse Testhow it fails, survivably

Seven failure paths simulated. In four of them, the product stalls past recovery while grinding full‑time with no customers — because full‑time grinding with no market feedback is how builders feel busy, not close. Zero paths where six funded months kill the product outright. The brave option is the fragile one.

Lens 15 · Incentive Trapwho owns you

You keep calling the contract "a detour." It isn't — it's the step that pays your team while you learn enterprise sales from the inside, which is precisely the skill your product lacks. The trap is the frame, not the money: any option that lets the ego stay clean will be over‑chosen. You have been pricing dignity at two years of compounding.

Lens 13 · Inversionthe case against

The strongest argument to decline, steelmanned: enterprise on‑site work is a slow anesthetic — six becomes twelve because the money is good and leaving mid‑project feels rude; the product decays quietly, and by the time you notice, the market window you're protecting has closed behind you. This is real. It is a scheduling risk, not a strategy risk, and scheduling risks get kill criteria, not refusals.

Lens 14 · Kill Criteriathe stop condition, now

Write these before signing, in ink: (1) any month where product time falls under two hours per week for six consecutive weeks, renegotiate to remote or resign from the on‑site requirement; (2) if after ninety days the client relationship yields no introductions in the vertical, the fellowship premise is dead — leave early without guilt; (3) hard calendar end at month six, decided now, not negotiated later under comfort.

Lens 18 · Fear Inventorydata vs weather

Two fears on the table. "The market window closes while I'm gone" — data: your competitor ships monthly; carve real mitigation, a two‑hour weekly product slot and one named owner for releases. "I'll become a guy who takes contracts" — weather. That fear is an identity costume, and identity costumes don't hire.

The verdict

8.1 / 10 confidence — take it

Go to Rotterdam for exactly six months, with the three kill criteria attached and two protected hours a week for the product, releases delegated by name. The contract is not the interruption of your company; the cash drought is. You were defending a story. The room's judgment: fund the company, learn enterprise from the inside, keep one hand on the wheel — the product survives on contact, not on full‑time devotion.

Confidence 8.1, not 9.5, because lens 13's scheduling risk is genuine and untested on you personally. That's what the ninety‑day check exists for.

Put your decision through the room →

This is a real dossier, shortened for the sample. Full dossiers run 8–12 pages with the risk map and every lens filed.