Your HEPO partner helps turn an organisational need into a working application of the software. The partner carries the customer-facing engagement: discovery, definitions, implementation, training and the advisory work you agree. HEPO supplies the platform behind that arrangement.
Your organisation keeps responsibility for its purpose, its definitions and the decisions entrusted to its people. The partner helps you make that responsibility practical in the software.
Establish who does what
Before delivery, agree the scope, deliverables, customer contact, support intake and escalation route. Identify who operates the infrastructure, maintains integrations, manages access and applies updates. Include any product support or specialised development needed behind the partner's engagement.
The commercial model packages the platform with the partner's professional work. The agreement should make the service and licensing responsibilities clear, including what happens when the scope changes.
Ask for four concrete demonstrations
The evidence and interpretation. Open a representative reading or recommendation and follow its available basis. Examine the relevant definition, records, limitations and the next responsible decision.
Catalogue ownership. Review the supplied definitions and what your organisation has adopted or changed. The catalogue need not start empty. The important question is whether you understand, approve and can maintain the vocabulary used in your work.
Execution and audit context. Follow an allowed action and a denied action. Inspect the available record of who acted, what process ran and what happened. Agree actual audit coverage, access and retention for your needs.
The deployment boundary. Follow local inference and any external business connections. Establish where data and files live, who can access them and who carries operating responsibilities. Use the architecture reference with your technical reviewers.
Keep your working knowledge usable
Your authored vocabulary, work records, evidence and decisions should remain available to the people authorised to use them. Agree access, documentation, export or transfer arrangements and responsibilities for maintaining the deployment.
A partner's explanation should leave your team able to understand the work it will carry. That includes who can revise a definition, how a report is interpreted and where a decision still requires a person's judgment.
Plan continuity at the start
If the partner relationship changes, the intended model is a transition to another suitable HEPO partner, with HEPO facilitating the agreed handover. The organisation's definitions and records remain its working assets.
Continuity needs preparation: licensing, credentials, operating knowledge, support, backups and any custom work must be addressed in the transition arrangements. Local deployment alone is not a guarantee of uninterrupted service under every circumstance.
Expect a useful first engagement
Start with discovery and definitions, configure and demonstrate the application, run a first cycle, then undertake any response you choose. The first-engagement guide explains that sequence.
P&C can support cultural inquiry and development. Process Orchestration can carry a defined workflow. Simulation & Gamification can help your people explore or rehearse. Choose the scope that serves your work, and review whether it continues to do so.