PegasusCollective The Engagement Arc · pilot-first
Pegasus Collective · the engagement arc

First touch to flying alone.

How an engagement runs, start to finish — the ExO way: pilot-first. The read qualifies you and shapes the first move; then you start a pilot, one workflow, and prove it. The deep Blueprint is real work and real value — but it runs alongside the pilot, not as a gate in front of it. You don't buy a full route before you're allowed to begin.

Pilot-first · ExO cohort model O-led · value-first read Blueprint runs alongside, not as a gate Grounded in ExO 3.0 · used with permission
00

HOT Scan

Self-serve · Beacon
Free
self-serve

The prospect reads all three lanes against published anchors — five minutes, no email wall. Beacon scores each on its own and returns a read meant to unsettle: the gap is rarely where the budget went. Most land further behind on the organization and people than on the platform.

O2.0
H2.6
T3.2
WeakestO
The hookPrintable read, yours to keep · deeper walk via a booking link.
01

Discovery Call

Conversion · Scout
Free
half an hour

Scout opens already holding the read — warm, not cold. The prospect learns what their weakest-lane read means and what the first move looks like. Headcount and starting estate come up here — enough to shape the pilot before a dollar changes hands.

Go / no-goReal organization, real mandate, a gap wide enough to warrant the walk.
02

Roadmap

ExO O-side read · Surveyor
Scoped
flat fee

Surveyor runs the eight ExO Readiness dimensions and an Org call on the 2s and 3s. The output is a four-wave shape and the first pilot named — enough to start. The deployment fork resolves here by headcount (Direct Mode or Edge Twin), and the starting position reads provisionally (inherit / extract / construct), to be confirmed by the pilot itself.

Deployment fork · resolved by headcount Starting position · provisional

Provisional is enough to begin — the pilot is where it's proven.

DeliveredThe Roadmap. Wall named (organization, not platform), first pilot scoped, fork resolved enough to start.
CreditThe Roadmap fee credits forward against the Blueprint, if and when it's run.
03
Concurrent — these two run at the same time
Main line · the primary path

Pilot

One workflow · parallel run · Scribe
TBD
scoped from route

Straight off the Roadmap — one workflow rebuilt on the stack, run in parallel first: the new capability proposes, the human still acts, and the divergence is the training signal. The pilot is where the reading actually happens — the provisional fork gets confirmed, and the reconciliation gaps surface as real evidence rather than a guess.

The test of a real transformation: the human-override rate falls over time.

Safety floor The one preserved gate: enforcement must be real before an agent acts on its own — identity on every action, a record of every change, integrity at the write, rollback in place. A safety floor, not a diagnostic paywall. If it isn't there, it gets built before autonomy — not before the pilot.
ProvesThe falling override rate. As it drops, the workflow earns expanded authority — with granular rollback and the governance rail never off.
Side lane · off the Roadmap

Blueprint

Reconciliation · sequenced route · Architect

The deep read — and the differentiator. Architect adds the Human read (readiness and need, scored apart) and the Technology read (enforcement), then the signature move: reconciliation, where two strands disagree about one control and the gap is the finding. It resolves the starting position into a dependency-sequenced route for waves 2–4.

Not a gate to the first pilot

It can run before the pilot, alongside it, or after — exactly as the ExO cohort runs deep work while the pilot is live. Most often concurrent: the pilot throws off the evidence the Blueprint metabolizes into the route, instead of the route being guessed in advance.

Before — if the client wants the full route first Alongside — the cohort default After — sharpen once the pilot proves
Rejoins the main line at Scale ↓
04

Scale

The remaining waves · Archivist
TBD
scoped from route

Once the pilot proves, the remaining waves execute against the route the Blueprint sequenced — easiest-first, one or two workflows in parallel at a time, each proving before the next. Continuous change becomes the operating rhythm rather than a project that ends.

W2 next workflows · the rise continues W3 governed operations W4 rewire · self-disruption standing
The fadeArchivist aggregates it into a sovereign leave-behind — the governed framework the client owns outright. They start running their own retros. We step away.
The arc, in numbers
2
free steps to first read
scoped
Roadmap · credits forward
TBD
Pilot · off the Roadmap
optional
Blueprint · parallel lane

Pilot-first. The Roadmap qualifies and shapes; the pilot is the first real build; the Blueprint deepens alongside rather than gating. Fees fixed in structure, set per engagement.

Read, then build — and deepen where it helps. One client who now flies alone.

Pilot-first · three strands · one rope
PegasusCollective · Pegasus Source LLC · 2026 · Grounded in ExO 3.0 · used with permission
Draft · illustrative engagement