Complete Sales Scripts

Script 1: Technical Discovery Call Opening

Context: First call with an engineering leader who expressed interest through website or community.

Opening:

"Thanks for taking the time. Before I say anything about what we do, I would love to understand your world. Can you walk me through what your deployment pipeline looks like today? Start from when a developer commits code and follow it through to production."

Why it works: Engineers love talking about their infrastructure. Starting with their reality, not your pitch, earns the right to ask deeper questions. The deployment pipeline question reveals tools, pain points, and maturity in one answer.

Follow-up Questions:

Script 2: PQL Outbound Outreach

Context: Product Qualified Lead identified through usage signals approaching limits.

Email:

Subject: Hitting limits on [tool name]?

Hi [Name],

I noticed your team has been actively using [tool name] for [specific use case] and you are approaching your current plan limits. That is great news, it means the tool is delivering value.

I wanted to reach out personally because teams at your usage level often benefit from [specific Pro/Enterprise feature]. I have helped similar teams at [Company A] and [Company B] make the transition, and I would be happy to share what worked.

Would you be open to a brief 15-minute call this week or next? No sales pressure, just want to make sure you are getting the most from the platform.

Best,

[Name]

Why it works: References specific usage (personalized), offers value (not just asks for a sale), low time commitment, and no-pressure tone.

Script 3: Enterprise Discovery with VP Engineering

Context: First conversation with an executive-level buyer.

Opening:

"Most VP Engineering leaders I speak with are focused on three things: shipping velocity, operational reliability, and team efficiency. Which of those is keeping you up at night right now?"

Probe deeper:

Why it works: Executive buyers think in strategic frameworks, not features. Connecting to board-level concerns and financial justification speaks their language.

Script 4: The 5-Minute "Aha" Demo

Context: Live demo where you need to demonstrate value fast.

Minute 1 - Setup: "I am going to show you something that takes most teams weeks to achieve. In the next five minutes, we will go from nothing to a fully automated deployment pipeline with monitoring."

Minute 2 - Install: Run the one-line installation. Emphasize speed. "One command, thirty seconds, ready to use."

Minute 3 - Configure: Show the guided setup. "No YAML to write yet. The CLI asks what it needs to know."

Minute 4 - Deploy: Execute the first deployment. Show it working. "That just deployed to staging with automated tests, security scan, and approval gate. Your current process requires how many manual steps?"

Minute 5 - Monitor: Show the dashboard with live data. "This is the moment where most teams say 'I need this.' You can see exactly what is happening, where it is happening, and whether it is healthy."

Close: "That was five minutes. Imagine what your team builds with this running in production next week."

Script 5: Enterprise Architecture Demo

Context: Demo for platform engineering or enterprise architecture teams.

Opening: "Before I show features, let me show you architecture. How this fits into your existing stack, how it scales, and how it integrates with what you already have."

Structure:

Close: "The platform team enables the product teams. This tool was built for that exact relationship."

Script 6: "We Can Build This Ourselves"

Response: "You absolutely can. Many teams do. The question is not whether you can build it, but whether you should. We have spoken with teams who spent eighteen months building an internal deployment platform. It worked, mostly. But here is what they told us: the opportunity cost was two product features that competitors shipped first, the engineer who built it left and nobody understood the codebase, and maintaining it became a full-time job for two engineers. At $150K per engineer, that is $300K annually just in maintenance. Our enterprise plan is a fraction of that, and it improves every two weeks without any effort from your team. Building in-house makes sense for your core differentiators. Infrastructure automation is not one of them."

Script 7: "Your Tool Is Too Expensive"

Response: "I appreciate you sharing that. Let me ask: expensive compared to what? Compared to doing nothing? Compared to building internally? Or compared to the alternative you are evaluating? [Pause for answer] Here is how I think about cost: if this tool saves each of your engineers two hours per week, that is 100 hours per week for a 50-person team. At $75 per hour loaded cost, that is $7,500 per week in reclaimed engineering time. Over a year, $390,000 in value. Our Pro tier is $2,000 per month, or $24,000 per year. That is a 16x return on investment, and that is before we factor in reduced downtime or faster delivery. What would your team ship with an extra 5,000 engineering hours per year?"

Script 8: "We Are Already Using [Competitor]"

Response: "[Competitor] is a solid choice. We see them in evaluations frequently, and they serve some teams well. Can I ask what led you to choose them originally? [Listen] That makes sense. Most teams we speak with who are evaluating alternatives mention one of three things: [specific limitation], [integration gap], or [scaling issue]. Are any of those resonating with your experience? [If yes, explore. If no, ask] What would need to change for your current setup to be ideal? That gap is exactly where we should focus."

Script 9: "We Need to Wait Until Next Quarter"

Response: "I understand budget cycles. Here is what I would suggest: rather than waiting three months to start, let us run a proof of concept now with one team. No commitment, no charge until next quarter. By the time budget opens, you will have measurable results to justify the spend, and we will have accelerated your timeline by three months. What is one team or use case where we could prove value quickly?"

Script 10: "Security Won't Approve This"

Response: "That is exactly the right concern, and I am glad your security team takes this seriously. Here is what I can share today: our SOC 2 Type II report, our latest penetration test results, and our security architecture documentation. I can also connect you directly with our security team to answer any specific questions. Most security reviews clear in under a week when we provide the documentation upfront. Would it be helpful if I sent our security packet to your InfoSec team directly?"

Script 11: The Assumptive Close

Context: After a successful POC or demo with clear interest.

"Based on what we have shown and the results from your POC, it sounds like [tool name] is a strong fit for your team. Let me walk you through what getting started looks like. We can provision your production environment this week, run a team onboarding session next week, and have your first production deployment automated within ten days. Does that timeline work for you?"

Script 12: The Alternative Close

Context: When the prospect is deciding between options.

"It sounds like you are evaluating a few paths forward. Let me simplify: Option A is our Pro tier, which gets your first team up and running with everything you need for $X per month. Option B is Enterprise, which adds SSO, audit logging, and dedicated support for $Y. Based on your team size and the security requirements you mentioned, which direction feels like the better starting point?"

Script 13: The Time-Bound Close

Context: End of quarter or promotional period.

"I want to be transparent: our current pricing tier changes at the end of this month. If you sign this week, I can lock in the current rate for your first year. That saves you [specific dollar amount] annually. The product is the same either way, but the timing affects your budget. Does starting this week work for your team?"

Script 14: Cold Outreach to Engineering Managers

Subject: [Company] deployment pipeline question

Hi [Name],

I was looking at [Company]'s engineering blog post about [specific technical topic]. Impressive scale. It got me thinking about your deployment pipeline at that volume.

Quick question: how many engineer-hours per week does your team spend on deployment-related tasks, troubleshooting pipeline failures, or managing infrastructure configuration?

I am asking because we built [tool name] specifically to reclaim that time. Teams like [similar company] reduced their deployment toil by 80% in the first month.

If reclaiming 500+ engineering hours annually sounds worth a 10-minute conversation, I would love to share how.

Best,

[Name]

P.S. - No pitch on the first call. I am genuinely curious about your setup.

Script 15: Follow-Up After Demo

Subject: [Company] + [tool name] next steps

Hi [Name],

Thanks for the time today. Great conversation about your pipeline challenges.

As promised, here is what I am sending over:

I also connected you with [Customer Name] at [Similar Company] who went through a very similar evaluation six months ago. Happy to provide an intro if that would be helpful.

Let me know what questions come up as your team reviews. I am around all week.

Best,

[Name]

Script 16: Re-Engagement of Dormant Free User

Subject: Something new you might like

Hi [Name],

You signed up for [tool name] a few weeks ago but did not get a chance to fully set it up. No worries, that happens more than you would think.

I wanted to reach out because we just shipped [new feature] that addresses a common setup friction point. Instead of configuring [complex thing], you can now [simple new way].

I would love to personally walk you through getting set up. Takes 15 minutes, and I can answer any questions about your specific stack.

Worth a shot?

Best,

[Name]

Script 17: Case Study Share

Subject: How [Customer] cut MTTR from 3 hours to 12 minutes

Hi [Name],

I remembered you mentioning incident response time as a priority in our last conversation. Wanted to share a quick story:

[Customer], a [industry] company with [team size] engineers, was averaging 3 hours to resolve production incidents. After switching to [tool name] for monitoring and alerting, their mean time to recovery dropped to 12 minutes.

The key change: instead of scattered alerts across three tools, they got correlated incident timelines with automatic root cause analysis.

Full case study here: [link]

Worth discussing how something similar might work for your setup?

Best,

[Name]

Script 18: Expansion Discovery Call

Context: Quarterly business review or proactive expansion outreach to existing customer.

"Thanks for the time. Before we get into anything, how has the experience been since we got your team live? [Listen] Great to hear. Now, I wanted to discuss something: since you started with [initial use case], your engineering team has grown from [X] to [Y] engineers, and you have added [new environments/clusters]. A lot has changed. I am curious: are there other teams or use cases where what we have built for [team] could add similar value? Most of our customers who started with one team have expanded to [typical expansion pattern]. Does that align with how you are thinking about growth?"

Script 19: Environment Expansion

Context: Customer adding new production environment or region.

"Congratulations on the [new region/product launch]. That is significant growth. As you expand into [new environment], I wanted to make sure your [tool name] setup scales with you. We have environment templates that can replicate your current production configuration in about ten minutes. Would it be helpful if I walked your platform team through the multi-environment setup? Most teams find it saves a full day of configuration work."

Script 20: Team-to-Organization Standardization

Context: Champion team has succeeded, time to expand organization-wide.

"Your platform team has been using [tool name] for six months now, and the results speak for themselves: [specific metrics]. I am curious: has there been interest from other teams in getting similar capabilities? We have worked with several customers on organization-wide rollouts, and there is a specific playbook that works well. It starts with a pilot program across three teams, then scales through your internal developer platform. Would it be worth discussing what that would look like for [Company]?"

Script 21: At-Risk Intervention

Context: Health score has dropped into yellow/red territory.

"Hi [Name], I noticed your team's usage has dropped off over the past few weeks, which is unusual given how active you were initially. I wanted to reach out personally to see if something changed. Sometimes it is a team restructure, sometimes a competing priority, sometimes a feature gap. Whatever it is, I would rather understand it and see if we can help than have you silently drift away. Can you share what is going on? I am here to help, not to sell."

Script 22: Champion Departure Response

Context: Key champion has left the company.

"Hi [Name], I heard that [Champion Name] moved on to a new opportunity. First, congratulations to them. Second, I want to make sure you are set up for continued success with [tool name]. I would love to schedule a brief call with whoever is taking over [Champion Name]'s responsibilities. I can provide a quick onboarding to the current setup and make sure there is no disruption. When works for a 15-minute sync?"

Script 23: Renewal Conversation

Context: 60-90 days before annual renewal.

"Hi [Name], your annual renewal is coming up in [timeframe], and I wanted to make sure we have a chance to review the value you have gotten before any paperwork moves. Here is what our data shows: [specific metrics, usage growth, incidents prevented]. That is a strong story. I also want to check in on two things: one, are there any upcoming needs or changes we should plan for? And two, is there anything about the current setup that is not working as well as it should? My goal is to make sure the next year is even better than the last."

Script 24: Win-Back After Competitive Loss

Context: Customer churned to competitor, potential win-back opportunity.

"Hi [Name], it has been [timeframe] since [Company] moved to [Competitor]. I hope the new setup is working well for your team. I am reaching out because we have shipped some significant improvements since you left: [specific features addressing known gaps]. I am not asking you to switch back today. But if your current solution is not fully delivering on [specific expectation], I would welcome a conversation about what has changed on our end. No pressure, just an update."

Script 25: Conference Booth Engagement

Opening: "What infrastructure challenge brought you to [conference] this year?"

If they share a problem: "That is exactly the kind of problem we solve. Can I show you something in 60 seconds?"

If they are browsing: "Fair warning: we are going to try to automate something you currently do manually. Interested in seeing what?"

Close: "Here is a sticker with a QR code. Scan it, install in one command, and if you get a deployment running before the conference ends, I will buy you coffee. Deal?"

Script 26: Technical Talk Opening

Context: Conference presentation or webinar.

"I am going to tell you a story about a deployment that went wrong. Not because I want to scare you, but because I want to show you exactly why the problem is solvable. Three months ago, a team I work with pushed a configuration change at 4 PM on a Friday. By 4:15, their production API was returning 500s. By 4:30, their on-call engineer was frantically rolling back. By 5:00, they were stable, but they had lost $200,000 in transaction volume and one engineer's faith in ever leaving work on time again. The worst part? The same thing had happened three months before that. Today I am going to show you the three changes that made sure it never happened again."

Script 27: Workshop Closing

Context: End of hands-on workshop.

"In the last 90 minutes, you went from installation to a fully functional deployment pipeline. You have seen the dashboard, configured alerts, and run your first automated deployment. Here is what happens next: take this back to your team, show them what you built, and if they want the same thing, we will help you roll it out organization-wide. My email is [email]. I will follow up tomorrow with resources. And if anyone has questions right now, I am here for the next twenty minutes. Thank you for your time and attention."

Script 28: Executive Briefing

Context: Small group presentation to VP Engineering and leadership team.

"I am not going to show you features. I am going to show you numbers. Three numbers, specifically. Number one: the engineering hours your team currently spends on infrastructure toil instead of product work. Number two: the cost of downtime and deployment failures over the past year. Number three: what both of those look like twelve months from now with [tool name] in place. Everything else, features, integrations, architecture, is in service of these three numbers. Shall we begin?"

Script 29: Partner Recruitment Conversation

Context: First conversation with a potential systems integrator or technology partner.

"We are building something in the [category] space, and we have learned that the best outcomes happen when implementation partners are involved from day one. Your firm has deep expertise in [specific area], and that is exactly where our customers need the most help. Here is what I am proposing: let us co-invest in a joint solution. We provide the platform, you provide the implementation expertise, and we go to market together. I have a draft partnership proposal, but first, I want to understand what a great partnership looks like from your perspective."

Script 30: Investor Update DevOps Metrics

Context: Board meeting or investor update focused on growth metrics.

"This quarter, we hit three milestones that matter. First: net revenue retention reached 128%, which means our existing customers are expanding faster than we need to acquire new ones. That is product-market fit in numerical form. Second: average time-to-activation dropped from twelve minutes to four minutes, which directly correlates with free-to-paid conversion. Third: three enterprise deals closed through cloud marketplace co-sell, validating our partnership strategy. The revenue number is [X], but these three underlying metrics are why I am confident about [next quarter target]."

Clozo Academy Proprietary Curriculum. The DevOps Growth System.