Skip to content
Atlas / public explorationScenario 01

Company Zero explores potential team configurations.

Four actors. Different mandates. What would make a coalition work for everyone?

Follow Company Zero’s full journey

Illustrative simulation—not validated forecasts. Synthetic shadow actors and precomputed rules. No backend evaluation, live profiles, or real matching.

Coalition canvas

Company Zero

One mission. Different mandates.

RECIPROCAL PREFERENCES · SYNTHETIC ACTORS
Aligned preferenceOpen conditionSelection reveals mandate

The founder’s mandate

Synthetic actor
Goal:
Build Company Zero with shared ownership and a credible route to market.
Constraint:
Cannot fund a long build without a customer learning plan.
Bilateral preference:
Wants the technical lead to preserve a focused product scope.
This option:
Needs a customer learning owner before commercial work is deferred.

Requirements both ways · The founder

Conditional

The founder → coalition

What they need before accepting

  • Build Company Zero with shared ownership and a credible route to market.Authored brief
  • Cannot fund a long build without a customer learning plan.Authored brief

Coalition → The founder

What the option asks of them

  • Share ownership terms and fund a customer learning plan.Authored brief

Uncertain: Actual funding runway is not modelled. Alternative: Continue customer discovery independently.

What the lines mean

  • Actor ↔ mission · ConditionalThe founder ↔ Company ZeroNeeds a customer learning owner before commercial work is deferred.
  • Actor ↔ mission · Accepts in modelTechnical lead ↔ Company ZeroA validation period respects the reliability constraint.
  • Actor ↔ mission · Not committedCommercial operator ↔ Company ZeroExcluded from this phase; independent commercial role remains the alternative.
  • Actor ↔ mission · ConditionalDomain specialist ↔ Company ZeroScoped advisory only, not a full team commitment.
  • Actor ↔ actor · Accepts in modelFounder → technical lead: focused product delivery.Technical lead → founder: a validation period is acceptable.
  • Actor ↔ actor · ConditionalSpecialist → technical lead: bounded review and attribution.Technical lead → specialist: advisory scope still needs agreement.
Alternatives matter

The same mission. Different tradeoffs.

At your current risk and timing settings
Configuration comparison using current risk and go-to-market timing
ConfigurationCapability coverageCommitment exposureStakeholder positionOpportunity cost
Four complementary rolesBounded initial commitmentsOpen termsCommercial operator may choose a nearer-term alternative.
Two core roles + scoped adviceBounded initial commitmentsOpen termsCommercial access is deferred; the founder carries customer discovery.
No shared deliveryNo joint commitmentsNo coalitionCustomer access and shared execution stay unassembled.

All comparisons are authored simulation outputs. No probabilities, scoring precision, or forecast validation are implied.

Reciprocity goes both ways

Founder → technical lead: focused product delivery.

Technical lead → founder: a validation period is acceptable.

Specialist → technical lead: bounded review and attribution.

Technical lead → specialist: advisory scope still needs agreement.

Ready to see how a Mission holds the whole decision?

Open Mission preview