Skip to main content
Launch · 90% off$300 $30

Complete Sales Scripts

Every script you need for AI & Automation Tools. Cold calls, discovery, demos, objections, negotiation, follow-ups, and expansion.

31 of 31 sections

Introduction

Script 1: Cold Outreach Email (Enterprise)

Subject: [Company Name]'s [specific process] — question about current approach

Hi [First Name],

I noticed [Company Name] recently [specific trigger: raised funding, expanded team, launched product, hiring for X roles]. Congratulations on the growth.

I work with [similar companies] in the [industry] space who were spending [X hours] weekly on [manual process your AI automates]. Most found that as they scaled, this process became a bottleneck that slowed down [business outcome].

We helped [similar company] reduce their [process] time from [X hours] to [Y minutes] with 99.5% accuracy, freeing their team to focus on [higher-value work].

Worth a brief conversation to explore whether this applies to [Company Name]'s situation?

Best,

[Your Name]


Script 2: LinkedIn Connection Request

Hi [First Name], I work with [target role]s in [industry] to automate [process] using AI. Noticed your background in [specific area] and would value connecting. No pitch — just interested in your perspective on how [industry] is adopting AI for [use case].


Script 3: Discovery Call Opening

"Thanks for taking the time today, [First Name]. My goal for our conversation is to understand how your team currently handles [process], what challenges you are facing, and whether our AI solution might be a fit. I will ask a lot of questions, and then I can share how we have helped companies in similar situations. Sound good?"


Script 4: The Transformation Demo Script

"I have prepared something specific for you today. Let me show you what [Company Name]'s current [process] looks like, and then what it looks like with our AI.

[Show before state: manual process, spreadsheet, queue]

Right now, your team is spending [X hours] on this every [time period]. The process involves [steps], and the typical accuracy rate is around [Y%].

[Run AI processing on their actual or representative data]

Here is the same workload processed by our AI. It completed in [time], with [accuracy]% accuracy. That represents [calculation: time saved, errors prevented, cost reduction].

[Show after state: completed work, dashboard, insights]

At your volume of [monthly volume], this translates to [monthly savings]. Over a year, that is [annual savings].

What questions do you have about what you just saw?"


Script 5: Handling the "Price Is Too High" Objection

"I appreciate you sharing that, [First Name]. Let me ask: when you say the price is high, are you comparing it to doing nothing, to a specific competitor, or to building this internally?

[Listen]

If we look at the total cost of your current approach — [calculate labor hours x hourly cost + error costs + opportunity costs] — you are currently spending [amount] per month on this process. Our tool costs [price] and delivers [savings]. That is a net positive of [ROI] from month one.

Would it help if I put together a specific ROI analysis using your actual numbers?"


Script 6: Proof-of-Concept Close

"Based on what you have seen and what you have shared about your priorities, I would recommend we run a structured proof of concept. Here is exactly how it works:

We will process [specific volume] of your actual [documents/data] over 14 days. We agree upfront on success criteria: [specific metric thresholds]. You pay a $[amount] POC fee, which is credited against your first year subscription if we hit those criteria.

At the end, you will have empirical data on whether this works for your specific use case. No guesswork. No commitment beyond the POC.

Does that sound like a reasonable next step?"


Script 7: Follow-Up After No Response (Sequence)

Day 3:

Hi [First Name], wanted to circle back on my note about [specific value prop]. I shared how [similar company] achieved [result]. Worth a brief conversation?

Day 7:

[First Name], I know priorities shift. Rather than keep following up, I will share one specific insight: [relevant industry stat or case study result]. If this resonates with a priority at [Company Name], I am here. If not, I will step back.

Day 14:

Hi [First Name], this is my last note. I am genuinely curious — is [process automation] not a priority right now, or did I miss the mark on how [Company Name] approaches this? Either way, I appreciate your time and wish you the best.


Script 8: Quarterly Business Review

"Welcome to our QBR, [First Name]. Today we will cover three things:

First, your results. Over the past quarter, our AI processed [volume] [items] with [accuracy]% accuracy. That represents [time saved] hours of manual work and [cost savings] in operational costs.

Second, usage trends. Your team has adopted [features] and usage has [grown/declined] by [X%]. Here is what that tells us about your workflow.

Third, opportunities. Based on your usage patterns, I see three opportunities to increase value: [expansion recommendations].

Before we dive in, what is your biggest priority for the next quarter?"


Script 9: Churn Prevention Call

"[First Name], I noticed [specific churn signal: usage declined, features abandoned, support tickets increased]. I wanted to reach out personally because that is not the experience we want any customer to have.

Can you help me understand what has changed on your end? [Listen actively]

Here is what I can do immediately: [specific intervention: additional training, feature optimization, temporary pricing adjustment, escalation of technical issues].

Beyond that, I would like to schedule a business review to make sure we are aligned on your goals and that our tool is delivering the value you need. Would Tuesday or Thursday work?"


Script 10: Website Headline and CTA Variations

Version 1 — Outcome Focused:

Headline: "Automate 80% of Your Document Processing in 48 Hours"

Subheadline: "AI-powered automation that reads, classifies, and routes documents with 99.7% accuracy — no code required."

CTA: "Start Free Trial — Process 500 Documents Free"

Version 2 — Problem Focused:

Headline: "Your Team Did Not Join Your Company to Copy and Paste"

Subheadline: "Free your people from repetitive data work. Our AI handles the routine so your team handles the remarkable."

CTA: "See How Much Time You Will Save"

Version 3 — Social Proof Focused:

Headline: "The AI Tool Trusted by 500+ Companies to Process 1 Billion Documents"

Subheadline: "Join organizations that cut processing costs by 60% while improving accuracy and speed."

CTA: "Watch a 2-Minute Demo"

Version 4 — Risk Reversal Focused:

Headline: "AI Automation That Pays for Itself in 30 Days — Guaranteed"

Subheadline: "Deploy in 5 days. See ROI in 30 days. If you do not see measurable savings, we will refund your first month."

CTA: "Calculate Your Savings"

Version 5 — Urgency Focused:

Headline: "Your Competitors Are Already Using AI Automation"

Subheadline: "Every day you wait, the gap widens. Start automating in 48 hours with the AI platform built for [industry]."

CTA: "Get Started — First 1,000 Calls Free"


Script 11: RFP Response Executive Summary

"[Vendor Name] is pleased to respond to [Prospect Name]'s Request for Proposal for [AI solution category].

We are a [funding stage/description] AI company specializing in [specific domain]. Our platform processes [volume] [items] monthly for [number] customers across [industries].

Key strengths relevant to your requirements:

[Specific capability matching RFP requirement 1]: [proof point]

[Specific capability matching RFP requirement 2]: [proof point]

[Specific capability matching RFP requirement 3]: [proof point]

We have completed [number] implementations in [industry], with average deployment time of [X days] and customer satisfaction score of [Y].

Our proposal includes: [pricing summary], [implementation timeline], and [SLA commitments].

We welcome the opportunity to demonstrate our platform in a live environment and answer any questions your evaluation team may have."


Script 12: Webinar Opening

"Welcome, everyone. Today we are going to show you something that might change how you think about [process].

I am going to share the exact framework that helped [customer name] reduce their [process] time by [X%] and save [$amount] in the first year.

This is not theory. This is a step-by-step playbook based on [number] implementations across [industries].

By the end of this session, you will know:

The 3 biggest mistakes companies make when automating [process]

Our 5-step framework for successful AI implementation

How to calculate the exact ROI for your specific situation

And you will see a live demo of our platform in action

Let us get started."


Script 13: Expansion Conversation

"[First Name], as we look at your account, I see some exciting trends. Your team has processed [volume] this quarter, up [X]% from last quarter. You are clearly getting value.

I also noticed something: your team is using [feature set A] heavily, but has not yet enabled [feature set B]. Based on what I have seen with similar customers, [feature B] typically adds another [Y%] efficiency gain on top of what you are already achieving.

[Specific customer example]: They were in a similar position and added [feature B]. Within 30 days, they [specific result].

Would it be worth a 15-minute conversation to explore whether [feature B] would make sense for your workflow?"


Script 14: Objection Handling — "We Will Build This Internally"

"That is a completely valid approach, [First Name]. Many companies consider building internally.

Can I share what we have learned from customers who went down that path?

[Company A] spent 8 months and $400K building an internal solution. It worked for their initial use case but could not scale to [volume]. They eventually migrated to our platform.

[Company B] built a prototype in 3 months but struggled with [specific challenge: accuracy, maintenance, scaling]. Their engineering team concluded that core competency was better spent on their product than on ML infrastructure.

Building internally gives you control. But it also gives you: ML engineering hiring, model maintenance, infrastructure scaling, accuracy monitoring, and ongoing optimization.

Our platform gives you production-ready AI today, with a team of specialists maintaining and improving it continuously.

What does your engineering team think about taking on ML infrastructure as a core responsibility?"


Script 15: Customer Success Check-In

"Hi [First Name], I hope you are doing well. I wanted to check in now that you have been using [product] for [time period].

Quick question: On a scale of 1-10, how would you rate the value you are getting? [Listen]

That is great to hear / I appreciate the honesty. What would make it a 10? [Listen]

Here is what I would like to do: [specific action based on response]. I will also share [resource: best practices, new feature, case study] that might be helpful.

One more thing: do you know anyone else at [Company Name] who might benefit from [product]? I would love to help them achieve similar results.

Thanks for your time, [First Name]. I will follow up with [specific commitment] by [date]."


Script 16: Objection Handling — "We Need to Wait for Budget Approval"

"I completely understand, [First Name]. Budget cycles are a reality for every organization. Let me ask you this: what would need to be true for this initiative to get budget priority in the next cycle?

[Listen]

What if we could build a business case together that makes budget approval straightforward? I have helped other [industry] companies put together ROI projections that their finance teams approved in days, not months.

Specifically, I would like to:

1

Calculate your current cost of [manual process]

2

Project the savings and efficiency gains from automation

3

Structure a phased implementation that spreads costs across budget periods

4

Create a one-page business case your CFO can approve quickly

Would it be helpful if I put that together using your actual numbers? I can have it to you by [day], and if it makes the case, we can plan for implementation as soon as budget is available.

What information would you need from me to make that useful?"


Script 17: Objection Handling — "Your Competitor Is Cheaper"

"I appreciate you sharing that, [First Name]. Price is important, and you should absolutely get the best value for your investment. Let me ask: when you look at the competitor's pricing, are you comparing the total cost of ownership, or just the list price?

[Listen]

Here is what we have seen when customers compare us thoroughly:

First, our pricing includes [features/capabilities] that cost extra with [competitor]. When you add those to their base price, the total is typically [X% higher/similar].

Second, our average deployment time is [Y days] compared to their [Z days]. Every week of delayed deployment costs you [calculate: weekly savings x delay weeks].

Third, our accuracy rate is [A%] vs their [B%]. At your volume, the cost of their additional errors is approximately $[amount] per month in rework and corrections.

Fourth, we include [support/training/services] that they charge [amount] for separately.

Would it be valuable to do a side-by-side total cost analysis? I am confident that over the first year, our total cost will be lower, and the ROI will be higher. I can have that analysis to you by [day]."


Script 18: Objection Handling — "We Tried AI Before and It Did Not Work"

"I hear this more often than you might think, [First Name]. AI has been overpromised and underdelivered for years, and many companies have been burned by bad implementations. Let me ask: what specifically did not work about your previous AI project?

[Listen carefully — identify the specific failure mode]

That is [a common issue/a specific challenge]. Here is why this time is different:

[If accuracy issue]: Our accuracy rate on [specific task] is [X%], validated by [number] customers processing [volume] items. We also offer an accuracy guarantee where you only pay for correct results.

[If integration issue]: Our average integration time is [X hours] using our pre-built connectors for [systems]. We provide dedicated solution engineering for every enterprise deployment.

[If adoption issue]: Our structured onboarding program achieves 95% team adoption within 30 days. We do not just deploy technology — we drive organizational change.

[If cost issue]: Our usage-based pricing means you only pay for what you use. We can start with a limited scope that delivers immediate ROI before expanding.

Would you be open to a structured 14-day proof of concept where we prove it works on your actual data? If it does not meet the success criteria we define together, you pay nothing beyond the POC fee."


Script 19: Objection Handling — "Your AI Is Not Accurate Enough for Our Use Case"

"That is a critical concern, [First Name], and I appreciate you raising it. Accuracy requirements vary significantly by use case, and I want to make sure we can meet your specific standards.

Let me ask: what accuracy threshold do you need to see for this to be production-ready?

[Listen]

Our platform achieves [X%] accuracy on [specific task type], measured across [number] production deployments. Here is how we validate that:

1

Benchmark Testing: We run standardized test sets that simulate your actual data distribution. I can share results from tests on [industry]-specific datasets.

2

Human-in-the-Loop Review: For use cases requiring maximum accuracy, our workflow routes low-confidence predictions to human review. This typically catches [Y%] of remaining errors.

3

Continuous Learning: Our models improve over time based on your team's feedback. Most customers see a [Z%] accuracy improvement in the first 60 days.

4

Accuracy Guarantee: We offer a performance-based pricing option where a portion of fees is tied to accuracy SLAs.

Would it be helpful to run a head-to-head accuracy test on your actual data? We will process [sample size] items and show you side-by-side results against your current approach. No commitment required."


Script 20: Objection Handling — "Our Data Is Too Sensitive for External AI"

"Data security is our top priority as well, [First Name]. We understand that [industry] organizations face unique data protection requirements. Let me share our security architecture and deployment options:

Deployment Flexibility:

Private Cloud: Deploy in your AWS/Azure/GCP account with complete data isolation

On-Premise: Full on-premise deployment for maximum data control

Hybrid: Sensitive processing on-premise, less sensitive workloads in our managed cloud

VPC Peering: Secure network connectivity without exposing data to the public internet

Data Protection:

Your data is encrypted at rest using AES-256 and in transit using TLS 1.3

Data never trains models for other customers — complete tenant isolation

We are SOC 2 Type II certified, [HIPAA/GDPR/other] compliant

Full audit logging of all data access and model interactions

Data retention policies you control, with instant deletion capability

Third-Party Validation:

Penetration testing by [firm name] conducted [frequency]

Security questionnaires and vendor risk assessments available

Customer references from [similar industry] organizations with equivalent security requirements

Would your security team like to review our security documentation or speak directly with our CISO? We are happy to participate in any security review process your organization requires."


Script 21: Objection Handling — "We Need More Features Before We Can Buy"

"I appreciate that feedback, [First Name]. Let me make sure I understand: which specific features are blockers for getting started?

[Listen and categorize]

If these are critical path features without which you cannot derive value, let me check our roadmap. We may have these in beta or be able to prioritize them for your deployment timeline.

If these are valuable enhancements but not blockers for initial deployment, let me suggest a different approach:

Most successful customers start with a focused initial deployment that delivers immediate ROI on core use cases. They then expand as we release additional features. This approach has several advantages:

1

Time to Value: You start seeing ROI in weeks, not months

2

Usage-Based Learning: Your team learns the platform, which informs how you use new features

3

Co-Development Partnership: Early deployment customers often influence our feature roadmap

4

Expansion Path: New features drive expansion revenue conversations rather than blocking initial sales

[Specific customer example] started with our core [feature A] in month one. When we released [feature B] in month four, they were our first expansion — adding $[amount] to their annual contract because they understood the value and were ready to expand.

Would it make sense to map out a phased deployment where we start with [core feature] and layer in [requested features] as they become available?"


Script 22: Objection Handling — "The Integration Will Take Too Long"

"I completely understand that concern, [First Name]. Integration timelines can make or break an AI initiative. Let me share what our actual integration data shows:

Typical Integration Timelines:

REST API integration: 2-8 hours

Pre-built connector (Salesforce, Slack, Zendesk, etc.): 1-2 hours

Custom webhook implementation: 4-16 hours

Enterprise system integration (SAP, Oracle, etc.): 1-3 weeks with our solution engineering support

What Accelerates Integration:

1

Pre-Built SDKs: We offer SDKs in Python, JavaScript, Java, and Go with copy-paste code samples

2

Sandbox Environment: Full sandbox with test data so your team can develop without touching production

3

Solution Engineering: Dedicated engineer for enterprise implementations

4

Postman Collections: Ready-to-use API request collections for every endpoint

5

Integration Documentation: Interactive docs with code examples in multiple languages

Risk Mitigation:

Parallel deployment option: run AI alongside existing process without disruption

Rollback capability: instant revert if any issues arise

Phased rollout: start with non-critical workflows, expand as confidence builds

[Specific customer example] integrated our API into their [system] in under 4 hours. Their engineering lead said it was the easiest third-party integration they had done in 5 years.

Would it help if I connected you with our solution engineering team for a 30-minute technical scoping call? They can map out the exact integration steps and timeline for your specific environment."


Script 23: Objection Handling — "We Do Not Have the Technical Team to Support This"

"That is actually one of the reasons our platform exists, [First Name]. We specifically designed it so organizations without large technical teams can deploy and manage AI automation.

How We Minimize Technical Burden:

1

Managed Infrastructure: We handle all model hosting, scaling, monitoring, and maintenance. Zero infrastructure management on your end.

2

No-Code Configuration: Business users can configure workflows through our visual interface without writing code.

3

Managed MLOps: Model updates, version management, and performance optimization happen automatically. Your team never touches a model.

4

24/7 Support: Our team handles technical issues, not yours. Average response time is [X minutes].

5

Customer Success Management: Dedicated success manager who proactively monitors your account and recommends optimizations.

What Your Team Actually Needs to Do:

Initial API integration (typically 2-8 hours, we provide code samples)

Occasional workflow configuration through our UI (no coding)

Review outputs periodically for quality assurance

What Your Team Does NOT Need:

ML engineers

Data scientists

DevOps specialists

Infrastructure management

Model training or fine-tuning expertise

[Specific customer example] deployed our platform with zero technical staff. Their operations manager handled the entire implementation with occasional support from our team.

Would it be helpful to see a demo of the no-code configuration interface? I think you will be surprised how little technical involvement is required."


Script 24: Objection Handling — "Our Legal Team Will Never Approve This Contract"

"I appreciate that concern, [First Name]. Legal review is a critical step in any enterprise procurement, and we have designed our contracting process to make it as smooth as possible.

Our Approach to Legal Negotiation:

1

Standard Contract Terms: Our MSA is designed to be enterprise-friendly from the start. We have removed the typical red flags that slow down legal review.

2

Fallback Positions: We have established fallback positions for the most common legal negotiation points:

- Liability Cap: Standard is [amount]. Willing to increase to [higher amount] for annual contracts over [threshold].

- Indemnification: Mutual indemnification with carve-outs for IP and data.

- Data Ownership: You own your data. Period. We have zero claim to customer data.

- Termination: [Notice period] notice with pro-rata refund for prepaid unused periods.

- Auto-Renewal: Can be removed or changed to annual opt-in upon request.

3

Pre-Approved Legal Packages: We have pre-approved legal packages for [industry] that address common regulatory requirements.

4

Legal Team Direct Contact: Your legal team can contact our legal team directly. No back-and-forth through sales.

Previous Negotiation Examples:

[Company A]: Legal review completed in 5 business days

[Company B]: Custom security addendum drafted and approved in 10 days

[Company C]: Modified liability terms approved in 2 weeks

Would it be helpful if I sent our standard MSA and security documentation directly to your legal team? That way they can review it in parallel while we continue the business discussions."


Script 25: Objection Handling — "We Need to See References from Similar Companies"

"Absolutely, [First Name]. Reference checks are an important part of due diligence, and I am happy to connect you with customers in similar situations.

Our Reference Program:

We have [number] customers who have agreed to serve as references, categorized by:

Industry: [industry] references available

Company Size: [size range] employee organizations

Use Case: [specific use case] implementations

Geography: [region] deployments

Reference Options:

1

Live Reference Call: 30-minute call with a reference customer to discuss their experience

2

Written Case Study: Detailed case study with metrics and customer quote

3

Video Testimonial: 5-minute video of customer discussing their results

4

Reference Visit: On-site visit to see the platform in action (for strategic accounts)

To Protect Our References:

We limit reference calls to [number] per quarter per customer

All reference calls must be scheduled in advance

We request that detailed questions be shared beforehand so the reference can prepare

Available References:

[Company A]: [industry], [size], implemented [use case], achieved [result]

[Company B]: [industry], [size], implemented [use case], achieved [result]

[Company C]: [industry], [size], implemented [use case], achieved [result]

Which type of reference would be most valuable for your evaluation? I can have something arranged within [timeframe]."


Script 26: Objection Handling — "Your AI Might Replace Our Employees"

"That is an important concern, [First Name], and I want to address it directly because this comes up frequently with leadership teams.

Our AI is not designed to replace people. It is designed to augment them. Here is what that looks like in practice:

What Our AI Actually Does:

Handles repetitive, low-judgment tasks that consume [X%] of your team's time

Flags items requiring human review based on confidence scoring

Processes high-volume, routine work during off-hours

Provides recommendations that human experts validate and implement

What Your Team Continues to Do:

Strategic decision-making and judgment calls

Complex problem-solving requiring domain expertise

Customer relationships and high-touch interactions

Quality assurance and exception handling

Innovation and process improvement

The Actual Impact:

[Specific customer example] deployed our AI and did not eliminate a single position. Instead, they:

Redirected 30 hours per week of manual work to customer-facing activities

Reduced employee turnover by 40% because staff were doing more engaging work

Grew their team by 20% because they could handle 3x volume without proportional hiring

Increased employee satisfaction scores from 6.2 to 8.7

The question is not whether AI will change work. It will. The question is whether you want to be the organization that shapes how it changes, or the one that reacts after competitors have already adapted.

Would it help to connect with [reference customer] who navigated this exact concern with their leadership team?"


Script 27: The Executive Sponsor Activation Email

Subject: [Company Name] + [Your Company] — request for [Executive Name]

Dear [Executive Name],

I am writing regarding our engagement with [Company Name] on [AI solution category]. [Champion Name] has been evaluating our platform for [use case], and the technical and business case is strong.

However, we have encountered [specific blocker: procurement delay, budget hold, competing priorities] that is preventing the project from moving forward.

Based on our experience with [number] similar implementations in [industry], companies that delay this decision by [timeframe] typically experience [specific cost of delay].

I would welcome a brief conversation to share how [similar company] achieved [specific result] and to understand any concerns that might be addressed at the executive level.

Would you be available for a 15-minute call this week or next?

Best regards,

[Your Name]

[Title]

[Your Company]


Script 28: The Competitive Displacement Play

"[First Name], I understand you are currently using [competitor] for [use case]. Many of our customers came to us after experiencing limitations with [competitor]. I am curious — how is that working for you?

[Listen for pain points]

That is consistent with what we hear. Specifically, customers tell us they face three challenges with [competitor]:

1

[Limitation 1]: [Description of how competitor falls short]

2

[Limitation 2]: [Description of how competitor falls short]

3

[Limitation 3]: [Description of how competitor falls short]

We built our platform specifically to address these gaps. Here is how we compare:

| Dimension | [Competitor] | Our Platform |

|-----------|-------------|-------------|

| [Dimension 1] | [Competitor performance] | [Your performance] |

| [Dimension 2] | [Competitor performance] | [Your performance] |

| [Dimension 3] | [Competitor performance] | [Your performance] |

| [Dimension 4] | [Competitor performance] | [Your performance] |

[Specific customer example] switched from [competitor] and saw [specific result] within [timeframe].

Would you be open to a side-by-side evaluation using your actual data? We offer a no-risk migration assessment that shows exactly what the switch would look like."


Script 29: The Procurement Acceleration Request

"[First Name], I want to be respectful of your procurement process while also making sure we are not losing valuable time. Based on our experience, the typical procurement timeline for a purchase of this size at [Company Name] is approximately [X weeks].

To help accelerate that timeline, I would like to proactively provide everything your procurement team typically needs:

Pre-Prepared Documentation:

Vendor registration packet (complete)

SOC 2 Type II report (attached)

Security questionnaire responses (attached)

Reference list (attached)

Insurance certificates (available upon request)

Diversity certifications (available upon request)

Legal Package:

Our standard MSA (attached)

Fallback positions for common negotiation points (available)

Previous legal negotiation precedents with similar companies

Financial Package:

Detailed pricing breakdown

3-year TCO analysis

ROI projection with your actual numbers

Flexible payment terms (annual, quarterly, monthly)

What additional documentation would help your procurement team move faster? I am happy to prepare anything specific to your organization's requirements."


Script 30: The Annual Renewal and Price Increase Conversation

"[First Name], I want to discuss your upcoming renewal and share some important updates.

First, the results. Over the past year, our AI has processed [volume] [items] for [Company Name] with [accuracy]% accuracy. That represents [time saved] hours and approximately $[cost savings] in operational savings. Your team has been a great partner.

Upcoming Changes:

Due to [specific reason: increased infrastructure costs, new features added, market adjustments], our pricing will increase by [X%] effective [date]. For your current plan, this means your new annual rate will be $[new price] compared to your current $[current price].

Options to Consider:

1

Annual Prepay: Lock in current rates for 24 months with annual prepay

2

Plan Optimization: We can review your usage and potentially right-size your plan

3

Feature Bundle: Add [new features] at a bundled rate that offsets the increase

4

Loyalty Discount: As a [tenure] customer, you qualify for [Y%] loyalty discount

Expansion Opportunity:

I also noticed your usage has grown [Z%] this year. Many customers in your situation have upgraded to [higher tier] which includes [additional capabilities].

Would you like to schedule a brief call to discuss these options and make sure we have the right plan for your next year?"


Clozo Academy Proprietary Curriculum — The AI Business Growth System