Method
How we build
Two ways in: an advisory engagement on how the function should run — its own timeline, its own price — or straight to the scoping workshop. Then eight to sixteen weeks, signature to live: what happens in each, what you see, and what you sign.
The weeks
Signature to live
8–16 weeks, signature to live. What happens in each one, what you see at the end of it, and what you sign.
Advisory
Before week 1 — its own scope and its own price, apart from the build
- What happens
- An advisory engagement on how the function should run — the PMO, the HR function, the strategy office or the performance management system — scoped and priced per engagement.
- What you see
- A detailed report on how the function works, with the recommendations.
- What you sign
- The scope of the platform build.
Week 1 of 16
8–16 weeks, signature to live
ScopeShapeBuildHardenLive
Scope
Weeks 1–2
- What happens
- Where the advisory was not bought, the stage opens with a workshop with the person responsible for the process. We write down what the work does today, so that the platform is built on the process as it actually runs.
- What you see
- The current process, written down, with its recommendations and its exceptions.
- What you sign
- The scope, with the full build price. Both are fixed from this stage.
Shape
Weeks 3–4
- What happens
- The screens and the data model are designed in Arabic and English.
- What you see
- The screens you will work on, in both languages, before anything is built behind them.
- What you sign
- Approval of the screens and the user journey.
Build
Weeks 5–12
- What happens
- We deliver in small increments you can see and use rather than one delivery at the end, with tests and continuous integration on every delivery. If the scope changes, we price the new scope before we build it.
- What you see
- A working system that grows with every delivery.
- What you sign
- Approval of the deliveries, and of any change to the scope.
Harden
Weeks 13–14
- What happens
- The parts that are invisible until they are missing: hosting and monitoring, dependency upgrades, and backups that have been restored from rather than assumed to work.
- What you see
- The system running on your own infrastructure, under load, with the monitoring you will keep.
- What you sign
- Nothing. This stage has no signature in it.
Live
Weeks 15–16
- What happens
- Handover. The platform's resources — the code, the data and the deployment — pass into your name as the agreement provides, and the people who will use the system are trained by the people who built it.
- What you see
- The platform in daily use, and the record of the process it was built from.
- What you sign
- Acceptance, and — if you want it — the care contract: its own monthly contract, offered at first delivery, which you choose to renew, not a dependency designed in.
Do you have processes or administrative work that should be running on a digital platform?
Tell us how the function runs today — or what your people do by hand. We will tell you honestly what it needs: advice on how it should run, a platform, both — or neither. And if it is neither, we will say so.