PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-6.1-sol)
Token size
633
Example input
[COMPANY & ACV PROFILE]: AegisCloud Security ($85,000 ARR) [INDUSTRY SECTOR]: B2B Enterprise Cybersecurity SaaS [BUYER & GTM CONTEXT]: CISOs and VP of Infrastructure at Fortune 1000 enterprises | Enterprise Field Sales with Solutions Engineering (SE) Proof-of-Value (PoV) [FUNNEL METRICS DATA]: 400 SQLs/quarter, 45% enter Technical PoV, 22% of PoVs convert to Commercial Proposal, 14% overall SQL-to-Win rate, 145-day average sales cycle [OBSERVED BOTTLENECKS]: Deals stall for 45+ days during InfoSec compliance reviews; SE team overloaded with unqualified PoVs
Example output
# **AEGISCLOUD SECURITY** ## **Board-Level Revenue Diagnostic & Pipeline Leakage Audit** High Revenue Risk Pipeline Efficiency 90-Day Remediation **Prepared for:** Chief Revenue Officer (CRO), Executive Leadership & Board\ **Business:** AegisCloud Security\ **Sector:** B2B Enterprise Cybersecurity SaaS\ **Target Segment:** Fortune 1000 CISOs and VP of Infrastructure\ **Primary GTM Motion:** Enterprise Field Sales with Solutions Engineering (SE) Proof-of-Value\ **Average Contract Value:** $85,000 ARR # **1. Executive Diagnostic Summary** \- **Primary revenue constraint — Technical PoV conversion:** Only 45% of SQLs enter Technical PoV, and just 22% of PoVs progress to Commercial Proposal. This identifies a significant qualification and technical-to-commercial progression problem. The available metrics do not establish whether the underlying cause is poor discovery, weak technical differentiation, insufficient business justification, or inadequate buying-committee alignment. \- **Highest-leverage bottleneck — SE capacity and PoV qualification:** The SE organization is overloaded with unqualified PoVs. Deploying scarce technical resources before confirming business urgency, decision authority, technical fit, and commercial intent creates operational inefficiency and reduces capacity for potentially winnable enterprise opportunities. \- **Deal velocity constraint — InfoSec compliance delays:** Deals experience 45+ days of inactivity during InfoSec compliance reviews against an overall average sales cycle of 145 days. Compliance friction is therefore a material source of sales-cycle risk. The absence of a structured security-review process creates exposure to stalled opportunities, delayed commercial decisions, and weakened forecast reliability. \- **Executive risk — Funnel measurement integrity and revenue predictability:** The reported 14% SQL-to-Win rate cannot be reconciled directly with the reported 45% SQL-to-PoV rate and 22% PoV-to-Proposal rate if all metrics represent the same opportunity cohort and sequential funnel definitions. This requires immediate validation. Until reconciled, management cannot confidently attribute revenue outcomes to individual funnel stages. **Executive conclusion:** AegisCloud's primary problem is not demonstrably insufficient SQL volume. It is the inability to efficiently convert enterprise demand into commercially qualified opportunities while controlling technical resource consumption and compliance-related delays. The immediate priority should be improving opportunity qualification, protecting SE capacity, and accelerating InfoSec progression—not simply increasing lead generation. # **2. Stage-by-Stage Pipeline Leakage & Friction Matrix** ## **2.1 Quantitative funnel reconstruction** Based exclusively on the supplied quarterly metrics: ## **Quarterly enterprise sales funnel** **SQLs** # **400** 100% of reported SQL volume **Technical PoVs** # **180** 45% of SQLs enter PoV **Commercial Proposals** # **39.6** 22% of PoVs progress to proposal; mathematical expected volume, not a verified whole-opportunity count **Reported SQL-to-Win rate** # **14%** Equivalent to 56 wins per 400 SQLs if measured on the same cohort. The win figure is not reconciled with the sequential proposal funnel. These are mathematical implications, not verified CRM counts. ### **2.2 Pipeline leakage and friction matrix** | Funnel Stage | Observed Performance / Metric | Primary Friction & Root-Cause Hypothesis | Severity | | --------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | SQL Generation | 400 SQLs/quarter | Lead quality and source-level conversion are not supplied. SQL volume alone does not establish enterprise buying intent. | Moderate | | SQL Qualification | 45% enter PoV | 55% do not enter PoV. Qualification criteria, decision authority, urgency, and technical fit need validation. | High | | Technical PoV | 45% of SQLs enter PoV; SE team overloaded | Unqualified opportunities consume SE capacity. Potential absence of mandatory PoV entry criteria and documented success criteria. | Critical | | PoV-to-Proposal | 22% conversion | Significant progression friction. Potential gaps in business-case development, technical validation, stakeholder alignment, or commercial readiness. | Critical | | InfoSec Review | 45+ days of deal inactivity | Security questionnaires, evidence collection, review ownership, and customer-side approval dependencies may be creating prolonged inactivity. | Critical | | Commercial Proposal | Proposal volume mathematically implied at 39.6 per quarterly SQL cohort | Commercial proposal creation, pricing approval, economic buyer engagement, and proposal acceptance metrics are missing. | High | | Negotiation & Closing | 14% SQL-to-Win | Reported win rate is inconsistent with the implied proposal count under a same-cohort sequential interpretation. Stage definitions and cohort attribution require reconciliation. | Critical | | Closed-Won / Revenue | $85,000 ARR ACV | Actual bookings, realized ACV, discounting, implementation costs, and customer retention are unavailable. | Data Missing | ## **2.3 Critical leakage findings** **Finding 1: PoV qualification is a resource-allocation problem.** AegisCloud sends 45% of SQLs into technical evaluation, equivalent to 180 PoVs per quarter. However, management reports that SE resources are overloaded with unqualified PoVs. This indicates a need to treat PoV entry as a controlled investment decision rather than an automatic next step in the sales process. Recommended mandatory PoV entry requirements: - Confirmed business problem and measurable customer impact. - Identified technical decision-maker. - Identified economic buyer or documented access path. - Confirmed technical compatibility. - Documented PoV success criteria. - Agreed evaluation timeline. - Defined commercial decision process following successful evaluation. **Finding 2: PoV-to-Proposal is the most visible measurable conversion constraint.** Only 22% of PoVs progress to Commercial Proposal. This is a critical transition because successful technical validation must translate into commercial justification. The organization should investigate whether PoVs are being conducted without: - A pre-agreed commercial decision framework. - Documented customer success criteria. - Executive sponsorship. - A validated business case. - Procurement and InfoSec stakeholders engaged early. These are hypotheses requiring CRM and deal-level validation, not established causes. **Finding 3: InfoSec friction requires a dedicated operating process.** The 45+ day inactivity period is a material deal-velocity concern. AegisCloud should move security assessment preparation upstream into qualification and discovery rather than treating it as a late-stage administrative activity. The organization should establish: 1. A centralized security documentation repository. 2. Standardized InfoSec questionnaire ownership. 3. Named internal security-review escalation owners. 4. Customer-side security stakeholder identification during discovery. 5. Explicit tracking of customer and vendor dependencies. 6. A security-review milestone in the CRM opportunity process. **Finding 4: Funnel reporting integrity is compromised until the denominator issue is resolved.** The mathematical inconsistency is important. - 400 SQLs × 45% = 180 PoVs. - 180 PoVs × 22% = 39.6 implied proposals. - 400 SQLs × 14% = 56 implied wins. Under a single sequential cohort, 56 wins cannot result from only 39.6 proposals. At least one of the following must be investigated: - Metrics use different reporting periods. - Metrics use different cohort definitions. - Stage conversion denominators are inconsistent. - Proposal conversion is reported incorrectly. - Win-rate calculations include opportunities outside the stated funnel. **Required action:** RevOps must reconcile the underlying CRM opportunity records before using these metrics for board-level revenue forecasting. # **3. Unit Economics & Deal Velocity Risk Audit** ## **3.1 ACV exposure** Average Contract Value # **$85,000** Annual Recurring Revenue per average contract Quarterly SQL volume **400** Reported SQL-to-Win rate **14%** Implied wins, same cohort **56** **Conditional implied new ARR** ## **$4.76M** Conditional arithmetic only: 56 × $85,000. Not verified bookings or a forecast. The funnel inconsistency and unverified ACV distribution prevent treating this as an established revenue result. The $85,000 ACV makes inefficient technical evaluations economically consequential. Every PoV consumes technical resources, management attention, and opportunity capacity. However, without verified SE delivery costs and opportunity-level profitability, the financial cost of those evaluations cannot be quantified. ## **3.2 Sales cycle and deal velocity risk** Average sales cycle # **145 days** InfoSec inactivity # **45+ days** The InfoSec delay creates three operational risks. **A. Revenue realization delay** Extended security reviews postpone commercial decisions and potentially delay the conversion of qualified pipeline into booked ARR. **B. Forecast deterioration** An opportunity that has technically progressed but remains inactive in security review may appear healthier than its actual commercial position. AegisCloud should distinguish between: - Technical progress. - Security approval progress. - Commercial decision progress. - Contractual execution progress. These must be independently visible in CRM. **C. Increased opportunity-management burden** A 145-day sales cycle requires disciplined follow-up, stakeholder engagement, and accurate close-date management. The organization should avoid allowing stalled InfoSec opportunities to remain in active forecast categories without verified customer-side progress. ## **3.3 Discounting pressure** Longer enterprise sales cycles can create pressure to use commercial concessions to recover delayed opportunities. Potential manifestations include: - End-of-quarter discounting. - Pricing concessions to compensate for delayed procurement. - Extended contract negotiations. - Unstructured commercial approvals. - Concessions without corresponding contractual commitments. These are risks to investigate, not confirmed occurrences. The following metrics are required: | Metric | Current Status | Required Evidence | | ----------------------------- | --------------------------------------------- | ----------------------------------------- | | Average discount percentage | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | CRM opportunity and quote history | | ACV before and after discount | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | CPQ and signed contract records | | Discount approval compliance | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Deal desk approval records | | Gross margin | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Finance revenue and delivery-cost records | **Recommendation:** Implement discount governance tied to documented commercial justification, deal economics, and approval authority. Do not use discounting as a substitute for resolving security-review delays. ## **3.4 Customer acquisition efficiency** AegisCloud cannot establish whether its current enterprise sales model is economically efficient without validated acquisition and retention inputs. | Unit Economics Metric | Required Input | | ------------------------------------- | --------------------------------------------- | | Customer Acquisition Cost (CAC) | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | CAC payback period | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Customer Lifetime Value (LTV) | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Gross revenue retention (GRR) | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Net revenue retention (NRR) | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Logo churn | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Gross margin | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Fully loaded SE cost per PoV | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Sales and marketing acquisition spend | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | | Cost per SQL | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | **Unit economics conclusion:** The available data establishes funnel inefficiency and deal-velocity risk, but does not establish the profitability of the current acquisition model. Management should not approve aggressive sales or SE headcount expansion based exclusively on SQL volume. First establish the relationship between technical evaluation costs, commercial conversion, realized ACV, customer retention, and acquisition costs. # **4. 90-Day Prioritized Revenue Remediation Roadmap** ## **Phase 1: Days 1–30 — Immediate Triage** Priority: Stabilize the pipeline **Objective:** Stop avoidable SE capacity consumption, identify stalled revenue opportunities, and restore visibility into the actual state of the pipeline. | Concrete Operational Action | Accountable Role | Measurable Leading Indicator | | ------------------------------------------------------------------------------ | ---------------------------------- | ------------------------------------------------------------------------------------ | | Audit all active PoVs against mandatory qualification criteria. | Sales Leadership + SE Leadership | Percentage of active PoVs with documented qualification evidence | | Introduce temporary approval requirements before assigning new PoVs. | SE Leadership | Percentage of new PoVs approved against entry criteria | | Create an InfoSec stalled-deal task force. | CRO + Sales Leadership | Number of stalled opportunities with assigned internal owners and next actions | | Review all opportunities inactive for 45+ days in InfoSec. | RevOps + Account Executives | Percentage of stalled opportunities with verified customer-side status | | Audit SQL, PoV, Proposal, and Win definitions in CRM. | RevOps | Reconciliation of opportunity counts across funnel stages | | Identify PoVs with no documented success criteria or commercial decision path. | SE Leadership + Account Executives | Percentage of active PoVs with documented success criteria and commercial next steps | ### **Immediate deliverables** 1. Active PoV qualification audit. 2. InfoSec stalled-deal register. 3. CRM funnel integrity report. 4. Named ownership for stalled enterprise opportunities. 5. Temporary PoV approval policy. **Executive checkpoint:** The CRO should receive a consolidated report identifying which opportunities are commercially viable, which require intervention, and which should no longer consume SE capacity. ## **Phase 2: Days 31–60 — Process & Enablement Fixes** Priority: Improve conversion efficiency **Objective:** Standardize the enterprise sales process so that technical validation translates into commercial progression. | Concrete Operational Action | Accountable Role | Measurable Leading Indicator | | ------------------------------------------------------------------------------- | ---------------------------------------- | -------------------------------------------------------------------------------------------- | | Implement formal PoV entry and exit criteria. | SE Leadership + RevOps | PoV compliance with documented entry and exit criteria | | Develop a standardized PoV success-plan template. | SE Leadership | Percentage of PoVs with customer-approved success plans | | Introduce a pre-PoV commercial qualification checkpoint. | Sales Leadership | Percentage of PoVs with documented economic buyer and commercial decision process | | Create a centralized InfoSec response repository. | Security Leadership + SE Leadership | Availability and usage of approved security documentation | | Introduce an InfoSec readiness checkpoint during discovery. | Account Executives + Security Leadership | Percentage of qualified opportunities with identified security stakeholders and requirements | | Develop objection-handling and business-case enablement for enterprise sellers. | Sales Enablement | Completion and application of documented enablement processes | | Establish a formal SE capacity allocation process. | SE Leadership + RevOps | SE utilization by qualified versus unqualified PoVs | ### **Operational design: PoV governance** The PoV process should operate as a controlled stage gate. ## **Proposed PoV qualification workflow** **Enterprise SQL** Initial discovery and qualification **Commercial & Technical Qualification** Business problem, technical fit, stakeholders, and buying process **PoV Approval Gate** SE authorization required Documented success criteria and customer commitment **Technical PoV Execution** Measured against pre-agreed evaluation criteria **Commercial Readiness Review** Business case, economic buyer, procurement, and InfoSec **Commercial Proposal** Documented business justification and agreed next steps The critical operating principle is straightforward: **A technical PoV should not begin merely because a prospect requests one. It should begin because the opportunity has earned the allocation of SE resources.** ### **Immediate InfoSec process correction** Introduce an enterprise security-readiness package containing: - Approved security documentation. - Standardized questionnaire response ownership. - Security-review escalation contacts. - Customer-side review dependencies. - Required approval milestones. - Open-question and issue tracking. The goal is to identify security objections before they become late-stage blockers. ## **Phase 3: Days 61–90 — Governance & Forecasting Calibration** Priority: Institutionalize revenue discipline **Objective:** Establish an operating system that makes conversion, pipeline quality, sales velocity, and forecast accuracy measurable and accountable. | Concrete Operational Action | Accountable Role | Measurable Leading Indicator | | --------------------------------------------------------------------------- | ---------------------------- | -------------------------------------------------------------------------- | | Introduce weekly funnel-conversion reviews. | RevOps + CRO | Availability of stage-level conversion reporting | | Implement opportunity aging and inactivity alerts. | RevOps | Percentage of aged opportunities with documented actions | | Establish formal InfoSec stage tracking in CRM. | RevOps + Security Leadership | Percentage of opportunities with current security-review status | | Introduce standardized forecast categories supported by exit criteria. | Sales Leadership + RevOps | Percentage of forecast opportunities meeting documented stage requirements | | Establish PoV capacity and workload governance. | SE Leadership | SE capacity allocation by qualified opportunity | | Build a stage-level win/loss analysis process. | RevOps + Sales Leadership | Percentage of closed opportunities with documented win/loss reasons | | Establish discount and commercial approval governance. | CRO + Finance | Percentage of commercial concessions with documented approvals | | Reconcile quarterly funnel reporting against opportunity-level CRM records. | RevOps | Agreement between CRM source records and executive funnel reporting | ### **90-day governance dashboard** The CRO should receive one consolidated operating dashboard. | KPI | Current Baseline | Required Governance | | ---------------------------- | --------------------------------------------- | --------------------------------------------------- | | Quarterly SQL volume | 400 | Monitor volume and qualification quality | | SQL-to-PoV rate | 45% | Track by source and qualification outcome | | PoV-to-Proposal rate | 22% | Track by SE, segment, and opportunity qualification | | SQL-to-Win rate | 14% | Reconcile against sequential stage conversions | | Average sales cycle | 145 days | Track stage-level aging | | InfoSec inactivity | 45+ days | Track customer and vendor dependencies | | PoV qualification compliance | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Establish baseline from audit | | PoV success-plan compliance | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Establish baseline from CRM | | Proposal-to-Win rate | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Establish verified proposal and win cohorts | | Average discount | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Establish baseline from signed contracts | | Forecast accuracy | "INSUFFICIENT DATA — PROVIDE VERIFIED METRIC" | Compare forecast with actual bookings | # **5. CRO-Level Prioritization & Executive Accountability** The following priorities should govern management attention throughout the remediation period. | Priority | Revenue Problem | Executive Owner | Expected Operational Outcome | | -------- | -------------------------------------- | -------------------------------------- | -------------------------------------------------------------------- | | 1 | Unqualified PoVs consuming SE capacity | SE Leadership | Better alignment of technical resources with qualified opportunities | | 2 | Low PoV-to-Proposal conversion | CRO + Sales Leadership | Improved technical-to-commercial progression | | 3 | 45+ day InfoSec inactivity | Security Leadership + Sales Leadership | Better security-review visibility and reduced avoidable inactivity | | 4 | Inconsistent funnel reporting | RevOps | Reliable conversion and forecast reporting | | 5 | Unknown acquisition economics | Finance + RevOps | Verified CAC, payback, retention, and acquisition efficiency | ## **Executive decision register** The CRO should make five explicit operating decisions: 1\. **Approve PoV qualification governance.** SE resources should be allocated against documented opportunity qualification, not prospect interest alone. 2\. **Assign an accountable InfoSec escalation owner.** Security-review delays must have clear internal ownership and documented next actions. 3\. **Mandate CRM funnel reconciliation.** The 14% SQL-to-Win rate must be reconciled with the reported stage conversion figures before board-level forecasting uses the funnel. 4\. **Establish cross-functional revenue accountability.** Sales, SE, Security, and RevOps must operate against shared opportunity progression criteria. 5\. **Require Finance-validated unit economics.** Expansion decisions should incorporate CAC, gross margin, SE delivery costs, payback, and retention. # **6. Final Board-Level Assessment** # **AegisCloud Security: Revenue Diagnostic Verdict** Operational intervention required **Primary constraint** Inefficient conversion of enterprise technical evaluations into commercial opportunities. **Most immediate intervention** Introduce mandatory PoV qualification and SE resource-allocation governance. **Most significant deal-velocity exposure** 45+ days of inactivity during InfoSec reviews within a 145-day average sales cycle. **Most important data-integrity issue** Reconcile the 14% SQL-to-Win rate against the implied proposal volume. **90-day management objective** Establish a repeatable, measurable enterprise revenue operating model that connects qualification, technical validation, security approval, commercial progression, and forecasting. ### **Final CRO recommendation** AegisCloud should not respond to its current revenue constraints by simply increasing SQL generation or adding Solutions Engineering capacity. That would risk increasing the volume of opportunities entering an already inefficient process. The correct sequence is: 1. **Control:** Eliminate unqualified PoV resource consumption. 2. **Convert:** Improve the transition from technical validation to commercial proposal. 3. **Accelerate:** Bring InfoSec readiness into early-stage enterprise qualification. 4. **Measure:** Reconcile funnel definitions and establish stage-level accountability. 5. **Optimize:** Validate unit economics before expanding acquisition and technical delivery capacity. **The central management challenge is converting technical interest into commercially executable enterprise revenue.** Until AegisCloud fixes qualification discipline, technical-to-commercial progression, and InfoSec execution, additional pipeline volume alone will not establish a more predictable revenue engine. *Data integrity note: All calculations above are derived from the supplied figures. Operational root causes are hypotheses for investigation, not verified findings. No external benchmarks, competitor claims, or unprovided financial metrics have been introduced.* **Recommended next deliverable:** Convert this diagnostic into a CRO execution scorecard with named owners, CRM fields, stage-exit criteria, weekly review cadence, and board-reporting definitions.
GPT

B2b Saas Revenue Pipeline Audit Pro

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-6.1-SOL
Tested icon
Guide icon
4 examples icon
Free credits icon
Audit B2B SaaS revenue bottlenecks, stage conversion drops, and pipeline leakage. Built for CROs, RevOps leaders, and founders to turn raw funnel metrics into an executive root-cause diagnosis and 90-day remediation plan. Outputs Included: - Executive Funnel Health Scorecard - Stage-by-Stage Leakage & Friction Matrix - Unit Economics & Deal Velocity Risk Audit - 90-Day Prioritized Action Roadmap Strict zero-hallucination rules flag missing data instead of guessing.
...more
Added 1 day ago
Report
Browse Marketplace