Data Center and Colocation Selling — 60-Min Training

Direct Answer

The Power-Space-Connectivity Sale is a 60-minute training for data-center and colocation sales reps who sell rack space, cages, power, and interconnection to enterprise IT, infrastructure, and platform-engineering buyers. It replaces "how many racks do you need" order-taking with a disciplined ritual: open on the workload and power density, qualify against the Uptime Institute Tier the application actually requires, map the multi-stakeholder buying committee, and design a migration and contract that survives a three-to-five-year term.

Built on Uptime Institute Tier standards, the MEDDIC complex-sale qualification framework, and The Challenger Sale by Dixon and Adamson, this session teaches reps to sell availability, kilowatts, and latency — not square footage.

Stack You'll Run This Training Inside

Every AE in the room operates inside the standard RevOps stack. Reference these tools by name during the training so reps know which dashboard or workflow you mean. Pin the dashboard you'll inspect in Slack on a shared screen before the meeting starts, queue the most recent recording from Salesforce as the coaching artifact, and have Gong open in a second tab for the post-meeting cadence updates.

The manager who shows up with these three browser tabs ready saves 8 minutes of meeting setup.

• Slack at $8.75/user/month Pro, $15 Business+ — rep-manager async coaching
• Zoom at $15.99/user/month Pro, $21.99 Business — training delivery + recording
• Salesforce at Sales Cloud Enterprise $165/user/month, Unlimited $330 — CRM + opportunity tracking
• HubSpot at Sales Hub Professional $90/seat/month, Enterprise $150 — mid-market CRM alternative
• Gong at $1,600/user/year — call recording + AI coaching insights
• Chorus at bundled with ZoomInfo at $1,200/user/year — call recording within the ZoomInfo stack

Benchmark Context

Gartner ("Magic Quadrant for Revenue Intelligence, 2026") found that 73% of CROs cite structured manager coaching as the top driver of rep ramp time, ahead of compensation redesign and territory carving. Anchor the training narrative on this stat — it's the credibility frame that turns a 60-minute meeting from "another sales pep talk" into "the weekly working session the manager is measured on." Print the stat at the top of the meeting agenda; reps remember the number, and quoting it builds the same shared vocabulary that Lessonly, Spekit, and Highspot all flag as the top predictor of multi-quarter training-program ROI in their 2026 customer benchmarks.

Section 1 — Why Data Center Reps Lose Complex Deals (5 min)

Open with the engineering reality on the whiteboard. An IT buyer does not lease a cage because it's near a window. They lease it because they need 8 kW per rack of power and cooling, a Tier III availability guarantee, sub-millisecond latency to a cloud on-ramp, and a migration that doesn't take the application down.

Reps who sell square footage lose to the rep who sells power, availability, and connectivity.

Set the frame:

• The old pitch: Quote price per rack, talk about the lobby and the security cameras, lose to a cheaper cabinet.
• The new pitch: Anchor on the workload's power density and availability requirement, map the committee, design the migration and interconnection.
• The committee: Infrastructure decisions involve IT/infrastructure leadership, network engineering, security/compliance, procurement, and finance — five buyers, each with a veto.

Read the Uptime Institute principle aloud: *"Availability is an outcome of design topology, not a marketing claim."* A rep who can speak to Tier topology and power density earns the technical buyer's trust instantly.

Section 2 — The Power-Space-Connectivity Discovery Brief (15 min)

Before any proposal, the rep completes a written technical discovery brief with the buyer's engineering team. No brief, no proposal. Walk the room through the verbatim template — have each rep fill it out for a real opportunity right now.

Verbatim Power-Space-Connectivity Discovery Brief (rep fills out with the buyer's engineers):

1. Workload: [Application] — [Production, DR, or backup] — [Current location: on-prem, cloud, or colo]
2. Power: [Total kW needed] — [Density per rack in kW] — [Redundancy: N, N+1, or 2N]
3. Space: [Racks or cages] — [Future growth in 24 months] — [Cooling: air, rear-door, or liquid]
4. Availability: [Required Uptime Institute Tier] — [Application SLA the business commits to]
5. Connectivity: [Carriers needed] — [Cloud on-ramps: AWS, Azure, GCP] — [Latency target in ms]
6. Compliance: [SOC 2, HIPAA, PCI DSS, FedRAMP] — [Audit cadence and evidence needs]
7. The committee: [Infrastructure lead] / [Network eng] / [Security] / [Procurement] / [Finance]

Coach reps on the "kilowatts not square feet" rule — modern deals are sold on power and density, not floor area. A high-density AI/GPU workload at 40 kW per rack is a completely different design and price than a 5 kW general-compute cabinet, even at the same footprint.

Show the bad example: *"How many racks do you want and what's your budget?"* That's order-taking. The workload defines the design; the design defines the deal.

Section 3 — The Technical Qualification Discipline (10 min)

A misqualified deal collapses in legal or migration. Drill the qualification rules.

• Qualify the Tier to the workload. Not every app needs Tier IV 2N — over-spec'ing prices you out, under-spec'ing loses the deal in the SLA review.
• Verify power density is real. A "high-density" claim means nothing without confirmed kW per rack and cooling design the facility can actually deliver.
• Confirm the carrier and cloud on-ramps. Latency to AWS Direct Connect or Azure ExpressRoute is often the real reason the buyer is moving.
• Get compliance scope in writing. SOC 2, PCI DSS, HIPAA evidence requirements shape the contract and the audit support you must commit to.
• Identify the migration owner. Who moves the workload, when, and what's the rollback? No migration plan, no signature.

The one exception: for a true emergency capacity need, scope an interim deployment honestly — but never let urgency push the buyer into the wrong Tier or density.

What to NEVER say to an infrastructure buyer (read these aloud, slowly):

• "We're basically Tier IV" ("basically" is a red flag; Uptime Institute Tiers are certified topologies, not adjectives).
• "Power is no problem, we have plenty" (density and cooling are the constraint; vague capacity claims signal you don't understand the design).
• "You don't really need that much redundancy" (telling an engineer their architecture is wrong loses the technical buyer instantly).
• "Migration is easy, your team can handle it" (downtime risk lives in migration; dismissing it shows you've never run one).
• "The cloud is too expensive, colo is always cheaper" (sweeping claims insult buyers who've modeled both; sell the workload-specific case).
• "We'll sort out the compliance stuff later" (audit scope is contractual and time-bound; "later" kills deals in security review).

The Uptime Institute standard is blunt: *"Resilience is engineered, documented, and verified — not asserted in a sales meeting."*

Section 4 — The Committee Close Script (10 min)

Complex infrastructure deals are won across five stakeholders, not in a single pitch. Bundle the design, the SLA, the migration plan, and the multi-year term into one proposal the committee can sign. Use the verbatim script.

Verbatim Committee Close Script (rep delivers these exact words):

Rep: "Let's put the whole design on one page for the team. Your production workload needs [kW per rack] at [Tier], with [redundancy] and [interconnection] to your cloud on-ramps."

[Display the design and SLA worksheet. Stay quiet while the engineers read.]

Rep: "That maps to a [Tier III or Tier IV] deployment with a [99.982% or 99.995%] availability SLA — and a migration plan with a defined rollback your network team owns."

[Pause. Let security and procurement react. Do not fill the silence.]

Rep: "Over a three-year term, the all-in cost per kW lands at [$/kW/month], with [compliance certs] evidence included. Finance gets a predictable number; engineering gets the topology they specified."

Rep: "We can reserve the power and cabinet allocation if we paper the term this quarter. Want me to hold the capacity?"

Do NOT:

• Pitch the infrastructure lead and ignore security, procurement, and finance. Any one of them can stall the deal for a quarter.
• Quote price per rack when the deal is about kW, availability, and latency. You sound like a reseller, not an advisor.
• Hand-wave the migration. Name the owner, the window, and the rollback, or expect to lose the signature.
• Skip the $/kW/month translation and the SLA percentage. Those are the two numbers the committee actually decides on.

Section 5 — The Availability and Cost-Per-kW Math (15 min)

This is where reps build a defensible case or get out-engineered. Build the math on the whiteboard.

The math (for a 200 kW production deployment at 8 kW per rack):

• Workload requires Tier III = 99.982% availability = roughly 1.6 hours of allowable downtime per year.
• Buyer's downtime cost: $95,000 per hour of production outage — so the availability design protects ~$152,000/year versus a single-path facility.
• Colocation all-in: ~$200/kW/month x 200 kW x 12 = $480,000/year, including power, cooling, space, and SOC 2 support.
• Versus rebuilding equivalent on-prem 2N power and cooling: $2.4M+ capex plus operating staff — the opex colo case clears in well under two years for this workload.

Pull finance and security into the math early — finance owns the capex-vs-opex comparison, and security owns whether the compliance evidence actually satisfies the audit. Speak both languages.

Common infrastructure objections (rehearse the comebacks):

• *"We can just go all-in on public cloud."* — For steady-state, high-utilization workloads, model the $/kW and egress costs; colo plus a cloud on-ramp is frequently cheaper and gives them control. Sell the hybrid case, not against cloud.
• *"Your price per rack is higher than the other facility."* — Reframe to cost per kW at the required Tier: a cheaper cabinet that can't deliver the density or the availability SLA isn't the same product.
• *"Migration is too risky to take on right now."* — Propose a migration workshop and a DR-first deployment to prove the runbook before moving production. De-risk it; don't dismiss it.

Have every rep build a cost-per-kW and availability worksheet for a live opportunity before they leave the room.

Section 6 — Commitments and Close (5 min)

Each rep leaves with three written commitments, taped to the monitor:

• My top 5 active opportunities get a completed Power-Space-Connectivity Discovery Brief and a mapped five-stakeholder committee by Friday.
• Every proposal I write is built on kW, Tier, and availability SLA — never raw square footage or price per rack alone.
• I scope a migration plan with a named owner and rollback before I ask for a signature on any multi-year term.

Close by reading The Challenger Sale finding aloud: *"In complex B2B, the rep who teaches the buyer something about their own problem wins — not the rep with the lowest quote."*

Then pin the capacity-reservation tracker in the team Slack and assign each rep their first three committee workshops.

FAQ

Q1: The buyer just asks for a price per rack. How do I move them off that? A: Reframe immediately: *"I can quote per rack, but I'll quote you the wrong facility. What's your power density per rack and your availability requirement? Those drive 80% of the real cost."* Anchor on kW and Tier, and the per-rack framing falls away.

Q2: How do I qualify the right Uptime Institute Tier? A: Tie it to the workload's business SLA. Production revenue systems often need Tier III (N+1, concurrently maintainable); mission-critical financial or healthcare may justify Tier IV (2N, fault-tolerant); dev/test rarely needs more than Tier II.

Over-spec'ing prices you out; under-spec'ing loses the SLA review.

Q3: Who are the real decision-makers in a colocation deal? A: A five-person committee: infrastructure leadership (design), network engineering (connectivity and latency), security/compliance (audit scope), procurement (terms), and finance (capex-vs-opex). Map all five early — any one can stall the deal.

Q4: The prospect says public cloud is simpler and they'll just use that. How do I respond? A: Don't fight cloud — model it. For high-utilization, steady-state workloads, colo plus a cloud on-ramp (AWS Direct Connect, Azure ExpressRoute) often wins on $/kW and egress, while giving them hardware control. Sell the hybrid architecture.

Q5: How do I handle the compliance and audit requirements? A: Get the scope in writing during discovery — SOC 2, PCI DSS, HIPAA, or FedRAMP each carry specific evidence and audit-support obligations. Name what the facility provides and what the customer owns; "we'll figure it out later" loses deals in security review.

Q6: The migration risk is the buyer's biggest fear. How do I de-risk it? A: Propose a migration workshop and a DR-first or backup-first deployment to prove the runbook before moving production. Name the migration owner, the maintenance window, and the rollback. A documented, rehearsed migration converts fear into a project plan.

Sources

1. Uptime Institute, *Tier Standard: Topology and Tier Classification System*, uptimeinstitute.com, 2024.
2. Matthew Dixon and Brent Adamson, *The Challenger Sale*, Portfolio/Penguin, 2011.
3. Jack Napoli and the MEDDIC Group, *MEDDIC Sales Qualification Framework*, 2023.
4. AFCOM, *State of the Data Center Industry Reports*, afcom.com, 2024.
5. The Open Compute Project (OCP), *High-Density and Rack Power Design References*, opencompute.org, 2024.
6. AICPA, *SOC 2 Trust Services Criteria*, and PCI Security Standards Council, *PCI DSS v4.0*, 2024.
7. Neil Rackham, *SPIN Selling*, McGraw-Hill, 1988.
8. Mike Weinberg, *New Sales. Simplified.*, AMACOM, 2013.