# 🔄 The BlackRoad Sales Process

**PROPRIETARY & CONFIDENTIAL**

---

## Overview

The BlackRoad Sales Process is a **7-stage methodology** optimized for complex B2B infrastructure sales.

It's based on proven frameworks (MEDDIC, Challenger Sale, SPIN Selling) but customized for our market, product, and customer.

**Process Duration:**
- SMB (Core): 30-60 days
- Mid-Market (Enterprise): 60-120 days
- Enterprise (Custom): 120-180 days

---

## The 7 Stages

```
1. PROSPECT → 2. QUALIFY → 3. DISCOVER → 4. PRESENT → 5. PROPOSE → 6. NEGOTIATE → 7. CLOSE
    ↓            ↓            ↓            ↓            ↓              ↓              ↓
  Identify    Validate    Understand   Demonstrate   Formalize     Finalize      Win &
  Potential    Fit &      Pain &        Value &       Solution &    Terms &     Onboard
  Customers   Urgency    Requirements   ROI          Pricing      Contract    Customer
```

**Key Principle:**
Each stage has **entry criteria** (what must be true to enter) and **exit criteria** (what must be achieved to advance).

Never skip stages. Shortcuts = longer sales cycles.

---

## Stage 1: PROSPECT

**Objective:** Identify and engage potential customers

### Entry Criteria:
- None (this is the starting point)

### Activities:
- **Outbound:** Cold email, LinkedIn outreach, calling
- **Inbound:** Respond to demo requests, content downloads, website inquiries
- **Referrals:** Warm introductions from customers, partners, investors
- **Events:** Trade shows, webinars, conferences

### Key Questions:
- Is this company in our ICP (Ideal Customer Profile)?
- Do they have the pain points we solve?
- Can we get to a decision-maker?

### Exit Criteria:
✅ Initial contact established (email reply, meeting booked, or intro call scheduled)
✅ Basic qualification: Right company size, industry, and tech stack

### Tools:
- **CRM:** HubSpot for lead tracking
- **Outreach:** Outreach.io, SalesLoft, or Apollo
- **Research:** LinkedIn Sales Navigator, Clearbit, ZoomInfo

### Metrics:
- Outreach volume: 30-50 touches/day
- Response rate: 5-10%
- Meeting-booked rate: 2-5%

**Pro Tip:**
Personalization matters. Generic outreach gets ignored. Reference something specific (recent funding, job posting, tech stack, industry news).

**Example Outreach:**
> Subject: Infrastructure for [Company's Recent Product Launch]
>
> Hi [Name],
>
> Congrats on the Series B and the new AI features you just announced! I noticed you're hiring 5 DevOps engineers—sounds like infrastructure is becoming a bottleneck.
>
> We work with companies like [Similar Customer] to scale infrastructure without scaling headcount. Would you be open to a 15-minute call to discuss your architecture challenges?
>
> Best,
> [Your Name]

---

## Stage 2: QUALIFY

**Objective:** Determine if there's a real opportunity worth pursuing

### Entry Criteria:
✅ Initial contact established
✅ Discovery call scheduled

### Activities:
- **First Call:** 20-30 minute qualification conversation
- **Research:** Review their website, tech stack, recent news
- **Stakeholder Mapping:** Identify decision-makers and influencers

### Framework: BANT++

We use an enhanced version of BANT:

| Criteria | Question | What You're Looking For |
|----------|----------|-------------------------|
| **Budget** | "What's your current infrastructure spend?" | >$100K/year (SMB) or >$500K/year (ENT) |
| **Authority** | "Who else will be involved in this decision?" | Access to economic buyer (VP, CTO, CFO) |
| **Need** | "What's the business impact of this problem?" | Clear, urgent pain (not nice-to-have) |
| **Timeline** | "When do you need this solved?" | <6 months (ideally <3 months) |
| **+Competition** | "What alternatives are you evaluating?" | Understand competitive landscape |
| **+Champion** | "Who internally is pushing for this?" | Identify internal advocate |

### Exit Criteria:
✅ All BANT++ criteria met (or clear path to meet them)
✅ Pain is urgent and quantifiable
✅ Decision-maker identified and accessible
✅ Timeline is realistic (<6 months)

### Red Flags (Disqualify):
- 🚩 No budget or unwilling to discuss
- 🚩 Can't get to decision-maker
- 🚩 "Just researching" with no timeline
- 🚩 Unrealistic expectations (want enterprise features on SMB budget)
- 🚩 Bad fit for product (e.g., non-technical company, too small)

**When to Walk Away:**
If 2+ red flags persist after 2-3 conversations, **politely disengage.**

**Example Disqualification:**
> "Based on what you've shared, it sounds like [our solution] might be over-engineered for your current needs. I'd recommend starting with [simpler alternative]. If your requirements change in the future, happy to reconnect. Best of luck!"

---

## Stage 3: DISCOVER

**Objective:** Deeply understand the customer's pain, requirements, and desired outcomes

### Entry Criteria:
✅ Opportunity is qualified (BANT++ met)
✅ Discovery call scheduled with key stakeholders

### Activities:
- **Deep-dive discovery calls** (1-2 hours with technical and business stakeholders)
- **Technical assessment:** Review current architecture, pain points, constraints
- **Business case development:** Quantify cost of problem and value of solution

### The SPIN Discovery Framework

#### 1. Situation Questions
*Understand their current state*

- "Walk me through your current infrastructure setup."
- "What tools are you using today for deployment, monitoring, and security?"
- "How many engineers do you have focused on DevOps/infrastructure?"
- "What cloud providers are you on? (AWS, Azure, GCP, multi-cloud?)"

#### 2. Problem Questions
*Identify pain points*

- "What are the biggest infrastructure challenges you're facing?"
- "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?"

#### 3. Implication Questions
*Explore consequences of inaction*

- "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 or outages to your business?"
- "How does lack of compliance certification limit your sales opportunities?"

#### 4. Need-Payoff Questions
*Quantify value of solving*

- "If you could reduce deployment time by 60%, what would that enable?"
- "What would it be worth to achieve SOC 2 compliance 3 months faster?"
- "If you could redeploy 3 DevOps engineers to product work, what's the revenue impact?"
- "How much would you save if infrastructure costs dropped 40%?"

### Technical Discovery Checklist

Gather this information:
- [ ] Current architecture diagram
- [ ] Tech stack (languages, frameworks, databases)
- [ ] Deployment frequency and process
- [ ] Current cloud spend (monthly/annual)
- [ ] Team size and composition
- [ ] Compliance/security requirements
- [ ] Integration requirements
- [ ] Pain points (ranked by severity)

### Exit Criteria:
✅ Comprehensive understanding of technical requirements
✅ Quantified business case (cost of problem, value of solution)
✅ Stakeholder map complete (decision-makers, influencers, users)
✅ Success criteria defined (what does "winning" look like?)
✅ Customer agrees to next step (demo or POC)

**Pro Tip:**
The best discovery calls feel like **consulting sessions**, not sales pitches. You're diagnosing before prescribing.

**Document Everything:**
Use a discovery template in your CRM. You'll need these details for proposals, demos, and internal alignment.

---

## Stage 4: PRESENT (Demo)

**Objective:** Demonstrate how BlackRoad OS solves their specific problems

### Entry Criteria:
✅ Discovery complete
✅ Demo scheduled with key stakeholders (technical + business)

### Demo Best Practices

#### Before the Demo:
1. **Customize the demo** based on discovery insights
2. **Use their data** (if possible and permissible)
3. **Prepare success criteria** (what does a good demo look like to them?)
4. **Invite a Solutions Engineer** for technical depth

#### During the Demo:
1. **Start with a story:** "You mentioned X problem. Let me show you how we solve that."
2. **Show, don't tell:** Live demos beat slides 10:1
3. **Keep it interactive:** Ask questions, pause for feedback
4. **Focus on outcomes:** Not "here's a feature" but "here's how this saves you 20 hours/week"
5. **Handle objections in real-time:** Don't defer tough questions

#### Demo Flow (60 minutes):
- **0-5 min:** Recap discovery and set agenda
- **5-10 min:** High-level overview (what is BlackRoad OS?)
- **10-40 min:** Live demo tailored to their use cases
  - Use case 1: Solve pain point #1
  - Use case 2: Solve pain point #2
  - Use case 3: Differentiation (why us vs. alternatives)
- **40-50 min:** Technical deep-dive (SE leads)
- **50-60 min:** Q&A, next steps, and call to action

#### After the Demo:
1. **Send follow-up email within 2 hours**
   - Recap what was shown
   - Address unanswered questions
   - Propose next steps (POC, proposal, reference call)
2. **Update CRM** with demo feedback and objections
3. **Internal debrief** with SE on what went well/poorly

### Exit Criteria:
✅ Customer sees clear value in BlackRoad OS
✅ Technical objections addressed (or path to address)
✅ Agreement on next step (POC, proposal, or contract discussion)

**Red Flag:**
If customer is unresponsive after demo, they're not interested. Follow up 2-3 times, then move on.

---

## Stage 5: PROPOSE

**Objective:** Formalize the solution, scope, and pricing in a written proposal

### Entry Criteria:
✅ Successful demo with positive feedback
✅ Customer requests proposal or pricing

### Proposal Structure

**1. Executive Summary** (1 page)
- Their pain points (from discovery)
- Proposed solution overview
- Expected outcomes (quantified ROI)
- Investment summary (pricing)

**2. Business Case** (1-2 pages)
- Current state (cost of problem)
- Future state (value of solution)
- ROI calculation (payback period, NPV, etc.)

**3. Technical Solution** (2-3 pages)
- Architecture overview
- Implementation plan (phases, timeline)
- Integration points
- Success metrics

**4. Pricing & Investment** (1 page)
- Platform subscription (monthly/annual)
- Professional services (if needed)
- Managed services (if applicable)
- Total investment (Year 1, Year 2, Year 3)

**5. Terms & Conditions** (1 page)
- Contract length (1-year, 3-year)
- Payment terms (annual prepay vs. monthly)
- SLA and support commitments
- Renewal terms

**6. Next Steps** (1/2 page)
- Timeline for decision
- Implementation kickoff date
- Mutual action plan

### Proposal Best Practices

- ✅ **Personalized:** Include their company name, logo, and specific pain points
- ✅ **Concise:** 5-8 pages max (not 50-page novels)
- ✅ **Visual:** Use diagrams, charts, and graphics
- ✅ **Outcome-focused:** Emphasize results, not features
- ✅ **Clear pricing:** No hidden fees or confusing line items

### Exit Criteria:
✅ Proposal delivered
✅ Customer confirms receipt and review timeline
✅ Follow-up meeting scheduled to discuss

**Pro Tip:**
Present the proposal live (via screen share) rather than just emailing it. Walk them through it, address questions in real-time, and advance to negotiation immediately.

---

## Stage 6: NEGOTIATE

**Objective:** Align on terms, pricing, and contract structure

### Entry Criteria:
✅ Proposal delivered and reviewed
✅ Customer expresses intent to move forward (verbally or in writing)

### Common Negotiation Points

| Customer Request | Our Response |
|------------------|--------------|
| **"Can you discount 20%?"** | "Let's discuss scope. What if we adjust [X feature] or extend payment terms?" |
| **"We need net-60 payment terms"** | "We can do that for annual prepay contracts. Monthly billing requires net-30." |
| **"Can we do a shorter commitment?"** | "1-year is our minimum for custom implementation. We can do month-to-month for self-service Core tier." |
| **"We need this feature"** | "That's on our roadmap for Q3. We can prioritize if you commit to a 3-year contract." |
| **"Competitor X is 30% cheaper"** | "Let's compare apples to apples. Do they include [Y and Z]? Our TCO is lower when you factor in..." |

### Negotiation Principles

1. **Never discount without getting something in return**
   - Longer commitment (3-year vs. 1-year)
   - Larger scope (more users, more features)
   - Prepayment (annual vs. monthly)
   - Case study / reference customer

2. **Anchor on value, not price**
   - "At $180K/year, you're saving $500K in infrastructure costs. That's 65% ROI."

3. **Know your walk-away point**
   - Don't do deals that set bad precedents
   - Consult sales leadership for approval on >20% discounts

4. **Use time as leverage**
   - "If we can close by end of quarter, I can get approval for [X]."

5. **Get legal and procurement involved early**
   - "Let's get our legal teams connected now so we don't delay later."

### Exit Criteria:
✅ Verbal agreement on pricing and terms
✅ Redlined contract sent to legal
✅ Signatures in progress (DocuSign, PandaDoc)

---

## Stage 7: CLOSE

**Objective:** Execute the contract and transition to Customer Success

### Entry Criteria:
✅ Contracts signed by both parties
✅ Payment received (or PO issued)

### Closing Checklist

- [ ] Contracts fully executed (both parties signed)
- [ ] Payment processed (initial invoice paid or PO confirmed)
- [ ] CRM updated (deal marked as "Closed-Won")
- [ ] Internal kickoff scheduled (Sales → CS handoff)
- [ ] Customer kickoff scheduled (onboarding call)
- [ ] Welcome email sent with next steps
- [ ] Implementation timeline confirmed

### Post-Close Activities

#### 1. Celebrate (Internally)
- Post win in `#sales-wins` Slack channel
- Share learnings with team (what worked well?)
- Update quota attainment

#### 2. Smooth Handoff to Customer Success
- **Handoff Document:** Include discovery notes, customer goals, technical requirements
- **Intro Call:** Sales rep introduces Customer Success Manager (CSM)
- **Set Expectations:** CSM owns relationship from here

#### 3. Ask for Referrals
- "Who else do you know with similar infrastructure challenges?"
- Warm introductions are 10x easier than cold outreach

### Exit Criteria:
✅ Customer successfully onboarded
✅ First milestone achieved (e.g., first deployment)
✅ Customer NPS survey sent (measure satisfaction)

**Deal is done. Relationship is just beginning.**

---

## Sales Velocity Metrics

**Goal:** Optimize time-to-close without sacrificing quality.

| Stage | Target Duration | Key Activities |
|-------|----------------|----------------|
| **1. Prospect** | 1-7 days | Outreach, initial contact |
| **2. Qualify** | 1-3 days | First call, BANT++ assessment |
| **3. Discover** | 1-2 weeks | Deep-dive discovery, stakeholder interviews |
| **4. Present** | 1 week | Demo prep, demo delivery, follow-up |
| **5. Propose** | 3-7 days | Proposal creation, delivery, review |
| **6. Negotiate** | 1-3 weeks | Negotiate terms, legal review, redlines |
| **7. Close** | 3-7 days | Signatures, payment, onboarding |

**Total: 30-60 days (SMB), 60-120 days (Mid-Market), 120-180 days (Enterprise)**

---

## Common Pitfalls & How to Avoid Them

### Pitfall 1: Skipping Discovery
**Symptom:** Demos that don't resonate, proposals that miss the mark
**Fix:** Never demo before thorough discovery

### Pitfall 2: Single-Threading (Only One Champion)
**Symptom:** Deal dies when champion leaves or loses influence
**Fix:** Build relationships with 3+ stakeholders (technical, business, executive)

### Pitfall 3: Weak Business Case
**Symptom:** Customer says "We'll think about it" and ghosts
**Fix:** Quantify ROI. "Think about it" = "I don't see the value."

### Pitfall 4: Premature Discounting
**Symptom:** Give discounts too early, then have no leverage in negotiation
**Fix:** Anchor on value. Only discount in exchange for concessions.

### Pitfall 5: Slow Follow-Up
**Symptom:** Deals stall because you didn't respond fast enough
**Fix:** Respond to customer inquiries within 4 hours (ideally <1 hour)

---

## Tools & Resources

**CRM:** HubSpot (track all activities and pipeline)
**Demo Environment:** staging.blackroad.io
**Proposal Tool:** PandaDoc, DocuSign
**Call Recording:** Gong, Chorus (for coaching and analysis)
**Competitive Intel:** Klue, Crayon
**Calendar:** Calendly (easy scheduling)

---

## Sales Process FAQs

**Q: Can I skip the qualification stage if the deal is inbound?**
A: No. Inbound leads still need to be qualified. "Inbound" ≠ "good fit."

**Q: What if the customer wants to skip the demo and go straight to pricing?**
A: Push back gently. "Happy to share pricing, but I want to make sure we're proposing the right solution for your needs. Can we do a 30-minute discovery call first?"

**Q: How do I handle a stalled deal?**
A: Send a "break-up email":
> "Hi [Name], I haven't heard back after our last conversation. It sounds like this might not be a priority right now, which I totally understand. If that's the case, no worries—I'll close out this opportunity. If timing changes, happy to reconnect. Let me know either way!"

Often, this re-engages the customer.

**Q: What's the typical win rate?**
A: Target >40% for qualified opportunities. If you're below 30%, you're either qualifying poorly or losing on value.

---

## Final Thoughts

The sales process is **not rigid**. Adapt it to the customer.

Some deals will move faster (inbound, strong urgency).
Some will move slower (enterprise, complex stakeholders).

**But don't skip stages.**

Discovery → Demo → Proposal → Close is the proven path.

---

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

*Master the process. Adapt to the customer. Close the deal.*