Teqfocus Gtm

Teqfocus GTM Skill

This skill governs all GTM asset creation for Teqfocus. It ensures every output reflects accurate company positioning, the right buyer persona, and the correct narrative structure for the asset type requested.

How to Use This Skill

1. Read this SKILL.md fully before writing any asset
2. Identify the asset type being requested → load the relevant reference file
3. Run the Brief Intake Checklist (Section 6) — ask the user if anything is missing
4. Write the complete, ready-to-use asset following the structure in the reference file

Reference Files

Load the appropriate reference file based on the asset type:

Section 1: Teqfocus Company Identity

Who Teqfocus Is

Teqfocus is a digital transformation partner that helps enterprises and mid-market companies across the Data, Analytics, AI, and Application layers — using 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

⚠️ Credential Rule: Salesforce Summit Partnership is an established, long-standing credential. Never say "recently achieved," "just became," or imply it is new. Same applies to all other partnerships.

Service Lines

Industries Served

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

Section 2: The Multi-Cloud Positioning Story

This is Teqfocus' core strategic differentiator. Use it deliberately — not as a platform list.

The Narrative

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.

Teqfocus solves this by working across the full stack — from data infrastructure (Snowflake, Databricks, cloud) through the intelligence layer (AI/ML, analytics) to the application layer (Salesforce, custom apps) — as a single, integrated partner.

How to Say It

❌ "We work with Salesforce, Snowflake, AWS, Databricks, and Tableau." ✅ "We connect your data, intelligence, and customer-facing systems into one architecture — so AI has something real to work with, and your teams see the results."

❌ "Our multi-cloud expertise spans several platforms." ✅ "Most AI projects fail at the data layer. We handle both — so you're not coordinating three vendors to get one outcome."

❌ "We are a full-stack partner." ✅ "Whether the problem starts in your data warehouse, your CRM, or your AI model — we own the entire chain."

Competitive Wedge Language

Section 3: Target Personas

Always confirm the target persona before writing. Each has a different entry point into the Teqfocus story.

🎯 CIO / CTO (Enterprise)

• Fear: Another transformation that underdelivers, creates debt, leaves a mess
• Owns: Platform stability, integration architecture, cost of ownership
• Entry Point: Risk reduction + integration credibility + industry proof
• Stack to Feature: Summit Partner credential, MuleSoft, cloud architecture
• Buying Trigger: Failed project, AI board mandate, M&A integration, cloud migration stall

🎯 CDO / Head of Data & AI

• Fear: AI that the business doesn't trust or use; data strategy without adoption
• Owns: Data quality, AI governance, platform ROI, analytics across the business
• Entry Point: Data maturity + AI readiness + governed pipelines
• Stack to Feature: Snowflake, Databricks, Data Cloud, Agentforce
• Buying Trigger: Failed POC, Data Cloud mandate, CEO asking "why isn't AI working"

🎯 Mid-Market RevOps / Ops Leader

• Fear: Salesforce build the sales team ignores; customization that breaks every release
• Owns: Pipeline visibility, CRM adoption, sales cycle speed, forecast accuracy
• Entry Point: Speed + adoption + practical outcomes in 90 days
• Stack to Feature: Sales Cloud, CPQ, Agentforce — light data layer unless there's a gap
• Buying Trigger: Salesforce renewal, new VP of Sales, poor adoption, growth breaking process

🎯 VP of Sales / Revenue Leader

• Fear: Salesforce as an expensive CRM nobody uses; no pipeline visibility
• Owns: Revenue target, pipeline health, forecasting accuracy, sales productivity
• Entry Point: CRM that actually drives revenue, not just tracks it
• Stack to Feature: Sales Cloud, Revenue Intelligence, Agentforce sales automation
• Buying Trigger: Missed quarters, manual forecasting, new sales motions (PLG, partner, expansion)

Section 4: Messaging Pillars

Every asset must connect to at least one. Choose based on persona and buyer stage.

Section 5: Industry Vertical Quick-Reference

Section 6: Brief Intake Checklist

Before writing any asset, confirm all that apply. If missing — ask before writing.

• Asset Type — Deck, one-pager, LinkedIn post, email, case study, event invite?
• Target Persona — CIO/CTO, CDO/Data Leader, RevOps, VP Sales, or combination?
• Industry Vertical — Healthcare, Telecom, FinServ, Retail, Hi-Tech, cross-industry?
• Primary Problem — Data layer? AI readiness? Salesforce ROI? Cloud migration? App modernization?
• Stack to Feature — Which platforms are relevant for this buyer context?
• Buyer Stage — Awareness / Consideration / Decision?
• Proof Point Available — Any approved case study, metric, or client outcome?
• Desired CTA — What action should the reader take after this asset?

A vague brief produces a forgettable asset. A precise brief produces a deal-moving one.

Section 7: Standing Output Rules

1. Always deliver complete, ready-to-use drafts — not outlines unless explicitly asked
2. Every headline = an outcome or insight statement — never a label or category title
3. Multi-cloud stack is the HOW — never lead with platform names, lead with the outcome
4. Flag unverified stats with [VERIFY] — never invent numbers
5. Flag design requirements with [DESIGN FLAG: description]
6. Summit Partnership is established — never "recently achieved" or "just became"
7. Never position Teqfocus as a vendor — always as a strategic transformation partner
8. Never use: "leverage," "synergy," "holistic," "best-in-class," "cutting-edge," "robust," "end-to-end solutions"
9. Always end with a specific CTA — not "contact us to learn more"
10. Industry specificity is non-negotiable — no generic slides or generic copy

Section 8: Proof Points Library

Section 9: Named Customer Proof Strategy

Teqfocus names customers in campaigns where approved. The approach:

• In ABM campaigns: Match the case study customer's industry to the target account's industry. Always name the customer if approved.
• In outbound emails: Introduce the named customer at Touch 3 or later — after relevance is established
• In LinkedIn posts: Name the customer prominently — it's the hook
• In microsites: Use in the "How We've Done This" section — industry-matched, named
• When name is not approved: Use "[Leading Healthcare System]", "[Fortune 500 Telecom]", etc.

Case study naming format in copy:

"When we did this for [Customer Name], a [Industry] company, the outcome was [specific metric]."

Section 10: Competitive Intelligence

Teqfocus most commonly competes against three types:

vs. Big SIs (Accenture, Infosys, Cognizant, TCS)

Their weakness: Generalist ramp-up billed to client, no Summit-depth Salesforce expertise Teqfocus wedge: "We go deeper on Salesforce and data than generalist consultancies — and we don't bill you for ramping up on platforms we've built on for years." Win condition: Prove Summit depth + full-stack + faster time-to-value

vs. Smaller Salesforce-Only SIs

Their weakness: No data layer — AI projects stall because the data feeding Salesforce isn't connected Teqfocus wedge: "We go beyond the CRM. A Salesforce implementation is only as good as the data feeding it." Win condition: Expand scope — show what's left on the table without the data layer

vs. Pure-Play Data Firms (Slalom, Sigma, boutique data consultancies)

Their weakness: Don't touch the application layer — data sits in pipelines that don't connect to where the business works Teqfocus wedge: "We don't stop at the pipeline. We connect data to the applications your business runs on — and build the AI layer in between." Win condition: Expand from data-only to data + Salesforce/application — show the full-stack ROI picture

Section 11: Project Role Map

Section 12: Brand Guidelines — The Complete Reference

Source of truth: Teqfocus Brand Guideline 2025. These are non-negotiable. Every asset, design flag, and copy element must follow exactly.

Official Color Palette

Primary Colors

Secondary Colors

Color Shades

Background Rules — MANDATORY

• ALL slide, PDF, and document backgrounds: White #FFFFFF always
• Color appears in text, headers, accents, borders, icons, CTAs — never as a full-page background fill
• The only exception: a thin footer bar or a narrow section accent strip may use #59267E or the brand gradient
• Never use dark full-page backgrounds in any GTM asset: no #59267E, no #7751E2, no #244495 as a page fill
• Never use off-brand colors: #1A1A2E, #16213E, or any dark navy not in the brand palette

Brand Gradient (official) #BD71EF → #B08DF3 → #8D9BF5 (bottom-left to top-right)

Color Distribution Rule: 60% primary colors · 30% secondary colors · 10% accent/shade colors

Color Emotion Map:

• Purple → Creativity, innovation
• Blue → Trust, professionalism, stability
• Combination → Technological expertise, forward-thinking approach

Typography

Primary Typeface: Poppins

• Bold: Titles, headlines, CTAs, all-caps section headers
• Regular: Body text, paragraphs, captions
• Available as Google Font

Secondary Typefaces (for subheadings, callouts, specific contexts):

• Satoshi — modern, clean body complement
• Gilroy — professional, readable subheadings
• Bahnschrift — structured, technical contexts
• Century — serif accent, limited use

Typography System:

• Title (Bold): "Find the True Talent" — Poppins Bold
• Title All-Caps: "THE EASIEST AND FASTEST WAY" — Poppins Bold + All Caps, purple
• Paragraph (Regular): Poppins Regular, body text
• Button (Bold): Poppins Bold, white text on purple CTA button
• Link (Bold): Poppins Bold, underlined, purple

Rules:

• Line spacing: 1.5× font size
• Body text: left-aligned
• Headlines/short phrases: center-aligned acceptable
• Letter spacing: default for body; slight increase for all-caps headlines
• Ensure sufficient contrast between text and background

Never use: Inter, Roboto, Arial, Space Grotesk, Open Sans, system fonts

Logo Rules

• Correct name: "Teqfocus" — always this exact casing
• Wrong: TeqFocus, TEQFOCUS, Teq Focus, Teqfocu's
• Full color logo: use on white or light backgrounds
• Reversed (white) logo: use on dark backgrounds
• Monochrome: single-color when color printing unavailable
• Icon (T mark): use for small spaces, social avatars, favicons
• Clear space: equal to height of the 'T' in Teqfocus on all sides
• Minimum size: 25mm wide (print) · 100px wide (digital)
• Logo placement: top-left (default), top-center acceptable
• In presentations: top-left corner of every slide
• Co-branding: equal visual weight, separated by vertical line

Never do with the logo: Crop · change transparency · recolor · distort · add drop shadows · rotate · outline · recreate in another typeface

Design Flag Protocol

Every design instruction in every skill must use exact hex codes.

✅ [DESIGN FLAG: Background #FFFFFF, headline #59267E Poppins Bold, CTA button #BD72EF with white Poppins Bold text] ✅ [DESIGN FLAG: White #FFFFFF background, gradient accent bar #BD71EF → #8D9BF5 at top, logo top-left] ❌ [DESIGN FLAG: Use brand colors — confirm with team] ❌ [DESIGN FLAG: Purple background, white text]

Voice Standards (reinforced)

American English — mandatory. No exceptions. Use: personalize, optimize, organize, recognize, color, behavior, center, program Never use British variants: personalize, color, behavior, program

Brand personality in copy: Innovative · Trustworthy · Insightful · Agile · Collaborative · Professional

Section 13: First-Attempt Accuracy Rules

Based on usage patterns, these rules prevent the most common output quality issues.

Before writing ANY asset — confirm these 5 things:

1. Persona confirmed? CIO/CTO, CDO, RevOps, VP Sales — never write for "all buyers"
2. Industry confirmed? Healthcare, Telecom, FinServ, Retail/CPG, Hi-Tech — never cross-industry without intent
3. Buyer stage confirmed? Awareness / Consideration / Decision — asset type depends on this
4. Named proof point available? Match case study industry to target. Use [VERIFY] if metric unconfirmed.
5. CTA confirmed? One specific CTA per asset. Never "contact us to learn more."

The specificity test — run on every draft:

"Could this sentence appear in a competitor's asset without changing a word?" If YES → rewrite it. If NO → it passes.

Common output failures to avoid:

• Opening LinkedIn posts with "I" or "We" → always open with an observation, insight, or question
• Subject lines over 50 characters → count before finalizing
• Stacking platform names without outcomes → always connect platform to result
• Announcing Summit Partnership → surface it naturally, once, never as news
• Generic CTAs → always name the meeting type ("30-minute data readiness review", not "let's connect")
• Missing preview text → every email needs a subject + preview text + body + CTA
• Inventing metrics → flag every unconfirmed number with [VERIFY]
• Writing for "enterprise and mid-market" simultaneously → pick one scale per asset

LinkedIn character limits (check before delivering):

• Connection request: 300 characters max → write to 200–250
• DM / InMail body: 1,900 characters max → write to 300–600
• Feed post: 3,000 characters → write to 800–1,300 for best engagement
• Article title: 100 characters → write to 60–80

Email subject line rules (apply every time):

• Under 50 characters — always count
• No exclamation points
• No "Quick question" (overused)
• No "I wanted to reach out"
• Must be specific to the industry, persona, or company — never generic

Background rule for every designed asset (slides, PDFs, one-pagers, social cards):

• Page/slide background: White #FFFFFF always — no exceptions
• Color lives in: headlines (#59267E), subheads (#7751E2), accent bars, borders, icon fills, CTA buttons, thin top/bottom strips
• The brand gradient (#BD72EF → #8D9BF5) is used as a thin accent element — never as a full-page fill
• Dark purple (#59267E) and Slate Blue (#7751E2) appear as text and accent colors — never as page backgrounds
• Footer bars may use #59267E — this is the only full-width dark element allowed
• Social quote cards and reel thumbnails: white background with purple text — not inverted
• If a design instruction says "dark background" — override it. White background, apply the brand palette as text/accents on top.

Reference: Teqfocus SF Practice deck (48 slides) — every slide uses white background with purple/blue content on top. This is the visual standard for all GTM assets.

Section 14: Content-to-Persona Mapping Matrix

For every asset, confirm the persona-stage match before writing:

Rule: Never write for all personas simultaneously. Pick one per asset.

Section 15: Message Testing Framework

Before scaling any campaign message, test it:

The 5-second test: Show the headline to a target buyer for 5 seconds. Ask: "What does this company do? Who is it for? Why does it matter?" If they can't answer all three — rewrite.

The "so what?" test: After every claim, ask "so what?" "We have 400+ Salesforce certifications" → so what? → "You're working with a team that's done this hundreds of times, not learning on your dime"

The competitor test: "Could this appear on Accenture or Slalom's website?" If yes — rewrite with more specificity.

The buyer language test: Would a CDO or CIO say this phrase in a meeting? "Holistic digital transformation" — no. "Getting AI to production" — yes.

Section 16: Brand Voice Examples

Positive examples — sounds like Teqfocus:

• "Agentforce is the right tool. Without the right data and integration, its impact is limited."
• "We don't bill you for ramping up on platforms we've been building on since 2012."
• "Your Salesforce implementation is only as good as the data feeding it. We fix both."
• "Summit-level depth — not because we announce it, but because you'll see it in week one."

Negative examples — does NOT sound like Teqfocus:

• "We're excited to announce our cutting-edge holistic AI transformation services."
• "Leveraging our best-in-class, robust, end-to-end Salesforce solutions."
• "As proud Summit Partners, we deliver synergistic value across your enterprise."
• "Our team is dedicated to your digital transformation journey."

The single best voice test: Would Andy Singh say this in a CXO dinner conversation? If yes — publish it. If no — rewrite it.

Section 17: Proof Point Canonical Source

The authoritative proof library for all Teqfocus GTM assets is: presales-agent/references/proof-library.md

This file contains:

• Tier 1: Public Salesforce customer references (naming-cleared, metric-verified)
• Tier 2: Teqfocus-delivered engagements (naming status and metric verification flagged per entry)
• Tier 3: Teqfocus accelerator patterns (anonymized, no metrics claimed)

Rules for all skills using proof:

• Never cite a customer name not in the proof library as naming-cleared: yes
• Never state a metric not marked metric-verified: yes — use [VERIFY] until confirmed
• Pairing rule: always pair a Teqfocus case (Tier 2) with a public SF reference (Tier 1) when available — see vocab-ladder.md pairing guide in presales-agent
• New entries: Customer Marketing adds entries after delivery. Flag to Avi Kumar for naming clearance.

For live deal situations: presales-agent retrieves proof directly from the library. For marketing assets (emails, posts, case studies): customer-marketing skill produces the asset; teqfocus-gtm proof rules apply.

Section 18: Buyer Language — Authoritative Source

The most complete buyer vocabulary substitution tables are in: presales-agent/references/vocab-ladder.md

These cover industry-specific buyer language for:

• Healthcare Providers
• Healthcare Payers
• Life Sciences
• Financial Services
• Insurance
• SaaS / Hi-Tech

Rule: When writing any Teqfocus asset for a specific vertical, check the vocab-ladder substitution table before finalizing copy. The tables replace internal/vendor language with the exact terms buyers use in their own conversations.

The banned words list in vocab-ladder.md supersedes any other reference. It is the master list. Banned: leverage, synergy, holistic, best-in-class, cutting-edge, robust, end-to-end solutions, "excited to share", "proud to announce", "unlock value", "unleash potential" Never open with "I" or "We". Open with: an observation, the prospect's situation, or an operational reality.

Section 19: Distribution Architecture — Personal-First Doctrine

This is structural, not optional.

Jas Kaur's personal LinkedIn profile is Teqfocus's primary distribution channel.

The 2026 LinkedIn algorithm allocates ~65% of feed to personal profiles and ~5% to company pages. That is an 8× engagement gap. Every GTM asset with a LinkedIn distribution component defaults to Jas's personal profile first. Company page is secondary amplification.

Employee advocacy is non-negotiable for Teqfocus. With 1 SDR/BDR, there is no outbound volume to compensate for low organic reach. Employee posts from Avi, Afraz, Suds, and practice leads multiply reach 5–10× without paid spend. 561% reach increase is the documented benchmark for employee advocacy vs. company-only posting.

Jas's posting target: 3–4 posts/week (validated as sustainable) Format rotation rule: never post the same format twice in a row — 40% faster follower growth. Weekly rotation: Carousel (Tuesday) → Native video clip (Wednesday) → Text post (Friday) → optional 4th

TeqTalk as primary TOFU engine: Target ~120 MQLs/year via PC-01. Every episode = Salesforce Campaign. Every listener = TOFU Campaign Member. The goal is not 1M subscribers — it is 100 listens from the right 100 CIOs in Healthcare, Insurance, and Hi-Tech. Guest-to-client conversion: 10% median, up to 48% when guests are pre-selected from the Dream 200 target account list. Podcast-engaged leads close at 2.7× standard MQL rate. Pipeline stages move 40% faster.

The LinkedIn CPL benchmark for Teqfocus: Per ABM strategy: CPL > $250 → pause and rotate creative. CPL > $300 → shift to InMail. Organic LinkedIn Lead Gen Forms: 10–15% conversion vs 2–5% on landing pages — use natively for gated assets.