Chapter 9: Selling Document Automation
Introduction
Chapter 8 taught you how to find prospects. Now you need to convert them into paying clients.
This chapter covers: - The discovery call framework - How to demo for maximum impact - Pricing psychology and presentation - Handling objections confidently - Closing techniques that work - Proposal templates that convert
By the end, you'll have a repeatable sales process from first call to signed contract.
The Sales Process Overview
Typical timeline: 7-21 days from first contact to close
Day 0: First Contact (LinkedIn, referral, community)
↓
Day 1-3: Discovery Call (30 minutes, qualify and understand)
↓
Day 4-7: Demo Call (45-60 minutes, show solution)
↓
Day 8-10: Proposal Sent (detailed scope and pricing)
↓
Day 11-14: Follow-up (answer questions, address concerns)
↓
Day 15-21: Close (sign agreement, collect payment)
Faster for warm leads (7-10 days) Slower for cold leads or complex sales (14-21 days)
The Discovery Call Framework
Goal: Understand their situation, qualify fit, build rapport
NOT: Pitch your solution yet
Pre-Call Research (15 minutes)
Before the call, research: - Their organization (website, LinkedIn, social media) - Industry challenges (read recent articles) - Their role (what do they do day-to-day) - Potential pain points (educated guesses)
Walk into call knowledgeable, not cold.
Opening (5 minutes)
Build rapport: "Thanks for taking the time, [Name]. Before we dive in, tell me a bit about [their organization]. How long have you been [in this role]?"
Set agenda: "I'd love to spend 20-25 minutes understanding how you currently handle [documents], what's working, what's not, and see if what I do might be helpful. Sound good?"
They feel: In control, not being sold to
Current State Questions (10 minutes)
Understand their process:
"Walk me through how you currently create [key document]. From start to finish, what are all the steps?"
Listen for: - Manual steps (copy-paste, find-replace) - Time sinks ("this usually takes 2-3 hours") - Pain points ("I always make mistakes on...") - Workarounds ("I have to...")
Dig deeper: "How often do you create this document?" "What happens if there's an error?" "Who else is involved in this process?"
Calculate pain: "So if it takes 3 hours, and you do it weekly, that's 156 hours per year. At your time value of $50/hour, that's $7,800 annually just for this one document?"
They feel: Heard, understood, problems quantified
Desired State Questions (5 minutes)
Envision the future:
"If you could wave a magic wand, what would the ideal process look like?"
Prompt for specifics: "How fast would you want to generate this?" "What level of customization do you need?" "Who needs access to this?"
They feel: Hopeful, excited about possibilities
Qualification Questions (5 minutes)
Ensure they're a fit:
"Have you looked at solutions for this before? What stopped you?"
"What's your timeline for solving this? Is this urgent or nice-to-have?"
"What's your budget for a solution like this?"
"Who else needs to be involved in this decision?"
Red flags: - "I have no budget" (can't afford) - "This is way down the priority list" (won't commit) - "7 people need to approve" (long sales cycle) - "We're happy with our current process" (not actually in pain)
Green flags: - "We have budget set aside" - "We need this ASAP" - "I can make this decision" - "This is our top pain point"
Transition to Next Step (5 minutes)
If qualified, set up demo:
"Based on what you've shared, I think I can help. I've worked with [other clients in vertical] on exactly this problem. Would it make sense to schedule a quick demo where I show you how we'd solve this for you?"
If not qualified, gracefully exit:
"Thanks for sharing all that. To be honest, it sounds like [reason] might not be the right fit for what I do. But I'd be happy to [offer something helpful - resource, introduction, etc.]."
They feel: Not pressured, appreciated for their time
Discovery Call Script Template
[5 min] Opening & Rapport
"Thanks for taking time today. Before we dive in, tell me a bit about [Organization]..."
[10 min] Current State
"Walk me through how you currently create [Document]..."
- Process steps?
- Time required?
- Frequency?
- Pain points?
- Calculate annual cost
[5 min] Desired State
"If you could wave a magic wand, what would the ideal process look like?"
[5 min] Qualification
- Timeline?
- Budget?
- Decision-makers?
- Urgency?
[5 min] Next Steps
"Based on what you shared, I think I can help. Let me show you how [Similar Client] solved this. Can we schedule 45 minutes for a demo next week?"
The Demo That Closes
Goal: Show them their future. Make it tangible.
NOT: Feature dump or tech showcase
Demo Structure (45-60 minutes)
Part 1: Recap Pain (5 minutes)
Start by summarizing what you heard in discovery:
"Last time we talked, you mentioned: - Class rosters take 3 hours every Monday - You manually insert 60 student photos - Allergies often get missed or hidden - Format breaks when you add students - And this costs you 156 hours and $4,000 per year
Did I get that right? Anything else?"
They feel: You listened, you remember, you care
Part 2: Show Current State (5 minutes)
Open their current document:
"Can you share your screen and show me the template you use now?"
Walk through it together:
"So you start with this Word doc from last semester..." "Then you manually type each student's name..." "Then you insert photos one by one..." "Then you hope the formatting doesn't break..."
They feel: "Yes, this is exactly my pain!"
Part 3: Show New Way (20 minutes)
Now share YOUR screen:
"Let me show you how this would work with automation."
Step 1: Show the data (2 minutes)
"All your student info lives in a simple spreadsheet. Excel export from your enrollment system, or you maintain it. Here's what it looks like..."
[Show CSV with student data]
"Just names, grades, photo file names, allergies. Nothing complicated."
Step 2: Show the template (5 minutes)
"And here's the template. Looks similar to yours, but with some special syntax..."
[Open Word template with DataPublisher syntax]
"These double brackets <
"This {{IF Allergies}} section only shows up when a student has allergies."
"And this {{ForEach:Students}} loop repeats for each student automatically."
Don't explain every detail. Show just enough to demystify.
Step 3: Generate live (3 minutes)
"Now watch this. I click 'Generate' and..."
[Click generate]
"...5 seconds later, here's your roster."
[Open generated document]
"All 60 students, photos inserted, formatted perfectly, allergies highlighted in red."
Pause for impact. Let them absorb.
Step 4: Show variations (5 minutes)
"And because it's automated, variations are easy."
"Need version without photos? Toggle one setting."
[Generate again, 5 seconds]
"Need version sorted by last name instead of first? Change the sort."
[Generate again, 5 seconds]
"Need separate rosters per class? Select all classes, batch generate."
[Generate 6 documents in 10 seconds]
"What used to take you 3 hours now takes 15 seconds."
Step 5: Show other documents (5 minutes)
"And rosters are just one document. Here's how we'd handle progress reports..."
[Quick demo of 2-3 other key documents]
"Invoice generation..."
"Member directory..."
They feel: "This is magic. I need this."
Part 4: Results & ROI (5 minutes)
Show the math:
"So for you, based on what you shared: - Current time: 15 hours/week on admin - Automated time: 4 hours/week - Savings: 11 hours/week = 572 hours/year - Value: 572 hours × $26/hour = $14,872 per year
And the investment is $399 setup + $599 annually.
First-year ROI: 1,288% Payback period: 10 days"
Share social proof:
"We've done this for 12 co-ops now. Riverside Co-Op went from 15 hours/week to 4. Forest Hills Co-Op saved 8 hours/week. Valley Homeschoolers cut admin in half."
Part 5: Next Steps (5 minutes)
"Questions so far?"
[Answer questions]
"If you want to move forward, here's what happens next: 1. I'll send a proposal with detailed scope and pricing 2. Once you approve, we schedule kickoff (1-2 weeks) 3. Implementation takes 2-3 weeks 4. You go live and start saving time immediately
Any questions about the process?"
Part 6: Trial Close (5 minutes)
"Based on what you've seen, does this feel like it would solve your problem?"
[If yes:] "Great! Let me get that proposal over to you today. When would you want to go live ideally?"
[If hesitant:] "What concerns do you have?" [Address objections - see below]
Demo Best Practices
DO: - Use their actual document types (don't demo unrelated examples) - Use realistic sample data (not "John Smith" 50 times) - Show speed (generate live, let them see how fast) - Focus on their top 3 pain points (not all 15 documents) - Pause for questions (don't monologue)
DON'T: - Explain technical details they don't need - Show features they don't care about - Rush through the demo - Skip the ROI calculation - Forget to ask for the sale
Pricing Psychology & Presentation
How you present pricing matters as much as the price itself.
Pricing Structures
Option 1: Setup + Annual - Setup: $4,000 (one-time) - Annual: $2,400/year
Present as: Total investment
"Year 1: $6,400 Year 2-5: $2,400/year 5-year total: $16,000"
Option 2: Monthly Subscription - Setup: $4,000 (one-time) - Monthly: $200/month (24-month minimum)
Present as: Monthly investment
"$200 per month, less than a part-time admin assistant"
Option 3: All-Inclusive Fixed - Year 1: $6,400 (everything included) - Year 2+: $2,400/year
Present as: Turnkey solution
"$6,400 gets you completely set up and operational. Nothing else to buy."
Which to use? - Small clients (co-ops): Monthly or annual (soften upfront cost) - Mid-size (law firms): Setup + annual (standard B2B) - Large (enterprise): Custom (based on scope)
Anchoring
Show savings BEFORE showing price:
"You're spending $15,000 per year on this problem."
[Let that sink in]
"Our solution costs $6,400 Year 1, then $2,400 per year."
$6,400 feels small compared to $15,000.
vs. showing price first:
"Our solution costs $6,400."
"Wait, WHAT? That's expensive!"
Tiered Options
Give them choices:
Basic Package: $3,500 setup + $1,800/year - 5 core documents automated - Email support - Quarterly updates
Professional Package: $6,400 setup + $2,400/year ⭐ Most Popular - 10 documents automated - Phone + email support - Monthly updates - Custom training
Enterprise Package: $12,000 setup + $4,800/year - Unlimited documents - Priority support - Weekly updates - Dedicated account manager
Most clients choose middle tier (which is your target pricing anyway)
Payment Terms
Make it easy to say yes:
Option A: Pay in full, get discount "Pay Year 1 upfront ($6,400), get 10% off ($5,760)"
Option B: Split payments "50% at signing ($3,200), 50% at go-live ($3,200)"
Option C: Monthly "Setup fee today ($4,000), then $200/month starting next month"
Accept: - Credit card (instant, but 3% fee) - ACH (2-3 days, lower fee) - Check (slower, but some clients prefer) - Financing (via Stripe Capital, if available)
Handling Objections
Common objections and how to address them.
Objection 1: "That's expensive."
Wrong response: "No it's not. It's actually cheap compared to..."
Right response:
"I understand. Let's look at it this way:
You're currently spending $15,000 per year in time on this problem. This solution costs $6,400 Year 1.
So you're actually saving $8,600 in Year 1.
And in Years 2-5, you save $12,600 each year.
Over 5 years, you save $59,000 while investing $16,000.
Does that help reframe the investment?"
Or offer smaller package:
"If the Professional package feels like too much, we have a Basic package at $3,500. It covers your top 5 documents. Would that work better?"
Objection 2: "I need to think about it."
Wrong response: "Okay, get back to me when you're ready."
Right response:
"Absolutely. Decisions like this shouldn't be rushed. Can I ask - what specifically do you need to think about?
Is it: - The pricing? - Whether this will actually work for you? - Timing? - Getting approval from someone else?
I want to make sure you have everything you need to make a good decision."
[Then address their actual concern]
Objection 3: "Can we start with just one document?"
Wrong response: "No, we have a minimum of 5 documents."
Right response:
"Great question. Here's what I've found:
When we only automate one document, clients don't see enough value to justify the cost. The ROI works when we automate your top 5-10 pain points together.
That said, we can absolutely prioritize. What if we start implementation with your #1 document (class rosters), get that working perfectly, then add the others?
You pay the full setup, but we phase the delivery. Does that work?"
Or offer trial:
"How about this: We do class rosters as a pilot. $1,500. If you love it, that $1,500 applies to the full setup. If not, you walk away with working rosters. Deal?"
Objection 4: "We might build this ourselves."
Wrong response: "No you won't. It's too hard."
Right response:
"That's definitely an option. A few questions:
- Do you have someone on staff with the technical skills to build this?
- How much of their time would it take? (Usually 120-200 hours for first solution)
- What's their hourly cost? (Let's say $50/hour = $6,000-$10,000 in labor)
- Who maintains it when they leave or get busy?
I'm not saying don't build it yourselves. Just make sure you're comparing apples to apples.
We've built this 12 times for co-ops like yours. We know all the edge cases. We support it ongoing. And it costs $6,400.
DIY might cost more in time and headaches. But I understand wanting control."
Often they realize: DIY isn't cheaper once they do the math.
Objection 5: "How do I know this will work?"
Wrong response: "Trust me, it will work."
Right response:
"Great question. Here's how we de-risk this for you:
-
Guarantee: If the solution doesn't save you at least 50% of the time you're currently spending, I'll refund your setup fee. No questions asked.
-
Milestones: You don't pay the final 50% until you see the system working and approve it.
-
References: I can connect you with [Riverside Co-Op coordinator] who uses this. She'll tell you her experience.
-
Pilot: Or we can start with just one document as a proof-of-concept.
What would make you comfortable moving forward?"
Objection 6: "This seems complicated. My team won't use it."
Wrong response: "It's not complicated at all!"
Right response:
"I hear you. Change is hard, especially when everyone's busy.
Here's what we've found: If the old way takes 3 hours and the new way takes 5 minutes, your team will adopt it. The time savings are so dramatic that there's no resistance.
And we provide: - 2-hour training session (hands-on, everyone practices) - Video tutorials they can rewatch - Quick reference guide (laminated, sits on their desk) - First 30 days of hand-holding (any questions, email or call me)
After 2-3 uses, it becomes second nature.
[Other co-op] had the same concern. Their coordinator is 68 years old, not technical. She's now generating rosters in her sleep."
The Proposal Document
After the demo, send a professional proposal.
Proposal Structure
Page 1: Executive Summary
"PROPOSAL FOR [CLIENT NAME]
Prepared by: [Your Name] Date: [Date] Valid through: [30 days]
PROBLEM You're currently spending 15 hours per week on administrative documents: class rosters, progress reports, invoices, directories. This costs $14,872 annually in coordinator time and limits your ability to grow.
SOLUTION Automate your 10 most time-consuming documents, reducing admin time from 15 hours/week to 4 hours/week.
INVESTMENT Year 1: $6,400 (setup + first year) Years 2+: $2,400/year
ROI Time saved: 572 hours/year Value: $14,872/year Payback: 10 days 5-year value: $59,000"
Page 2: Scope of Work
"DOCUMENTS TO BE AUTOMATED
- Class Rosters with Photos
- Current time: 3 hours/week
- Automated time: 5 minutes
-
Features: Photos, allergies, contact info
-
Student Progress Reports
- Current time: 40 hours/semester
- Automated time: 2 hours
- Features: Per-student customization, grades, comments
[Continue for all 10 documents]
DATA STRUCTURE
We'll design a master database structure including:
- Families
- Students
- Classes
- Teachers
- Enrollments
- Fees
[Simple diagram]
TRAINING & SUPPORT - 2-hour training session for coordinator and assistant - Video tutorials for all key tasks - Quick reference guide - 30 days of unlimited email/phone support - Ongoing support included in annual fee"
Page 3: Timeline
"IMPLEMENTATION TIMELINE
Week 1: Kickoff & Discovery - Review current documents - Gather sample data - Finalize template specifications
Weeks 2-3: Build - Develop templates - Test with sample data - Refine based on feedback
Week 4: Training & Go-Live - Training session - Import live data - Generate first documents together - Go-live
Week 5: Support - First week of live use - Address any issues - Optimize as needed"
Page 4: Investment & Terms
"INVESTMENT
Setup Fee: $4,000 Includes: Discovery, template development, data structure design, testing, training, 30-day support
Annual License: $2,400/year Includes: Software access, template updates, ongoing support, feature enhancements
Year 1 Total: $6,400 Years 2-5: $2,400/year
PAYMENT TERMS - 50% ($3,200) due at signing - 50% ($3,200) due at go-live
Accepted: Credit card, ACH, check
GUARANTEE If you're not saving at least 8 hours per week within 60 days, we'll refund your setup fee. No questions asked."
Page 5: Next Steps
"TO PROCEED
- Review and approve this proposal
- Sign agreement (attached)
- Submit payment ($3,200 deposit)
- We schedule kickoff within 5 business days
Questions? Call/text me at [Phone] or email [Email].
Looking forward to working together!
[Your Signature] [Your Name] [Your Title]"
Proposal Best Practices
DO: - Send within 24 hours of demo - PDF format (professional, can't be edited) - Personalize every proposal (not generic template) - Include testimonials or case study snippets - Make next steps crystal clear
DON'T: - Overpromise (under-promise, over-deliver) - Use jargon client won't understand - Forget the guarantee (reduces risk) - Make it 20 pages (keep it 3-5 pages max)
Closing Techniques
How to actually get them to sign.
The Assumptive Close
"Great! Let me get that proposal over to you today. What's the best email?
And when would you ideally want to go live? Next month or the month after?"
Assumes they're buying, just working out logistics.
The Alternative Close
"Would you prefer to start with the Basic package or go straight to Professional?"
Both options are "yes." They're just choosing which yes.
The Timeline Close
"We have availability starting [Date]. If we get kicked off by [Earlier Date], you'd be live before [Event/Deadline]. Does that timing work?"
Creates urgency without being pushy.
The Referral Close
"I'd love to work with you. As you probably gathered, most of my clients come from referrals. If this goes well, would you be open to introducing me to other coordinators in your network?"
Secures future pipeline while closing current deal.
The Silence Close
You: "Based on everything we've discussed, does this make sense for you?"
Them: "Well, I think so, but..."
You: [STAY SILENT. Wait for them to talk.]
People are uncomfortable with silence. They'll fill it. Often with "yes" or revealing their real objection.
Following Up After Proposal
Day 1 (proposal sent): "Proposal sent! Let me know if you have any questions."
Day 3: "Wanted to check if you had a chance to review the proposal. Any questions I can answer?"
Day 7: "I know you're busy. Just wanted to make sure you got the proposal and see if there's anything holding you back from moving forward."
Day 14: "Last follow-up from me! If timing isn't right, no worries - we can revisit in a few months. But if you want to move forward, let me know and we can get started!"
Don't ghost them. Stay in touch until you get clear yes or no.
Key Takeaways
Sales process: 1. Discovery call (understand pain, qualify) 2. Demo (show solution, calculate ROI) 3. Proposal (scope, pricing, timeline) 4. Follow-up (answer questions, address objections) 5. Close (sign agreement, collect payment)
Discovery call essentials: - Listen more than you talk - Quantify their pain (hours + dollars) - Qualify (budget, timeline, decision-maker) - Set up demo (don't pitch yet)
Demo that converts: - Recap their pain - Show current state (their documents) - Show new way (live generation) - Calculate ROI (dramatic savings) - Social proof (other clients) - Ask for sale (trial close)
Pricing presentation: - Show savings before showing price (anchoring) - Offer tiers (most choose middle) - Make payment easy (split, monthly options)
Objection handling: - Acknowledge concern (don't dismiss) - Dig deeper (what's the real objection?) - Reframe (ROI, guarantee, social proof) - Offer alternatives (pilot, basic package)
Closing: - Assumptive (when do we start?) - Alternative (package A or B?) - Timeline (creates urgency) - Silence (let them talk) - Follow up persistently (don't give up after one email)
Next chapter: How to actually deliver the project successfully—from kickoff to go-live.
End of Chapter 9
Next: Chapter 10 - Project Delivery Methodology