Digital Transformation
Fixing the manual work around your systems, so automation has something solid to sit on.
What is digital transformation?
Digital transformation, in the sense we use it, means replacing the paper, the rekeying and the undocumented workarounds that sit between your existing systems, so that work moves reliably before anything is automated on top of it.
It is rarely a software purchase. Most of the available gain comes from connecting what you already own and settling, on paper, how work is supposed to move through it.
We record how each process genuinely runs, including the shortcuts nobody mentions in meetings, then redesign around the constraints you actually have. Staff numbers and appetite for change are constraints, not excuses.
The finished state is a process a person can run the same way twice. That is the minimum condition for a machine running it at all, and it is the step most automation projects skip.
Why this is the least glamorous work we sell
Duara does transformation work from Nairobi, mostly in warehouses, finance offices and dispatch rooms rather than in strategy sessions. The evidence for how a process really works is never in the manual.
We are candid that this is the least glamorous work we sell. It is also the work that decides whether everything bought afterwards returns anything, which is why we push clients toward it before they buy AI.
Who this is for
- You run important work on spreadsheets and email
- Your systems do not exchange data
- You want to automate but are not ready to
- The same details get typed into several places
Industries we serve
- Distribution and wholesale
- Manufacturing
- Logistics and courier
- Healthcare administration
- Professional services
- Retail operations
Problems this solves
These four appear together so often that finding one usually means the other three are present.
- The same details typed repeatedly. An order or invoice is keyed into two or three systems by hand, which is slow and is where most downstream errors originate.
- Processes that exist only in people. The real method lives in a few heads, changes without anyone deciding, and cannot be automated because nobody can describe it.
- Work waiting in inboxes. Jobs stall because the next person never noticed the email, not because any part of the task was difficult.
- Nobody can say where anything is. Answering a customer question about their order requires ringing three people, because status lives nowhere.
What we deliver
A redesigned and documented process with the manual handoffs removed, the necessary system connections built, and a shared view of where every job has reached.
A map of how each process genuinely works today
A simplified process with the manual steps designed out
The connections required between your existing systems
A training and transition plan for the staff affected
A live view of where each job has reached
Documentation your own team can maintain and amend
Features
- Mapping from observation. We record what people actually do, including the undocumented workarounds that keep the business running.
- Connection before replacement. We connect what you own wherever it is possible, because replacing systems is slower, dearer and riskier.
- Staged rollout. Changes arrive in stages so trading continues throughout. We never switch a critical process in a single step.
- Shared status visibility. One view of where each job sits, which removes most of the internal chasing between departments.
- Written handover. Documentation detailed enough that your team can adjust the process later without calling us back.
Benefits
- Fewer errors reaching customers. Removing rekeying removes the single most common source of mistakes further down the line.
- Shorter turnaround times. Most elapsed time is waiting rather than working, and waiting is exactly what this removes.
- A foundation automation can stand on. A repeatable process can be automated. A chaotic one cannot, at any price.
- Less internal chasing. Shared status removes a large share of the calls and emails that currently pass between teams.
Technologies we use
- API integration. Connecting your existing CRM, accounting and operational systems so information is entered once and travels.
- M-Pesa reconciliation. Matching mobile money receipts against invoices and orders where that sits inside the process.
- Workflow rules. Approval routing, reminders and escalation driven by conditions you define and can change.
- Document capture. Reading details off forms, delivery notes and invoices so nobody has to type them in again.
- Status reporting. A single view assembled from the systems already in use, without adding another place to check.
The technology here is deliberately unexciting. Connections and rules do most of the work, and that is a feature rather than a limitation.
How the process works, step by step
A single process usually takes four to eight weeks from mapping through to the team working the new way.
-
Step 1
Free process call
We pick the process causing the most internal complaints and agree what a better version would look like.
-
Step 2
Observation and mapping
We watch the work being done and write down what actually happens, including every workaround.
-
Step 3
Redesign with the team
We rebuild the process with the people who run it, so the result is something they will actually follow.
-
Step 4
Build the connections
We construct the integrations and rules that remove the manual steps from the redesigned process.
-
Step 5
Transition and training
The team moves across in stages, with documentation and support during the changeover.
Quality assurance and how we work
The commitments that apply specifically to transformation work.
- We map before we recommend. No change is proposed until we have watched the process being performed, not merely described.
- Trading continues throughout. Changes are staged. We will not switch a business-critical process over in a single cutover.
- The people who do the work redesign it. Staff who helped design the new process are the ones who make it stick afterwards.
- We measure before and after. Cycle time and error rate are recorded during mapping, so the improvement is checkable.
- You can maintain it without us. Documentation is written for your team, and we would rather you changed the process yourselves.
Frequently asked questions about digital transformation
What does digital transformation mean in practice?
Replacing paper, rekeying and undocumented workarounds between your systems so work flows reliably, usually without buying any new software.
Do we have to buy new software?
Usually not. Most of the gain comes from connecting what you own. We recommend new software only when the current tool genuinely cannot do the job.
Will this disrupt trading?
Changes are staged so the business keeps running. We do not switch a critical process across in one step.
How long does one process take?
Typically four to eight weeks covering mapping, redesign, build and transition.
Why map the existing process first?
Because the documented process and the real one differ, and anything built against the documented version fails immediately.
What if staff resist the change?
We involve them in the redesign. People who helped design a process are far more likely to follow it.
Is this the same thing as automation?
No. This makes the process reliable. Automation comes afterwards and works far better once this has been done.
Can you connect systems that are quite old?
Usually, through an API where one exists, or scheduled file exchange or a direct database connection where it does not.
What happens to all the workarounds?
The genuinely useful ones become official steps. The rest disappear once the limitation that caused them is fixed.
Do we get documentation?
Yes, written so your own team can amend the process later without needing us.
How is improvement measured?
Cycle time and error rate, compared against the baseline recorded while mapping.
Can we start with a single department?
Yes, and that is usually the right scope. Finance and operations are the most common starting points.
Does this cover M-Pesa reconciliation?
Where mobile money forms part of the process, yes. It is one of the most common manual steps we remove for Kenyan businesses.
What if the process changes after you leave?
It is documented and adjustable. Your team can change it, or we can, but you are not dependent on us.
Who needs to be involved from our side?
The people who perform the work daily, plus whoever can approve a change to how it is done.
Will you tell us if a process is fine as it is?
Yes, and it happens. Some processes are manual because manual is genuinely the cheapest option at your volume.
How do you handle processes spanning several departments?
Those are usually the most valuable to fix, and we map the whole chain rather than one department view of it.
What does a transformation programme cost?
It depends on the process and how many systems it touches. We quote a fixed figure after the free process call.
Do you work on site?
Yes. Observation has to happen where the work happens, so mapping is nearly always done in person.
Can this be done before an AI project?
It should be. Automating a broken process simply produces the wrong result faster and at greater cost.
Glossary of terms
The terms used in process work, without the management consultancy vocabulary.
- Digital transformation
- Redesigning and connecting the manual work around your systems so processes run reliably.
- Rekeying
- Typing the same information into a second system by hand because the two do not talk.
- Workaround
- An unofficial step staff invented to get past a system limitation, almost always undocumented.
- Handoff
- The point where work passes between people or teams, which is where most delay accumulates.
- Process owner
- The person accountable for how a process runs and for approving any change to it.
- Cycle time
- How long a job takes end to end, including all the time it spends waiting for someone.
Related services in AI Consulting
Talk to us about digital transformation
Tell us which process causes the most arguments internally. That is almost always the right one to start with.
Start your project