You see what it could save you, in writing, before you commit.
Every engagement follows the same five steps, with your team in control. Early on we estimate the staff hours and naira at stake, and each step ends with something you can see, check and keep.
The five steps
-
Agree the problem and the outcome
We start from a real business problem, not a list of features. Together we agree what "better" means, and how we will both know it has happened.
You get: a one-page summary of the problem, the outcome and how it will be measured, such as hours spent on fee reconciliation or days to produce a report.
-
Review what you already use
We look at your current tools, data and process, and talk to the people who do the work, before suggesting anything new.
You get: a map of your current records, workflows and tools, the confirmed bottlenecks, and an estimate of the hours and naira they cost you.
-
Keep, connect, improve or build
For each part of the system we recommend one of four options. We only build where improving or connecting what you have will not meet the agreed requirements.
You get: a written recommendation with the reasons, and a proposed first phase, with its scope and price.
-
Start with a small first phase
We deliver the part that matters most first, show you progress regularly, and check the result against the outcome we agreed.
You get: a working improvement or system for that part of the business, tested with your staff.
-
Hand over, train and support
We train the people who use the system, hand over documentation, and agree support in writing if you want it.
You get: user and admin guides, trained staff, and a support arrangement with response times.
What guides every project
Solve a useful business problem
We establish the actual need and agree the intended outcome with you before any work starts.
Improve or build as appropriate
We assess your current tools first and decide what to keep, connect, improve or develop.
Build dependable foundations
Records and workflows are organised so that essential operations keep working without AI.
Use automation and AI where they add value
We choose them where they genuinely help, with staff controlling consequential decisions.
Tell you when you do not need us
If the right answer is training, a setting change or no new software at all, we will say so.
Leave you in control
Documentation, training and access arranged so the system does not depend on any one person, including us.
How we use AI, and how we limit it
AI is a tool inside the system, not the system itself.
What AI may do
- Draft replies to customers for a person to check and send
- Summarise long records, notes or message threads
- Sort incoming requests and suggest who should handle them
- Flag unusual entries, such as a payment that does not match any invoice
What stays with your staff
- Approvals, refunds, discounts and any change to money or records
- Messages that commit the business to something
- Decisions about people, patients, pupils or customers
If an AI service is slow or unavailable, the system carries on without it. Before go-live we agree in writing what the AI can see, what it can do, and who reviews its output.
Your data, handled under the NDPA 2023
Many of the systems we build and improve hold personal data: pupils, guests, patients and customers. We treat that seriously from the first meeting.
- We agree in writing what data we may access, for what purpose, and for how long.
- We only access the data a piece of work needs, and work with test data where we can.
- When we process data for you, you remain the data controller and we act on your documented instructions.
- We design access by role, keep audit trails, and plan backups before go-live.
- Our access ends when the work ends, unless you ask us to support the system.
This describes our approach, not legal advice. Your organisation's own obligations under the Nigeria Data Protection Act 2023 depend on what data it processes. See our privacy notice.
What a Systems Review report looks like
An outline for a fictional school, to show the shape of the report. The school, figures and findings are invented.
Example: a fictional school
Example Secondary School, Abuja: fees and results review
Current state
Fees recorded in Excel by the bursar, receipts handwritten, results computed in a spreadsheet per class, parents contacted on WhatsApp.
Confirmed bottlenecks
Matching transfers to pupils takes the bursar most of the first two weeks of term; report cards take the teaching staff several days to compile and check.
Recommendation
Keep the bank account and WhatsApp. Build a fees module with payment matching and SMS receipts. Improve the results spreadsheet now; move results into the system in phase two.
First phase scope
- Student list and fee schedule by class, imported from Excel
- Payment matching from bank statements, with a review queue for the bursar
- Receipts by SMS, and a balances report by class
- Training for the bursar and two admin staff
Price and timeline stated here in a real report. Later phases: results and report cards; parent notices; attendance.
Ready for step one?
Step one is a conversation. It is free, and it takes thirty minutes.