// Our approach
Designed for the day after.
Most programmes are planned around delivery. We plan around what happens next: who will own the system, who will run it, how it connects to everything around it, and how it will be paid for. Six principles shape how we do that.
What we believe
- Systems over standalone projects.
- A successful pilot is not the same as a functioning national system. We look at how a solution connects to the institutions, budgets, processes and other systems around it.
- Governance alongside technology.
- Data ownership, accountability, standards and decision rights are part of the architecture, not paperwork for later. We address them from the start.
- Ownership over dependency.
- The institutions that inherit a system need the authority, people, resources and confidence to run it. We plan for that, starting from the capacity already there.
- Implementation over presentations.
- A strategy is only useful when it becomes clear responsibilities, workable processes and everyday use. Our recommendations are written to be carried out.
- Context over imported assumptions.
- Low connectivity, constrained budgets and many stakeholders are the operating environment, not exceptions. We plan around them.
- Independent advice over vendor interests.
- We take no commissions from technology vendors. Our only interest is what will work for you.
How an engagement unfolds
Every engagement is scoped to the question in front of you. Some cover one stage; few cover all four. Where the work requires technical delivery, we bring in trusted local partners or work alongside your existing ones.
- 1
Understand the context.
Who owns what today, which systems already exist, how decisions are made, and where the money comes from.
- 2
Assess readiness.
What the institution, its people, infrastructure and processes need before a system can be adopted and run.
- 3
Plan implementation and ownership.
Integration with national systems, roles and decision rights, costs over time and the handover path, agreed with the people who will carry them out.
- 4
Build capacity and prepare for handover.
Supporting the teams who will run the system, so the transfer is a planned step rather than a deadline.
- Before you invest
- While it runs
- At handover
What working with us is like
- You work directly with senior advisers from the first conversation to the final recommendation.
- Scopes are defined in writing, with clear deliverables and an end date.
- We say what we think, including when the answer is not the one that was hoped for.
- We work with your teams and partners, not around them.
Independence
We are an advisory firm, not a software vendor or an implementation contractor. We take no commissions from technology vendors and have no products to sell, so when we recommend a system, a standard or a partner, it is because it is right for you. We will tell you if we are not the right fit.