revenue-goal-funnel-math
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill when a founder sets a revenue or income goal and needs to know what it takes each week, or when a weekly review shows the goal slipping. Produces a backwards funnel from the goal down to weekly outreach volume, the actual-versus-required gap at every stage, and the one bottleneck to fix this week. Also use for "how many calls do I need", "reverse funnel", "goal math", "what's the bottleneck", "are we on pace", "weekly pipeline review".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Use measured rates, not hoped-for ones.
- Distinctive: line 32
Write 3 to 5 actions, each dated, each tied to the bottleneck stage.
- Distinctive: line 46
MUST split discovery and proposal into separate stages.
- Distinctive: line 47
MUST label every rate as measured (with sample size) or assumed.
- Distinctive: line 48
MUST name exactly one bottleneck per review.
- Distinctive: line 49
MUST pick the most upstream broken stage when several are below the line.
- Distinctive: line 50
NEVER count a proposal that was not actually delivered.
- Distinctive: line 51
NEVER set a revenue goal without checking what it pays the owner.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies when there is a number to hit and nobody has worked out what it means for this week. Produces one page: the chain from goal to touches, required versus actual at each step, and one named bottleneck.
The play
- Anchor the goal. If it is the owner's income, convert it first: income ÷ owner's share of profit ÷ margin = revenue needed. A revenue goal that pays the owner too little is a failed plan, so check this before going further.
- Work backwards, one link at a time, using the chain in references/funnel-chain.md:
- Revenue → clients needed (÷ average monthly value per client).
- Clients → closes per month (net adds + expected churn).
- Closes → proposals (÷ proposal-to-close rate).
- Proposals → discovery calls held (÷ discovery-to-proposal rate).
- Discovery calls → replies (÷ reply-to-call rate).
- Replies → touches (÷ reply rate).
- Divide by 4 for the weekly number.
- Use measured rates, not hoped-for ones. Where you have fewer than 10 settled outcomes for a stage, use the planning defaults in references/thresholds.md and mark them as assumed.
- Split the sales call stage in two: discovery and proposal. One "close rate" hides which call is broken. A 13% overall rate could be 60% × 22% (a proposal problem) or 30% × 43% (a discovery problem). The fixes are opposite.
- Pull the trailing 7 days and the trailing 28 days of actuals for every stage. Put required and actual side by side.
- Name the bottleneck. Compare each stage with the alarm lines in references/thresholds.md. If several are broken, pick the one furthest upstream. Fixing close rate with no calls on the calendar is theatre.
- Write 3 to 5 actions, each dated, each tied to the bottleneck stage. "By Friday, rewrite the first touch for the two lowest-reply segments" is an action. "Improve reply rate" is not.
- Re-run monthly. If a measured rate differs from the planning default for two months in a row, replace the default. A model that flatters you is worse than none.
Worked examples are in references/worked-examples.md.
What good looks like
- First thing I check that most people skip: whether the close rate in the model is measured or assumed. It is usually assumed, usually 25%, and usually generous. Halve it and the required call volume doubles.
- The mediocre version: a top-down plan ("we need 10 clients") with no weekly touch number, one blended close rate, and three things to fix at once. It feels like a plan and changes nothing on Monday.
- I know the math is right when the owner can say one line from memory: "X touches a week → Y replies → Z calls → 1 close." If they cannot say that line, the review did not land.
- I know the review worked when next week's actuals moved on the one stage named, and nobody touched the others.
Rules
- MUST split discovery and proposal into separate stages.
- MUST label every rate as measured (with sample size) or assumed.
- MUST name exactly one bottleneck per review.
- MUST pick the most upstream broken stage when several are below the line.
- NEVER count a proposal that was not actually delivered. A fake proposal in the funnel corrupts every rate below it.
- NEVER set a revenue goal without checking what it pays the owner.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

