Best for

Life after go-live: incidents, support packs, small enhancements, the quiet half of SAP.

You own

Priorities, business sign-off, and what counts as urgent.

We own

The rota, the response, and keeping the knowledge when individuals move on.

How it works

  1. Describe the estate. Modules, versions, interfaces and how much of it is standard.
  2. Agree the shape. Hours, response expectations and who may raise what.
  3. Transition. A handover from whoever built it, documented rather than remembered.
  4. Run. Support, plus a monthly allowance for small change so the backlog does not calcify.

What you get

  • Cover that does not depend on one person's holiday plans.
  • Small change included, so "we will raise it next year" stops being the answer.
  • The same people who can quote a bigger piece of work when one appears.
  • Knowledge stays with the engagement rather than leaving with a contractor.

When this is the wrong fit

If what you actually have is a half-finished implementation, support will spend its time on it — finish the project first.

The other two

Next step

Pricing for anything paid on the Hub is on the pricing page. What an engagement itself costs depends on the scope, which the estimator will size for you before you commit to anything.