A HEPO partnership is a professional-services model built around the platform. Your firm delivers the agreed customer engagement; the software supports the assessment, implementation, review and development work included in it.
The commercial structure puts the platform licence beneath the partner's package: the partner contracts and invoices the customer for the agreed offering, while HEPO supplies the licence to the partner. Exact terms, responsibilities and pricing belong in the arrangement agreed for that engagement.
What the package contains
| Work | Concrete deliverable |
|---|---|
| Assessment and discovery | A defined question, scope, stakeholders and evidence-readiness account; a reading only when its prerequisites are ready |
| Catalogue facilitation | Client-approved definitions, evidence scope and review responsibilities |
| Implementation | Configured environment, agreed integrations, access, validation and handover |
| Reading and review cycles | Supported readings with their basis, an interpretation discussion and recorded next decisions |
| Advisory and programme work | A chosen response, development or process-change activity, and a plan for subsequent review |
| Simulation and learning design | A declared scenario or participatory activity, facilitation and a debrief where that offering is in scope |
A partner should scope what its people will actually do, including preparation, configuration, training, review and follow-up. Not every engagement needs every service.
Where recurring work can arise
The first engagement establishes definitions, working records and a way to review them. A later period, another cohort or a changed workflow may need a further reading and interpretation. A selected response may need programme design, facilitation or an examination of outcomes.
Familiarity with the client's vocabulary and context can make the original partner well placed to do this work. Continuation still depends on the client's need and the value of the service. The catalogue remains the client's asset; knowledge transfer and continuity should be part of delivery.
Distinguish the responsibilities behind the package
HEPO maintains the platform under the agreed product arrangement. The partner carries its professional work and customer-facing coordination. The customer or selected infrastructure operator carries the operating responsibilities assigned to it.
The package should therefore explain software updates, custom extensions, support intake, escalation, infrastructure operation and recovery. A local deployment does not by itself remove a partner's obligations, and a platform licence does not describe every service needed to operate the environment.
Price a real scope
Use the first-engagement stages to identify people, effort, dependencies and acceptance evidence. Separate initial work from any agreed recurring review. Include the platform licence and the support arrangements required to carry the engagement.
This page describes the revenue structure. It does not publish a price list, margin, guaranteed renewal or return on investment. Those figures require the proposed scope and current commercial terms.