Skip to content
Cover illustration with the caption: Monday plan, Friday robot
Phillip Mwaniki Automation

Start Small: Your First Automation Project in One Week

Is your business waiting for the "big digital transformation" that has been on the agenda since 2019? The one with the steering committee, the consultant, and the slide deck that nobody has opened since the launch meeting? Here is a gentler idea. Automation for small businesses in Kenya works best when it starts tiny: one task, one week, one visible win that makes everyone ask what else you can fix.

This is a practical, day-by-day plan. It assumes you have a busy team, a modest budget, and at least one person who sighs loudly every time they open a particular spreadsheet.

Monday: find the most annoying task

Do not start with the most important process. Start with the most irritating one. Ask your team a simple question at the morning meeting: "What do you do every week that makes you want to throw your laptop into the Nairobi River?"

You will get answers quickly. Typical candidates include:

  • Copying M-Pesa payments from statements into a sales sheet.

  • Sending the same weekly stock report to five people.

  • Reminding clients about appointments one phone call at a time.

  • Typing up delivery notes that contain the same details as the invoice.

  • Chasing managers for approval on small purchases.

Pick one. The ideal first project happens often, follows clear rules, and does not involve sensitive judgement calls. If it takes someone two hours a week and could take ten minutes, that is your winner.

Tuesday: write down how it works today

Sit with the person who actually does the task. Not the manager who thinks they know how it is done, the person who does it. Ask them to walk you through every step, including the weird workarounds. You will discover things like "Then I check the WhatsApp group in case Omondi sent the figures there instead of email."

Write each step on paper. Mark which steps are pure copying, which are decisions, and which only exist because two systems do not talk to each other. The copying steps are where automation lives.

Wednesday: choose the simplest tool that works

You do not always need custom software on day one. Depending on the task, the answer might be:

  • A shared online form that feeds a spreadsheet automatically.

  • Scheduled emails or reports from a system you already pay for.

  • An automated payment confirmation from your payment provider.

  • A simple workflow tool that moves information between apps.

The goal this week is not perfection. It is proving that the boring task can disappear. If it turns out the task genuinely needs something built for your business, that is a fine discovery too, and now you know exactly what to ask for.

Thursday: test with real work

Run the new process alongside the old one for a day. Let Fatuma, who usually does the task by hand, compare the results. Did every payment show up? Did the report go to the right people? Did anything strange happen, like the system emailing the stock report to a supplier by mistake?

Expect small problems. Fix them. This is also when you decide who owns the automation going forward. Every automated process needs a named human who notices when it stops working, especially after a blackout or a password change.

Friday: switch over and celebrate

Turn off the old manual process and let the new one run. Then do the most underrated step in any project: tell people. Share how much time it saves. Buy mandazi. Let Fatuma explain what she will do with her two free hours, which hopefully is something more interesting than answering emails.

Small wins build trust. Once people see one boring job vanish, they start suggesting the next one, and suddenly you have an automation culture without a single steering committee meeting.

Automation for small businesses in Kenya: what comes next

Keep a simple list of candidate tasks, ranked by how often they happen and how annoying they are. Tackle one at a time. When you reach the processes that need proper business software, such as payroll, school fees or client billing, you will already have the habits that make bigger projects succeed.

If you want a hand picking your first project, or you have found one that needs more than a form and a spreadsheet, talk to Philsoft. You can also see the kinds of systems we build on our services page. Start small, start this Monday, and save the steering committee for something truly important, like choosing the office tea brand.

← All posts