The 4-Call Close — J&M’s end-to-end sales runbook

The discovery-call-script.md in this folder covers one call — the paid Assessment. This document is the whole sequence it lives inside: how a lead goes from first call to signed contract across four calls, not one, with specific actions in the gaps between them so momentum holds without chasing.

Why four calls. Trying to close on call one either pressures the prospect or exposes a missing process — either way they “need to think,” then ghost. Splitting the decision into Discovery → Strategy → Scoping → Contract lets the prospect qualify themselves deeper at each step, so by the contract call the close is a formality. And if they’re going to ghost, they ghost before you’ve built anything — that’s the system working, not failing. This is the AAIC high-ticket path (01-business-plan.md §Custom Build) and the standard across the communities.

Provenance: the checklist below is adapted from a public post by @lukepierceops (x.com/lukepierceops/status/2072655023880688043 — “AI Agency Sales Process Checklist,” signed 85+ clients on this exact split). It matched our existing framing closely enough to adopt as the connective tissue between our already-built assets; each stage is wired to the J&M asset that executes it. Raw OCR archived at sources/reference/lukepierce-4call-checklist.md.

Which lane uses this

• Custom Build / high-ticket cold ($5–30k): the full 4-call process, start to finish.
• Assessment → Concierge (our front door): the paid Assessment is Call 1 + Call 2 fused — you’ve already diagnosed and quantified, so you often collapse to Scoping → Contract. Don’t run four calls when two will do; run the number the deal size warrants.

What was already ours vs. what this adds

The point of adopting it was to close the gaps, not re-document what we had.

Call 1: Discovery

Our full script: discovery-call-script.md. The checklist below is the spine of it — you talk < 20% of the time. - [ ] Open with what motivated them to book, then shut up and listen - [ ] Map their current process step by step, in their own words - [ ] Ask about tech stack and every tool they touch daily - [ ] Dig for pain numbers: hours wasted, who does it, their hourly rate (this feeds the ROI math — get it on the call) - [ ] Confirm budget range and who makes the decision - [ ] Book the strategy call before you hang up, 3–5 days out (never leave the next step to email) — and if they’re not the sole decision-maker, get the other decision-maker invited to it ON the call (“who else needs to see this? Let’s pick a time that works for them too”). A strategy call without the decision-maker is a Continuation wearing an Advance’s clothes.

Between calls 1 and 2

• [ ] Send a recap message same day: what you heard, what’s next
• [ ] Build the strategy doc — current state, proposed systems, ROI per system. → run 04-proposal-generator/generate_proposal.py on your call notes (call-setup-and-notes-template.md is shaped to feed it); ROI is computed from their numbers, never asserted
• [ ] Build a quick demo only if the use case is clear enough (one obvious automation) — otherwise a before/after process map
• [ ] Send a reminder the day before with what you’ll be showing

Call 2: Strategy / Demo

• [ ] Re-open the needs before the doc: “Last time you said [top pain] was costing you about [number] — still the case? Anything moved since?” Only walk the doc against needs they re-confirm out loud. Needs decay between calls; a demo against a stale need creates objections.
• [ ] Walk through the strategy doc as a joint working session (“let’s pressure-test this together”), not a presentation — their pain numbers up top; you’re mirroring their words back with a price on them
• [ ] Show the demo or the before-and-after process maps
• [ ] Tie every proposed system to an ROI number from their own data
• [ ] For each system beyond the top pain, ask a need-payoff question BEFORE showing it (“would fixing [X] actually matter to you, or is it noise?”) — cut any system they shrug at. A benefit only exists against a need they’ve stated.
• [ ] Answer security and integration questions now, not later (data handling, where it runs, what it touches)
• [ ] Book the scoping call live, don’t leave it to email

Between calls 2 and 3

• [ ] Send the strategy doc so it’s in their hands same day
• [ ] Prepare custom scoping questions specific to their business
• [ ] List every login, API, and access point you’ll need to verify (build this list now so Call 3 is fast)

Call 3: Scoping

Template: sources/contracts/OWHomes-Scoping-Call-Agenda.docx — a real 60-min scoping agenda. - [ ] Rapid-fire through your scoping questions - [ ] Have them log into their tools live, verify API access on the call — this is the step that kills post-signature surprises; if the access isn’t there, you find out before you scope around it (this is also the deepest commitment in the sequence — a prospect who grants access has mentally hired you) - [ ] Confirm exactly what’s being built and what’s out of scope - [ ] Lock the timeline and the milestones - [ ] Book the contract call before you hang up

Between calls 3 and 4

• [ ] Update the strategy doc with final scope and final pricing
• [ ] Send the contract before the call so they can read it — pick the MSA by who owns the build: sources/contracts/ (MSA-Client-Owns-Work-Product / -Agency-Owns-Build-No-Annual-Fee / -Agency-Owns-Build-With-Annual-Fee) + a SOW modeled on SOW-OWHomes.docx
• [ ] State your real build-slot availability in the contract email (“I start builds on the 1st and 15th; the next open slot is [date] — signing this week holds it”). Genuine capacity only — never invent a deadline.
• [ ] Prep answers for the objections you already heard (see objection-handling.md)

Call 4: Contract Review

• [ ] Walk through the updated strategy with the updated pricing
• [ ] Go through the terms line by line, no surprises
• [ ] Expect repeat questions you’ve already answered — stay patient; repetition here is buying-signal nerves, not a red flag
• [ ] Send the contract for signature on or right after the call
• [ ] Confirm the deposit and book the onboarding call same day — the deal isn’t closed until money moved and the next call is on the calendar

The three rules that make it work

1. Each call has one job. Don’t scope on the discovery call; don’t sell on the scoping call. One job per call is why the prospect never feels pressure.
2. Never leave the next step to email. Every call books the next one live, before you hang up. Email is where momentum goes to die.
3. Ghosting is a feature. If they drop, they drop before you’ve built anything. Cheap to lose a ghost at Call 2; expensive to lose one after a build. Let the process filter. A ghost after Call 1 usually means Call 1 ended in a Continuation — audit the recording for whether the advance was actually booked live.