Fictional example assumptions
Reporting periods, calculations, and test rules behind the illustrative dashboards.
All numbers, periods, thresholds, and decisions on this page are invented for the worked example. They are not reporting-frequency recommendations or company results. Use the separate metric definitions for ongoing reporting.
Calendar and scope
The recurring Executive and Marketing views report August 2026, reviewed as of August 31. Growth includes H1 actuals and the year-end outlook; coverage looks ahead to Q4; acquisition payback uses completed Q2 versus Q1 cohorts. Each card states its own window. The Operating View covers August 24–30 and is a subset of August.
The pilot acquisition period is July 1–August 11. Outcomes are observed through August 31 in the example. Each evaluation receives 90 days of follow-up, with the last possible evaluation-start cohort reaching 90 days on November 9. Pilot totals must not be added to monthly totals.
Financial and pipeline reconciliation
| Item | Calculation or scope |
|---|---|
| H1 ARR | Opening $20M + $4.4M new-customer ARR + $1.2M expansion − $1.2M contraction/churn = $24.4M. Net new ARR is $4.4M versus $5M planned |
| Year-end outlook | Original $27.6M outlook + $150K live ARR from three pilot customers = $27.75M; $30M target leaves $2.25M gap. All other forecast assumptions held unchanged |
| Pilot purchases | Four contracts at $50K = $200K contracted recurring annual value. Three live = $150K ARR; one $50K contract awaits activation. These contracts were not included in the original outlook |
| August pipeline creation | Core 18 opportunities / $2.1M + pilot 6 / $0.3M = 24 / $2.4M versus 30 / $3M plan. Both measures are 20% below plan |
| Pilot creation across months | 12 evaluations at $50K entry value = $0.6M. Six entered in July and six in August; the $0.6M is not all August creation |
| Coverage | $5M eligible open annual recurring contract value / $2M remaining Q4 new-business bookings target = 2.5×. Internal 3.5× requirement is an illustrative planning assumption, not a standard. The denominator is not the net ARR forecast gap |
| August win rate | 10 wins / (10 wins + 20 losses) = 33.3%, displayed as 33%. July had 16 / 40 = 40%. August includes the pilot's four wins and two losses. Closed records can have been created before August |
| Sales cycle | Median days from qualification to win: August 84, July 70. Won-only measurement needs open-aging and segment-mix context |
| Monthly spend | August $300K actual and budget includes $24K pilot and $276K other work. July contains the remaining $36K of the pilot's $60K total. These period allocations are separate from the paid/community channel split |
| CAC payback | Q2 acquisition cohort: $900K allocated acquisition cost / ($800K acquired ARR / 12 × 75% gross margin) = 18 months. Q1 comparable cohort: 15 months. This is not the six-week pilot's CAC |
Marketing and operating measures
| Item | Calculation or scope |
|---|---|
| August qualification | 24 admitted evaluations / 120 substantive sales conversations = 20%; July 30 / 120 = 25%. Observation and admission status are as of each month-end, not a final long-horizon conversion comparison |
| August website conversion | 800 inquiries / 40,000 relevant visits = 2%; July 1,000 / 40,000 = 2.5%. Conversations are a subset of inquiries; inquiries do not all become opportunities |
| Stalled evaluations | 8 of 40 open at August 31 have no completed milestone for 30 days. The 40 are a balance across multiple start cohorts, not the month's 24 new entries |
| Share of Search | August 1,200 / 50,000 = 2.4%; July 1,000 / 50,000 = 2%. Fixed comparable competitor set, geography, terms, and source. +0.4 percentage points. Invented comparable volumes, not independently normalized Trends scores |
| Direct traffic | August 4,800 versus July 4,000; these visits are subsets of the 40,000 respective monthly visits |
| Weekly website conversion | August 24–30: 200 inquiries / 10,000 visits = 2%; preceding week 2.5%. The weekly counts are subsets of August totals |
| Weekly paid CTR | 1,500 clicks / 100,000 impressions = 1.5%; preceding week 2%. Paid clicks are not the total visit count |
| Weekly qualification | 6 / 30 conversations = 20%; preceding week 25%. Of 20 paid conversations reviewed, eight involved unsupported requirements. These records are within the recurring weekly population, not necessarily pilot records |
| Weekly follow-up | 26 / 30 due handoffs = 86.7%, displayed as 87%; the scenario's service target is 95%. This is distinct from the pilot's community handoff measure |
Pilot criteria and observed results
Before launch, the company specifies six purchases within 90 days of each evaluation start as the primary commercial criterion. Guardrails include at least $300K contracted annual value, maximum $60K program spend, one shared engineering sprint, no customer-specific feature commitments, and current activation capacity of four customers per month. These thresholds are fictional choices, not recommended benchmarks.
At August 31, the interim checkpoint of 12 evaluations is met. Four purchases and $200K contracted recurring annual value do not meet the final criteria yet. The observation window remains open, and delivery effort is still being assessed. The proper status is “not yet established,” not “successful” or necessarily “failed.” There is no statistical causal-lift claim.
| Pilot channel | Spend | Conversations | Evaluations | Purchases | Ended without purchase | Open |
|---|---|---|---|---|---|---|
| Paid campaigns | $36K | 40 | 4 | 1 | 1 | 2 |
| Community outreach | $24K | 20 | 8 | 3 | 1 | 4 |
Program cost per evaluation: $9K paid and $3K community. Six of 20 community handoffs missed the agreed two-business-day target; 14/20 = 70% met it. These are diagnostic comparisons between different audiences, not causal attribution or full acquisition cost.
How the warning travels
The illustrative sequence begins with weekly operators spotting poorer response and fit, then Marketing reviewing pipeline risk and recommending the pilot. The August pages provide a later recurring snapshot and progress review of that pilot. Earlier warning is a possible benefit of connected reporting, not a guarantee that leading indicators predict future revenue.