For any business with 5 to 60 staff. One company, one private workspace.
Someone stops replying, a job slips a day, then three, and you hear about it when it is already late. Put your whole team in one place and Kazi does the following up. Everyone sits on one chart of who reports to who, coloured by the work they finished and the dates they hit. Nobody fills anything in. Every evening each person gets a private reminder on their phone about their own late work. Every morning you get the list of who did not reply.
The problem
Your list of jobs is full and nothing on it got finished this week.
Someone stops replying on Tuesday. You hear about it on Thursday, when the deadline has already passed.
Two people carry most of the work. You know which two. They are also the two who end up leaving.
Nothing gets approved unless you approve it, so the work stops whenever you are busy, and the only record of what was decided is what you remember.
What changes
Your team do not have to learn anything new. They do the same jobs they already do, and they answer one question on their phone when it arrives. Kazi builds the record out of that.
Your week today
Your week with Kazi
Writing the work down is the easy part. Getting it finished on time is not.
Following up, done for you
Kazi does the following up on your company’s own clock. You never have to remember to do it, and nobody is ever named in front of the rest of the team.
At 5.30pm anyone with a job due today, or already late, gets a private message about that job on their phone, tagged to their name, asking for a quick update before they finish for the day. Anyone who already worked on that job the same day is skipped, and nobody is asked twice in one day.
At 8.30am each manager gets one message listing their own people who did not reply overnight. Opening Kazi shows that list first: the person, the job, how many days late it is, how long since they last replied, and the exact question they were asked. Ring them, press the button to say you called, type what they said, and it is saved on the job and the row clears.
When your team open Kazi, the questions waiting for them are the first thing on the screen, each with four ready made answers under it. One tap on a phone saves a real reply on the job and takes them off tomorrow’s list. A comment, a message, moving the job forward or finishing it all count, and finishing it earns a short thank you message.
On Friday at four, a summary of the week is written for each person. A manager reads it and either sends it or throws it away. No weekly message reaches anyone unless a person decides to send it.
How many reminders were answered out of how many were sent. The typical time people take to reply. How many had to go to a manager. How much work was finished on time. All of it week by week and person by person, over whatever period you pick, with Kazi’s own record of every reminder it sent underneath.
Before you switch it on for real, send a test reminder to your own team and watch it go. Sent, delivered, replied: each step appears on the screen in front of you. The first reminder Kazi ever sends goes to your own people, while you are watching.
Quiet hours, days off and one master switch all sit on a single settings page, and the schedule will not accept a send time that falls inside your quiet hours. You can edit the wording of every automatic message before anyone receives it. Messages go to the phone first, and by email when the phone does not pick them up. Every message sent is written into a record you can read.
Who reports to who
A chart of who reports to who, with your managers, team leads and every member of staff on it. Each person’s box takes its colour from the jobs they are already working on. Click a name and the detail sits underneath: what they have open, what is late, and by how many days.
How the colours are decided.
No forms. No timesheets. Nobody rates themselves. The colour comes from real jobs, real dates and work actually finished, so nobody can talk their way into a better one. Every box says in plain words why it is the colour it is.
Managing people
How much each person finished, how much of it was on time, and the last five weeks side by side, worked out from the work itself every time you open it. Nobody fills anything in, so nobody can talk their way to a better number.
One short document per person that says what the job is: the results they are responsible for, the standard to hit, and the goal. What they are supposed to be doing sits right next to how they are actually doing.
Four levels, shown on every profile. Level 4, waits to be told what to do. Level 3, suggests what to do, then does it once you agree. Level 2, does it, then tells you straight away. Level 1, works on their own and tells you afterwards. Everyone can see the level they are on and the one above it.
At 5.30pm each person with a job due today or already late gets a private reminder about that job, written from the job itself: what it is, how many days it has slipped, and what stage it is sitting in. It arrives on their phone. Anyone who already worked on that job that day is skipped. Every reminder and every reply is saved, so the card reads “Reminded (2)” with who asked, how and when, and any manager can still send one by hand.
Everything else Kazi does
For investors and boards
Funds, accelerators and boards all end up at the same question: is this a company, or one person holding it together? When everyone works in Kazi, that answer gets written down as people work, instead of being put together in a rush the week before a meeting.
Looking at why Kenyan companies that had raised real money still failed, PwC said it plainly: investors rely on financial, legal and tax checks while overlooking the operational mechanics of the businesses they fund, which lets the weakness carry on until the company runs out of cash. How a company is run day to day is exactly what Kazi records.
Spending that is not in the budget goes up as a request with an amount and a reason. Who approved it, who objected, and when, are all saved. You never have to go looking through old chat messages to find out how a decision was made.
Record the meeting, get the notes and action points back, and turn each one into a job with a named owner and a date. On one screen you can see what the board decided and whether anyone actually did it.
Who reports to who, with each person's record of finished work under their name. If your company depends on one or two people, you can show exactly who, and by how much.
How much each person finished and how much of it was on time, worked out from the work itself. Nobody assembled these numbers to impress anybody, which is what makes them worth showing.
Nobody had to prepare any of it. It was written down as people worked.
Pricing
You pay for the people who use Kazi. Add someone and the bill goes up by one. Take someone off and it goes down. Whichever plan you end up on, your first 15 days are free and every Business feature is switched on.
For teams of up to 6 people
$6 per person, per month
First 15 days free, every Business feature on
Any team size
For teams of 7 people or more, or anyone who wants the management tools
$10 per person, per month
First 15 days free, nothing to pay until they are up
Billed monthly by card or M-Pesa. Kenyan companies are billed in shillings, KES 800 and KES 1,300 per person. Prices do not include VAT. No setup fee, no contract, and you can stop at the end of any month.
Compare Kazi to hiring someone, not to other software.
The other way to fix all of this is to hire somebody to do it. An operations coordinator whose whole job is asking where things are, following up on what slipped, and writing up who did what. That is a salary every month, statutory deductions, leave days, a laptop, a hiring round, weeks of training, and a notice period at the end of which the whole picture walks out of the door with them. A team of twenty on Business is 200 dollars a month. Kazi starts working the day you switch it on, it keeps the record for every person at once, and it never goes on leave.
Questions owners ask
There is nothing for them to learn. Your team is asked for one thing: answer the question when it arrives. It comes to their phone in the evening, it is about their own work, and their home screen opens on Waiting on you with four ready made replies under each question, so answering is one tap. Finishing the job counts as an answer too, and they get a thank you for it. No timesheets, no status forms, no weekly self assessment and nothing extra to type, because the numbers are worked out from the jobs, dates and finished work that already exist. Everyone gets a home screen with their own numbers on it, the same numbers their manager sees, on the same day. Setup includes a live training session and a written manual for the team.
No. Kazi reads what is already true: a job moved, a date passed, a piece of work was delivered. There are no screenshots, no record of what people type, no location tracking, no idle timers and no timesheets. Nobody fills in a form about themselves. Everyone sees their own numbers on their own home screen, the same numbers their manager sees. The evening question is private. It goes to one person, about their own work, and it is never posted anywhere the team can watch. If someone says nothing, that reaches their manager the next morning as one quiet list, never as a callout in front of everyone. The weekly summary is written for you and then sent by a person, or thrown away by a person. Quiet hours, days off, a switch that pauses everything, and the wording of every sentence are yours. What it really does is stop your reliable people from carrying the quiet ones without anybody noticing, which is how you lose the reliable ones.
Then their manager hears about it the next morning, not next month. A question left twelve hours unanswered while the job is still open moves up a level: at 8.30am each manager gets one list of their own people who went quiet, and their home screen opens on it, showing the person, the job, how late it is, how many days they have been silent, and the question that was asked. Ring them, press Called, type what they said, and it goes onto the job and clears the row. It reaches that person’s manager and nobody else, once a day, as a list rather than an announcement. The page that shows whether it is working then tells you how often this had to happen at all, week by week and person by person.
No. You set quiet hours and days off, and every scheduled message obeys both. The settings will not even accept a send time that falls inside your quiet hours. Times are read on your company’s own clock, so 5.30pm means 5.30pm in Nairobi. Each person chooses whether a message reaches them on their phone or by email. One switch pauses every automatic message without touching your schedule, and you can change the wording of each one before a single message goes out.
Kazi is yours because of how it is built, not because of a promise. It runs on your own server. You hold the settings file, the storage and the nightly copies of the database, and putting it all back from those copies is a written procedure that has been done for real. The agreement puts it past argument: if the monthly service stops for 90 days, the source code is handed to you under a permanent licence to use inside your company.
In your own Postgres database, in your own storage, on the machine you choose: Nairobi, Europe, or your own office. A compressed copy is taken every night and the last 14 are kept. No other company is in your database, so there is nothing to share and nothing to leak sideways. AI requests leave your server only when you switch them on, and the key stays on the server, never in a browser.
Yes, and that is the only charge. Team is six dollars per person per month for up to six people. Business is ten dollars per person per month for any size of team. Add a person and the bill goes up by one. Take someone off and it goes down. You are never charged for guests.
Then you already know the shape of the problem. A board holds the work and shows you what exists. It has no view on who is delivering, it never tells you that somebody has gone quiet, and it never follows anyone up, so the following up is still you, twice a week, from memory. That missing piece is what Kazi is: a colour worked out from what people actually delivered, a record for each person that nobody had to type, one shared list of what is urgent, and a reminder that takes one click and stays on the record.
Your jobs, comments, extra fields and documents all come across from whatever you use today. The move is done with you and checked together before anyone switches over, so nothing has to be typed again.
Count the hours you spent last week asking people where things were, and the meetings that existed only to produce an update. Multiply that by what an hour of your time is worth. You are already paying for this. You are paying in the wrong currency, and the bill is a week of your attention instead of a line in the accounts. The prices are above: six dollars per person on Team, ten on Business, and nothing else on the invoice.
Kazi installs as a real app on iPhone and Android, with proper notifications, a five tab layout and a calendar built for small screens. Laptops install it the same way from Chrome or Edge.
No. AI features are switched on for each workspace separately, requests go out only when somebody uses them, and nothing in your workspace is used to train a model. Leave the key blank and the whole workspace runs without it.
Start free
Fill this in and your own private workspace is ready in about a minute. Your own web address, your own database, and your team in it today. Fifteen days free, and no card until you pick a plan.
We have sent a link to . Click it and your workspace is built while you watch, in about a minute.