Volume 3: Human-System Collaboration

Chapter 16: Sales & ROI

Introduction: Sales as Service

"Sales as most people know it seems sleazy sometimes. Used car salesmen get the brunt of the jokes. It does not have to be that way. From SPIN selling to consultative selling, there are many ways to present and sell your product. Without a sale, the product does not get to help people. In the end, we are trying to help people solve problems and have better lives. With more sales, we can help solve more problems and make the world a little bit better."

The truth about sales:

Most developers and implementers dread sales. They think it means: - Manipulating people into buying things they don't need - High-pressure tactics and closing techniques - Exaggerating benefits and hiding drawbacks - Being pushy, aggressive, "always be closing"

That's not sales. That's fraud.

Real sales is: - Understanding someone's problem deeply - Determining if your solution truly helps them - Explaining clearly how it works and what it costs - Letting them make an informed decision - Supporting them to success after they buy

The moral framework:

If your pattern-based system genuinely: - ✅ Reduces permit processing from 10 days to 2 days - ✅ Prevents drug interaction errors that could kill patients - ✅ Cuts invoice processing cost by 80% - ✅ Helps families afford food (SNAP benefits) - ✅ Makes commerce accessible to small businesses globally

Then you have a MORAL OBLIGATION to sell it.

Every day you don't sell is a day: - Someone waits 10 days for a permit unnecessarily - A patient is at risk from preventable drug interactions - A business wastes money on inefficient processes - A family struggles with bureaucracy to get benefits - A small business can't compete because of technology barriers

This chapter teaches you to sell ethically and effectively so your pattern-based systems can help the maximum number of people.

Section 1: Consultative Selling Framework

Forget "Always Be Closing." Instead: Always Be Helping.

The SPIN Selling Method

Developed by Neil Rackham after studying 35,000 sales calls. SPIN stands for: - Situation - Problem - Implication - Need-Payoff

How it works:

1. Situation Questions (Understand their current state) - "How do you process permit applications today?" - "What system do you use for patient intake?" - "Walk me through your invoice approval process." - "How many forms do you process per month?"

Goal: Understand context without overwhelming them with questions.

2. Problem Questions (Surface pain points) - "What frustrates you most about the current process?" - "How often do applications get rejected due to errors?" - "What happens when someone submits an incomplete form?" - "How long does it typically take to process each application?"

Goal: Get them to articulate their pain (they sell themselves).

3. Implication Questions (Amplify consequences) - "What's the cost when projects are delayed 10 days waiting for permits?" - "How many patients have had adverse drug reactions that could have been prevented?" - "What does it cost to manually correct errors in invoices?" - "What opportunities do you miss when processes take so long?"

Goal: Make the problem feel urgent (they realize they need a solution NOW).

4. Need-Payoff Questions (Let them envision the solution) - "How valuable would it be if permits were approved in 2 days instead of 10?" - "What would it mean if the system automatically checked for drug interactions?" - "If invoices were validated before submission, how much time would that save?" - "What could you accomplish with the time you'd save?"

Goal: They imagine the value themselves (more powerful than you telling them).

Example SPIN Conversation: Permit System

Salesperson (You): Tell me about how you process building permits today. (Situation)

City Clerk: We use a DOS-based system from 1995. Applicants fill out paper forms, bring them to City Hall. We manually enter data, check zoning compliance, route to inspectors.

You: What frustrates you most about that process? (Problem)

Clerk: Everything! Forms are incomplete, we have to call applicants back. Wrong addresses. Zoning violations we don't catch until later. Takes 6-8 weeks to approve a simple deck permit.

You: What happens when projects are delayed 6-8 weeks? (Implication)

Clerk: Contractors get frustrated, move on to other jobs. Citizens complain constantly. We get bad reviews online. Some people give up and don't pull permits at all, which is worse.

You: What would it mean for your department if permits could be approved in 2-3 days? (Need-Payoff)

Clerk: That would be amazing! Citizens would be happy. Contractors wouldn't have to wait. Our reputation would improve. We could handle more volume without adding staff.

You: Let me show you how our system does exactly that...

Notice: The clerk sold themselves. You just asked questions.

Section 2: ROI Calculations by Domain

People buy on value, not features. Show them the return on investment.

Healthcare: Drug Interaction Prevention

Current state (without system): - Manual drug interaction checking (pharmacist reviews each prescription) - Average time: 5 minutes per prescription - Pharmacist salary: $60/hour = $5 per prescription - Error rate: 0.5% (5 in 1,000 prescriptions have missed interactions) - Cost per adverse drug event: $25,000 (hospitalization, treatment, liability)

With intelligent system: - Automatic real-time interaction checking - Time: 30 seconds per prescription (system does the work) - Error rate: 0.01% (99% reduction) - Cost per prescription: $0.50 (system cost)

ROI calculation (medium pharmacy, 50,000 prescriptions/year):

Time savings: - Current: 50,000 × 5 min = 250,000 minutes = 4,167 hours - New system: 50,000 × 0.5 min = 25,000 minutes = 417 hours - Time saved: 3,750 hours × $60/hour = $225,000/year

Error reduction: - Current errors: 50,000 × 0.5% = 250 errors/year - New system errors: 50,000 × 0.01% = 5 errors/year - Errors prevented: 245 errors/year - Cost avoided: 245 × $25,000 = $6,125,000/year

Total value: $6,350,000/year

System cost: $50,000/year (licensing + support)

ROI: 127x (pay $1, get $127 in value)

Payback period: 3 days (yes, days!)

Government: Permit Processing

Current state (city processing 10,000 permits/year): - Average processing time: 30 days - Staff time per permit: 6 hours @ $35/hour = $210 - Total staff cost: $2,100,000/year - Citizen satisfaction: Low (complaints, bad reviews) - Economic impact: Projects delayed = $50M in delayed economic activity

With intelligent system: - Average processing time: 3 days (90% reduction) - Staff time per permit: 0.5 hours (automated validation, workflows) - Total staff cost: $175,000/year - Citizen satisfaction: High (fast, transparent) - Economic impact: Projects start immediately

ROI calculation:

Staff cost savings: - Current: $2,100,000/year - New: $175,000/year - Savings: $1,925,000/year

Economic impact: - Projects start 27 days sooner on average - 10,000 permits × $5,000 average economic value per day of delay - Economic benefit: $1,350,000,000/year (yes, $1.35 billion!)

Total value: $1.35B economic + $1.925M operational = $1.35B/year

System cost: $100,000/year

ROI: 13,500x

Payback period: 19 hours (recover cost in less than 1 day!)

Financial: Expense Management

Current state (company with 500 employees, 25,000 expenses/year): - Manual expense submission and approval - Average time per expense: 30 minutes (employee + manager + finance) - Error rate: 15% (out-of-policy expenses approved) - Fraud rate: 2% (duplicate submissions, inflated amounts) - Average expense: $250

With intelligent system: - Automated policy checking and approval routing - Average time: 5 minutes (system validates, auto-routes) - Error rate: 0.5% (real-time policy validation) - Fraud rate: 0.1% (duplicate detection, OCR receipt matching)

ROI calculation:

Time savings: - Current: 25,000 × 30 min = 750,000 min = 12,500 hours - New: 25,000 × 5 min = 125,000 min = 2,083 hours - Time saved: 10,417 hours × $50/hour (blended rate) = $520,850/year

Error reduction: - Current errors: 25,000 × 15% = 3,750 out-of-policy expenses - Average overage: $50 per error - Cost: 3,750 × $50 = $187,500/year wasted

Fraud prevention: - Current fraud: 25,000 × 2% = 500 fraudulent expenses - Average fraud amount: $250 - Cost: 500 × $250 = $125,000/year stolen

Total value: $520,850 + $187,500 + $125,000 = $833,350/year

System cost: $50,000/year (500 users × $100/user)

ROI: 16.7x

Payback period: 22 days

E-commerce: Checkout Optimization

Current state (online store with $5M annual revenue): - Cart abandonment rate: 70% - Checkout errors: 40% of attempts have errors - Average order value: $100 - Conversion rate: 2% (visitors → buyers)

With intelligent system: - Cart abandonment rate: 35% (50% reduction via inline validation, address autocomplete) - Checkout errors: 5% (real-time validation) - Average order value: $110 (smart upsells) - Conversion rate: 3.3% (65% improvement)

ROI calculation:

Revenue increase from conversion improvement: - Current: 100,000 visitors × 2% × $100 = $2,000,000 - New: 100,000 visitors × 3.3% × $110 = $3,630,000 - Increase: $1,630,000/year

Revenue increase from reduced abandonment: - Current abandoned carts: 30,000 (70% of 43,000 cart additions) - New abandoned carts: 15,000 (35% of 43,000) - Recovered carts: 15,000 × $100 = $1,500,000/year

Total value: $3,130,000/year

System cost: $50,000/year

ROI: 62.6x

Payback period: 6 days

Education: Homeschool Co-op Management

Current state (co-op with 100 families): - Coordinator spends 20 hours/week on admin - Manual enrollment forms (paper, incomplete, errors) - Excel spreadsheets for scheduling, attendance - Email for all communication (confusion, missed messages) - Volunteer coordination via Facebook posts (chaos)

With intelligent system: - Coordinator spends 5 hours/week on admin - Online enrollment with validation (complete, correct) - Automated scheduling, attendance tracking - Integrated communication (targeted emails, notifications) - Volunteer management (signups, reminders, tracking)

ROI calculation (value to coordinator):

Time savings: - Current: 20 hours/week × 40 weeks = 800 hours/year - New: 5 hours/week × 40 weeks = 200 hours/year - Saved: 600 hours/year × $30/hour (volunteer time value) = $18,000/year

Error reduction: - Current: 10% of enrollments have errors (10 families) - Time to fix each: 2 hours - Cost: 10 × 2 × $30 = $600/year

Better experience: - Family satisfaction improves (professional system) - Retention increases (families stay longer) - Word-of-mouth (co-op grows 10% year over year) - Value: 10 new families × $1,000/year tuition = $10,000/year

Total value: $28,600/year

System cost: $600/year ($50/month)

ROI: 47.7x

Payback period: 8 days

More importantly: Coordinator gets 600 hours per year back to focus on education, not administration. Priceless!

Section 3: Demo Strategies That Close Deals

Features tell. Demos sell. Stories close.

The Perfect Demo Structure

1. Start with their pain (not your features)

Bad: "This is our dashboard. It has these 47 features..."

Good: "You mentioned you waste 2 hours per day correcting errors in forms. Let me show you how this system prevents those errors before they happen."

2. Use their actual data (not fake data)

Before the demo, ask for: - Sample forms they currently use - Example data (anonymized if necessary) - Real scenarios they face

During demo: "Here's YOUR enrollment form. Watch what happens when someone enters an invalid zip code... See? Immediate feedback. No more incomplete forms."

3. Let them drive (give them the mouse)

Bad: You click through everything while they watch passively.

Good: "Here, you try entering a permit application. Go ahead, make some mistakes. See how the system guides you?"

Why this works: They experience it firsthand. They're not watching a show, they're using the product.

4. Show the "aha moment" within 5 minutes

Attention spans are short. Get to value FAST.

Example: Permit system demo - Minute 1: "Let's submit a permit application together." - Minute 2: Enter address → System validates with USPS → "See? It caught the apartment number was missing." - Minute 3: Enter deck size → System checks zoning → "Your deck is 180 sq ft, which exceeds the 150 sq ft limit. System suggests making it 150 sq ft to avoid variance process." - Minute 5: Submit → System shows approval timeline → "Estimated approval: 3 days vs your current 30 days."

Aha moment: "Holy cow, it caught the zoning issue BEFORE I submitted? That alone would save us weeks of back-and-forth!"

5. Address the elephant in the room

Every product has weaknesses. Address them proactively.

Example: "You might be wondering: 'What if my internet goes down?' Great question. The system has offline mode - you can keep working, and data syncs when connection is restored."

Why this works: You build trust. You're not hiding anything.

6. End with a clear next step

Bad: "So... any questions?"

Good: "Based on what you've seen, I'd recommend we run a 30-day pilot with your planning department. 10 users, real data, no commitment. If it doesn't save you at least 10 hours per week, we part as friends. Sound fair?"

Demo Scripts by Persona

For technical buyers (IT, engineers): - Show the architecture (how it works under the hood) - Demonstrate integrations (APIs, databases, external services) - Discuss security (encryption, access controls, compliance) - Highlight extensibility (can they customize it?)

For business buyers (managers, directors): - Show the ROI (time saved, cost reduced) - Demonstrate workflow improvements (before/after) - Focus on team productivity (how many people it helps) - Highlight reporting (metrics they can show their boss)

For end users (staff who will use it daily): - Make them use it hands-on (can they figure it out?) - Show how it makes their job easier (not harder) - Address learning curve (how fast can they be productive?) - Demonstrate support (what happens when they need help?)

For executives (C-level, budget approvers): - Start with the problem (what pain are we solving?) - Show the financial impact (ROI in dollars) - Demonstrate strategic value (competitive advantage, growth enabler) - Timeline (how quickly do we see results?) - Keep it to 15 minutes (they're busy)

Section 4: Objection Handling

Objections aren't rejections. They're questions disguised as concerns.

The Framework: Acknowledge → Clarify → Respond

Don't: Get defensive or argue Do: Listen, understand, address

Common Objection 1: "It's too expensive"

What they're really saying: "I don't see enough value to justify the cost"

Bad response: "Actually, we're cheaper than our competitors."

Good response: "I understand budget is a concern. Let's look at the numbers together. You're currently spending $2.1M per year on permit processing. Our system is $100k per year and reduces that to $175k. So you save $1.925M per year. That means the system pays for itself in 19 hours. Is the concern the upfront cost, or are these numbers not accurate for your situation?"

Technique: Reframe from cost to investment. Show the return.

Common Objection 2: "We need to think about it"

What they're really saying: "I have concerns I haven't voiced" OR "I need to convince others"

Bad response: "What is there to think about? The ROI is clear."

Good response: "Absolutely, this is an important decision. To help your thinking, can I ask what specific aspects you want to evaluate? Is it the technical fit, the budget approval process, or something else? I want to make sure you have everything you need."

Technique: Uncover the real concern. Give them information to bring to decision-makers.

Common Objection 3: "Our current system works fine"

What they're really saying: "Change is risky/scary" OR "I don't see the problem"

Bad response: "Your current system is terrible! Let me tell you why."

Good response: "That's great that it's working for you! I'm curious - you mentioned earlier that permits take 30 days to process and staff spend 6 hours per permit. If you could cut that to 3 days and 30 minutes without changing anything else, would that be interesting? The question isn't whether your current system works, it's whether a better system would create value."

Technique: Acknowledge status quo, reframe as opportunity (not problem).

Common Objection 4: "We tried something like this before and it failed"

What they're really saying: "I'm scared of repeating past mistakes"

Bad response: "Well, that was a different product."

Good response: "I appreciate you sharing that. Failures are painful. Can you tell me what went wrong? Was it the technology, the implementation process, user adoption, or something else? I want to make sure we don't repeat those mistakes."

[Listen to their answer]

"Thank you for explaining. Here's how we address that specifically: [solution]. Would you be open to a pilot with a rollback plan so you can validate it works before committing fully?"

Technique: Show you understand the past failure. Explain specifically how you're different.

Common Objection 5: "We don't have time to implement this right now"

What they're really saying: "Implementation seems like a huge burden"

Bad response: "Implementation is easy!"

Good response: "I completely understand - you're busy. That's exactly why this system matters, because it saves you time once implemented. Here's our typical timeline: Week 1 is setup (we do most of it), Week 2-3 is training (2 hours per person), Week 4 you go live with support. Total time investment for your team is about 10 hours. You mentioned you waste 20 hours per week on manual processes. So you break even in 3 days, then save 20 hours every week after that. Would it make sense to invest 10 hours to save 1,000 hours this year?"

Technique: Acknowledge concern, show implementation is manageable, reframe as time investment with huge return.

Section 5: Pricing and Packaging Conversations

How you present pricing determines if they buy.

The Price Reveal

Bad: Send them a price sheet and hope they buy.

Good: Walk them through value BEFORE revealing price.

Script: "Before I share pricing, let me make sure I understand your situation. You process 10,000 permits per year, currently takes 30 days, staff cost is $2.1M annually. Is that accurate?"

[Confirm numbers]

"Great. So with our system, processing drops to 3 days, staff cost drops to $175k. You save $1.925M per year. The system costs $100k per year. So your net benefit is $1.825M per year. Does that math make sense?"

[Let them absorb]

"Given that ROI, does the $100k investment seem reasonable?"

[They'll almost always say yes because you framed it as $1.825M gain, not $100k cost]

The Comparison Close

When they're comparing you to competitors:

Bad: Trash-talk competitors.

Good: Help them make informed decision.

Script: "It sounds like you're evaluating multiple solutions, which is smart. May I suggest a framework for comparison? I'd evaluate on three dimensions:

  1. Functional fit - Does it solve your specific problems?
  2. Implementation risk - How likely is it to succeed in your environment?
  3. Total cost of ownership - License + implementation + support + staff time

Would you like me to help you create a scorecard for evaluating all vendors?"

Why this works: You're helping them buy, not selling. They'll remember your helpfulness and often choose you because of it.

The Pilot Proposal

Reduce risk with a small test:

Script: "I understand this is a big decision. What if we did a 30-day pilot? Here's what I propose:

  • 10 users in one department
  • Real data, real workflows
  • We measure results (processing time, errors, user satisfaction)
  • After 30 days, you decide: roll out to the full organization, or we part as friends
  • No long-term commitment required

The only thing you invest is 30 days of trying it. If it doesn't deliver the value we discussed, you haven't lost anything. Fair?"

Why this works: Low risk, high transparency. They can validate everything you've claimed.

Section 6: Customer Success Stories

Stories are more powerful than statistics.

The Story Structure

1. Before (the pain) "Springfield County was struggling with permit processing. 30-day average processing time, citizens frustrated, staff overwhelmed with manual data entry and phone calls about status."

2. The solution (what you built) "We implemented our intelligent permit system with real-time validation, zoning compliance checks, and automated workflows."

3. The process (how you did it) "8-week implementation: Week 1-2 setup, Week 3-4 pilot with planning department, Week 5-6 training, Week 7-8 full rollout. We ran the old system in parallel for safety."

4. After (the results) "Processing time dropped from 30 days to 3 days. Citizen satisfaction went from 35% to 92%. Staff time per permit dropped from 6 hours to 30 minutes. The County processes 20% more permits with the same staff."

5. The quote (social proof) "'This system transformed how we serve citizens. We're faster, more accurate, and our staff is happier.' - Jane Smith, City Clerk"

6. The numbers (the ROI) "ROI: $1.925M annual savings. Payback period: 19 hours. System paid for itself in less than one day."

Multi-Stakeholder Stories

Show how different people benefit:

Healthcare drug interaction story:

For the CIO (buyer): "We reduced adverse drug events by 99%, saving $6M in liability costs and improving patient outcomes."

For the pharmacist (user): "I used to spend 30 minutes per shift manually checking drug interactions. Now the system does it instantly, and I can focus on counseling patients."

For the patient (end beneficiary): "The system caught a dangerous interaction between my new prescription and a supplement I take. It potentially saved my life."

Different people care about different outcomes. Address them all.

Section 7: The Sales Process Timeline

B2B sales take time. Here's a realistic timeline:

Small Business / Self-Service (1-30 days)

Day 1: Discover your website / marketing Day 1-3: Evaluate (demo, free trial) Day 3-7: Internal discussion (small team decides) Day 7: Purchase decision Day 7-30: Onboarding and implementation

Your role: Make evaluation frictionless. Self-service demo, clear pricing, easy signup.

Mid-Market (30-90 days)

Week 1: Initial discovery call Week 2: Technical demo to team Week 3: Business case presentation to manager Week 4: Proposal and pricing discussion Week 5-6: Legal review, contract negotiation Week 7-8: Purchase order Week 9-12: Implementation

Your role: Guide them through internal process. Provide collateral they can share (ROI calculator, case studies, references).

Enterprise / Government (6-12 months)

Month 1: Discovery and needs assessment Month 2: Technical evaluation (IT, security, compliance) Month 3: Business case presentation (executives) Month 4: RFP process (if required) Month 5: Vendor selection Month 6-8: Contract negotiation, procurement, legal Month 9: Purchase order Month 10-12: Implementation planning and rollout

Your role: Patience, persistence, helping them navigate bureaucracy. Provide everything they need for approvals.

Section 8: Metrics to Track

What gets measured gets improved.

Sales Metrics

Lead Sources: - Website visitors: 10,000/month - Trial signups: 100/month (1% conversion) - Demo requests: 50/month (0.5% conversion)

Track which sources convert best.

Sales Pipeline: - Leads: 100/month - Qualified leads: 40/month (40% qualify) - Demos: 30/month (75% attend demo) - Proposals: 20/month (67% request proposal) - Closes: 10/month (50% close rate)

Overall conversion: 10% (leads to customers)

Identify bottlenecks and optimize.

Sales Cycle Length: - Average: 45 days (lead to close) - Small business: 15 days - Mid-market: 60 days - Enterprise: 180 days

Know what to expect by segment.

Deal Size: - Average contract value: $25,000/year - Small business: $5,000/year - Mid-market: $25,000/year - Enterprise: $100,000/year

Focus effort on highest-value opportunities.

Customer Acquisition Cost (CAC): - Total sales + marketing cost: $50,000/month - New customers: 10/month - CAC: $5,000 per customer

Goal: CAC should be recovered in 12 months or less.

Lifetime Value (LTV): - Average customer lifetime: 4 years - Annual contract value: $25,000/year - LTV: $100,000

LTV:CAC Ratio: 20:1 (excellent! Aim for 3:1 minimum)

Section 9: The Moral Imperative

Let's return to the fundamental truth about sales:

"Without a sale, the product does not get to help people. We are trying to help people solve problems and have better lives. With more sales, we can help solve more problems and make the world a little bit better."

Every sale you make enables:

Healthcare: A patient whose life is saved because the system caught a drug interaction Government: A family that starts their home renovation 27 days sooner Education: A homeschool coordinator who gets 600 hours back per year to focus on teaching Finance: A company that stops losing $125,000/year to expense fraud E-commerce: A small business that can compete with Amazon on customer experience

These aren't abstract benefits. These are real people's lives improved.

When you fail to sell: - That patient is still at risk - That family is still waiting - That coordinator is still drowning in paperwork - That company is still losing money to fraud - That small business is still struggling to compete

Sales is not sleazy when you're solving real problems.

Sales is service. Sales is helping. Sales is making the world a little bit better, one customer at a time.

Your job is to: 1. Build systems that genuinely solve problems (you've done this) 2. Explain clearly how they work and what they cost (consultative selling) 3. Help people make informed decisions (not manipulate them) 4. Support them to success after they buy (customer success) 5. Sell to as many people as possible (maximize impact)

With more sales, you help more people. With more revenue, you can hire more engineers. With more engineers, you can build more features. With more features, you can solve more problems. With more problems solved, you make the world better.

It's a virtuous cycle, and it starts with sales. 🌍

Section 10: Sales Scripts and Templates

Cold Outreach Email Template

Subject: [Their Problem] - Question

Hi [Name],

I noticed [City/Company] is using [Old System] for [Process]. I work with organizations like yours to reduce [Pain Point] by [Percentage/Amount].

Quick question: Are you open to a 15-minute conversation about how [Similar Organization] reduced [Process Time] from [Before] to [After]?

If yes, here's my calendar: [Link] If not, no worries.

Either way, I hope you have a great week.

Best, [Your Name]

Why this works: - Short (< 100 words) - Specific problem - Concrete result from peer - Easy yes/no decision - Respectful of their time

Discovery Call Script

Your: Thanks for taking the time to chat. Before I tell you about what we do, I'd love to understand your situation better. Can you walk me through how you [Process] today?

[Listen, take notes]

You: What's the most frustrating part of that process?

[Listen, listen, listen]

You: What have you tried to improve it?

[Understand past attempts]

You: If you could wave a magic wand and fix one thing about [Process], what would it be?

[This is their true pain point]

You: Got it. Based on what you've shared, I think we can help. Would you like to see a demo of how [Similar Organization] solved exactly this problem?

Proposal Template

EXECUTIVE SUMMARY

[Client] currently processes [X] per [timeframe] using [current system]. This results in: - [Pain Point 1] costing $[X]/year - [Pain Point 2] taking [X] hours/week - [Pain Point 3] causing [frustration/errors/delays]

Our proposed solution delivers: - [Benefit 1] saving $[X]/year - [Benefit 2] reducing time by [X]% - [Benefit 3] improving [metric] by [X]%

ROI: [X]x return in [timeframe] Payback Period: [X] days

PROPOSED SOLUTION

[Description of your system and how it addresses each pain point]

IMPLEMENTATION PLAN

Week 1-2: Setup and configuration Week 3-4: Pilot with [Department] Week 5-6: Training Week 7-8: Full rollout

Total timeline: 8 weeks Your team investment: 10 hours total

PRICING

Annual license: $[X]/year Implementation: $[X] one-time Training: $[X] one-time (or included)

Total first year: $[X] Subsequent years: $[X]

EXPECTED RESULTS

Year 1: $[X] in savings/revenue Year 2: $[X] Year 3: $[X]

Cumulative 3-year benefit: $[X] Total 3-year investment: $[X] Net benefit: $[X]

NEXT STEPS

  1. Review proposal
  2. Schedule pilot kickoff
  3. Begin implementation

Questions? Let's schedule a call: [Calendar Link]

Section 11: When NOT to Sell

Ethical selling means sometimes saying no.

Don't sell when:

1. Your solution doesn't fit their problem If they need something your system doesn't do, tell them. "Based on what you've described, I don't think we're the right fit. You should look at [Alternative] instead."

2. They can't afford it If the ROI doesn't make sense for them, tell them. "Given your volume, the payback would be 5 years, which is too long. Maybe revisit when you've grown 10x."

3. They're not ready for change If they're resistant and won't change processes, don't force it. "It sounds like now isn't the right time. I'll check back in 6 months and see if anything has changed."

4. You can't deliver If they need features you don't have or timelines you can't meet, be honest. "We can't deliver that in 30 days. The realistic timeline is 90 days. Is that acceptable?"

5. Better alternatives exist If a competitor truly fits their needs better, tell them. "Based on your requirements, you should also evaluate [Competitor]. They specialize in [Their Strength]."

Why walk away from sales?

Short-term: You lose revenue. Long-term: You build trust, reputation, and referrals.

People remember when you put their interests first. They'll: - Come back when the timing is right - Refer others who are better fits - Give you honest feedback - Speak highly of you in the market

Your reputation is worth more than any single sale.

Conclusion: Sales as Service

You've built pattern-based systems that: - Prevent drug interactions that could kill patients - Process permits in 3 days instead of 30 - Reduce expense fraud by 95% - Help families get food assistance in days instead of months - Enable small businesses to compete globally

These systems make the world better. But only if people buy them.

Sales is not sleazy. Sales is: - Understanding problems deeply (SPIN selling) - Quantifying value clearly (ROI calculations) - Demonstrating solutions effectively (great demos) - Addressing concerns honestly (objection handling) - Helping people make informed decisions (consultative approach) - Supporting them to success (customer success)

With more sales, you help more people. With more people helped, the world gets a little bit better.

That's not sleazy. That's service. That's not manipulation. That's mission.

Now go sell. 🚀

Not because you need the money (though you do). But because people need your help.

Every day you don't sell is a day: - Someone waits unnecessarily - Someone makes preventable errors - Someone struggles with outdated systems - Someone can't compete because of technology barriers

You have the solution. They have the problem. Sales is how you connect the two.

PART IV COMPLETE: IMPLEMENTATION GUIDE

You now have everything you need to: - Chapter 12: Implement the patterns (foundation four, priority matrix, phases) - Chapter 13: Build the architecture (timeless principles, current tech, future-proofing) - Chapter 14: Migrate legacy systems (strangler fig, data migration, parallel running, rollback) - Chapter 15: Choose your business model (SaaS, consulting, hybrid, marketplace) - Chapter 16: Sell the systems (consultative selling, ROI calculations, ethical sales)

Go build. Go sell. Go help people. 💪

Further Reading

Sales Methodologies

Consultative Selling: - Rackham, N. (1988). SPIN Selling. McGraw-Hill. - Situation, Problem, Implication, Need-payoff questions - Research-based B2B sales methodology - Adamson, B., Dixon, M., & Toman, N. (2012). "The End of Solution Sales." Harvard Business Review, 90(7/8), 60-68. - Challenger Sale methodology - Miller, R. B., & Heiman, S. E. (2005). The New Strategic Selling. Grand Central Publishing. - Complex sales to multiple stakeholders

Value Selling: - Anderson, J. C., Narus, J. A., & Rossum, W. V. (2006). "Customer value propositions in business markets." Harvard Business Review, 84(3), 90-99. - Articulating value in B2B contexts - Iannarino, A. (2013). The Only Sales Guide You'll Ever Need. Portfolio. - Modern consultative sales approach

ROI Calculation

Financial Analysis: - Phillips, J. J., & Phillips, P. P. (2007). Show Me the Money: How to Determine ROI in People, Projects, and Programs. Berrett-Koehler. - Comprehensive ROI methodology - Hubbard, D. W. (2014). How to Measure Anything (3rd ed.). Wiley. - Quantifying intangible benefits

Total Cost of Ownership: - Ellram, L. M. (1995). "Total cost of ownership: An analysis approach for purchasing." International Journal of Physical Distribution & Logistics Management, 25(8), 4-23. - TCO framework for technology purchases - Gartner TCO Methodology: https://www.gartner.com/en/information-technology/glossary/total-cost-of-ownership-tco

Business Case Development

Frameworks: - Schmidt, M. J. (2002). The Business Case Guide (2nd ed.). Solution Matrix Ltd. - Structure for business case documents - Gambles, I. (2009). Making the Business Case: Proposals that Succeed for Projects that Work. Gower Publishing. - Winning executive approval

Templates: - PMI Business Case Template: https://www.pmi.org/learning/library/business-case-template-sample-project-6261 - HBR: "How to Build a Business Case": https://hbr.org/2011/03/how-to-build-a-business-case

Change Management Economics

Adoption and Value Realization: - Kotter, J. P., & Cohen, D. S. (2002). The Heart of Change. Harvard Business Press. - People don't change based on ROI alone—emotion matters - Heath, C., & Heath, D. (2010). Switch: How to Change Things When Change Is Hard. Crown Business. - Psychology of organizational change

Time to Value: - Murphy, S. A., & Kumar, V. (2010). "The role of predecisional distortion of product information in channel member decisions." Journal of Marketing, 74(1), 58-73. - How long it takes to realize ROI affects purchase decisions

Pricing Strategy

Value-Based Pricing: - Nagle, T. T., & Holden, R. K. (2002). The Strategy and Tactics of Pricing (3rd ed.). Prentice Hall. - Pricing to capture created value - Hinterhuber, A. (2008). "Customer value-based pricing strategies." Journal of Business Strategy, 29(4), 37-41. - https://doi.org/10.1108/02756660810887079

SaaS Pricing: - Skok, D. "SaaS Metrics 2.0." For Entrepreneurs. - https://www.forentrepreneurs.com/saas-metrics-2/ - CAC payback, LTV:CAC ratio - Price Intelligently (now ProfitWell): https://www.profitwell.com/ - SaaS pricing optimization research

Ethical Sales

Professional Ethics: - Grant, A. (2013). Give and Take. Viking. - Givers succeed in sales by creating genuine value - Pink, D. H. (2012). To Sell Is Human. Riverhead Books. - Modern sales is about serving, not manipulating

Trust-Based Selling: - Maister, D. H., Green, C. H., & Galford, R. M. (2000). The Trusted Advisor. Free Press. - Building client trust in professional services - Covey, S. M. R., & Merrill, R. R. (2006). The Speed of Trust. Free Press. - Economics of trust in business relationships

Sales Enablement

Tools: - Gong: https://www.gong.io/ - Revenue intelligence platform - Highspot: https://www.highspot.com/ - Sales enablement platform - Seismic: https://seismic.com/ - Content management for sales

CRM: - Salesforce: https://www.salesforce.com/ - Leading CRM platform - HubSpot: https://www.hubspot.com/ - Inbound sales and marketing - Pipedrive: https://www.pipedrive.com/ - Sales-focused CRM

Demo and Proof of Concept

Best Practices: - Cohan, P. S. (2006). Great Demo! iUniverse. - Doing discovery-driven demonstrations - PreSales Collective: https://www.presalescollective.com/ - Community for sales engineers

Sandbox Environments: - Building effective POC environments - Measuring POC success criteria - Converting POCs to purchases

Related Trilogy Content