ClaudeSuperPower

sales-ops

Skill

Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean s

Install

git clone https://github.com/Airtable/skills.git ~/.claude/skills/sales-ops

What is sales-ops?

Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks (Clay-equivalent enrichment, AI-assisted outbound, conversation-intel ingestion). Use when the user wants to track deals, manage accounts, build a pipeline, run a deal desk, coordinate partners, manage RFPs, or build an AI-forward GTM stack. Defaults to augmenting existing CRMs (Salesforce / HubSpot); also supports Airtable-as-CRM and AI-native stacks. Asks scope first. Commercial workflows only; post-sale support belongs to a future customer-success skill.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~192 tokens of context used while enabled, before you invoke anything

Trust

83/100 · Excellent

2 factors scored below maximum

Documentation

README · ~20 min read

Sales operations and CRM workflows

Set up and run sales operations workflows in Airtable — pipeline, accounts, renewals, deal desk, RFP tracking, partner CRMs, vertical sales-shaped systems. Adapts to team size, existing CRM, and industry. Ask scope before scaffolding; the same trigger can mean a 3-table pipeline for a 5-person team, a Salesforce-augmenting deal desk for a 200-person enterprise sales org, or a vertical-specific CRM for a mortgage broker / real estate firm / public-works contractor.

Who this serves and what they're solving for

Sales operations spans more roles and verticals than the "VP Sales running Salesforce" stereotype.

  • Revenue leaders (CRO / VP Sales / RevOps / sales-ops manager) — pipeline coverage, forecast accuracy, segment visibility, lead-to-revenue efficiency. "Broken" means "I can't trust the numbers."
  • Daily operators (AE / SDR / BDR / account manager) — prospect context at the point of contact, fast inbound routing, deal-stage clarity, low-friction logging. "Broken" means "I'm pasting between five tabs to send one email."
  • Cross-functional support (deal desk, sales engineering, sales-ops analysts) — approval routing with audit trail, capacity vs. demand, technical-fit scoring, exception triage. Distinct product surface from the CRM itself.
  • Partner / channel managers — partner-led pipeline rollups, deal registration with anti-conflict rules, joint account planning, MDF tracking.
  • Vertical operators — mortgage loan officers, real-estate brokers, capture managers (public works / AEC), donor relations leads, capital-markets desk operators — sales-shaped workflows with industry-specific vocabulary, regulators, and integrations.

Cross-cutting problems: the existing CRM is usually staying but bleeds into spreadsheets where work actually happens ("swivel-chair work," "single source of truth"); per-seat licensing pushes stakeholders out of the system, so visibility breaks; the modern sales-tech stack (Outreach / Salesloft / Apollo / Gong / CaptivateIQ) is often absent in non-tech and mid-market footprints; AI-forward teams want an open data substrate to build Clay-equivalent enrichment + AI-drafted outbound + conversation-intel ingestion on, not a CRM with AI bolted on.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.