Skip to main content

Studio program

EcosystemArchitect

A six-month studio partnership prescribed after Keyteller Discovery for ventures whose product, partners, incentives, and operating model must work as one system. Scope, cadence, and terms are defined per engagement.

6 months
Duration
By fit and capacity
Partnership
Scoped after Discovery
Fee

The work

Map, design, then launch

Three connected cycles turn a multi-party constraint into an operating model the team can run. Discovery decides whether this partnership is the right next step.

Phase 1: Map (Months 1-2)

Make the system and constraint explicit

Focus: name the participants, incentives, dependencies, and the assumption that would change the work.

Output

A system map, constraint thesis, and evidence plan.

Key action

Interview the parties whose coordination currently blocks progress.

Phase 2: Design (Months 3-4)

Choose the operating model

Focus: decide the platform, partnership, commercial, and measurement mechanics the venture can actually run.

Output

Operating-model decisions, partnership framework, and launch architecture.

Key action

Make the few design choices that determine whether the exchange can repeat.

Phase 3: Launch (Months 5-6)

Sequence a controlled launch

Focus: turn the architecture into owners, a pilot or launch sequence, and a review rhythm.

Output

A launch plan, operating scorecard, and next-stage priorities.

Key action

Run the smallest launch that tests the coordination model with real partners.

Format

How the partnership runs

System work

The engagement is organised around the coordination problem, not a generic product roadmap.

Studio partnership

Keyteller roles join the workstreams where they change a decision. This is not a staff-augmentation retainer.

Working cadence

Remote and in-person time is set around the work, not offered as a generic perk.

Fit

Who this is for

Ecosystem Architect is for platform ventures with a coordination problem that a product roadmap cannot resolve.

  • A venture whose progress depends on multiple parties coordinating, not just a feature roadmap
  • A material constraint that can be investigated and designed around
  • Founder or operating leadership able to make and own decisions through the work
  • Access to customers, partners, or evidence needed to test the system

Bring the system that is hard to coordinate

Discovery assesses the constraint and evidence first, then determines whether this studio partnership is the smallest useful next step.