Diagnosis only — no selling until the Phase 3 pivot. Phase 1 Intro (5m) · Phase 2 Deep Dive (20–25m) · Phase 3 Synthesis + Pivot (10–15m).

Phase 1 · Introduction (5 min)

Set the frame: "My goal isn't to sell you anything — my job is to understand your day-to-day reality." Ask for brutal honesty; nothing is embarrassing; it stays between us.

• Magic wand: "If you could eliminate one single process friction point — any size — what would it be, and why that one?"
• Waste: "What tasks does your team spend time on that feel the most wasteful right now?"

Phase 2 · Deep Dive (20–25 min)

Turn every vague complaint into a number. Never accept "the sales process is bad" — pin it to one step. For each pain point run What / Who / How Often / How Much, and force the math ("15 min/day × 2 people = 10 hrs/week — what does that cost you?"). Cover 2–3 areas:

• A · Lead → Onboarding: "Walk me through it from first contact to signed contract, step by step. Where's the handoff? How does a lead get into your system — automatic or typed in?"
• B · Service Delivery: "Once signed, walk me through one typical project from day one. List every tool you touch. Any copy-paste between apps? Is there one place to see the status of every active project?"
• C · Admin & Money: "How does money move from a finished project to your bank? Who invoices? What happens when a payment is late? Do you know at any moment how much is owed and when?"

Phase 3 · Synthesis + Pivot (10–15 min)

Only after 3+ quantified pains. Summary: mirror the pains back in their own numbers → land on "~$X,XXX/month in recoverable loss, conservatively." Diagnosis: "This isn't a technology problem — it's a process-architecture problem. The fix is a structural redesign of how work flows." Pivot: recommend the Operational Audit — a structured dive into every tool and handoff; the deliverable is a prioritized ROI roadmap, fully credited back against any build. Close: "You're paying for certainty, not a report. Does it make sense to take that next step?"

Objection handling

• "Just tell me what to fix now" → assuming the wrong tool is a real risk; the audit protects both of us.
• "That's a lot for a report" → you're losing ~$X/month; it pays for itself in week one and credits back to the build.
• "I need to think / ask my partner" → offer a one-page pain + numbers summary; capture their email.

Open the full script ↗

From "yes" to money in the bank to project delivered.

Client portal — quick facts

• Client URL: team.athanorsolutions.net/portal · sessions last 30 days.
• Demo account (safe to show on calls): blueridge / 12345 — the Blue Ridge Motion practice client.
• Each portal auto-themes to the client's brand color. Update via Claude or portal_db.json.

Open the full workflow ↗

No automation runs behind the scenes — each agent is a hand-written prompt you run in Claude. For every step: open the Prompt Library (Agents tab) → copy the prompt → paste into Claude (Pro, web search ON) → fill every [BRACKET] → review the output like an editor → save it where the step says.

The five rules that never bend

1. No money talk in outreach — no dollar figures, no price comparisons, no "you're wasting X," in any email, ever.
2. Flagged leads are frozen — a lead with a caution flag gets no outreach without Eser's explicit decision.
3. Mark-as-Sent immediately — the log is the only thing preventing double-sends across the team.
4. Prompts change only in prompts.json — no private copies, no inline chat edits that never make it back to the file.
5. Review before saving — every agent output gets human eyes before it touches the database. The agent drafts; a person decides.

Open the full SOP ↗