Sales Playbook · Telecom
Built to let the product sell itself.
Pain, proof, workflow, ROI, pilot, expansion. Each persona has a specific hook tied to the buyer's job risk — not just a list of features.
Buyer Personas
🏢
COO / Operations
Pain: Margin erosion from rework, duplicate work, and disconnected handoffs.
Hook: AI-assisted QC gates + PM approval controls protect actualized margin from estimate to closeout.
⚙️
VP Engineering
Pain: Engineering and field teams operate in silos — no traceable handoff.
Hook: One workflow spanning desk and field: QC gates, PM review queue, and traceable department approvals.
🏗️
Construction Director
Pain: Crew mobilization happens before design or permits are fully resolved.
Hook: Phase-gating blocks construction release until engineering, permits, and QC are approved.
🏛️
Public Works Director
Pain: Council needs cross-utility status without mixing utility data models.
Hook: Portfolio dashboard with per-utility drill-down, grant tracking, and council-ready reports.
💼
Investor / Buyer
Pain: No recurring platform moat — just another spreadsheet workaround.
Hook: SaaS lease model: per-vertical, per-seat, per-connector. ARR grows with each new utility or project type.
6-Step Sequence: Discovery → Lease
01
Identify utility vertical(s)
Match the buyer's operating context to the correct vertical data model and talk track.
02
Run Discovery question bank
Use the Discovery module to scope pain, urgency, team size, integrations, and compliance need.
03
Send Pitch + Deep Dive
Per-vertical pitch deck content, pricing lanes, buyer profile, and value drivers.
04
Demo live workflow
Dashboard → Tracker → QC gate → Estimator → ROI. 20 minutes max.
05
Issue Pilot SOW
30-day deployment sprint. Paid pilot. One real project. Clear acceptance criteria.
06
Convert to annual lease
ROI report with real numbers. Conversion proposal. Hand off to annual platform lease.
Cold Email Templates — Telecom
Email 1
Pain-point opener
Subject: Reducing Telecom project rework with an AI command center Hi [Name], Most Telecom teams are managing Telecom delivery across 3–5 disconnected tools — and rework usually surfaces after crew mobilization, which is the most expensive place to find it. El1te AIO v1 puts the full lifecycle — planning, QC gates, PM approvals, actuals, invoicing, and closeout — in one controlled workflow. Worth 20 minutes to see how it maps to your current process? [Your name]
Email 2
Pilot offer
Subject: 30-day pilot to prove Telecom delivery control Hi [Name], We're offering a structured 30-day pilot for one Telecom project team — no enterprise contract required upfront. You get: full workflow, QC gates, PM review queue, estimator, alerts, and closeout readiness — scoped to your project type. We cover setup and onboarding. You validate the ROI on a real project. Interested in scoping a pilot? [Your name]
Email 3
ROI proof follow-up
Subject: Follow-up: Telecom ROI numbers from our model Hi [Name], Based on typical Telecom project volumes, our ROI model shows: • 25–45% reduction in PM reporting time • 15–30% rework cost reduction via QC gate blocking • Platform payback in 4–8 months at mid-market scale I can share the full model scoped to your team size, project count, and utility type. Would that be useful? [Your name]