01 / Agree the baseline
Define the business period, markets, channels and categories, including how exceptional changes will be handled.
PARTNERSHIP / SHARED VALUE
Project delivery, ongoing operations, incremental value sharing and joint development all start with a real business need. The right structure depends on business foundations, resources and scope.

PARTNERSHIP MODELS
| Model | Best suited to | What we agree together | Commercial basis |
|---|---|---|---|
| Discovery / advisory | Clarifying business challenges and implementation priorities | Diagnosis report, scenario map and roadmap | Defined discovery scope |
| Project implementation | Delivery projects with reasonably clear objectives and scope | Milestone deliverables, trial operation and handover | Milestone-based payments |
| Subscription + operations | Ongoing use, maintenance and improvement | Usage scope, operating cadence and maintenance responsibilities | Agreed service periods |
| Base fee + incremental value sharing | Growth projects with a transparent baseline and shared investment | Resources, attribution, accounting, settlement and exit | Delivery fee plus agreed incremental returns |
| Joint development | Business parks, industry clusters and ecosystem partners | Shared audiences, demonstration projects and replication model | Negotiated resources, rights and responsibilities |
INCREMENTAL GROWTH
Define the business period, markets, channels and categories, including how exceptional changes will be handled.
Agree team, supply-chain, budget and systems contributions, with an owner on each side.
Specify metrics, costs, attribution scope, data sources and review methods.
Settle on an agreed schedule, review regularly and define conditions for expansion, suspension and exit.
Eligibility and sharing terms are negotiated after discovery and data verification. Formal agreements govern the actual arrangement.
SCOPE BEFORE PRICE
Business complexity, data readiness, integrations, duration and team training all affect the resources required. Smaller teams can start with a single workflow.
Distinguish learning memberships, single-workflow pilots, enterprise implementation and ongoing support. Discovery defines scope; a pilot tests feasibility; implementation builds team capabilities. See our services and pricing pages for proposed budgets and boundaries. Final quotes follow scope agreement.
Your business type, target markets, team, main systems, the problem to improve and an indicative investment range. Passwords, customer lists and full financial records are not needed for an initial conversation.
Agree the change process and review points at the outset. Before adding channels, systems, budget or workflows, assess the impact and update scope, deliverables and commercial terms.
FIT BEFORE COMMITMENT
An established trading record, verifiable data definitions, dependable fulfilment and both parties willing to assign owners and pilot resources.
No available baseline or operating budget, an expectation of guaranteed returns, or a desire to transfer all business risk. Discovery or independent learning may be a better starting point.
After discovery, specify inclusions, exclusions, each party’s deliverables and acceptance samples. If a stage does not meet the agreed conditions, expansion can stop.
A CONVERSATION THAT MOVES YOU FORWARD
Tell us about your business, team and goals.
Let us find the right place to start.