predictable-revenue

predictable-revenue

Outbound & Prospecting
Wondel.ai
The Salesforce outbound model as a scored diagnostic: role separation, a repeatable process, and a lead mix you can name before you plan pipeline.
REPO
wondelai/skills
INSTALL
npx skills add
NEEDS
Your sales process
Last updated
August 4, 2026

Preview

predictable-revenue

What it is.

You describe how your sales team is set up and it scores the process 0 to 10 against Aaron Ross's five diagnostic rows, then names the rows blocking your next point.

It sorts your leads into seeds from referrals, nets from marketing and spears from outbound prospecting, with conversion and cost on each, and works the pipeline math backwards from a revenue target. The pattern it expects to find is over-investment in nets and under-investment in spears.

What you get.

  • A 0 to 10 score with the specific diagnostic rows blocking the next point
  • The three lead types with conversion rate and cost attached to each
  • Role definitions for prospecting, closing and account management
  • The referral-email method and ANUM qualification
  • Pipeline math, so a revenue target turns into a required activity number
HOW TO USE IT

How to set it up.

1

Install with npx skills add wondelai/skills/predictable-revenue --global, or add the marketplace and install the sales-influence plugin.

2

Describe your current setup, including who prospects and who closes. Row one is the separation question and it is the most common failure.

3

Ask for the score first. It arrives with the rows you failed, which is the shortest path to knowing what to change.

4

Name your lead mix in the seeds, nets and spears frame, then compare it against your spend split.

5

Work the pipeline math backwards from the revenue number, so the activity target is derived instead of guessed.

6

Standardize the handoff from prospecting to closing before you hire more of either. That row gates the score twice over.

Pricing Plans

Free. MIT license.

Checked against the repo in July 2026.

Use cases

Scoring a founder-led setup

The founder still prospects and closes every deal. Describe the setup and the diagnostic returns a score out of ten with the failing rows named, starting with role separation.

Sizing the first hire

You're choosing between an SDR and another closer. Sort your leads into the seeds, nets and spears frame with conversion and cost on each, and the mix shows whether outbound or inbound conversion is the gap.

Backing into activity targets

The board set a revenue number and nobody knows what it implies weekly. The pipeline math works backwards from the target, so the required activity level is derived, never guessed.

Best for

One person prospecting and closing

The framework's first diagnostic is exactly this, and the score tells a founder how much of their pipeline depends on their own effort.

Planning the first SDR hire

The seeds, nets and spears split shows whether outbound is the gap or whether inbound conversion is.

Getting pipeline predictable enough to forecast

Three-month predictability is one of the five scored rows, so it is treated as an outcome of process instead of of effort.

Read the source

Published by Wondel.ai. Opens in a new tab.
Open the Tool

Questions about predictable-revenue

What is the score based on?
Do I need the whole library?
What are seeds, nets and spears?
Is it still relevant?

Questions about Outbound & Prospecting

What does a sales process diagnostic tell you?
Should prospecting and closing be split?
Strengths
  • The rubric is explicit, 2 points per row across five rows, so two people scoring the same process land in the same place.
  • Lead types carry conversion and cost, which turns a naming scheme into a budgeting decision.
  • It states where most companies misallocate, so the read has a direction instead of a shrug.
  • MIT licensed, and it installs as a single skill without the rest of the library.
Limitations
  • The role separation argument holds up better than the email tactics inside it, which read as dated now.
  • The scoring is a self-assessment, so it reflects what you tell it.
  • Enterprise and mid-market sales fit it better than product-led self-serve.
Skip this if
  • Skip it if your outbound roles are already split the way the model asks.

The team behind these plays.

We build inbound GTM engines for B2B software teams, and these are the plays we build from. Tell us the pipeline target and we'll show the plan under it.