Revenue leaders, RevOps teams, Sales leaders, Founders, Operations managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a revenue operations strategist. Your task is to identify the main constraints limiting revenue growth and produce a practical plan to remove or reduce them.
### Required Input
- Revenue Goal: [Example: grow from $5M to $8M ARR in 12 months]
- Current Performance: [Provide revenue, pipeline, win rate, sales cycle, churn, expansion, quota attainment, or other key metrics]
- Sales Motion: [Example: inbound-led SMB sales, enterprise outbound, channel sales]
- Team Structure: [Example: SDRs, AEs, CSMs, managers, RevOps support]
- Funnel and Pipeline Data: [Stage conversion, pipeline coverage, velocity, source performance, or segment data]
- Known Constraints: [Example: not enough qualified pipeline, slow legal review, low rep productivity, poor retention]
- Market or Capacity Limits: [Example: hiring freeze, limited territories, product gaps, budget pressure]
- Time Horizon: [Example: next quarter, next 12 months]
### Input Validation
Check whether the user has provided a revenue goal, current performance context, and at least some funnel or pipeline evidence. If these are missing, ask specific follow-up questions and pause.
### Instructions
Analyse revenue growth as a system, not a single metric. Consider constraints across demand creation, qualification, pipeline coverage, sales capacity, conversion, velocity, pricing, retention, expansion, data quality, and operational execution.
Identify which constraint is most likely limiting growth now. Do not list every possible issue equally. Separate primary constraints, secondary constraints, and symptoms. For example, low revenue may appear to be a pipeline issue, but the true constraint could be low conversion from poor qualification or insufficient sales capacity.
Use evidence from the input to explain each constraint. Where evidence is incomplete, label the confidence level and identify the data needed to confirm it. Estimate commercial impact directionally when exact figures are not available.
Make recommendations realistic for the stated team and constraints. Prioritise actions that unlock the largest growth improvement with the least operational complexity. Avoid recommending broad transformation projects unless the problem genuinely requires them.
### Output
- Executive Summary: the most important growth constraint and why it matters
- Growth System Review: demand, pipeline, conversion, velocity, capacity, retention, and expansion
- Constraint Ranking: primary, secondary, and low-priority constraints with evidence
- Symptom vs Root Cause Analysis: what appears wrong versus what is likely causing it
- Revenue Impact Assessment: how each constraint limits growth
- Constraint Removal Plan: specific operational actions to address the top constraints
- Trade-Offs and Risks: what could worsen if the team focuses on the wrong area
- Data Needed To Increase Confidence: missing metrics, reports, or analysis
- 30/60/90-Day Roadmap: sequenced actions, owner type, and success measures
- Leadership Summary: concise explanation suitable for a revenue leadership meeting
Include a one-page board-ready summary of the top three growth constraints and recommended actions.
This strategic audit applies Theory of Constraints (ToC) principles to the revenue operations infrastructure of the Cross-Border Customs API Hub. Our core objective is to scale from $5M to $8M in ARR over the next 12 months.
An end-to-end diagnostics check across our complete revenue machinery highlights the following functional performance levels:
| Constraint Priority | Identified System Bottleneck | Supporting Context & Evidence | Confidence Level |
|---|---|---|---|
| 1. Primary Constraint | Technical Evaluation Gating: Reps run generic product tours instead of securing cross-functional IT alignment early. | Stage 3 to 4 conversion drops to 22%; average age in this stage is 42 days. | HIGH (Verified by CRM opportunity lifecycle logs) |
| 2. Secondary Constraint | Operational Capacity Overload: Mid-Market AEs are buried under excessive territory account loads. | Reps manage 140 accounts each; CRM notes reveal highly inconsistent follow-up cadences. | MEDIUM (Inferred via task execution logs) |
| 3. Low-Priority Constraint | Top-of-Funnel Lead Volume: Raw lead acquisition numbers. | Marketing delivered 1,200 qualified MQLs this half, outstripping downstream sales processing capacity. | HIGH (Confirmed via marketing automation reports) |
| Observed Pipeline Symptom | Apparent Surface Problem | Underlying Operational Root Cause |
|---|---|---|
| Low Team Quota Attainment (45%) | Reps lack sales motivation or basic product competency. | Loose qualification gates let reps advance unqualified deals into the active forecast pool, wasting time on dead opportunities. |
| Severe Late-Stage Discounting (22%) | Our software price point is too high for the current market. | A complete lack of upfront value metrics forces reps to use price concessions as their primary negotiation tool during procurement. |
| Delayed Onboarding Timelines (45+ Days) | The post-sale implementation team is understaffed. | Sellers fail to document technical infrastructure requirements before contract signature, forcing duplicate engineering discovery. |
The Real Cost of Our Mid-Funnel Leak:
The 42-day bottleneck in our solution demonstration phase acts as an operational dam on our pipeline. It traps an estimated $1.2M in active pipeline value mid-funnel every single quarter. If we optimize our process to reduce this stage’s duration by just 10 days, the increased system velocity would generate an additional $450,000 in incremental ARR annualized—fully unlocking our growth trajectory without requiring a single dollar of additional top-of-funnel marketing spend.
To eliminate our primary conversion bottlenecks without adding software platforms or scaling headcount, we will execute three tactical process shifts:
Get access to all workflows, across every sector, with structured systems built for better results.