06 / Partnerships

Choose how much of the engine you want to own.

The right structure depends on product ambition, internal capability, speed, capital model and the level of ongoing operation you want from us.

Discuss the model Compare options

01 / Build & transfer↗

You operate the platform.

We design and engineer a defined product, document the system and transfer the agreed deliverables to your organization or technology team.

Best for firms with technical ownership
Commercial scope and acceptance milestones
Handover, documentation and enablement
Optional post-launch support

02 / Managed platform↗

You own the brand. We run the engine.

We build, host, monitor, support and iterate the platform while the client experience remains entirely under your identity.

Best for speed without an internal product team
Recurring platform and support agreement
Defined service levels and change process
Exit, export and transition rights in contract

03 / Co-delivery↗

Your team and ours share the operating model.

The firm controls legal delivery and selected client functions; we provide technology, automation and agreed operational capacity.

Best for complex or fast-growing service lines
Clear responsibility matrix
Shared quality and performance review
Expandable modules and operations

04 / Channel enablement↗

Give partners a product they can confidently offer.

We create the branded referral, member or employer experience and route demand into your firm’s workflow.

Best for associations, benefits and advisor channels
Partner portals and attribution
Eligibility and jurisdiction rules
Program analytics and support workflows

Commercial principles

No mystery math.

A proposal should state what drives the price and which costs may change with usage. We do not publish invented packages before understanding the system.

Scope and integration depth

How many journeys, roles, systems and jurisdictions?

Hosting and support responsibility

Who operates, monitors and responds?

AI and third-party consumption

Model, storage, messaging, signature and API usage.

Ownership and licensing

Source, configuration, reusable components and exit rights.

Managed service volume

Work type, turnaround, review and exception complexity.

What every proposal includes

The terms that prevent future surprises.

Deliverables and explicit exclusions
Milestones, dependencies and acceptance
Data location, access and export
Code, configuration and license treatment
Third-party services and usage costs
Support, incident and change responsibilities
Confidentiality and subcontractor disclosure
Termination and transition assistance

Commercial FAQ

Before numbers, align the model.

Do you offer revenue share?

It can be considered when the service, distribution channel, responsibilities and unit economics are sufficiently clear. Revenue share does not remove infrastructure, support or third-party costs, so the complete model must be evaluated.

Can we license only one AI module?

Yes, where the module has a well-defined input, review path and integration point. A focused module is often a lower-risk way to validate adoption before a larger platform.

Is there a long-term contract?

Build-and-transfer work is typically milestone-based. Managed services require an operating term appropriate to the infrastructure and support commitment. The exact term, renewal and exit mechanics are stated in the proposal.

Can our IT team review the architecture?

Yes. We expect security, privacy and technology stakeholders to review the design. Evidence requirements should be raised during discovery so they become planned deliverables.