The 40-Minute Cowork Session

0. The Conversation Map

Before the minute-by-minute detail, see the whole shape at once: seven beats inside the 40 minutes, then the branch you should be walking toward the moment you finish. Nothing below is optional filler — every box on this map gets its own fully-scripted stop in Section 4, and the branch at the right gets its own roadmap in Section 11.

Figure 0 — Beats 1–3 (teal) place Cowork on the map and open the governance wedge. Beats 4–5 (dark teal) survive the two objections that actually kill deals. Beats 6–7 (purple) convert the sale into a named next step — which is also where the session hands off into the six-rung ARR ladder that runs for months afterward.

1. Purpose & Outcomes

Forty minutes is not enough time to teach Cowork. It's enough time to give you the four moves you need to have the conversation — and this design is built around exactly those four, in order. This guide picks up exactly where the Shadow AI discovery conversation leaves off: your customer has a Copilot license, or is about to, and now you have to decide what to say about Cowork.

Everything below is a building block, deliberately. Each stop in Section 4 is independently reusable in a one-on-one customer meeting, a lunch-and-learn, or a QBR — if you only retain Stop 4 (the reframe) or Stop 5 (the cost story), you still walk out able to run half the conversation.

2. Before You Walk In — the Tools You'll Actually Use

This conversation is deliberately low-tech in delivery — no live tenant, no login risk — but it leans on four real tools you'll use live, not just cite afterward. Know each one cold before you walk in.

Your materials checklist

• One screenshot, not a login — the Cost Management → Agents & services view from a real month-one tenant (§13), printed large enough to reference at a glance. Useful in Stop 5 as "here's what governed looks like once you're live" — not the opener.
• The Cowork Cost Simulator, loaded offline on your machine.
• An ASPX export for at least one real reseller ID, pulled the morning you run this.
• The objection cards — for practicing the Stop 4 drill with a colleague, if time allows (Section 9).
• A blank index card — for your closing 30-day commitment in Stop 7.

3. The Shape of the Session

Three acts in forty minutes — each one a building block you can redeploy on its own. The pacing is intentionally front-loaded on objection handling because that's where deals actually die: not in the pitch, in the second question from the CFO or the CIO who already has a Claude subscription.

4. The Conversation, Beat by Beat

Every stop below has the same three-part anatomy: what you say (the talk track), what you show (the visual or comparison), and the segue — the exact line that pulls the conversation into the next stop. Read it top to bottom once before your first live run; after that, the segues alone are enough to keep you on track.

5. The Deep Claude Cowork Comparison — for When You Get Pushback

Stop 4 gives you the reframe. This section is what's behind it — pull it out when a colleague, or a customer later, wants the full dimension-by-dimension teardown.

Rehearsed objection handles

6. The Licensing Snapshot — What to Quote Without Blinking

Stop 6's objection “we don't own Purview or Defender for Cloud Apps” only lands cleanly if you have the current SMB licensing math memorized. Here it is.

This is exactly what the License Uplift Calculator (§2) is built to walk a customer through line by line — three columns (BP alone / BP + Suites / E5), each Shadow AI capability marked ✓ / partial / ✗, so nobody has to take the delta on faith.

7. Objection Vault — What You'll Hear Every Week

8. The Eight Discovery Questions You Walk In With

These are the bridge from this conversation to your first customer call. Better still: don't start from a blank slate. Pull your top account through ASPX first (§2) so Question 8 already has a data point behind it before the customer even answers.

1. Which AI tools does the leadership team know your staff is using?
2. Which AI tools does your staff actually use? (It's more than the answer to Q1.)
3. What data classification standard exists today — what labels, and who owns them?
4. Do you have an AI Acceptable Use Policy? When was it last reviewed?
5. Is there an approved Copilot budget, and is Cowork line-itemed separately from it?
6. What's your cyber insurance renewal date — does the questionnaire ask about AI use?
7. What does your SharePoint estate look like — Copilot-ready, or an oversharing risk?
8. If you named your top three AI use cases, what would they be? (The Cowork positioning wedge — chat can't do them; Cowork can.)

9. If You Have 90 Minutes Instead of 40

The forty-minute design is deliberately spare. When the agenda allows a longer block, these five exercises turn the same building blocks into hands-on practice.

1. Simulate your own customer. Open the Cost Simulator (§2), enter a real target account's persona mix, model a pre-purchase discount, and print a co-branded leave-behind.
2. Design your Cowork monthly retainer. Scorecard, artifacts, cadence, price point for a 25-seat customer — talk it through with a colleague or your manager.
3. The billing-wall drill. Have a colleague play the customer's CFO while you walk the Azure plan purchase and Cost Management activation from memory.
4. The Claude objection drill. Pair up: one of you plays a CIO who prefers Claude Cowork, the other reframes using Stop 4's script and the §5 deep comparison. Two rounds each, then switch.
5. The month-one review dry run. Using a sample tenant's numbers, draft your month-two recommendation, then have a peer tear it apart.

10. Keep Your Delivery Sharp

• ✓ Lead with the customer's own number — you have ASPX access, so pull it before Stop 1.
• ✓ Say “same model, different governance” three times — Stop 4, again in Stop 5, once more in the close.
• ✓ Say “sanction” in the same breath as “block,” every time. The posture is discover → sanction → govern, not shutdown.
• ✓ Protect the clock in Stop 4, not Stop 2. The lineup card can compress to ninety seconds if things are moving fast; the objection reframe needs its full eight minutes.
• ✓ Close with the written commitment, not open Q&A. Save questions for after — write your card, say it out loud, and move.
• ✗ Do not demo Cowork live. This is a strategic conversation, not a lab — if you must show anything, it's the screenshot, not a live tenant.
• ✗ Do not sell Cowork into EU/EFTA/UK/gov-cloud tenants without a caveat — check Anthropic sub-processor status first.
• ✗ Do not plan to sell Cowork before confirming a CSP-channel Azure subscription exists — you'll hit the billing wall in week one.

11. What's Next — the Path After Minute 40

The index card from Stop 7 is the first rung of a ladder, not a one-off sale. Six service lines compound off the same 4-week discovery engagement that starts with the call you just booked — training runs underneath every rung as the recurring evidence layer that keeps audit and insurance renewals painless.

And specifically for Cowork accounts — the admin motion that earns the retainer

Once a customer is live on Cowork, the Managed AI Governance retainer (Rung 3) has concrete monthly work behind it — pulled straight from the field-tested Cowork admin playbook:

The monthly scorecard you should ship on that retainer: Cowork Credits used (exact calendar month), active users and sessions, median/top-5 concentration, % tasks scheduled vs. user-initiated, retained users week-over-week, and users at ≥50%/≥80% of their limit as the early-warning list.

12. The Walk-Out Artifact and the 30/60/90

In hand at 0:40

The follow-on 30/60/90

13. Reference Library

Every figure, quote, and talk track in this guide traces to one of the sources below. Cite these by name when someone pushes back — the credibility is earned, not asserted.