Complete Sales Scripts

1.1 PQL Outreach — Warm Introduction

Context: Reaching out to a product-qualified lead who has demonstrated high usage.

Email:

Subject: Your team is crushing it with [Product] — let us level you up

Hi [First Name],

I noticed [Company Name] has been really active with [Product] over the past few weeks — [specific usage insight, e.g., "15 team members collaborating on 8 active projects"].

I work with teams like yours to help them get even more value from [Product]. I would love to show you how [similar company] used [specific feature] to [specific result, e.g., "reduce project delivery time by 30%"].

Worth a brief conversation? I am thinking 15 minutes — no pitch, just ideas.

Best,

[Your Name]

LinkedIn Message (shorter):

Hi [First Name] — noticed [Company] has been getting great mileage out of [Product]. Quick question: are you hitting any walls with [specific use case]? I have seen teams in [industry] solve that with [approach]. Happy to share if useful.

1.2 PQL Outreach — Value Expansion

Context: User is approaching limits or showing expansion signals.

Email:

Subject: You are at 85% of your [limit] — let us talk before you hit the wall

Hi [First Name],

I see [Company Name] is powering ahead with [Product] — you are at 85% of your [limit type] on the [Current Tier] plan.

Rather than hitting a hard stop, I wanted to reach out proactively. A quick upgrade to [Next Tier] would give you:

Plus, as a growth-stage [industry] company, you might benefit from [specific enterprise feature].

Want to jump on a quick call to walk through your options? I can have you unblocked in 10 minutes.

[Your Name]

1.3 Enterprise Cold Outreach

Context: First touch with a target enterprise account.

Email:

Subject: [Company Name] + [Product]: Reducing [pain point] by [benchmark]%

Hi [First Name],

[Product] helps [industry] companies like [Company Name] [core value proposition].

We recently helped [Similar Company]:

I believe [Company Name] could see similar results, especially given [specific observation about their company].

Would you be open to a brief conversation next week? I will come prepared with specific ideas for your team.

Best,

[Your Name]

P.S. — Here is a [case study/resource] specifically for [industry] teams: [link]

1.4 Follow-Up After No Response

Context: Second and third touch with no reply.

Email 2 (Day 4):

Subject: Re: [Original Subject]

Hi [First Name],

Quick follow-up — I know priorities shift. Wanted to make sure this did not get buried.

The bottom line: [Company Name] could [specific benefit] with [Product]. I have a 5-minute video walkthrough specifically for [industry] teams if that is easier than a call: [link]

Worth a look?

[Your Name]

Email 3 (Day 8):

Subject: Should I close the loop?

Hi [First Name],

I do not want to be the person who keeps emailing when the timing is not right.

Quick question: should I check back in a few months, or is [Product] not a fit for [Company Name] right now?

Either way, no hard feelings. Just want to respect your time.

[Your Name]

2.1 Vertical Content Promotion — Marketing Agencies

Subject: The agency guide to project profitability

Hi [First Name],

I just published a guide specifically for marketing agencies: "How to Track Project Profitability Without Adding 5 Hours of Admin Work Per Week."

It covers:

Grab it here: [link]

Would love your take — especially if you have found other ways to keep projects profitable.

[Your Name]

2.2 Vertical Content Promotion — Engineering Teams

Subject: Sprint planning benchmark report (engineering teams)

Hi [First Name],

We analyzed sprint planning data from 200+ engineering teams and compiled the findings into a benchmark report.

Key insight: teams using structured planning tools ship 34% more story points per sprint than teams using spreadsheets.

The full report includes benchmarks by team size, industry, and methodology: [link]

Thought your team might find it useful.

[Your Name]

2.3 Webinar Invite — Industry Specific

Subject: Live: How [Customer] Scaled From 10 to 100 Projects

Hi [First Name],

We are hosting a live session next [Day] at [Time]:

"How [Customer] Scaled Their [Industry] Operations From 10 to 100 Projects Without Adding Headcount"

[Customer Contact] will walk through:

Registration is free but limited: [link]

See you there,

[Your Name]

2.4 Product Update — Feature Launch

Subject: New: [Feature Name] is now live (your team will love this)

Hi [First Name],

I know [Company Name] uses [Product] heavily for [use case]. We just launched [Feature Name], and I think it will save your team significant time.

[Feature Name] lets you:

Here is a 2-minute demo: [video link]

Want to try it? It is available on your current plan — just log in and [instructions].

Let me know if you have questions!

[Your Name]

3.1 Discovery Demo (15 minutes)

Opening (1 min):

"Thanks for making time. Before I show you anything, I want to understand what brought you to [Product] today. What is the problem you are trying to solve?"

Discovery Questions (3 min):

Demo (8 min):

"Based on what you shared, here is how [Product] solves [specific problem]:"

[Show only features relevant to their stated problems. Do not show everything.]

Closing (3 min):

"Does this approach what you had in mind for solving [problem]?"

"What questions do you have about implementation?"

"What would the next step look like on your end?"

3.2 Enterprise Demo (30 minutes)

Opening (2 min):

"I have prepared this demo specifically for [Company Name] based on our earlier conversation. I will focus on [3 specific areas]. If at any point you want me to go deeper or shift focus, just say so."

Structure:

Close:

"Based on what you have seen, what would a pilot look like for your team?"

4.1 Health Score Intervention — At Risk

Context: Health score dropped to 60. Proactive outreach.

Email:

Subject: Quick check-in — want to make sure you are getting value

Hi [First Name],

I noticed [Company Name] has not been as active with [Product] recently. Wanted to reach out personally to make sure everything is okay.

Sometimes teams hit a roadblock — integration issues, workflow questions, or just needing a fresh perspective on setup. Whatever it is, I am here to help.

Do you have 10 minutes this week for a quick call? No agenda — just want to make sure you are getting the value you signed up for.

Best,

[Customer Success Manager Name]

4.2 Quarterly Business Review

Agenda:

4.3 Expansion Conversation

Context: Account showing expansion signals. Proactive upsell.

"Hi [First Name], great to see [Company] growing so fast. I noticed you have added [X new users] this quarter and your team is using [feature] heavily.

I wanted to flag something: at your current pace, you will hit your [tier limit] by [estimated date]. Rather than hit a wall, I wanted to talk through your upgrade options.

The [Next Tier] plan would give you:

Plus, given how your team is using [Product], I think [specific premium feature] would be a game-changer for [specific use case].

Want to walk through what the upgrade would look like? I can have a proposal ready by [date]."

5.1 In-App Upgrade Prompt

Context: User hits a free-tier limit.

Modal Title: You have reached your [limit] limit

Body:

You are doing great work — [X projects/Y teammates/Z reports] and counting. To keep going without interruption, upgrade to [Tier Name].

With [Tier Name], you will get:

CTA: Upgrade to [Tier] — $[Price]/mo

Secondary: Remind me later

Social Proof: "Join [X]+ teams on [Tier Name]"

5.2 Trial Expiration Sequence

Email 1 (3 days before expiration):

Subject: Your trial expires in 3 days — save 20% if you upgrade now

Hi [First Name],

Your [Product] trial expires in 3 days. We would hate for you to lose access to [specific feature they used].

If you upgrade before expiration, you will get 20% off your first year. That is $[savings] saved.

[Upgrade Button]

Questions? Just reply — I am here to help.

[Your Name]

Email 2 (Day of expiration):

Subject: Your trial expires today

Hi [First Name],

This is it — your trial expires today at [Time].

Upgrading takes 2 minutes, and you will keep everything you have built so far.

[Upgrade Button — 20% off first year]

Not ready? No problem — you can export your data anytime.

[Your Name]

6.1 In-App Referral Prompt

Context: User achieves a milestone.

Title: Love [Product]? Share the love.

Body:

You have been crushing it with [Product] — [X projects completed / Y hours saved / Z teammates onboarded].

Know someone else who could benefit? Invite them and you both get [reward].

[Your unique link: product.com/invite/friend]

Incentive Display:

6.2 Email Referral Request

Context: Quarterly referral campaign to happy customers.

Subject: A favor — and a reward

Hi [First Name],

Quick question: do you know anyone else at a [industry] company who struggles with [problem]?

If you send them our way and they sign up, we will give you both [reward].

It takes 30 seconds: [referral link]

No pressure — just thought of you since [Product] has been such a great fit for [Company Name].

Thanks!

[Your Name]

7.1 Case Study Recruitment Email

Subject: Feature [Company Name] on our website?

Hi [First Name],

I have been watching [Company Name] grow with [Product] over the past few months — your results have been incredible.

Would you be open to being featured in a case study on our website? It would include:

This is great exposure for [Company Name] — our site gets [X] visitors per month, and we promote case studies across our social channels.

Interested? The interview takes 30 minutes, and we handle all the writing.

[Your Name]

8.1 Integration Partner Outreach

Subject: Integration idea: [Your Product] + [Their Product]

Hi [First Name],

I am [Your Name] from [Product]. We have [X] users in the [industry] space, and [specific number] of them are also [Their Product] customers.

I would love to explore a native integration between [Product] and [Their Product]. Our users have been asking for it, and I think it would drive significant mutual value.

We recently built a similar integration with [Similar Partner] and saw [result — e.g., "500 new activations in the first month"].

Worth a brief conversation? I am happy to share our API docs and integration requirements.

Best,

[Your Name]

8.2 Referral Partner Outreach

Subject: Partnership opportunity: Earn [commission]% recurring

Hi [First Name],

I noticed [Partner Company] works with [industry] companies on [service]. Many of your clients probably need [problem your product solves].

We would love to partner with you. Here is how it works:

Our average partner earns $[amount] per month in passive referral income.

Interested in learning more? I can send our partner deck and set up a brief call.

[Your Name]

9.1 "It is too expensive."

Response: "I understand budget is a key consideration. Let me ask: what is the cost of not solving [problem]? [Similar Company] estimated they were losing $[amount] per month to [problem] before switching to [Product].

The [Tier Name] plan is $[price]/month. If it saves your team [X hours] or prevents [Y problem], what is that worth?

That said, if budget is truly the blocker right now, we can start with [lower tier] and upgrade when you are ready."

9.2 "We are already using [Competitor]."

Response: "Many of our best customers came from [Competitor]. What I typically hear is that [Competitor] is great for [strength], but teams struggle with [weakness].

Is [weakness] something you have experienced? If so, I would love to show you how [Product] handles that differently.

No pressure to switch — even if it is just useful to know your options."

9.3 "We need to think about it."

Response: "Absolutely — this is an important decision. To make sure I have given you everything you need, what specifically are you evaluating? Is it [factor 1], [factor 2], or something else?

Also, what is your timeline? I want to make sure I follow up at the right time without being pushy."

9.4 "We need approval from [stakeholder]."

Response: "Totally understand. Want me to put together a one-page business case that you can share with [stakeholder]? I can include ROI projections, implementation timeline, and references from similar companies.

Also, would it help if I joined a call with [stakeholder] directly to answer any technical questions?"

9.5 "We can build this in-house."

Response: "You absolutely could. Many companies consider that. What I have seen is that building in-house takes [X months] and costs $[Y] in engineering time. Plus, you own the maintenance forever.

[Product] gives you this today for $[price]/month, and we handle all the updates, security, and support.

Want to try it for 30 days? If your team prefers the in-house approach, no hard feelings."

10.1 Board Update — Growth Metrics

Opening:

"This month, we grew MRR by [X]% to $[amount]. Net Revenue Retention is [Y]%, and we added [Z] new customers. Here is what drove those results and what we are focusing on next."

Sections:

10.2 Investor Pitch — Horizontal SaaS

The Story:

"[Product] is the [category] platform for [primary segments]. We serve [X] customers across [Y] industries, with $[Z] ARR and [NRR]% net revenue retention.

The horizontal SaaS market for [category] is $[X] billion, but existing solutions are either too generic or too vertical-specific. We have built a platform that serves multiple industries while feeling purpose-built for each one.

Our growth is driven by three engines: product-led acquisition ([X]% of signups), sales-led expansion ([Y]% of revenue), and ecosystem-driven retention ([Z]% lower churn for integrated users).

We are raising $[amount] to [use of funds]."

Clozo Academy Proprietary Curriculum — The Horizontal SaaS Growth System

All scripts are frameworks. Customize with your specific product details, customer stories, and brand voice.

9.1 "It is too expensive."

Response: "I understand budget is a key consideration. Let me ask: what is the cost of not solving [problem]? [Similar Company] estimated they were losing $[amount] per month to [problem] before switching to [Product].

The [Tier Name] plan is $[price]/month. If it saves your team [X hours] or prevents [Y problem], what is that worth?

That said, if budget is truly the blocker right now, we can start with [lower tier] and upgrade when you are ready."

9.2 "We are already using [Competitor]."

Response: "Many of our best customers came from [Competitor]. What I typically hear is that [Competitor] is great for [strength], but teams struggle with [weakness].

Is [weakness] something you have experienced? If so, I would love to show you how [Product] handles that differently.

No pressure to switch — even if it is just useful to know your options."

9.3 "We need to think about it."

Response: "Absolutely — this is an important decision. To make sure I have given you everything you need, what specifically are you evaluating? Is it [factor 1], [factor 2], or something else?

Also, what is your timeline? I want to make sure I follow up at the right time without being pushy."

9.4 "We need approval from [stakeholder]."

Response: "Totally understand. Want me to put together a one-page business case that you can share with [stakeholder]? I can include ROI projections, implementation timeline, and references from similar companies.

Also, would it help if I joined a call with [stakeholder] directly to answer any technical questions?"

9.5 "We can build this in-house."

Response: "You absolutely could. Many companies consider that. What I have seen is that building in-house takes [X months] and costs $[Y] in engineering time. Plus, you own the maintenance forever.

[Product] gives you this today for $[price]/month, and we handle all the updates, security, and support.

Want to try it for 30 days? If your team prefers the in-house approach, no hard feelings."

9.6 "The setup looks too complex."

Response: "That is a fair concern. Our average customer is fully set up within [timeframe], and most of that is just connecting the tools you already use.

Here is what the typical setup looks like:

Plus, you get a dedicated onboarding specialist at [Tier Name] who walks through this with you. Would it help if I showed you a 5-minute setup video from a [industry] company just like yours?"

9.7 "We need SOC 2 / GDPR / compliance certifications."

Response: "Great question — security and compliance are non-negotiable for us. We are SOC 2 Type II certified, GDPR compliant, and support HIPAA configurations for enterprise customers.

Here is our security documentation: [link]

And our compliance overview: [link]

If your security team has specific requirements, I am happy to set up a technical call with our security lead. We have passed security reviews at [Company A], [Company B], and [Company C]. Would that be helpful?"

9.8 "The free version does enough for our needs."

Response: "I am glad the free version is delivering value! That is exactly what we designed it for. Most teams at your stage find it works well — until they hit one of these walls:

Based on your team size and usage, I estimate you will hit the [specific limit] in about [timeframe]. When that happens, the upgrade takes 2 minutes and you keep everything you have built.

Want me to send you a heads-up when you are approaching that limit?"

9.9 "Your competitor has [feature] and you do not."

Response: "You are right — [Competitor] has [feature] and we do not have that exact functionality yet. Here is what I can share:

[Option A - On roadmap]: This is actually on our roadmap for [quarter]. I can add you to the early access list.

[Option B - Workaround]: What most [industry] teams do is use [workaround] which achieves the same outcome. [Customer] uses this approach and [result].

[Option C - Not prioritizing]: We have deprioritized this because our research shows [alternative approach] actually delivers better results for [use case].

Would any of these work for your workflow?"

9.10 "We are not ready for a paid tool right now."

Response: "I hear that a lot from teams at your stage, and it makes sense. Here is what I would suggest:

Stay on the free plan for now. You get [free tier benefits] which should cover you for [estimated timeframe].

I will check in when your team hits [specific growth milestone]. At that point, the [Tier Name] plan becomes a no-brainer because [specific benefit].

In the meantime, I will send you our [industry] playbook — it is free and has some great workflows you can implement today. Sound good?"

9.11 "The contract length is too long."

Response: "I understand the preference for flexibility. Here is what we offer:

Most [industry] teams start monthly and switch to annual once they see the value. The discount alone usually covers [specific benefit].

Would monthly work better for your current situation?"

9.12 "We need SSO / SAML for our security team."

Response: "SSO and SAML are included in our [Tier Name/Enterprise] plan. We support:

Setup takes about 30 minutes with your IT team. We have a dedicated security guide and our team can walk your IT admin through the configuration.

Should I connect you with our technical team to review the setup process?"

9.13 "I need to see ROI before committing."

Response: "Absolutely — every buying decision should have a clear ROI. Let me walk you through the math:

Current State:

With [Product]:

[Customer] in [industry] saw [specific ROI result].

Want me to build a custom ROI calculator with your specific numbers?"

9.14 "Your support hours do not cover our timezone."

Response: "That is a valid concern. Here is our current support coverage:

For [Tier Name], you get priority support with [coverage hours]. Additionally, our knowledge base and community forum are available 24/7, and most questions are answered there within an hour.

If timezone coverage is critical, I can loop in our support lead to discuss custom coverage options for your team."

9.15 "The mobile app is not good enough."

Response: "I appreciate the honest feedback. Mobile is something we are actively investing in. Here is the current state and roadmap:

Current Mobile Capabilities:

Our Mobile Roadmap:

In the meantime, our web app is fully responsive and works great on tablets. [Customer] uses the web app on mobile for [use case] and has been happy with the experience.

Want me to add you to the mobile beta list?"

9.16 "We are locked into an annual contract with [Competitor]."

Response: "That makes sense — switching mid-contract rarely makes financial sense. Here is what I would suggest:

Want to start the trial now so you are ready when the contract ends?"

9.17 "Your API rate limits are too restrictive."

Response: "API limits vary by plan:

For your use case with [specific integration/workflow], [Tier Name] should handle [calculated volume] comfortably.

If you need custom limits, our enterprise team can design a plan. [Customer] processes [volume] API calls/month with their enterprise configuration.

Want me to connect you with our API team to review your specific requirements?"

9.18 "The learning curve is too steep for our team."

Response: "I get that concern. Adopting a new tool is a real investment. Here is how we make it as smooth as possible:

Onboarding:

Support:

Results:

Plus, we offer a 30-day money-back guarantee. If your team is not productive within 30 days, you get a full refund."

9.19 "We need custom integrations that do not exist."

Response: "Custom integrations are something we handle regularly. Here are your options:

Option 1: Zapier/Make Integration

Option 2: API Integration

Option 3: Professional Services

[Customer] built a custom integration with [system] in [timeframe]. Want me to set up a technical scoping call?"

9.20 "The reporting is not sophisticated enough."

Response: "Reporting needs vary by team size and use case. Here is what we offer:

Standard Reporting:

Advanced Reporting ([Tier Name]):

Custom Solutions:

Would you like to see a demo of our advanced reporting, or should I connect you with our team to discuss your specific requirements?"

9.21 "I have heard bad reviews about your product."

Response: "I appreciate you bringing that up. We take all feedback seriously. Here is what I can share:

Our Reviews:

Common Themes:

What We Have Done:

References:

Want me to set up that conversation?"

9.22 "Your uptime / reliability is a concern."

Response: "Reliability is mission-critical for us. Here are our current metrics:

Uptime:

Infrastructure:

Enterprise SLA:

You can view our real-time status and historical uptime here: [link]. Our enterprise customers receive monthly reliability reports as part of their package."

9.23 "We need multi-tenancy / workspace isolation."

Response: "Multi-tenancy and workspace isolation are core features of our platform:

Workspace Management:

Security:

Use Cases:

[Customer] manages [X] separate workspaces with [Y] total users. Would you like to see a demo of our workspace management features?"

9.24 "The onboarding requires too much manual data entry."

Response: "We have automated most of the setup process. Here is how to avoid manual entry:

Automated Import Options:

Typical Migration:

Professional Migration:

Want me to set up a migration assessment? It takes 15 minutes and we will give you a detailed migration plan."

9.25 "We need white-label / custom branding."

Response: "White-label and custom branding are available on our [Tier Name] plan:

Customization Options:

Implementation:

[Customer] in [industry] white-labeled the platform for [X users] with [specific branding].

Should I show you the branding customization options in a quick demo?"

9.26 "The team is resistant to changing tools."

Response: "Change management is real, and we have helped hundreds of teams through it. Here is our proven approach:

Phase 1: Champions First (Week 1)

Phase 2: Pilot Group (Week 2-3)

Phase 3: Full Rollout (Week 4)

Results:

Want me to share our change management playbook? It has templates for announcements, training schedules, and feedback collection."

25+ Objection Handling Scripts from The Horizontal SaaS Growth System — $997 Premium Curriculum

Copyright © Clozo Academy. All Rights Reserved.