RICHU field notes / Growth partnerships

Define incremental value before sharing it

Align on what counts as incremental value, from the baseline and attribution boundaries to the accounting period.

Start with an agreed baseline

A rise in total sales does not mean a partnership generated the same amount of incremental value. Seasonality, existing customers, organic traffic, price changes and promotions can all affect results. Choose a comparable period and record market, channel, product and budget conditions before starting. Both parties must agree the baseline and how to reassess it after significant business changes.

Document scope and contributions

A new market, category or channel and an improvement to an existing workflow are different projects. Define the scope, then specify who provides people, assets, systems, supply chain and operating budget. Where existing teams or other providers are involved, assign responsibilities clearly to avoid double counting.

Consider revenue and costs together

Additional revenue does not necessarily mean additional profit. Advertising, discounts, refunds, fulfilment and platform fees affect results. Choose metrics aligned with the project, and agree cost definitions, data sources, review methods and the measurement window. Do not rely on one headline metric simply because it is easy to increase.

Give the pilot a clear exit

Agree review points, conditions for continued investment and a suspension mechanism within a limited pilot. Even if expected growth does not materialise, reusable data, workflows and review records should remain. Shared-value partnerships require ongoing understanding of risk, investment and the value created.

RELATED SOLUTION

Build your next growth opportunity

Explore how this method could apply to your business, including eligibility and partnership options.

Explore the related solution

PUT IT INTO PRACTICE

Turn reading into a bounded experiment.

Choose one task

Define the problem, owner, inputs and outputs. Do not begin with broad automation.

Set one check

Use a standard example and an exception example to verify facts and approvals against business requirements.

Make one decision

Expand when use is reliable. Pause when information or permissions are missing, and name the person responsible for resolving the gap.

A CONVERSATION THAT MOVES YOU FORWARD

Start with a real business question.
Explore what comes next.

Tell us about your business, team and goals.
Let us find the right place to start.

Discuss a partnership