blackroad-os-sales-playbook/05-execution/TALK_TRACKS.md

# 🎤 Talk Tracks & Sales Scripts

**PROPRIETARY & CONFIDENTIAL**

---

## Overview

**Scripts are training wheels. Master them, then improvise.**

This document provides proven talk tracks for every stage of the sales process. Use these as templates, then adapt to your style and the customer's context.

---

## Cold Outreach

### Email Template 1: Problem-Focused

**Subject:** Infrastructure bottleneck at [Company]?

**Body:**
```
Hi [Name],

I noticed [Company] is hiring 5 DevOps engineers and recently raised a Series B.
Congrats! That usually signals infrastructure is becoming a constraint.

We work with companies like [Similar Customer] to scale infrastructure without
scaling headcount. Most save $500K+/year and ship features 3x faster.

Would you be open to a 15-minute call to discuss your infrastructure challenges?

Best,
[Your Name]
BlackRoad OS
```

**Why It Works:**
- Personalized (hiring, funding round)
- Shows research
- Social proof ([Similar Customer])
- Quantified value ($500K, 3x faster)
- Low ask (15 minutes)

---

### Email Template 2: Trigger Event

**Subject:** Re: [Recent Product Launch]

**Body:**
```
Hi [Name],

Congrats on launching [Product Feature] last week! Saw the TechCrunch coverage.

Scaling new features is tough. Most companies we work with face the same challenge:
infrastructure becomes the bottleneck just when they need to move fastest.

We help companies like [Similar Customer] deploy 10x faster without hiring a
massive DevOps team. Happy to share how—15 minutes?

Best,
[Your Name]
```

**Why It Works:**
- Timely (recent news)
- Relevant (product launch = infrastructure stress)
- Social proof
- Specific value (10x faster)

---

### LinkedIn InMail Template

**Subject:** Simplifying infrastructure at [Company]

**Body:**
```
Hi [Name],

I help [Job Title]s like you eliminate infrastructure complexity so you can
focus on product instead of DevOps firefighting.

Quick question: How much time is your team spending on deployment pipelines,
scaling, and incident response vs. building features customers want?

If the answer is "too much," we should talk. Companies like [Similar Customer]
save 60% of their DevOps time using our platform.

Worth a 15-minute conversation?

Best,
[Your Name]
```

**Why It Works:**
- Empathetic (understands their pain)
- Asks a question (creates engagement)
- Quantified value (60% time savings)

---

## Discovery Call

### Opening (First 2 Minutes)

**Goal:** Build rapport, set agenda, establish credibility

**Script:**
```
"Hey [Name], thanks for taking the time today. I know you're busy, so I'll make
this valuable.

Here's what I'd like to cover in the next 20-30 minutes:
1. Learn about your current infrastructure setup and challenges
2. Understand your goals and what success looks like
3. If there's a fit, discuss next steps. If not, I'll point you to better resources.

Sound good?

Before we dive in—quick context: We work with companies like [Similar Customer 1]
and [Similar Customer 2] to simplify infrastructure management. But every company
is different, so I'd love to start by hearing about your situation.

Tell me—what's driving your interest in talking today?"
```

**Why It Works:**
- Respects their time
- Clear agenda
- Establishes credibility (customer names)
- Open-ended question (gets them talking)

---

### Discovery Questions (SPIN Framework)

#### Situation Questions
```
"Walk me through your current infrastructure setup."

"What cloud providers are you using? (AWS, Azure, GCP, multi-cloud?)"

"How many services or microservices are you running in production?"

"How big is your DevOps/infrastructure team?"

"What tools are you using for deployment, monitoring, and security?"
```

#### Problem Questions
```
"What are the biggest infrastructure challenges you're facing right now?"

"How often do deployments fail or need to be rolled back?"

"What percentage of engineering time goes to infrastructure vs. product features?"

"What keeps you up at night about your current setup?"

"If you could wave a magic wand and fix one thing about your infrastructure,
what would it be?"
```

#### Implication Questions
```
"What happens if you don't solve this in the next 6 months?"

"How does slow deployment velocity affect your ability to compete?"

"What's the cost of downtime to your business?"

"How does lack of compliance certification limit your sales opportunities?"

"What would it mean to your roadmap if you could deploy 10x faster?"
```

#### Need-Payoff Questions
```
"If you could reduce infrastructure costs by 40%, what would you do with that budget?"

"What would it be worth to achieve SOC 2 compliance 6 months faster?"

"If you could redeploy 3 DevOps engineers to product work, what's the impact?"

"How much faster could you move if deployments were automated and reliable?"
```

---

### Qualifying (BANT++)

**Budget:**
```
"Just to make sure we're aligned—what's your current annual infrastructure spend?
(Cloud bills + DevOps headcount)"

"Do you have budget allocated for infrastructure improvements, or would this need
to be justified as a new initiative?"
```

**Authority:**
```
"Who else will be involved in this decision besides you?"

"Typically, we work with the CTO, VP Engineering, and sometimes the CFO for budget
approval. Who on your side should we loop in?"
```

**Need:**
```
"On a scale of 1-10, how urgent is solving this problem? What's driving that urgency?"

"What's the business impact if this doesn't get solved?"
```

**Timeline:**
```
"When do you need this solved by?"

"What's driving that timeline? (Budget cycle, product launch, compliance deadline?)"
```

**Competition:**
```
"What alternatives are you evaluating? (AWS, Heroku, OpenShift, DIY?)"

"What do you like and dislike about each option?"
```

**Champion:**
```
"Who internally is pushing for this? Who's the strongest advocate?"

"If you could only get one person to say 'yes,' who would it be?"
```

---

### Closing the Discovery Call

**Script:**
```
"This has been super helpful. Based on what you've shared, it sounds like
[summarize pain points]:
1. [Pain point 1]
2. [Pain point 2]
3. [Pain point 3]

And your goals are [summarize desired outcomes]:
1. [Goal 1]
2. [Goal 2]

Here's what I'd recommend as next steps:

[Option A: Strong Fit]
Let's schedule a demo where I'll show you exactly how BlackRoad OS solves
[pain point 1] and [pain point 2]. I'll tailor it to your environment and
use cases. Does [specific date/time] work?

[Option B: Need More Discovery]
I'd like to bring in our Solutions Architect to do a deeper technical assessment.
We'll map out your current architecture and show you exactly how we'd optimize it.
Sound good?

[Option C: Not a Fit]
Based on what you've shared, I'm not sure we're the right fit right now. You might
be better served by [Alternative]. If things change in 6 months, happy to reconnect.

Which path makes sense to you?"
```

---

## Demo

### Demo Opening

**Script:**
```
"Before I start the demo, let me quickly recap what you told me in our discovery call:

You're struggling with [pain point 1], which is costing you [quantified impact].
Your goal is to [desired outcome] by [timeline].

Today, I'm going to show you exactly how BlackRoad OS solves these problems.
I'll cover three things:
1. [Use case 1 that addresses pain point 1]
2. [Use case 2 that addresses pain point 2]
3. [Differentiation: why us vs. alternatives you're evaluating]

I'll keep this interactive—feel free to interrupt and ask questions anytime.

Sound good? Let's dive in."
```

---

### Demo Key Moments

#### **Moment 1: The "Wow" (First 5 Minutes)**

**Script:**
```
"Let me show you something that usually takes 3 hours in AWS—and we'll do it in
3 minutes.

[Deploy an app with one click]

There. We just:
- Deployed a containerized app
- Auto-configured load balancing
- Set up SSL certificates
- Configured auto-scaling
- Integrated monitoring and logging

All in 3 minutes. How long does this take you today?"

[Let them respond—usually "hours" or "days"]

"Exactly. This is what we mean by 'enterprise-grade infrastructure without the
enterprise-grade complexity.'"
```

---

#### **Moment 2: Address Specific Pain Point**

**Script:**
```
"You mentioned deployments fail 20% of the time and you spend hours debugging.
Let me show you how we solve that.

[Show automated rollback and health checks]

Notice how the system automatically detected the failed deployment and rolled
back? No manual intervention. No pager duty at 2 AM.

This is why our customers see 90% fewer deployment failures. How would that
change your team's velocity?"
```

---

#### **Moment 3: Differentiation**

**Script:**
```
"You mentioned you're also looking at [Competitor]. Great choice—they're solid.
Here's the difference:

[Show side-by-side comparison]

With [Competitor], you'd need to manually configure [X], [Y], and [Z]. We do
that automatically.

The result? You're live in 2 weeks instead of 6 months. Does that matter for
your timeline?"
```

---

### Demo Closing

**Script:**
```
"Alright, that's the core demo. Let me recap what we covered:

1. ✅ Solved [pain point 1] with [feature]
2. ✅ Addressed [pain point 2] with [feature]
3. ✅ Showed how we're different from [competitor]

Questions before we talk next steps?

[Answer questions]

Great. Based on what you've seen, does this solve your problems?

[If yes:]
Awesome. Here's what I recommend: Let's do a 2-week pilot in your environment.
We'll migrate one of your apps, measure the results, and you'll see firsthand
how this works. If it delivers value, we scale up. If not, no hard feelings.

Sound good?

[If hesitant:]
What would you need to see to feel confident moving forward?"
```

---

## Proposal Presentation

### Proposal Walkthrough

**Script:**
```
"Thanks for giving me 30 minutes to walk through the proposal. I want to make
sure we're aligned on scope, pricing, and expected outcomes.

Here's the agenda:
1. Business case: Why this makes sense for [Company]
2. Technical solution: What we're proposing
3. Investment and ROI: What it costs and what you get
4. Next steps

Let's start with the business case.

[Page through proposal]

Right now, you're spending approximately $X/year on infrastructure:
- Cloud bills: $Y
- DevOps headcount: $Z
- Downtime/incidents: $W

Our proposal saves you $A/year through:
- 40% cloud cost reduction
- 60% DevOps time savings
- 90% fewer incidents

Total investment: $B/year
Net savings: $C/year
ROI: D%
Payback period: E months

Does that math make sense?

[Pause for questions]

Now let's talk about the technical solution..."
```

---

## Negotiation

### Price Objection: "Too Expensive"

**Script:**
```
"I appreciate you being direct. Let's talk about the total cost of ownership.

Right now, you're spending:
- $500K/year on cloud infrastructure
- $1M/year on DevOps salaries (5 engineers)
- $200K/year on downtime and incidents

Total: $1.7M/year

With BlackRoad OS:
- Cloud costs: $300K/year (40% savings via optimization)
- DevOps salaries: $400K/year (reallocate 3 engineers to product)
- Downtime: $20K/year (90% reduction)
- BlackRoad OS: $180K/year

Total: $900K/year

You're saving $800K/year. In that context, is $180K too expensive?"
```

---

### Discount Request: "Can You Do Better on Price?"

**Script:**
```
"I can work with you on pricing, but I need something in return to justify a
discount to my leadership.

Here are a few options:

1. **Longer commitment:** If you commit to 3 years instead of 1, I can get you
   25% off (saves you $45K/year).

2. **Annual prepay:** If you pay annually upfront instead of monthly, I can get
   you 15% off.

3. **Case study:** If you're willing to be a reference customer and do a case
   study, I can offer 20% off.

4. **Larger scope:** If you bring in additional teams or use cases, we can
   reduce the per-unit cost.

Which of these works for you?"
```

---

### Competitor Comparison: "Competitor X is Cheaper"

**Script:**
```
"You're right—their sticker price is lower. Let's make sure we're comparing
apples to apples.

Does [Competitor's] pricing include:
- 24/7 support?
- Compliance automation (SOC 2, HIPAA)?
- Managed services?
- Professional services for migration?

[Usually the answer is no]

When you add those in, what's their total cost?

[Walk through TCO]

Now let's compare that to our all-in pricing. What do you see?"
```

---

## Closing

### Trial Close

**Script:**
```
"Hypothetically, if we could solve [objection], is there anything else preventing
you from moving forward?"

[Uncovers hidden objections]
```

---

### Assumptive Close

**Script:**
```
"Based on everything we've discussed, it sounds like BlackRoad OS solves
[pain points] and delivers [ROI].

I'd recommend we start with a [pilot/implementation] on [timeline]. I'll send
over the contract and SOW this afternoon.

Who on your side should I include in the DocuSign?"
```

---

### Urgency Close

**Script:**
```
"If we can get this signed by [end of quarter], I can lock in:
- Current pricing (we're raising rates 10% next quarter)
- Priority onboarding (vs. 4-week wait)
- Dedicated Solutions Architect for implementation

Does that timeline work for you?"
```

---

### Binary Close

**Script:**
```
"So we have two options:

Option A: Start with a 1-year commitment at $180K/year, includes everything.

Option B: Start with Core tier at $30K/year, then upgrade to Enterprise when
you're ready.

Which makes more sense for your situation?"
```

---

## Objection Handling Quick Scripts

### "We Need to Think About It"

**Script:**
```
"Totally fair. What specifically do you need to think about? Is it:
- Budget/pricing?
- Technical fit?
- Timeline?
- Internal stakeholders?

If we can address [specific concern] right now, would that help you make a decision?"
```

---

### "We're Happy with Current Solution"

**Script:**
```
"That's great—continuity is valuable. Just curious: if you're happy, what
prompted this conversation?

[Usually reveals hidden pain]

It sounds like while [current solution] works, there's room for improvement in
[area]. Would you agree?"
```

---

### "We Don't Have Budget"

**Script:**
```
"I hear you. Most of our customers didn't have 'budget for BlackRoad OS' either.
They reallocated budget from:
- Canceled DevOps job reqs (saves $200K each)
- Reduced cloud spend (we optimize that)
- Deferred consultant fees

For example, [Customer] canceled 2 open DevOps roles and used that budget to
fund BlackRoad OS. They came out ahead.

Is there a similar opportunity here?"
```

---

## Voicemail Scripts

### Voicemail 1: First Touch

**Script:**
```
"Hi [Name], this is [Your Name] from BlackRoad OS. I help companies like
[Similar Customer] reduce infrastructure costs by 40% while shipping faster.

I'd love to share how we're doing this—might be relevant for [Company].

My number is [Phone]. I'll also send an email. Talk soon."
```

---

### Voicemail 2: Follow-Up

**Script:**
```
"Hi [Name], [Your Name] from BlackRoad OS again. I sent you an email about
simplifying infrastructure at [Company].

Quick question: How much time is your team spending on DevOps firefighting vs.
building product features?

If the answer is 'too much,' we should talk. [Phone] or reply to my email."
```

---

## Email Follow-Ups

### After Discovery Call

**Subject:** Next Steps for [Company] + BlackRoad OS

**Body:**
```
Hi [Name],

Great talking today! Here's a quick recap:

Pain Points You Shared:
- [Pain point 1]
- [Pain point 2]
- [Pain point 3]

Your Goals:
- [Goal 1]
- [Goal 2]

Next Steps:
✅ Demo scheduled for [Date/Time]
✅ I'll tailor the demo to show [specific use cases]
✅ I'll invite [Solutions Architect] to answer technical questions

Looking forward to showing you how we solve these challenges.

Best,
[Your Name]
```

---

### After Demo (Positive)

**Subject:** BlackRoad OS Demo Recap + Pilot Proposal

**Body:**
```
Hi [Name],

Thanks for the great demo conversation today! Glad to hear BlackRoad OS resonates.

Quick recap:
✅ Showed how we solve [pain point 1] with [feature]
✅ Addressed [pain point 2] with [feature]
✅ Differentiated vs. [Competitor]

Next Steps:
I've attached a proposal for a 2-week pilot. This includes:
- Migration of [App/Service]
- Hands-on support from our Solutions Architect
- Success metrics: [X, Y, Z]

If the pilot delivers value, we'll expand. If not, no hard feelings.

Available for a quick call to discuss? [Calendly link]

Best,
[Your Name]
```

---

### After Demo (Lukewarm)

**Subject:** Re: BlackRoad OS Demo - Questions?

**Body:**
```
Hi [Name],

Thanks for your time on the demo yesterday. I sensed some hesitation—totally
understandable.

Quick question: What would you need to see to feel confident moving forward?

Options:
- Deeper technical dive with our Solutions Architect?
- Reference call with [Similar Customer]?
- Custom POC tailored to your specific use case?

Happy to accommodate whatever would be most helpful.

Best,
[Your Name]
```

---

## Final Tips

### Talk Track Principles

1. **Listen 80%, Talk 20%**
   - Questions > Statements

2. **Match Their Language**
   - If they say "Kubernetes," use "Kubernetes" (not "container orchestration")

3. **Quantify Everything**
   - "40% cost savings" > "saves money"

4. **Use Stories**
   - "[Customer] had the same problem. Here's how they solved it..."

5. **Pause for Impact**
   - After key points, pause. Let them process.

6. **Confirm Understanding**
   - "Does that make sense?" "Do you see how this applies to your situation?"

---

**Version:** 1.0.0
**Last Updated:** January 4, 2026
**Owner:** Joaquin, Sales Master

*Scripts are training wheels. Master them, then make them your own.*