The Six-Month Warning: Forecasting Revenue Risk from a Consideration Trend
Objective: Given a rolling four-quarter brand tracking trend and the lesson's 6-12 month lead-lag principle, forecast when a consideration decline is likely to hit renewal revenue and decide how urgently to escalate.
You're the brand insights lead at Grab Holdings. Consideration for Grab's ride-hailing vertical has been sliding since Q1 while a regional competitor gains ground. Leadership wants to know if this is worth interrupting the roadmap for.
Use the lesson's 6-12 month lead-lag window and the cadence guidance to forecast the revenue-risk window and recommend an escalation timeline.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, sufficient for a simple date-range projection off quarterly data
The process
2 steps
Step 01 of 02
Research cited in the lesson shows brand metrics like consideration typically precede sales figures by 6-12 months in consumer categories, giving teams an early warning window before revenue is hit.
Grab's consideration score dropped from 52% (Q1) to 43% (Q4), a 9-point decline over three quarters. Using the 6-12 month lead-lag window, by when should leadership expect to see this show up in renewal or repeat-usage revenue if nothing changes?
Procedure
- Chart the consideration trend by quarter and mark the quarter the decline began (Q1)
- Apply the 6-12 month lead window to that starting quarter to calculate the earliest and latest revenue-impact dates
- Cross-check against the competitor's rising trend over the identical period to confirm this is a relative, not just absolute, decline
- Write the forecast window as a date range, not a single date
Consideration: Q1 52%, Q2 49%, Q3 46%, Q4 43% (decline started Q1) Competitor (GoJek): Q1 46%, Q2 47%, Q3 49%, Q4 50% Lead-lag window: 6-12 months from Q1 start = revenue impact expected between Q3 and Q1 of next year
Healthy
The forecast window is flagged to leadership at least one full quarter before the earliest revenue-impact date, giving time to adjust creative or spend before the income statement shows it.
Unhealthy
Waiting for the actual renewal-rate dip to appear before escalating, which per the lesson's 6-12 month lag means the decision window to cheaply course-correct has already closed.
What this means
A 9-point relative consideration swing over three consecutive quarters, with the decline starting in Q1, means the revenue-risk window opens as early as Q3 this year. Escalating now, not after Q3 numbers land, is what makes the forecast useful.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Consideration decline exceeds 5 points over 3+ quarters relative to the named competitor | Escalate to leadership immediately with the forecast window, not after the next wave | half day |
Step 02 of 02
The lesson's cadence table recommends monthly tracking for fast-moving consumer categories and notes that monthly cadence catches trust erosion roughly two reporting cycles earlier than quarterly.
Grab is currently tracking quarterly. Given the recommended cadence table, should the ride-hailing vertical move to monthly tracking, and what does that change about the forecast window?
Procedure
- Check the lesson's cadence table for Grab's category (fast-moving consumer/superapp usage)
- Compare current quarterly cadence to the monthly recommendation
- Recalculate how much earlier a monthly cadence would have caught the Q1 inflection point
Current cadence: quarterly (4 waves/year) Recommended: monthly for fast-moving consumer categories Estimated earlier detection: ~2 reporting cycles, meaning the Q1 inflection could have been flagged in month 2 instead of the Q1 wave
Healthy
The team moves to monthly tracking for the affected vertical after this incident, shortening future detection windows.
Unhealthy
The team stays quarterly and re-discovers the same lag problem on the next slow-moving trend.
What this means
Cadence is not a formality, it directly sets how much of the 6-12 month lead time is actually usable before revenue impact.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| A category matching the table's 'monthly' recommendation is still tracked quarterly | Propose moving that vertical to monthly cadence in the next budget cycle | 30 min |
Final deliverable
A written forecast memo giving a specific revenue-impact date range, the evidence behind it, and a cadence recommendation.
See a reference example
Forecast memo, Zendesk support-suite consideration trend (excerpt) Consideration fell from 44% to 34% between Q1 and Q4 while Freshdesk rose from 38% to 43% over the same window. Applying the 6-12 month lead-lag window from the Q1 inflection point, expect renewal-rate impact between Q3 this year and Q1 next year. Recommend moving from quarterly to monthly tracking for this segment to catch the next inflection ~2 cycles earlier.
Success criteria
You're done when you can:
- Forecast window is expressed as a date range derived from the 6-12 month lag, not a single guessed date
- Uses the competitor's opposite trend as corroborating evidence, not just Grab's own numbers
- Cadence recommendation is grounded in the lesson's cadence table, not invented