THE DEMO HARNESS a field manual for the AI-equipped solution engineer · drewbreyer.com

Part IV · The rehearsal and the room · 8 min

Delivery day

The pre-flight checklist as the site's one printable card, the discipline of the room, and the quiet fact that everything already ran at 7 a.m.

Objectives

  • Run a pre-flight that catches problems before the room, not in it
  • Manage the room — beats against the clock, a parking lot for rabbit holes
  • Recover from a dead beat without breaking the story

THE ENGAGEMENT

Delivery day has a checklist, and it is the one thing on this site worth printing. Tenant health, a data-freshness query, agent warm-up runs, the fallback deck on local disk, a second browser profile, a network fallback. Print it, carry it, work it before anyone joins the call:

9 beats · about 35 minutes

  1. B1 Cold open

    S1
    On screen
    Morning brief in M365 Copilot surfaces the consultant's overnight email about Meridian; pivot into Dynamics.
    The line
    “This is where the seller already lives — mail and Teams, not a new portal.”
    Risk
    The brief pulls nothing relevant.
    Fallback
    A pre-captured brief screenshot from the rehearsal folder.

  2. B2 Client 360

    S1
    On screen
    Meridian record: mandates, coverage, service history, and meeting notes in one pane.
    The line
    “One record. Everything the last five people learned about Meridian is here.”
    Risk
    A related grid is empty because data did not load.
    Fallback
    The understudy screenshot of the fully loaded record.

  3. B3 Pipeline review with Copilot

    S2
    On screen
    The $400M global-equity win-back at Meridian; Copilot summarizes what changed this week.
    The line
    “The pipeline is data now, not a quarterly slide someone rebuilt by hand.”
    Risk
    Copilot summary is generic.
    Fallback
    Read the change log directly from the opportunity timeline.

  4. B4 Relationship intelligence

    S1
    On screen
    Who-knows-whom via consultant coverage.
    The line
    “"Who here knows Meridian's CIO" used to take days. It is one hop now.”
    Risk
    Coverage graph is sparse.
    Fallback
    The coverage table with the analyst and rating columns.

  5. B5 RFP agent

    S3
    On screen
    New DDQ intake → drafted answers with provenance → SME review queue.
    The line
    “Weeks of re-answering the same questions become a first draft in hours, every line sourced.”
    Risk
    The agent drafts without citations.
    Fallback
    A pre-run draft in the review queue with provenance shown.

  6. B6 Onboarding

    S4
    On screen
    Aldgate Re board; the KYC chase agent's reminder fires; state advances.
    The line
    “The board shows the funding date and exactly what is blocking it.”
    Risk
    The trigger does not fire on cue.
    Fallback
    Advance the stage manually; show the agent run history.

  7. B7 Service

    S5
    On screen
    Tier-1 inquiry deflected with a grounded answer; a complex case routed with context.
    The line
    “The safe questions self-serve; the hard ones arrive with the context already attached.”
    Risk
    The grounded answer is wrong or unsupported.
    Fallback
    Show the citation panel and the guardrail that withholds an ungrounded answer.

  8. B8 Governance interlude

    S6
    On screen
    For Sarah: agent identity, permissions, audit trail.
    The line
    “Every agent you just saw has an identity, a permission boundary, and a log.”
    Risk
    Security asks a question the demo tenant cannot answer.
    Fallback
    The governance slide with Entra Agent ID and the audit-log excerpt.

  9. B9 Close

    S1 · S2 · S3 · S4 · S5 · S6
    On screen
    The S1–S6 traceability table; leave-behind commitment.
    The line
    “Here is every success criterion you set, and the beat that met it.”
    Risk
    Running long; the close gets rushed.
    Fallback
    The one-page traceability table as a printed leave-behind.

Delivery-day pre-flight

Everything below runs at 7 a.m., not in the room.

  • Tenant health — sign in on both browser profiles; confirm no forced password reset.
  • Data freshness — run the story-account timeline query; confirm Meridian and Aldgate Re look right.
  • Agent warm-up — trigger one RFP draft and one KYC chase so the first live run is not the first run.
  • Fallback deck on local disk — the understudy screenshots, exported, offline.
  • Second browser profile — a clean, logged-in fallback if the primary session wedges.
  • Network fallback — a phone hotspot configured and tested.

The close maps beats to criteria

  • S1One client 360.
  • S2One mandate lifecycle with stage-appropriate AI.
  • S3RFP first-draft from weeks to hours, with provenance.
  • S4Onboarding orchestration with visible state and automated document chase.
  • S5Tier-1 service deflection safely grounded in client data.
  • S6Every capability shown has a governance answer.

In the room, run the beats against the clock. Keep a parking lot for the rabbit holes — “great question, I’ve noted it, let me come back to it” — so one curious stakeholder does not eat beat six. Time the governance interlude for when Security is still watching. And when a beat dies, do not narrate the failure: cut to the understudy’s screenshot of that beat working, say your line, and keep moving. The story survives a dead beat; it does not survive you debugging live.

THE HARNESS

The reason you can be calm is that nothing in the room is happening for the first time. The understudy walked every beat at 7 a.m.; the smoke test came back green or told you exactly what drifted; the screenshots are on disk. You are not carrying a hope that the demo works — you are carrying a rehearsed system that already did, this morning, with the evidence in a folder.

The pre-flight is not optional

Every item on that card exists because it failed for someone once. The data-freshness query catches the overnight sandbox reset. The second profile saves you when the primary session wedges mid-demo. The network fallback is why a conference-room Wi-Fi outage is an inconvenience and not the end. Skipping pre-flight to save ten minutes is how you lose the forty that follow.

In the field

Print the pre-flight card and run it against your own demo environment cold, as if it were delivery morning. Time how long it takes. That number is how early you need to start on the real day.

← Field check →