We · Insure
Keep the product relationship working through risk and change.
Status Planned service direction. No live service, enrolment or purchase is available on this site.
What the status labels meanOn this page
The sale is a beginning.
A company needs more than a product delivered once. It needs service, repair, upgrades and a clear allocation of responsibility as the product ages. Menexus We starts from that ongoing relationship.
From supply to a responsible end.
- 01
Specify and source
Define the product, intended use, dependencies and supply responsibilities.
- 02
Deliver and maintain
Set acceptance criteria, maintenance duties, incident handling and who the customer can hold responsible.
- 03
Refresh and recover
Declare hardware and software refresh rules, compatibility, downtime expectations and recovery procedures.
- 04
Return or continue
Make renewal, transfer, purchase options if any, data export, asset return and end-of-life responsibilities explicit.
The first proposed programme: XAAS.
Product-as-a-service means an ongoing agreement rather than a one-off sale. The proposed programme combines delivery, maintenance and a declared upgrade path. No subscription or fleet is offered here.
Before a pilot, name who owns and finances the fleet, who supplies and maintains it, who bears loss, and what happens at termination. Prices and service commitments follow that definition; none is published here.
Useful for the whole life of the product.
Three proposed applications—not three available subscriptions. Each needs a clear service responsibility and a reason to choose an ongoing agreement.
The test is not whether a device can be put on a subscription. It is whether a continuing service solves a real problem better than buying the device and arranging ordinary support.
Electric mobility
An e-bike is useful when it is ready to ride. A programme could bring servicing, battery care and breakdown handling into one agreement. It must name the vehicle owner, maintenance provider, any replacement provision, damage responsibilities and return conditions.
Wearables
The relationship should last beyond the unboxing: repairs, battery replacement and software support. An ongoing agreement only makes sense if that support is useful. Define what data is needed, who may receive it, and how the device, account and permitted records are handled when you leave.
Humanoid robots
Start with one workplace task—not a promise of general autonomy. Before a pilot, establish task suitability, human supervision, stop conditions, maintenance and incident responsibility. Equipment ownership, operating limits and return arrangements must be clear before use.
Insure is not an insurance licence.
Menexus is not presented as an insurance carrier. Whether a proposed activity involves intermediation or another regulated role depends on the actual workflow and jurisdiction.
Calling a service a connector—or describing it as administration of existing cover—does not establish a regulatory safe harbour. Insurance-related activity remains held for qualified review, permissions and named-provider responsibility before any offer.
Keep the agreement checkable.
Cortex holds the permitted record of evidence and commitments. Menexus delivers and coordinates the services it expressly contracts to provide, with each provider’s responsibilities identified.
A service programme is a versioned view of existing evidence, commitments and permissions. It does not create a new kind of authority or allow an AI to sign.
Company services do not include access to personal genetic evidence. Any other cross-service data use requires its own lawful purpose and applicable permission.
An exit you can plan around.
The agreement must distinguish customer property from financed or leased equipment. Define returns, outstanding obligations, permitted data export and revocation. Do not promise ownership or departure with assets the customer does not own.