Skip to content
NEW: Martech Stack Builder on your phone →

Workspace Rollouts

Plan the migration, not just the diagram.

Sequence the stacks you already have into a staged rollout, then step through it on the canvas. At every phase, see exactly what changes — tools added and removed, the cost delta, and the risk — computed for you.

Build a rollout See pricing →
Loop, 15 seconds, no sound: a three-phase rollout stepped through on the canvas. Phase 2 highlights the warehouse and modeling tools it adds; phase 3 retires the newsletter tool and the Changes panel shows one vendor fewer and the monthly cost going down.

From scattered diagrams to a staged plan

Rollouts build on the diagrams already in your workspace. No new drawing, no duplicate to maintain.

Step 1

Sequence your phases

Pick the saved stacks that represent each stage of your migration and order them into a rollout. Each phase points at a real diagram, so the plan stays live as those diagrams change.

Step 2

Step through on the canvas

Walk phase by phase with arrow-key navigation. The canvas auto-fits each stage and an on-canvas insight panel travels with you, so the plan reads like a story, not a spreadsheet.

Step 3

See the delta at every step

Each transition is diffed automatically against the two diagrams — what's added, what's retired, the change in cost, and the new risk the phase brings in.

The insight panel does the diffing for you

Every phase-to-phase transition is computed from the underlying diagrams — no manual comparison, no stale slides.

Tools added

Exactly which vendors come online in this phase.

Tools removed

What gets retired or replaced, so nothing is orphaned.

Cost delta

The change in monthly spend as the stack evolves.

Risk read

New systems holding personal data, new hubs, and new tools that need consent.

Ask AI about any transition — in context

Ask reads the actual tools and edges involved in a phase, so its answers are grounded in your stack, not generic advice.

“What could break moving from phase 2 to phase 3?”

“Which integrations do I need live before I retire the old CDP?”

“Does this phase introduce any single points of failure?”

In a team workspace, the whole team steps through the same plan.

The method

Plan the rollout by hand

A migration plan that is one long list gets abandoned in week three. This procedure produces phases that can each be finished, which is what makes them survivable. A day of planning per quarter of rollout.

  1. Write down the end state and the current state as two inventories

    Same columns, two sheets. The difference between them is the work — and writing it this way stops the end state drifting during delivery.

  2. Split the difference into changes that can ship alone

    Each change should be completable and leave a working stack behind. If a change only makes sense alongside three others, it is one change, not four.

  3. Order by dependency, then by risk

    Things that unblock other things first. Among equals, do the risky one earlier — a nasty surprise in month one is recoverable, in month eight it is not.

  4. Give each phase an exit test

    One check that proves the phase is done. Without it, phases stay 90% complete and the rollout stalls in a state nobody can describe.

  5. Assign an owner and a date per phase, and leave slack

    A plan with no slack is a plan that fails at the first surprise. Some phases will be wrong; the sequencing is what you are protecting.

Worked example Illustrative

CDP replatform, current stack 18 tools, target 14, four phases.

Changes identified 23
Shippable alone 17
Bundled into dependent groups 6 → 2 changes
Phases 4
Phase 1 exit test identity parity, both systems

Reading it: Nineteen shippable changes across four phases, each with an exit test, is a plan someone can be held to. The same nineteen as one list is a project that reports 80% complete for five months.

The shortcut: Workspace rollouts sequence existing per-phase diagrams and compute the delta between them, so step 1 is two saved stacks rather than two spreadsheets.

The argument behind this

Should your CDP take a year to implement?

On implementation timelines and what actually drives them.

Frequently Asked Questions

What is a Workspace Rollout?
A staged migration plan built from the diagrams you already have. Instead of drawing one "before" and one "after" picture, you sequence your existing phase diagrams into an ordered rollout and step through them on the canvas — with the changes between each phase computed for you.
Do I have to redraw my stack for each phase?
No. Rollouts sequence the diagrams already in your workspace. Each phase points at a real saved stack, so the rollout stays in sync as those diagrams evolve — you are not maintaining a separate copy.
What does the insight panel show between phases?
For each transition it computes the delta directly from the two diagrams: tools added, removed and changed, the change in monthly cost, and a risk read: new systems holding personal data, new hubs, and new tools that need consent. No manual diffing.
Can I ask AI about a specific transition?
Yes. From the on-canvas insight panel you can use Ask on any phase-to-phase transition in context — "what could break moving from phase 2 to phase 3?" — and it answers against the actual tools and edges involved.
How is this different from a before/after comparison?
A comparison is two states. A rollout is the whole sequence — phase 1 through N — with the deltas, costs, and risk at every step, presented as a plan your workspace can step through together.
Which plans include Workspace Rollouts?
Consultant, Agency, Team and Enterprise. On Consultant a rollout sequences your own stacks; in an Agency client workspace or a Team or Enterprise workspace it sequences the shared stacks and everyone in the workspace sees it.

Turn a scary migration into a plan you can walk through

Sequence the stacks you already have, step through the phases, and let the canvas show you the cost and risk of every move — before you make it.

Build a rollout See pricing

No credit card required. Free plan available.