Process & Systems Improvement
Work out what should change before paying to build it
We review how work moves through the business, where time is being lost, and whether the answer is a better process, an existing tool, automation or custom software.
What we review
How information moves
Where people re-enter or search for the same information.
Handoffs
Where work waits for another person or department.
Approvals
Where decisions depend on messages or memory.
Tools
Which spreadsheets, software and communication tools are being used.
Reporting
Where management information comes from and how it is assembled.
Customer-facing steps
Where customers wait, ask for updates or provide information repeatedly.
What you receive
- Current process map
- Main bottlenecks and duplicated work
- Practical improvement recommendations
- What can stay as-is
- What can be simplified
- Where automation may help
- Where software may be justified
- Recommended next steps
The answer is not always new software.
Simplify
Remove unnecessary steps.
Use what you have
Configure an existing tool better.
Automate
Connect a repeated workflow.
Build
Create software when the process genuinely needs it.
How it works
- 01
Review
Understand the current process.
- 02
Map
Document how work and information move.
- 03
Identify
Find unnecessary steps, delays and gaps.
- 04
Recommend
Produce a practical next-step plan.
Pricing
- Starting from
- KES 25,000
- Typical range
- KES 25K–60K
- Estimated delivery
- 5–10 business days
Timing depends on scope, integrations, feedback and existing data.
What changes the price
- Number of workflows reviewed
- Number of teams involved
- Number of systems/tools involved
- Depth of documentation required
- Follow-up workshops
Frequently asked questions
What do we receive at the end of the review?
Depending on scope, you can receive a current process map, a list of bottlenecks and duplicated work, practical recommendations, guidance on what can stay or be simplified, and clear next steps. The deliverables are agreed before the review starts.
Does this always lead to a software project?
No. Sometimes the better answer is a simpler process, better use of an existing tool, or a focused automation. New software is recommended only when it is justified.
Can you review a process that already uses software?
Yes. Many reviews look at how people actually use the tools they already have, where those tools overlap, and where workarounds have grown around them.
How much of the business should we review?
It depends on the problem. A focused review of one workflow can be enough. Broader reviews covering several teams take more time and sit higher in the range.
What happens after the recommendations?
You decide what to do next. If a build or automation follows, the review becomes the basis for a clearer project proposal. Any credit of the assessment fee toward later work is handled in that proposal if agreed.
How long does the review take?
Most focused reviews take around 5–10 business days. A larger review involving several teams or workflows may take longer.
Discuss your project.
Tell us what the business needs to do and where the current process falls short.
