Expansion Consultation
Expansion Handoff
Outcome: Warm expansion lead handed to sales with full context Trigger: Client asks about another workflow OR opportunity spotted in Friday report/support Duration: ~20-30 min (dev time only)
Quick Reference
1
Spot opportunity
β
Dev
2
Prepare handoff package
15-20 min
Dev
3
Send client intro + Slack to sales
5 min
Dev
4
Consultation call
60 min
Sales
5
Quote & follow-up
β
Sales
Note: Dev spots and hands off. Sales runs the consultation and closes.
Full Guide
Part 1: Spotting Opportunities (Dev)
Triggers for Expansion Handoff
Client asks
Email, Slack, call
Initiate handoff within 24 hours
We spot opportunity
Friday report analysis
Suggest in report, gauge interest, then handoff
Pain point mentioned
Support conversation
Offer to discuss, then handoff
Conversation Starters
Use these when spotting opportunities in Friday reports or support conversations:
High manual volume
"I noticed you're processing {X} per week manuallyβworth discussing automating that?"
Repeated support asks
"You've asked about {topic} a few timesβshould we explore automating it?"
Error patterns
"I'm seeing recurring issues with {process}βautomation could prevent those."
Growth signals
"With your volume increasing, have you thought about scaling {workflow}?"
Once client shows interest β Move to Part 2.
Part 2: Handoff Prep (Dev) β 15-20 min
Preparation Checklist
Context Sources
Original AI Roadmap
clients/{CODE}/context/docs/AI-ROADMAP.md
Current workflow metrics
Friday reports, n8n
Hours used this month
Time tracking
Client pain points
Support tickets, call notes
Handoff Package Contents
Prepare this information for sales:
Client name & contact
Full name, company, email
Opportunity summary
1-2 sentences on what they want to automate
AI Roadmap reference
Which specific opportunity from discovery
Current performance
# workflows, $/mo value, success rate
Why now?
What triggered the interest
Recommended approach
Your technical opinion (optional)
Part 3: Handoff to Sales (Dev) β 5 min
Two-part handoff:
Client-facing email β Introduces the next step
Internal Slack message β Gives sales full context
Step A: Client-Facing Email
Step B: Internal Slack Message to Sales
Post in #sales or DM the assigned sales person:
Dev handoff complete. Sales takes over from here.
Sales Reference Material
Note: The following sections are for sales to run. Included here for completeness and context.
Part 4: Consultation Call (Sales) β 60 min
Booking Response (Sales sends)
Call Agenda
Understand pain
10 min
What's driving the interest? Current process deep-dive
Review AI Roadmap
10 min
Show documented opportunities from discovery
Workflow walkthrough
20 min
Step-by-step: triggers, inputs, outputs, edge cases
Gather specs
15 min
Systems involved, data formats, approval flows, exceptions
Quote & next steps
5 min
Investment, timeline, close
Opening Question
"You mentioned you're thinking about another workflow. Tell me what's driving thatβwhat's taking up your time or causing headaches?"
Listen for:
Time spent on manual tasks
Error-prone processes
Team frustration points
Growth bottlenecks
Review AI Roadmap
"When we did your AI Roadmap, we identified [X, Y, Z] as opportunities. Based on what you've told me today, I'd recommend starting with [X] because..."
Reference the specific opportunities from their original discovery. This shows continuity and that we planned for this.
Workflow Walkthrough (20 min)
"Let me walk you through how this workflow would work end-to-end..."
Cover:
Trigger: What kicks off the workflow? (webhook, schedule, manual, email)
Inputs: What data comes in? What format?
Processing: What happens to the data? What decisions are made?
Outputs: Where does data go? What gets created/updated?
Edge cases: What happens when X fails? What if Y is missing?
Sketch it out: Share screen and draw the flow as you discuss. This becomes the basis for the Technical Blueprint.
Gather Specs (15 min)
"Now let me get some specifics so I can build an accurate quote..."
Ask:
Document as you go: These specs feed directly into the quote and eventual Technical Blueprint.
Present Quote
"For a new workflow, it's $8,995 to build plus $995/month ongoingβwhich adds another 6 hours per month to your allocation. Timeline is typically 2-4 weeks depending on complexity."
Close
"Want me to send over a formal quote? If you're ready, we can schedule the Workshop for next week."
Part 5: Quote & Follow-Up (Sales)
After the Call
Expansion Quote Email (Sales sends)
When to send: Within 24 hours of consultation
Follow-Up (if no response after 1 week)
When Deal Closes
Sales notifies dev via Slack:
Pricing Reference
New workflow build
$8,995 (one-time)
Ongoing maintenance
$995/month
Dev hours added
6 hrs/month per workflow
Workshop to go-live
2-5 weeks
ROI Estimation (for handoff prep)
Verify
Dev Checklist (Parts 1-3)
Sales Checklist (Parts 4-5) β For Reference
Last updated