Project-based
A defined scope, a defined price, delivered against a statement of work.
Best for
A piece of work whose edges you can describe: a rollout, a migration, a module going live.
You own
The business decisions, sign-off at each phase, and your own people's time.
We own
The plan, the team, the estimate and the delivery against it.
How it works
- Size it. The estimator turns a scope into consultant-days, phases and a budget in minutes.
- Agree the statement of work. What is in, what is out, and what each phase produces.
- Deposit and start. A deposit against the accepted quote; the balance is invoiced as phases complete.
- Deliver and hand over. Through Explore, Realize, Deploy and Run, against the plan you signed.
What you get
- The cost is known before you commit, and the breakdown reconciles line by line.
- Scope changes are visible, because the original estimate does not get rewritten.
- A quote keeps the catalogue it was priced under, so nobody re-prices history.
- Export the whole thing as a document, a workbook or a deck for your own approvals.
When this is the wrong fit
A scope nobody can describe yet is not a project — size it as a short discovery first, or you are buying an argument.
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.