Skip to content
Academy
Marketing Academy · Field Work●Growth Marketing
CoreBuild the Asset· 50 minutes

Building RateGain's Champion-Led Expansion Loop Map

RateGain Travel Technologies

Objective: Using the lesson's Inputs/Actions/Outputs/Feedback framework, build a champion-led expansion loop map for RateGain's RevGain Insights add-on, from a single hotel revenue manager's adoption to a multi-department contract expansion.

You're on the growth team at RateGain Travel Technologies, mapping how a single hotel revenue manager's use of RevGain Insights could expand into a property-wide, then group-wide, RateGain contract.

Fill in each stage of the Inputs/Actions/Outputs/Feedback framework with RateGain-specific detail, then write the one-sentence business case a champion would need to justify expansion to procurement.

Before you start

What you'll need

Free path (everything below is enough to finish)

FreeBuild the loop map and draft the business case

Free, sufficient for a 4-row framework map and a short paragraph draft

The process

2 steps

Step 01 of 02

Mapping a champion-led expansion loop using the Inputs/Actions/Outputs/Feedback framework

The lesson's mapping framework breaks any B2B loop into Inputs (what brings a customer in), Actions (the smallest step to a moment of truth), Outputs (what changes after that moment), and Feedback (what compels repeating the action).

A single hotel revenue manager starts using RevGain Insights for demand forecasting. Map what input brought her in, what action created her moment of truth, what output resulted, and what feedback mechanism would pull in the GM and then the ownership group.

Google Sheets— Build a 4-row template, one row per framework stage, filled with RateGain-specific detail.

Procedure

  1. Row 1, Input: what search or referral brought the revenue manager to RevGain Insights
  2. Row 2, Action: the smallest action that produces her moment of truth (a forecast that changes a real pricing decision)
  3. Row 3, Output: what changes in her world after that moment (a documented revenue lift she can show her GM)
  4. Row 4, Feedback: what compels the GM, then ownership, to expand the contract
Sample output
RevGain Insights champion-expansion map

INPUT: Revenue manager finds RevGain Insights via a RateGain webinar on 2026 demand forecasting
ACTION: Runs a 7-day demand forecast against an upcoming low-occupancy week, adjusts room rates accordingly
OUTPUT: Documented 6% RevPAR lift for that week, screenshotted into her monthly GM report
FEEDBACK: GM asks for property-wide access; group ownership sees the RevPAR lift across 3 properties and asks procurement to add group-wide seats

Healthy

Each stage produces a concrete, RateGain-specific artifact (a webinar name, a documented RevPAR number, a named stakeholder) rather than a generic restatement of the framework.

Unhealthy

Filling in the four rows with abstract statements like 'user finds value' and 'company expands' with no specific input, action, or number.

What this means

A loop map is only useful if it's specific enough to design an actual campaign around, a vague map can't tell you which webinar to fund or which GM report template to build.

So what do I do about it?

SymptomActionEffort
Output row has no documented number the champion can show upwardBuild a one-click 'RevPAR impact' export inside RevGain Insights the champion can screenshotdev ticket
EitherYou or a developer can handle this, depending on your access.

Step 02 of 02

Writing a champion's expansion business case in ROI terms, not feature terms

The lesson's Salesforce example shows a champion's expansion succeeds because she 'creates a business case, demonstrates ROI to procurement' rather than asking for a feature; the lesson's four loops all monetize on business value, not on excitement.

Using the documented 6% RevPAR lift from Step 1, write the one-paragraph business case the revenue manager would actually bring to her GM to justify expanding RevGain Insights property-wide.

Google Sheets— Write the business case paragraph in a new sheet row, then check it against the ROI-vs-feature test.

Procedure

  1. State the documented result first (the 6% RevPAR lift), not the tool's features
  2. Translate the percentage into a rupee figure the GM can defend to ownership
  3. Name the specific expansion ask (property-wide seats, then group-wide)
  4. Check: does the paragraph mention a feature name before it mentions the ROI number? If yes, rewrite
Sample output
Business case draft:
'RevGain Insights produced a 6% RevPAR lift on one low-occupancy week, worth an estimated ₹4.2L in incremental revenue at this property alone. Rolling it out to all 40 rooms and all revenue-managed rate categories property-wide would let us apply the same forecasting discipline to every low-occupancy week this quarter, not just the one we tested.'

ROI-before-feature check: PASS, first sentence is the number, not the tool.

Healthy

The business case leads with a rupee-denominated result and only mentions the product name in service of that result.

Unhealthy

A business case that opens with 'RevGain Insights has powerful AI forecasting features' before ever stating a number.

What this means

Procurement funds ROI, not features, a champion who leads with the number gets approved faster than one who leads with a feature list.

So what do I do about it?

SymptomActionEffort
Business case opens with a feature description instead of a numberRewrite so the first sentence is always the documented result5 min
YouYou can do this yourself, no engineering access required.

Final deliverable

A completed Inputs/Actions/Outputs/Feedback loop map plus a one-paragraph, ROI-led expansion business case.

See a reference example
Sample output
Utkarsh Small Finance Bank champion-expansion map (excerpt)

INPUT: Branch manager finds the Utkarsh digital lending dashboard via an internal training session
ACTION: Approves 15 MSME loans in a week using the dashboard's faster risk-scoring flow
OUTPUT: Documented 3-day reduction in average approval time, reported to the regional head
FEEDBACK: Regional head requests the dashboard for 8 more branches in the cluster

Success criteria

You're done when you can:

  • All four framework stages contain RateGain-specific, non-generic detail
  • The business case leads with a documented ROI number before mentioning any feature name