Prospecting
AuraScore 81/100

Enterprise Account Propensity and Net Present Value Assessment

Quantify enterprise account viability using financial disclosures, tech telemetry, and discounted cash flow modeling.

Use this template when evaluating high-ACV target accounts requiring analytical scrutiny before committing dedicated account-based sales resources. It is ideal for strategic sales reps and revenue architects assessing deal solvency and pipeline yield.

Template

Role: Quantitative Revenue Architect specializing in high-ACV enterprise account scoring and valuation modeling.

Context

  • Target organization under evaluation: {{target_account_name}}
  • SEC 10-K and financial report disclosures: {{financial_disclosures}}
  • Telemetry and tech-stack maturity data: {{tech_stack_telemetry}}
  • Benchmark win-rate and ACV historical dataset: {{historical_deal_metrics}}
  • Corporate hurdle rate and discount rate for valuation: {{discount_rate}}
  • Estimated industry cohort churn benchmark: {{churn_benchmark}}

Task

Perform a rigorous quantitative propensity and net present value (NPV) analysis for {{target_account_name}} to determine whether outbound account-based resources should be allocated, synthesizing mathematical probability scoring with fundamental financial analysis.

Method

  1. Extract capital expenditure flexibility and operating margin pressures from {{financial_disclosures}} to assess macroeconomic purchasing readiness.
  2. Map {{tech_stack_telemetry}} against our solution prerequisites to compute a composite Technical Fit Index (0.0 to 1.0).
  3. Cross-reference {{historical_deal_metrics}} to establish baseline probability coefficients for initial discovery-to-close conversion.
  4. Calculate the risk-adjusted Expected Contract Value (ECV) using probability-weighted ACV models.
  5. Model multi-year pipeline return by calculating the 3-year Expected Customer Lifetime Value (LTV) discounted at {{discount_rate}} and adjusted for {{churn_benchmark}}.
  6. Determine an Account Attractiveness Score (AAS) combining financial solvency, technical readiness, and expected yield.
  7. Run sensitivity testing across bear, base, and bull adoption scenarios for {{target_account_name}}.
  8. Synthesize quantitative findings into an actionable prospecting go/no-go recommendation with designated entry triggers.

Constraints

  • MUST show all intermediate calculations including formula definitions for ECV and AAS.
  • MUST classify the target account strictly into Tier 1 (Strategic), Tier 2 (Programmatic), or Tier 3 (Nurture/Disqualify).
  • MUST NOT rely on ungrounded qualitative assumptions without anchoring to {{financial_disclosures}} or {{historical_deal_metrics}}.
  • Limit total analysis to under 800 words while maintaining dense quantitative rigor.

Output format

  • Section 1: Executive Propensity Matrix (AAS Score, Tier Classification, Go/No-Go Decision)
  • Section 2: Mathematical Valuation Model (Formulas, Inputs, ECV, and 3-Year Discounted LTV)
  • Section 3: Scenario & Sensitivity Analysis (Bear/Base/Bull Table with probability weights)
  • Section 4: Prospecting Hypotheses & Entry Triggers (Three data-backed outbound hooks)

Self-review

  • Confirm all mathematical formulas reflect the provided {{discount_rate}} and {{churn_benchmark}}.
  • Verify that technical fit and financial solvency are calculated independently before aggregation.
  • Ensure every outbound trigger references a specific line-item or metric from the financial disclosures.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-prospecting
complex-reasoning-analysis-math
account-scoring
financial-analysis
enterprise-sales