The platform budget should not begin with a feature list.
It should begin with rights.
A consulting firm may own the method, model, diagnostic or agent and still lose the economics around it. The client may own the workflow. A model provider may own discovery. An enterprise platform may own context. The product may work while the control point moves elsewhere.
The rights-retention checklist
| Right | Question to ask | Preserving decision | Failure mode |
|---|---|---|---|
| Distribution | Where will the client discover, invoke and combine the capability? | Decide whether the offer must live in a firm-controlled environment, a client environment, a marketplace or a portable module with branded support. Preserve ranking, bundling or direct-client access where the economics require it. | The firm owns useful code, but another platform controls discovery, substitution and the client relationship. |
| Client context | What data, workflow state, permissions and decision history make the answer valuable? | Specify the minimum context the product needs, the lawful basis for using it, the integration pattern and the data boundaries the client will accept. | The product is knowledgeable but operationally peripheral because the useful context sits elsewhere. |
| Improvement | What will the firm learn from repeated use? | Contract for client-authorised feedback, evaluation results, outcome evidence or privacy-preserving telemetry. Build the product so learning returns to the firm without violating confidentiality. | The client receives value while the platform owner or client accumulates the learning loop. |
| Accountable endorsement | Who stands behind outputs used for consequential decisions? | Define reviewed, unreviewed and expert-endorsed states. Price expert review separately when endorsement is the product. | The client cannot tell what the firm stands behind, and the offer becomes a generic tool rather than an advisory relationship. |
The funding gate
Before approval, the platform sponsor should answer four questions in writing.
Which rights create the business? A self-service diagnostic, a workflow agent and an expert-endorsed decision product do not need the same rights.
Why will the client grant them? Firm ambition is not enough. The client needs a reason: better assurance, better adaptation, less integration burden, clearer accountability or lower operating cost.
What revenue are we willing to shrink? If the platform works, some traditional work should become smaller. The business case should say which revenue declines, which revenue replaces it and when.
What survives outside our interface? If the client or software provider owns the environment, the product should still preserve the right that matters most: context, improvement or endorsement.
Clause and design prompts
Use these prompts before procurement, product design and pilot contracting separate.
- Distribution: Does the agreement preserve direct access to the buyer or decision owner?
- Context: Does the design specify exactly which client data can be used, retained or excluded?
- Improvement: Can the firm learn from deployment without retaining confidential client material?
- Endorsement: Does the product state when output is machine-generated, reviewed or institutionally endorsed?
- Economics: Does the P&L separate product revenue, expert-support revenue and cannibalised project work?
The decision is not whether to build a platform.
It is which rights the firm refuses to give away.