Dev Ramanathan — Operator

Blended · consequential company decisions. Dev wants an adversarial worst-case run before a launch, pricing change, or board commitment. The world can include a light evidence crawl.

Snapshot

Why he buys

Dev is surrounded by dashboards and opinions. His scarce resource is a legible record of the move: who knew what, which constraint mattered, and what the company gave up. An adversarial run is worth more than another brainstorm if it leaves the team able to retry.

The causal loop

Name the decision → build a blended world → let seats attack the premise → commit one move → observe the branch → ask what the company caused → retry with a changed constraint.

Opening objection

“My company is too specific for a template.” That is the point of a kept, private situation. The engine does not fill unknowns with confidence; missing information stays visible.

What the model captures

Company actors, incentives, information asymmetry, resources, and branch consequences. It can preserve the decision record. It does not replace diligence, counsel, or a board.

What would lose him

Weak access controls, uninspectable generated claims, a generic business story, or a commitment made on his behalf.

Shipped / direction boundary

Blended Domains and bounded Scenario runs ship. A light two-cycle crawl can ground a world. Automated search, full team governance, and micro reading are direction.

Seeded situation

• Situation: launch a pricing tier while a larger competitor is copying the category.
• Actors: Dev, product lead, finance, competitor, existing customers.
• Incentives: runway, retention, differentiation, and board confidence.
• Private information: churn signals, true margin, and roadmap capacity.
• Constraints: one quarter, limited engineering, reputational cost.
• Open Fate question: does the tier clarify the category or hand the competitor the frame?
• Candidate moves: launch broadly; pilot with a segment; delay; bundle into the current offer.