An honest shortlist
Which workflows are worth automating, what each would save, and which ones should stay human.
Most automation fails for human reasons, not technical ones. I start with how your people actually work, find the repetitive steps that cost the most, and build the smallest system that takes them off their desks.
For SMEs and operations-heavy companies, in logistics, education, finance, health and services, where people spend hours on copy, check and reply.
01/What you get
Working automations
Email and ticket triage, document and invoice extraction, report generation, dispatch and follow-ups, wired into your existing tools.
Local integrations
M-PESA, PesaPal, WhatsApp, SMS and the spreadsheets that actually run the business, not just the systems on the org chart.
Training and ownership
Your team learns to run, adjust and trust the automation, with a clear owner for each one.
02/How it works
- Step 1
Shadow the work
A few hours watching the workflow as it really happens, not as the process document describes it.
- Step 2
Pick one
Automate the single workflow with the clearest payback first, and measure hours saved.
- Step 3
Run it together
Two to four weeks side by side with your team, fixing what reality reveals.
- Step 4
Scale what worked
Repeat the pattern on the next workflow, now with numbers to justify it.
03/Proof
04/Questions
Are you a consultant or do you build?+
I build. The assessment is short and exists to choose what to build first. The bulk of every engagement is working software in production.
We're a small business. Is this for us?+
Often more than for large ones. A single automation that saves one person ten hours a week is a meaningful return for a small team.
What does it cost?+
It depends on scope. Most first automations are a fixed-price project of a few weeks. Send a short description of the workflow and I'll reply with options.
Related writing