Project Tracking for Small Agencies Across Africa
A small agency is a juggling act: five clients, three deadlines this week, one client who keeps "just adding one more thing", and a team of four that all need to know what's happening. If that's your Monday in Lagos, Nairobi, Cairo, Johannesburg, Accra or Dakar, the way you track work quietly decides whether you finish on time and get paid on time.
This guide is for agencies of roughly two to twenty people — design studios, marketing shops, software teams, media houses — that have outgrown a WhatsApp group and a spreadsheet but don't want to buy software built for a much bigger company.
What agency work needs that generic task lists don't give you
- Work grouped by client. You need to see everything for one client at a glance, and everything across all clients at once.
- Clear owners and dates. When five things are due Friday, "who has this?" can't be a chat question.
- Approvals that don't stall. A lot of agency delay is waiting on a client. That waiting needs to be visible.
- A record of what was asked for. When scope drifts, you want the original request in front of you.
A simple structure that scales to about ten clients
Start with one team and a small number of boards, then use labels to separate clients. A setup that works for most small agencies:
- One board for active client work, with the statuses To do, In progress and Done.
- One board for internal work — your own website, pitches, admin — so it stops competing invisibly with billable work.
- A label per client, so you can filter to one client in a couple of clicks.
- A ticket for every request, however small, with an owner and a due date.
Worth knowing about limits: Alignr's free plan includes one team and two boards, the Team plan four boards across two teams, and Business is unlimited. Labels are the reason you don't need a board per client — that would use up your boards quickly.
Make waiting on the client visible
Add a status such as "Waiting on client" to your board (statuses are yours to add and rename). It looks like a small thing, but it changes the conversation: a card sitting there for a week is a reminder to chase, and evidence when a deadline slips for a reason that isn't yours.
Working with clients in more than one country
Many African agencies serve clients across borders — a fintech in another country, a brand in Europe, an NGO with offices in three time zones. That adds friction that a single-city agency never sees, and most of it is easy to head off if you write it down:
- Time zones. Note the client's time zone on their label or in the ticket, and agree review windows in their working hours, not yours.
- Working weeks. Weekends differ — in some countries the days off are Friday and Saturday, not Saturday and Sunday — so a "Friday deadline" can mean different things.
- Public holidays. Count both your holidays and the client's when you plan a cycle, or a two-week sprint quietly becomes eight working days.
- Currency. If you quote in one currency and invoice in another, record which one on the ticket so scope and price changes stay comparable.
None of this needs special software. It needs the details attached to the work, where everyone can find them, instead of buried in a chat from three weeks ago.
Handle scope creep with tickets, not arguments
Most scope creep isn't bad faith — the client asks for something small, the team says yes over chat, and nobody records it. Fix this with one habit: every request becomes a ticket. When something new arrives, ask two questions in the ticket itself. Is it in the original scope? If not, does it change the timeline or the price? You're not being difficult; you're making the trade-off visible before it becomes a dispute.
"Yes, we can add that — it moves the launch by three days." is a much easier sentence when the ticket is already in front of you.
Use short sprints for retainer and project work alike
Agencies often assume sprints are only for software. They're just a way of saying "this is what we'll do in the next two weeks." For a retainer client that's the month's content plan chopped into fortnights; for a build it's the next milestone. At the end, a short retro on what slowed you down — usually client feedback, unclear briefs or underestimated design rounds — is how estimates get better over time. Our guide to sprints for small teams covers the basics.
Keep the records you need without the enterprise price
Two things matter for agency cash flow: knowing what was delivered when, and being able to pull it into a report. You can export a board's tickets to CSV or Excel, which makes it easy to build a status update for a client or back up a monthly summary. The analytics dashboard on the Team plan shows throughput and cycle time, which helps when you're pricing the next project.
What it costs
A four-person agency on the Team plan pays $8 a month (USD, $2 per user), and the free plan is enough to test the setup with one or two people first. Compare that against the time lost to one missed deadline. For more on weighing the cost of tools in a dollar-priced market, see our guide to free Trello alternatives for African small teams.
Try it with one real client this week — set up the board, add the requests as tickets, and see how it feels by Friday. Start free.