# Optimize Revenue Operations and Lead Handoffs

Disconnected lifecycle rules create slow handoffs and unreliable pipeline data. This skill designs scoring, routing, automation, and dashboard specifications for aligned revenue teams.

## Install

```bash
npx skillstore add coreyhaines31/revops
```

## Metadata

- Status: approved
- Slug: coreyhaines31-revops
- Version: 2.0.0
- Author version: 2.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: a2a893ba1b8f04df7a6d82c8678a0aac1d84ad517871e57fac4ba657efd64cb4
- Author: coreyhaines31
- GitHub username: coreyhaines31
- License: MIT
- Repository: https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops/
- Ref: 635f69fb8d2f4e6330ba47a4e5a0fb239c04d110
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/coreyhaines31-revops
- Manifest: https://skillstore.pages.dev/api/skills/coreyhaines31-revops/manifest

## Capabilities

- Defines lifecycle stages with entry criteria, exit criteria, owners, and service-level agreements.
- Builds fit and engagement scoring models with negative signals, thresholds, and recalibration guidance.
- Designs round-robin, territory, account, and skill-based routing rules with fallback ownership.
- Specifies CRM workflows for handoffs, alerts, stage changes, stale deals, and meeting events.
- Creates pipeline stage requirements and dashboard metrics for marketing, sales, and executives.
- Adapts recommendations to HubSpot, Salesforce, Calendly, SavvyCal, and Zapier workflows.

## Use Cases

- Redesign lifecycle handoffs: Document shared stages, owners, SLAs, and recycling rules for marketing, sales, and customer success.
- Launch scoring and routing: Create an initial lead scoring model and routing decision tree for a growing inbound program.
- Establish pipeline governance: Define opportunity stages, required fields, approval rules, and executive metrics for consistent forecasting.

## Prompt Templates

### Map our lifecycle

```
Map a lead lifecycle for [company type] using [GTM motion]. Define each stage, entry criteria, exit criteria, owner, and handoff SLA.
```

### Build a lead scoring model

```
Create a 100-point lead scoring model for [ICP] with [ACV] and [sales cycle]. Include fit, engagement, negative signals, threshold, and calibration plan.
```

### Design routing and automation

```
Design lead routing for [team structure] in [CRM]. Include precedence, capacity handling, fallback ownership, SLA alerts, recycling, and an audit log.
```

### Audit the revenue engine

```
Audit this lifecycle, scoring, routing, pipeline, and automation setup: [details]. Identify leaks, conflicting rules, missing data, risks, priorities, and measurable fixes.
```

## Limitations

- Provides specifications and guidance; it does not connect to or modify CRM systems.
- Requires business context and historical data for reliable scoring thresholds and benchmarks.
- Platform examples may require adjustment for account tiers, custom fields, and current product features.
- Does not replace legal, finance, or data privacy review for automation and deal processes.

## Best Practices

- Use historical closed-won and disqualified lead data before assigning scoring weights.
- Agree on stage definitions and ownership before implementing CRM automation.
- Pilot changes with a small segment, monitor exceptions, and recalibrate quarterly.

## Anti Patterns

- Do not automate undefined stages or conflicting handoff rules.
- Do not treat one engagement event as sufficient qualification without fit.
- Do not launch routing without fallback ownership, capacity checks, and decision logging.

## Security Audit

- Audited at: 2026-07-13T18:33:20.81\+00:00
- Summary: All 20 static findings are false positives caused by ordinary prose, Markdown formatting, and relative documentation links. The cited passages contain no executable commands, traversal operations, prompt injection, or data-exfiltration behavior.

## Stats

- Views: 95
- Downloads: 10
- Favorites: 0
- Popularity score: 0