Walk into every client call knowing the system
Tomorrow's call is with a client whose account you've never opened, and their agenda will include at least one question about their actual system. Your options today: borrow a builder's evening and hope for a summary, or walk in generic and promise follow-ups. The prep you actually want costs fifteen minutes, alone.
The walkthrough
The steps
- 1
Read the plain-language rundown of the account. Ten minutes buys you the shape of the system and the vocabulary to talk about it without bluffing.
The account described in plain language, system by system. - 2
See what Patchy flagged — what looks stale, abandoned, or drifting — before the client finds it live on the call.
What looks stale, abandoned, or drifting — before the client finds it first. - 3
Check what your team changed since the last call. Every change they logged, tied to the exact thing it touched. "Did the thing we asked for in March ever happen?" — answered from the record.
- 4
Chase the client's agenda with Patchy. What does the reactivation system do, which workflows message those contacts — down to specifics, no builder in the loop.
Chase the client's agenda down to specifics, no builder required. - 5
Walk in with the account's agenda, not just the client's.
Why this changes the call
What Patchy flags is agenda material. "We spotted two workflows that reference a deleted form — we're fixing them this week" is care the client can feel, and it's the kind of sentence renewals are built on. The worst version of that list is the client discovering one of its items live, on the call, as a complaint.
Your team's change log closes the other gap: what's been done since you last spoke is a trail you read, not a relay through delivery. You're not trying to become the technician — you're arming yourself to represent the technicians accurately, and borrowing nobody's evening to do it.
Across a whole book of accounts, it compounds: you stop being the account manager who relays questions and become the one who arrives already knowing.
The takeaway
Fifteen minutes of prep, nobody's evening borrowed. You walk into every call already knowing the account — and knowing what changed since the last one.
FAQ
I'm not technical. Will the documentation make sense to me?
That's who it's written for. The descriptions are plain-language explanations of what each system does, not workflow internals — and the chat answers follow-ups in the same terms.
Does this replace asking the delivery team?
It replaces asking them for orientation, which is most of what call prep used to cost them. Judgment calls still belong with the people doing the work — now as a two-minute conversation about a specific issue instead of "can someone walk me through this account."