Skip to content

About us

Software built around how your business runs

We're a software team in Nairobi. We build custom systems, websites and integrations for businesses in Kenya and East Africa, starting from how your team actually works.

Our story

Software that fits the business

We started Chacha Technologies to close the gap between what businesses need and the software they were being sold.

In 2020, businesses in Kenya knew they needed better systems, but off-the-shelf tools rarely fitted how they worked. Generic ERPs and template websites made teams change their processes to suit the software, and custom work was often expensive, poorly built, or abandoned after launch.

We build the other way round: we learn how the business runs, then build the system around it, and we stay involved after launch.

Since then we've built for schools, microfinance institutions, event organisers, care marketplaces, non-profits and agricultural businesses in Kenya, Tanzania and beyond.

The aim hasn't changed: software should save your team time, not create more work.

How we work

What makes us different

We could tell you we're “innovative” and “client-focused.” Every tech company says that. Here's what we actually do.

  • We test for real conditions

    Most software is tested in good conditions. We also test for unstable internet, power cuts, traffic spikes and messy data, because that is what real use looks like.

    For example: We test what happens when a payment confirmation arrives late or never arrives, not just when everything works.

  • We recommend the simpler option

    We start with the business problem, not the feature list. Sometimes the answer is an existing tool rather than new software, and we'll say so even when it means less work for us.

    For example: A client wanted a custom booking system. We suggested integrating an existing tool instead, which cost less and covered what they needed.

  • We stay after launch

    Bug fixes are free during the warranty in your quotation, and maintenance plans are available after that. You deal with the people who built the system.

    For example: A client's system went down late on a Saturday night. We fixed it the same night, because their business depends on it.

  • We explain things in plain language

    You don't need to know what "REST API" or "PostgreSQL" means. You need to know whether your system will work, so updates and decisions are explained in business terms.

    For example: Not "microservices architecture" — we say "your system will keep working as you add more customers."

  • Fixed quotations, priced changes

    Fixed-price quotations stay fixed. If the scope changes, we price the change in writing and you approve it before we start.

    For example: For a school management system, we agreed the timeline at the start and delivered within it.

  • Built in Nairobi

    We're based in Nairobi, so we build for phone-first customers, mobile money and unreliable connections from the start, and we can meet in person.

    For example: Mobile money, SMS and WhatsApp are part of the design from the first week, not added at the end.

Process

What working with us looks like

A typical ten-week project, and how much of your time each stage needs.

  1. 01

    Week 1

    Discovery

    A working session to understand the problem, your goals and what the system needs to do.

    Your time: 2–3 hours

  2. 02

    Weeks 2–3

    Planning and design

    Visual mockups so you can see it before it's built, the technical plan in plain language, and a timeline with milestones. You approve each stage before we build it.

    Your time: 3–5 hours

  3. 03

    Weeks 4–8

    Building

    Regular working demos, and a project page where you can follow progress and sign off each stage.

    Your time: 1–2 hours a week

  4. 04

    Week 9

    Testing and training

    Your team tests the system, we fix what you find, and we train the people who will use it. We launch when it is ready.

    Your time: 5–10 hours

  5. 05

    Week 10

    Launch and support

    We deploy, watch the system closely for the first 72 hours, and fix bugs free during the warranty. After that, support continues on a maintenance plan.

    Your time: Minimal

Tell us about your project

Tell us what you need and we'll explain how we would approach it.