Skip to content
  1. Home
  2. Our Engagement Model

Engagement model

Our engagement model

How a project runs from the first call to maintenance, what is delivered at each step and who is responsible for what, in one place.

Steps

From the first call to maintenance

  1. First call

    We talk about your need, your process and where your data lives. If you need an NDA, just tell us before the call. You leave with a clear answer on whether the problem can be solved and a proposed first step.

  2. Scope and proposal

    We review the process and systems with you and put the scope in writing: deliverables, the success criterion, responsibilities and which data goes where. We share the project timeline and fee once the scope is clear.

  3. Pilot

    We build a narrow but end to end working version in a single process, with your real data and real users. The success criterion is defined as a number at the start, and you decide on the result whether to move to production.

  4. Delivery and acceptance

    We roll the system out with your team, with authorisation, monitoring and security settings in place. Acceptance follows the success criterion written into the scope.

  5. Training and handover

    We hand the system over to your team with its documentation and handover training. Code developed for you is yours; Verhex products come under licence, and third party components under their own licences.

  6. Maintenance and support

    After delivery we continue under a defined maintenance agreement or with support called upon as needed. In the first period we follow up on improvement with you at defined intervals.

Once the scope is clear, we share the project schedule and timeline.

Responsibilities

Who is responsible for what?

Verhex

  • One lead who runs the project
  • Process design, development and integration
  • A written data flow showing which data goes where
  • Documentation and handover training

Your organisation

  • A process owner and a decision maker
  • Access to systems and data
  • Real users and feedback during the pilot
  • Sign off on the success criterion and acceptance

Have a project? Let's talk.

Tell us briefly and we will get back to you. The first call is not a pitch: we listen to what you need and say plainly whether it can be solved. If you need an NDA, please let us know before the call.

Get in touch