Aan de slag
Revenue Operations — No more leads falling through

Revenue Operations — No more leads falling through

Stop losing deals to broken handoffs. Share your GTM motion, ACV, sales cycle, and CRM — and walk away with a complete RevOps system: lifecycle stages from Subscriber to Customer, lead scoring, lead routing rules with speed-to-lead SLAs, a pipeline configuration, and a metrics dashboard spec. Built for PLG, sales-led, or hybrid motions. Specs written to HubSpot, Salesforce, and Apollo's configuration logic.
#Verkoop#Productiviteit#Analyse
Beoordeling
Meer beoordelingen nodig
Verkocht
2
Gebruikswijze
Uitvoeren op Capafy
Ook in externe apps
Publisher levert
claude-sonnet-4-6

Stop losing revenue between marketing and sales.

Good leads go cold.

Sales rejects MQLs. Marketing blames follow-up. Deals sit in fake stages. Leadership sees three versions of the truth.

image.webp

Revenue operations is not one broken workflow. It is the handoff system between marketing, sales, CS, and the CRM. This RevOps skill turns that system into implementation-ready specs instead of another list of suggestions.

Replace the patchwork with one revenue operating system

image.webp

You get the pieces a CRM admin actually needs to build the system:

  • Lifecycle stage document - Subscriber, MQL, SQL, Opportunity, and Customer definitions with entry criteria, exit criteria, owners, SLAs, recycle paths, and reason codes.
  • Lead scoring specification - fit score, engagement score, negative score, and MQL threshold logic.
  • Lead routing rules - assignment logic, fallback owners, speed-to-lead SLA, escalation, and audit trail.
  • Pipeline configuration - pipeline stages, required fields, stale-deal alerts, and close-date discipline.
  • Metrics dashboard spec - marketing, sales, and executive views from the same revenue data model.

These are written as CRM implementation specs for HubSpot, Salesforce, Apollo, or your current stack so an admin can adapt them directly.

Built for the moments your funnel starts lying to you

image.webp

Use this when:

  • Sales says lead quality is weak - lead scoring needs fit + engagement, not one noisy activity.
  • Marketing says sales follow-up is too slow - lead routing needs ownership, fallback coverage, and speed-to-lead SLA.
  • Pipeline stages do not reflect real deal progress - stages need required fields and observable exits.
  • Leadership does not trust the metrics dashboard - teams need role-based views from one data model.

Why this is different

  • Definitions before automation - CRM automation cannot fix a process nobody has defined.
  • Fit + engagement scoring - MQL quality is based on ICP match and intent.
  • Lead routing with fallback owners - no qualified lead quietly waits without accountability.
  • Pipeline stages with observable exits - deals advance on evidence, not rep confidence.
  • Role-based dashboards from one data model - marketing, sales, and executives stop fighting over spreadsheets.