Example scenarios

Step into Alex Morgan’s day at Vantry. Work through a renewal at Pfizer, an expansion at Cloudflare, and a service rollout at Siemens. Each scenario starts with an executive decision and follows the evidence, people, and commitments that determine the next move.

Pfizer: protect the renewal

The account looks healthy

Eight pilot labs are live. Weekly active use is 88%, and sample rework has fallen from 4.8% to 1.9%. Operations estimates 320 staff hours released each month. The COO is supportive.

Then three developments change the decision. The CFO asks how much of that time represents actual cash savings. The COO moves to another role before renewal. Alex's promised evidence pack misses its deadline.

The risk is easy to miss if the team reads only adoption or the most recent meeting summary. The relationship now needs a specific answer for a different audience.

What to connect

The meeting establishes that Elena, the CFO, owns approval. She needs a defensible pack before the September 25 Finance committee, with a September 24 reading deadline. A later email confirms that the pack Alex promised for September 21 has not arrived.

The sponsor's handover introduces Grace as the operating owner, with a Payroll baseline due September 23. Grace explicitly says to stop chasing the departing sponsor for that file.

The same account also has an audit export issue. Its resolution matters to the evidence pack, but it does not replace Payroll validation or purchasing approval.

The next move

Plan the evidence-pack work for today. Inspect the CFO's original request, then ask the Assistant to prepare a brief that separates:

• The measured rework improvement and its eight-site scope.
• The estimated capacity released, with its assumptions.
• The 96 agency hours that Operations estimates it avoided, still awaiting Payroll validation.
• The missing evidence, owner, and next checkpoint.

Keep the ten unlaunched labs out of the renewal savings calculation. Send the operating handover to Grace and the budget evidence to Elena. These are different audiences with different decisions to make.

When the evidence changes

Jon later confirms that all 240 sampled records now contain the correct approver timestamps. The export verification leaves Waiting on them. Review Jon’s reply in the account’s interactions: Payroll remains outstanding, and Elena has still not approved renewal.

That is the useful continuity: the account moves forward without turning one successful check into an invented commercial outcome.

Cloudflare: earn the expansion

Interest has conditions

Nina, the VP of CS, is considering 60 seats for the European team. The problem is specific: promises made in Sales handoffs arrive too late for implementation, and time to first value averages 45 days. The pilot target is 30 days without adding two implementation managers.

Three pilot customers reach their first outcome in 26, 28, and 29 days. The fourth is at day 24 and waiting for its own ERP credentials. Security still needs to approve the data region and retention configuration.

What to connect

The executive's interest, the individual pilot results, the fourth customer's dependency, and Security's open request come from different conversations. Together, they define a credible opportunity and the work required to earn it.

Beatrice owns the pilot outcome. Leo owns Security approval. Nina sponsors the budget request. Procurement issues the purchase order. A positive message from one person does not complete the others' decisions.

The next move

Prepare the promised September 25 readout for Nina's October 2 budget meeting. Show all four customer timelines, label the $72,000 annual increment as indicative, and list the remaining pilot and Security gates.

Ask the Assistant: “Prepare Nina's decision brief using the four-account sample. Explain the progress, the fourth account's dependency, and what is required before an expansion proposal is justified.”

The opportunity becomes actionable because the team can follow the conditions behind the interest. Do not describe three successful pilots as four, or count the expansion as closed revenue.

Siemens: make the rollout real

The ticket is closed. Is the customer live?

Two service centers are piloting Vantry before seasonal maintenance demand peaks. Five of twenty Rotterdam test jobs route to the wrong supervisor. Engineering fixes the mapping and closes its issue.

Rachel, the VP of Service Operations, sees the closed ticket and good training attendance. She asks whether she can tell the COO that all six centers are live.

But Dan, the IT program manager, has accepted only 12 of 20 sample jobs so far. Four centers have not started. The original success criterion was a complete service approval without returning to spreadsheets, not attendance at training.

What to connect

Follow the technical resolution alongside the customer's original acceptance criteria and Dan's later progress update. Customer acceptance remains a distinct dependency even when an engineering issue has closed.

The next move

Give Rachel a precise operating-review brief: the fix is deployed, 12 of 20 acceptance jobs have passed, the remaining eight are due September 23, and four launches are still gated on sign-off.

Ask the Assistant to prepare the September 24 rollout update with an owner and checkpoint for each remaining dependency. Keep the distinction between fixed, accepted, and live visible throughout the plan.

For a CS leader, this is a more useful answer than another green status. It explains what is true today and what must happen next.