Revenue architecture is an engineering problem, not a tool choice.
Winning by Design’s recurring-revenue approach includes the work that follows acquisition. We examine how to adapt this framework to different revenue models.
Last reviewed:
Winning by Design treats acquisition, post-sale usage, retention and expansion as connected processes for recurring revenue. Hornpiper uses this perspective to examine data, ownership and handoffs, adapting stages and metrics to the company’s revenue model.
Shared definitions and responsibilities
- Customer and account definition
- Lifecycle stages
- Entry and exit criteria
- Ownership and service level
- Conversion, velocity and capacity measures
Local optimization can hide a system constraint.
More MQL volume can overload qualification. A shorter sales cycle can admit the wrong customer. Faster onboarding can weaken usage quality. Every improvement needs to be measured through its effect on the next stage.
The existing operation determines the implementation order.
- Use reliable existing processes and data rather than rebuilding them.
- Where records are missing, a bounded CRM or reporting implementation can support the investigation.
- Define the task, owner, data and acceptance conditions together for integrations and automation.
- Choose the sequence according to risk, dependencies and learning needs; no single order applies to every engagement.
Not every revenue model operates like a subscription.
Renewal and expansion may matter in a subscription business. Project delivery, follow-on scope and repeat engagements raise different questions, as does repeat purchasing in a transactional business. Use measures such as ARR or NRR only where the revenue model and data definitions fit. This adaptation is Hornpiper’s application advice, not a claim that the framework produces the same outcome in every business.