# Sales Enablement

> Sales enablement skill for Teqfocus — a Salesforce Summit Partner and full-stack Data, AI, and Application transformation company. Use this skill whenever the user wants to create any asset that helps the sales team sell more effectively or move deals forward. This includes: sales decks, vertical pitch decks, one-pagers, battlecards, competitive positioning guides, objection-handling guides, discovery question frameworks, proposal templates, case study sell sheets, SDR call scripts, and meeting follow-up templates. Also trigger when the user mentions sales collateral, deal support, pitch preparation, competitive intel, handling objections, or building a sales kit. Always use this skill before writing any Teqfocus sales enablement asset — do not attempt from memory alone.

- Skill: `teqfocusadmin/sales-enablement` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add teqfocusadmin/sales-enablement`
- Raw SKILL.md: https://api.skillmd.com/api/skills/teqfocusadmin/sales-enablement/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: TeqfocusAdmin (https://skillmd.com/u/teqfocusadmin)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/teqfocusadmin/sales-enablement

---


# Teqfocus Sales Enablement Skill

This skill governs all sales enablement asset creation for Teqfocus. Every asset must be built for a specific persona, a specific stage in the sales cycle, and ready to use — not require significant editing before it goes in front of a prospect.

## How to Use This Skill

1. **Read this SKILL.md fully** before producing any asset
2. **Identify the asset type** → load the relevant reference file
3. **Confirm the Brief** using Section 5 before writing
4. **Deliver complete, ready-to-use assets** — copy, structure, design flags, all included

## Reference Files

| Asset Type | Reference File |
|---|---|
| Sales Deck / Vertical Pitch Deck | `references/sales-deck.md` |
| One-Pager (Persona / Industry / Service Line) | `references/one-pager.md` |
| Battlecard (Competitive Positioning) | `references/battlecard.md` |
| Objection-Handling Guide | `references/objection-handling.md` |
| Discovery Question Framework | `references/discovery-questions.md` |
| SDR Call Script / Meeting Opener | `references/sdr-scripts.md` |
| Proposal / SOW Narrative | `references/proposal-narrative.md` |

---

## Section 1: Teqfocus Company Identity

### Who Teqfocus Is
Teqfocus is a **digital transformation partner** for enterprises and mid-market companies — operating across the **Data, Analytics, AI, and Application layers** on a modern multi-cloud architecture. Technology-agnostic in approach, outcomes-obsessed in delivery.

**Core Positioning Statement:**
> *"Teqfocus helps enterprises transform across the Data, Analytics, AI, and Application layer — powered by a multi-cloud architecture built on Salesforce, Snowflake, AWS/Azure/GCP, Databricks, and Tableau. We bring deep industry vertical expertise so every engagement starts with your problem, not our platform."*

### Partnership Credentials
| Partner | Status |
|---|---|
| **Salesforce** | **Summit Partner** — top tier of the global Salesforce partner ecosystem |
| **Snowflake** | Partner |
| **AWS / Azure / GCP** | Cloud Partners |
| **Databricks** | Partner |
| **Tableau / CRM Analytics** | Partner |

> ⚠️ **Credential Rule:** Summit Partnership is an established, long-standing credential. Never say "recently achieved" or imply it is new. Frame it as risk reduction — not a badge.

### Service Lines
Data & Analytics · AI & Machine Learning · Salesforce Transformation · Cloud Infrastructure · Custom App Development · Managed Services / AMS

### Industries
Healthcare · Telecom · Financial Services · Retail / CPG · Hi-Tech / SaaS

---

## Section 2: The Multi-Cloud Competitive Story

This is Teqfocus' core differentiator in sales conversations. Use it deliberately.

**The Problem With Competitors:**
Most enterprise technology problems are architecture problems — not platform problems. Data lives in silos. AI stalls because the foundation isn't ready. Salesforce underperforms because it isn't connected to where data actually lives.

**Single-Layer Partners fail here:**
- Salesforce-only SIs: Don't touch the data layer. Leave the client coordinating 3 vendors.
- Pure-play data firms: Don't connect to the application layer where teams actually work.
- Big 4 / Global SIs: Generalist coverage, premium billing rates, ramp-up at client expense.
- Offshore IT vendors: Delivery shops, not strategic partners. No Summit credentials, no industry IP.

**Teqfocus wins by owning the full chain:**
Data infrastructure (Snowflake, Databricks, cloud) → Intelligence layer (AI/ML, analytics) → Application layer (Salesforce, custom apps) — as one integrated partner with one throat to grab.

### Competitive Language That Works
| Against | Use This |
|---|---|
| Big 4 / Global SIs | "We go deeper on Salesforce and data — and we don't bill you for ramping up on platforms we've built on for years." |
| Salesforce-only SIs | "We go beyond the CRM. If your data isn't ready, your Salesforce investment isn't either. We fix both." |
| Pure-play data firms | "We don't stop at the pipeline. We connect data to the applications your business runs on — and build the AI layer in between." |
| Offshore IT vendors | "We're a strategic partner with Summit credentials, industry IP, and accountability for outcomes — not hours." |
| Internal teams | "We accelerate what your internal team can't prioritize — and leave them with something they can maintain." |

---

## Section 3: Buyer Personas — Sales Entry Points

### CIO / CTO (Enterprise)
- **Fear:** Another transformation that underdelivers; integration debt; AI without a foundation
- **Sales Entry Point:** Risk reduction + architecture credibility + Summit credential
- **Discovery Angle:** Where did your last major transformation stall? What does your current integration architecture look like?
- **Proof to Use:** Phased delivery, architecture stability, Summit credential as de-risker
- **Buying Trigger:** Failed project, AI board mandate, M&A integration, cloud migration stall
- **Deal Size:** Large — enterprise transformation, multi-phase
- **Champion Profile:** VP of IT, Enterprise Architect, or CTO reporting to CIO

### CDO / Head of Data & AI
- **Fear:** AI the business doesn't trust; data strategy without adoption; failed POC
- **Sales Entry Point:** Data maturity + AI readiness framework
- **Discovery Angle:** Where is your AI initiative today — and what's slowing it down?
- **Proof to Use:** Data Cloud + Databricks + Snowflake implementation outcomes
- **Buying Trigger:** Failed AI POC, Data Cloud mandate, CEO pressure on AI ROI
- **Deal Size:** Large to mid — data platform + AI layer
- **Champion Profile:** Data Engineering lead, AI/ML team lead, Analytics director

### RevOps / Ops Leader (Mid-Market)
- **Fear:** Salesforce nobody uses; customization that breaks; manual forecasting
- **Sales Entry Point:** Speed + practical CRM outcomes in 90 days
- **Discovery Angle:** What does your current Salesforce adoption look like? What's your team doing outside of Salesforce that should be inside it?
- **Proof to Use:** CRM adoption rate improvement, forecast accuracy, 90-day delivery
- **Buying Trigger:** Salesforce renewal, new VP of Sales, growth breaking process
- **Deal Size:** Mid — Salesforce optimization, AMS
- **Champion Profile:** RevOps manager, Sales Ops director, CRM admin lead

### VP of Sales / Revenue Leader
- **Fear:** Salesforce as an expensive CRM nobody uses; missed quarters; no pipeline visibility
- **Sales Entry Point:** Revenue impact + pipeline visibility
- **Discovery Angle:** How confident are you in your current forecast? What's the biggest thing slowing your sales team down?
- **Proof to Use:** Pipeline visibility improvement, sales cycle compression, Agentforce automation
- **Buying Trigger:** Missed quarters, manual forecasting, new sales motion (PLG, partner, expansion)
- **Deal Size:** Mid — Sales Cloud, Revenue Intelligence, Agentforce
- **Champion Profile:** VP Sales, Chief Revenue Officer

---

## Section 4: Sales Cycle Stages & Asset Map

Match every asset to the right stage. The wrong asset at the wrong time loses deals.

| Stage | What the Buyer Needs | Right Assets |
|---|---|---|
| **Awareness** | To recognize they have a problem worth solving | One-pager, LinkedIn post, thought leadership blog |
| **Consideration** | To understand their options and evaluate approaches | Sales deck, battlecard, vertical deck, case study |
| **Evaluation** | To de-risk the choice and justify internally | Detailed case study, proposal narrative, objection-handling guide, reference stories |
| **Decision** | To get internal buy-in and sign | Proposal narrative, exec summary one-pager, ROI framing |
| **Post-Sale** | To ensure adoption and expand | AMS pitch, expansion one-pager, QBR deck |

---

## Section 5: Sales Enablement Brief Intake Checklist

**Confirm before writing any sales asset:**

- [ ] **Asset Type** — Deck, one-pager, battlecard, objection guide, discovery framework, proposal?
- [ ] **Target Persona** — CIO/CTO, CDO, RevOps, VP Sales?
- [ ] **Industry Vertical** — Healthcare, Telecom, FinServ, Retail, Hi-Tech?
- [ ] **Sales Cycle Stage** — Awareness, Consideration, Evaluation, Decision?
- [ ] **Specific Competitor or Objection** — Is this for a competitive deal or a specific objection?
- [ ] **Proof Point Available** — Approved case study, metric, or client outcome?
- [ ] **Delivery Format** — Deck (slides), PDF, printed one-pager, talk track doc?
- [ ] **CTA / Next Step** — What do we want the prospect to do after seeing this asset?

> A sales asset built for the wrong stage or the wrong persona will slow deals, not accelerate them.

---

## Section 6: Sales Asset Voice Rules

### Always
- Every headline = a complete outcome or insight — never a category label
- Proof before pitch — credentials after you've established the problem
- Write for the economic buyer reading alone — every asset must stand without a presenter
- Frame Summit credential as risk reduction, not as a badge or achievement
- One clear next step per asset — not multiple options

### Never
- "Leverage," "synergy," "holistic," "best-in-class," "robust," "end-to-end solutions"
- Feature-listing platforms without connecting to outcomes
- Announcing Summit Partnership as news
- Fabricating metrics — use `[ADD APPROVED METRIC]` as a placeholder
- Generic CTAs like "contact us to learn more"

---

## Section 7: Proof Points Library for Sales

| Proof Point | Stage to Use | Persona |
|---|---|---|
| Salesforce Summit Partner — top tier globally | Consideration + Evaluation | All |
| Multi-cloud: Salesforce + Snowflake + Databricks + AWS + Tableau | Consideration | CIO/CTO, CDO |
| Agentforce + Data Cloud implementations operationalizing AI | Evaluation | CDO, CIO |
| Deep industry deployments: Healthcare, Telecom, FinServ, Retail, Hi-Tech | All stages | Vertical-specific |
| AMS / Managed Services practice for long-term optimization | Decision + Post-sale | CIO, RevOps |
| TeqTalk — CXO-level podcast, ecosystem credibility signal | Awareness + Consideration | All |
| `[ADD: Specific implementation metrics per industry — VERIFY]` | Evaluation + Decision | All |
| `[ADD: Total clients / implementations count — VERIFY]` | Evaluation | All |

---

## Section 8: Industry Quick-Reference for Sales

| Industry | Lead Pain | Winning Angle | Stack to Lead With |
|---|---|---|---|
| **Healthcare** | Fragmented patient data, SDOH gaps, HIPAA complexity | AI-powered care coordination, interoperability | Health Cloud, Data Cloud, Snowflake, Databricks |
| **Telecom** | Churn, field service gaps, CX fragmentation | Predictive churn, field service AI, omnichannel CX | Service Cloud, Field Service, Databricks, AWS |
| **Financial Services** | Advisor productivity, compliance, fragmented client 360 | Compliant AI, advisor intelligence, unified client data | FinServ Cloud, Data Cloud, Snowflake, Tableau |
| **Retail / CPG** | Disconnected commerce + service, loyalty gaps | Unified commerce, AI personalization, distributor portals | Commerce Cloud, Snowflake, Databricks, Tableau |
| **Hi-Tech / SaaS** | Slow sales cycles, CS churn, PLG ↔ CRM gap | CPQ optimization, renewal automation, CS-to-sales handoff | Sales Cloud, CPQ, Agentforce, Databricks |

---

## Section 9: Competitive Battlecard Quick Reference

### Battlecard A — vs. Big SIs (Accenture, Infosys, Cognizant, TCS)

**How they position:** Scale, global delivery, "one-stop shop"
**Hidden weakness to expose:** Their Salesforce and data practices are separate — clients coordinate between them. Ramp-up time is billed to you. No Summit-level depth.
**Teqfocus counter-positioning:**
- "We bring Summit-level Salesforce depth that generalist firms can't match — and we've been doing this long enough that you're not paying for our learning curve."
- "We work across the data and application layer as one integrated team — they hand off between practices."
**Proof to use:** Specific Summit credential + case study showing faster time-to-value than expected
**Win condition:** When the client is tired of coordinating vendors and wants one accountable partner

### Battlecard B — vs. Salesforce-Only SIs

**How they position:** Salesforce specialists, deep CRM expertise, lower rates
**Hidden weakness to expose:** They stop at the CRM layer. AI initiatives, data-driven personalization, and modern analytics all require the data layer they don't build.
**Teqfocus counter-positioning:**
- "Salesforce is only as good as the data feeding it. A Salesforce-only partner leaves you with a CRM that underperforms because the foundation isn't there."
- "We implement Salesforce AND build the data infrastructure it needs — you don't need to coordinate a second vendor."
**Proof to use:** Case study where Teqfocus connected Salesforce to data layer and showed the difference
**Win condition:** When the client has already had a Salesforce implementation that underperformed

### Battlecard C — vs. Pure-Play Data Firms (Slalom, Sigma, boutique data)

**How they position:** Modern data stack expertise, AI/ML capability, engineering depth
**Hidden weakness to expose:** They build pipelines that don't connect to where decisions get made (Salesforce, ops systems). Data sits in the warehouse but doesn't reach the business.
**Teqfocus counter-positioning:**
- "We don't stop at the pipeline. We connect data to the applications your teams work in — which is where ROI actually lives."
- "A data platform without an application layer is infrastructure for its own sake. We build both."
**Proof to use:** Case study showing data + Salesforce + AI outcome — not just data architecture
**Win condition:** When the client's AI or analytics initiative is stalling because it's not connected to operations

---

## Section 10: Asset Map by Campaign Project

| Project | Sales Enablement Assets Used |
|---|---|
| P1 ABM Engine | Account 1-pager, first-call deck outline, competitive battlecard |
| P2 Outbound Engine | SDR call script, follow-up email, discovery question framework |
| P4 Events Engine | Event leave-behind, post-event proposal |
| P5 Customer Marketing | Expansion one-pager, QBR leave-behind, renewal framing |

---

## Section 8: Demo Script Framework

Structure every Teqfocus product or capability demo in 5 parts:

### Part 1: Anchor the Problem (2 minutes)
Before showing anything, restate their specific problem.
"Based on our discovery call, you're dealing with [X]. Is that still the right framing?"
Never start a demo without confirming the problem you're solving.

### Part 2: Set Up the Story (1 minute)
"What I'm going to show you is how [similar company in their industry]
solved [this exact problem] using [Teqfocus + platform]. By the end of this,
you'll see what [outcome] looks like in practice."

### Part 3: The Demo (15–25 minutes)
- Show the journey, not the features
- Narrate from the buyer's perspective: "As your CDO, you'd see..."
- Pause at each key moment: "What does this mean for your team?"
- Show the before/after — not just the after

### Part 4: Proof Moment (3–5 minutes)
"A [healthcare payer/FinServ firm/Hi-Tech company] we worked with
had this exact situation. Here's what changed after 90 days." [VERIFY timeline]

### Part 5: Next Step (2 minutes)
Single specific ask — never "any questions?" as the close.
"Based on what you've seen, the logical next step is [scoping session / data assessment / proposal].
Can we put 2 hours on the calendar for [specific date options]?"

---

## Section 9: Discovery Question Bank by Persona

Ask these before any demo or proposal. Not all at once — work them into conversation.

**For CIO:**
- "What's the one technology investment you can't afford to get wrong this year?"
- "When you think about your Salesforce and data infrastructure 18 months from now — what needs to be true that isn't today?"
- "What's your current thinking on the build vs buy vs partner decision for AI?"

**For CDO / Head of Data & AI:**
- "Where does your data pipeline currently break down before it reaches a Salesforce workflow?"
- "How many of your AI initiatives are in production vs still in proof-of-concept?"
- "What would have to be true about your data layer to make Agentforce actually work?"

**For RevOps / VP Sales:**
- "How much time does your team spend correcting Salesforce data that came in wrong?"
- "What's your current forecast accuracy — and how confident are you in it?"
- "If Salesforce showed your reps exactly what to do next with each account — what would change?"

---

## Section 10: Deal Qualification Framework (MEDDPIC for Teqfocus)

Before investing AE time in a deal, validate these criteria:

| Letter | Criterion | Qualifying question |
|---|---|---|
| **M** | Metrics | "What does success look like in numbers?" |
| **E** | Economic buyer | "Who signs the contract?" (Are we talking to them?) |
| **D** | Decision criteria | "How will you evaluate options?" |
| **D** | Decision process | "What does the path to a decision look like?" |
| **P** | Paper process | "Once decided, how long to contract?" |
| **I** | Identify pain | "What happens if this doesn't get solved this year?" |
| **C** | Champion | "Who inside is advocating for this to happen?" |

**Disqualify early if:**
- No economic buyer access after 3 touches
- No defined budget or timeline by second meeting
- No champion identified — "just exploring" with no internal driver
- Scope is below Teqfocus's minimum viable engagement