Everything that happens
after a sales call.

Sarah articulated the fragmentation pain clearly (three sources of truth plus a glue layer). You reflected the framing back accurately, which earned trust. The crisp problem statement emerged from her side, not actively elicited by you with a structured opening, which limited the score.

Limited drilling into root causes. The conversation surfaced the symptom (context-switching) but did not get to underlying drivers such as team structure, ownership boundaries, or downstream impact when a case is routed wrong.

You stayed in discovery for the first 12 minutes, which is decent restraint, then pivoted into the case routing demo before the problem was fully framed. Pricing surfaced at minute 18. Partial restraint, not full.

Consequences of the current setup were never quantified. No hours-per-week figure, no deals-lost number, no glue-script maintenance cost was surfaced. The 12-month "what if nothing changes" projection never came up.

The demo tied case routing to operational throughput, but the business outcome chain (routed cases per week → SLA met → revenue retained) was implied rather than stated. Buyer-relevant metrics (hours saved, capacity returned) were not used.

Sarah signalled procurement timing implicitly (RevOps team capacity issues). You did not surface or reinforce urgency, but the buyer's own timeline supplied some.

You did mention glue-script maintenance as a hidden line, partial credit. The forecast accuracy drop and the onboarding-time cost angles were available and not used.

Demo anchored around a single workflow (case routing) is good craft, but the conversation stayed at workflow level. No elevation to RevOps maturity, team scaling, or capability architecture.

The current setup (three systems plus glue) was reflected back without any reframing or pushback. Validating is not challenging. No alternative model was put on the table.

One brief mention of "other teams we work with" but no concrete data, no anonymised case, no comparative numbers. Loose name-drop, not evidence.

The buyer's framing was reflected back accurately but never reframed. A move like "we see RevOps teams at your scale hit three predictable costs with this exact pattern" was the missing one.

You did mention glue-script maintenance as a hidden line, partial credit. The forecast accuracy drop and the onboarding-time cost were available and not used.

The reframe ("three sources of truth plus a glue layer") matched Sarah's framing precisely. She said "exactly" twice in 30 seconds. Marc, quiet for 8 minutes, engaged after the reframe landed.

The demo used a real Brevant Salesforce record, not a generic sandbox. Specificity carried weight. Some claims about "other teams we work with" stayed vague, lowering the score slightly.

Marc surfaced the context-switching cost mid-call. Sarah stayed candid about the stack and the timing. Budget and political dynamics were not on the table yet.

Next steps were mutually shaped (working session, SOC2 thread, calendar). Sarah confirmed she will attend. Marc was not asked directly whether he will attend the working session, a small gap.

Working session for next Wednesday at 10:00 PT was proposed with specific structure (walk through case routing with two real Salesforce records). Concrete and well-scoped.

Marc explicitly took ownership of the SOC2 thread on the buyer side. Sarah confirmed she will attend the working session. Both buyer-side roles have skin in the game.

Date and time confirmed for the working session. Marc was not explicitly asked whether he will attend, which leaves the second-attendee timing slightly open.

Sarah confirmed the calendar slot verbally. Calendar invite was not sent during the call. Confirmation was solid but not locked in writing on the call.