Task tools are excellent at what they do - they hold a list of work. What they can't answer is who that work is for, what it cost and what comes next. Five questions your task manager can't answer, and what to do about it.
Task managers deserve credit. They brought something into companies that was often missing: visibility. Who is doing what, by when, and whether it's finished. Freelo, Trello, Asana and their relatives do that job well, and there's no point pretending otherwise.
But a list of work is only one layer. The second one - who the work is for, what it cost and what should happen next - simply isn't in a task manager. And that's exactly where the hours leak away.
Five questions a task manager can't answer
Try them on your nearest project:
- How much did we actually make on this job? A task manager knows tasks, not the invoice or the logged hours in money.
- Where is the signed contract for this client? Probably in email, on a drive, or in another tool.
- What should happen the day after we finish? Raise an invoice, send a handover report, schedule the service visit. The task manager doesn't know, because it doesn't know the job type.
- How many jobs has this client given us this year? Projects don't relate to one another - each is its own island.
- What did we promise them? That came out of a sales conversation that was never in the task manager.
Every one of these questions is answered the same way in most companies today: somebody opens three tools and spends half an hour looking.
Where the lost hours actually come from
The loss isn't people working slowly. It's three recurring activities:
Retyping. A job arrives by email, gets copied into the task manager, hours go into a spreadsheet, the invoice is raised in the accounting package. The same information passes through hands four times.
Hunting. “Where's that handover report?” “What did we charge them last time?” A ten-second question with a twenty-minute answer.
Reconciling. At month end somebody compares what's in the task manager with what's been invoiced. If it were in one place, that work wouldn't exist.
The same task. Once on its own, once with context.
Nothing is added to the task itself. It simply finally knows which client, job, timesheet and invoice it belongs to.
What a data model adds
The difference between a task manager and a system isn't the number of features. It's that things know about each other.
| What you need | Task manager | System with a data model |
|---|---|---|
| A list of work | Yes | Yes |
| Who the client is | Text in the task title | A record the task points at |
| Time spent | Separately, in a spreadsheet | A timesheet attached to the task |
| Invoice | In the accounting package | Generated from the job |
| Profitability | Manually, after the fact | Recalculated automatically |
| What comes next | In the project manager's head | An automation based on job type |
When a task is linked to a client and a job, margin is a subtraction of two numbers the system already holds. When it isn't, it's half a day in a spreadsheet - every month, from scratch.
You don't need more tools
The instinctive response to this problem is to add another tool - for timesheets, for profitability, for documents. That just multiplies the thing that caused the problem: data in separate places. The fix runs in the opposite direction.
How to move without breaking everything
The move doesn't have to be a big bang. A pattern that works has three steps:
1. Start where it hurts most. For agencies and service businesses that's usually job profitability, or keeping track of what was promised to whom. Build one database first - jobs - and attach clients to it.
2. Add what belongs with it. Timesheets, documents, client correspondence. At this point most companies discover they no longer need half their spreadsheets.
3. Leave tasks until last. They're the simplest data and the quickest to move. And crucially: only now does it make sense, because tasks finally have somewhere to belong.
The step-by-step move is covered in Migrating from Excel or Notion. What job profitability looks like in practice is in The agency that knows what it actually earned. A direct comparison with a specific tool is on the Apexloop vs. Freelo page. The full life cycle of a job, from enquiry to margin review, is in the guide to managing jobs and profitability.
Common questions about moving on from a task manager
Does this mean we have to stop using our task manager?
Not immediately. Plenty of companies start by building job and client tracking alongside the task manager, and only move tasks across once it's clear they make more sense sitting on the job. Nobody is forcing a single-step migration.
Isn't a system overkill for a small team?
Complexity comes from the number of places you keep data, not from team size. A three-person agency with four spreadsheets and a task manager runs a more complicated operation than a fifteen-person firm with one system.
Will we lose the simplicity of a task manager?
A task list stays a task list - it just gains the ability to click through to the client, the job and the timesheet. Anyone who only wants to tick things off carries on ticking things off.