
Practice 05 of 11
Digital solutions built, tested, handed over
Websites, portals, knowledge assistants, reporting automation, accessibility work and voice or WhatsApp services, each scoped to a user need and handed over with the tests that prove it works.
Discuss a projectLed byMichael Gagakuma and Kenneth Gagakuma 6 services 4 free tools
The practice
Websites, portals, knowledge assistants, reporting automation, accessibility work and voice or WhatsApp services, each scoped to a user need and handed over with the tests that prove it works.
Practice 05 of 11
When organisations call us, and where we stop.
The situations this practice exists for, and the lines we do not cross.
When to call
- A process runs on email and spreadsheets
- Your website no longer serves the people who use it
- You want an AI assistant you can trust and audit
- Accessibility is required for a procurement or by law
Our boundaries
- We start with one workflow or page type, not a large build scoped in one go.
- Running costs and provider fees are shown before anything is built.
- You own what we build unless agreed otherwise.
Services in this practice.
Each one starts with a defined first scope and a fixed fee agreed in writing.
- 05.01 Donor MEL reporting automationWe convert one approved indicator workbook into one funder reporting template, with reconciliation checks and exception handling, so each reporting cycle takes hours instead of weeks and every figure can be traced.
- 05.02 Accessibility audit and remediationWe audit and remediate a defined set of pages or templates against WCAG 2.2, including manual keyboard and assistive-technology checks, and hand over a record of what was fixed and how it was tested.
- 05.03 Knowledge-base chatbots and internal assistantsWe build a bounded assistant over your permitted documents that cites its sources, refuses what it should not answer, and is tested for leakage before anyone relies on it.
- 05.04 WhatsApp and voice agentsWe prototype one voice or WhatsApp journey for your users, with language review and an honest view of the channel’s running costs, before any wider rollout.
- 05.05 Data portals and web applicationsWe build a defined portal workflow with roles, validation and acceptance tests, then scope the wider application from what works.
- 05.06 Institutional website designWe design and build focused institutional websites with the content, performance and accessibility criteria agreed up front, the way this site was built.
How the work runs.
User need, then scope, then build, then test, then handover. Each stage ends in something you review.
Stage 1 of 5
User need
Confirm the user need and how success is measured.
Review pointUser needs agreed.
Stage 2 of 5
Scope
Write the scope with acceptance tests.
Review pointScope and tests approved.
Stage 3 of 5
Build
Build in short, demonstrated steps.
Review pointMilestones demonstrated.
Stage 4 of 5
Test
Test with real users and data.
Review pointAcceptance tests passed.
Stage 5 of 5
Handover
Hand over code, access and documentation.
Review pointHandover confirmed.
Try the method before you buy.
Free working tools from this practice. Results on screen straight away; the full report by email if you want it.
Free tool Colour contrast checker
Check colour pairs against the WCAG 2.2 contrast ratios for text and interface parts, then record the manual tests an automated scan cannot do. The worksheet shows what passed, what failed and what was never tested.
Open the tool
Free tool AI knowledge assistant readiness checklist
Before you build a chatbot over your documents, check the content, permissions, questions, evaluation and ownership it depends on. You get a readiness score, the gaps to fix and a starter evaluation set that includes the questions it must refuse.
Open the tool
Free tool Web app requirements template
Name your users and what they need to do, then list features with the need behind each, a priority and the test that proves it works. The builder turns it into a specification and test checklist you can hand to developers.
Open the tool
Free tool WhatsApp and IVR journey planner
Plan a WhatsApp or voice journey step by step, including what happens when the connection drops, speech is not recognised or the user needs a person. The planner flags steps with no failure path and choices that do not suit your users.
Open the toolDocumented experience.
Roles held by our principals, each with its source. Demonstrations are labelled as demonstrations.
Individual experience of our principals, before or outside GKM Strategic Advisory & AI. Not GKM contracts.
Who answers for the work
Who commissions this work
- NGOs, donors & development partnersInstitutions↗
- Governments & public institutionsInstitutions↗
- Agencies & consulting primesBusinesses↗
- Professional bodies, chambers & membership organisationsInstitutions↗
- Health organisations & care providersInstitutions↗
- Technology, SaaS, telecoms & fintech companiesBusinesses↗
- Corporates & large employersBusinesses↗
- Foundations, philanthropies & impact fundsInstitutions↗
- Schools, TVET institutions & education networksInstitutions↗
- UN agencies & multilateralsInstitutions↗
- Social enterprises & community organisationsInstitutions↗
- Faith-based organisations & charitiesInstitutions↗
What needs to move forward?
Tell us the decision, the challenge or the opportunity. We reply with a scoped approach, a named principal and a fee before any work begins.
No charge to submit an enquiry.
