How it works

You bring the job. The engine brings the method.

Every job runs through a real methodology — Double Diamond, the d.school micro-cycle, Lean/JTBD — and reaches for one move at a time: a council, a prototype test, a head-to-head, a red-team. Like a doctor: you arrive with the complaint, they run the process, and reach for the right test inside it.

01Frameworks

The process a run follows.

Not a prompt — a process. Each framework paces a run from ambiguity to a buildable answer: diverge to surface the real pain, converge on a tested point of view. These are the methodologies the engine actually executes, step by step.

02Formats

One move at a time.

Inside the process, the engine reaches for single, concrete moves — a moderated council that argues, a prototype personas actually use, a head-to-head that forces a preference, a red-team that argues the case against you. The same move serves many jobs; the framework decides when.

03Why you can trust it

Convergence is earned, not assumed.

The frameworks gate every conclusion: a run can’t converge until enough diverse personas have weighed in, every verdict carries the quote behind it, and the council log stays auditable line by line. And the engine itself is open source — you can read the method you’re trusting. Explore Open Core

  • Evidence gates — no convergence until enough diverse personas have weighed in
  • Grounded councils — every claim traces back to a persona’s quote and memory
  • Coverage by design — each job declares the persona spread it needs to be trustworthy
  • Open source core — the methodology engine is on the record, not behind a curtain