A client project without forty emails
The feedback is in message twenty three, the new deadline in thirty one, and the reply from your colleague is on a different thread. Five habits that keep the client in email and the work somewhere you can find it.
The UnaTask team, Building UnaTask. Mar 12, 2027. 6 min read.
It is Thursday afternoon and the client wants to know where the homepage is. You are fairly sure they approved the blue version. You go looking. The thread has forty messages. The approval is somewhere around message twenty three, except it was an approval of the layout, not the colour, and the colour came up again in a separate thread your designer started, which the client answered from their phone, with one word, to only half the people.
Twenty minutes later you have reconstructed the decision, mostly. You are not completely sure. You write back anyway.
What the thread is really costing
Email is a very good way to talk to a client and a very bad place to keep a project. The trouble is that it quietly becomes both. Every request, every decision, every change of date lives inside a message, and messages are sorted by when they arrived, not by what they are about. After a few weeks, the current state of the project exists nowhere. It has to be rebuilt from the thread every time somebody asks.
Then there is the CC. Five people copied on every message means five people reading every message, most of which is not for them, and five people who might reply. When two of them do, you now have two threads, and the client has two answers.
Nobody decides to run a project this way. It just happens, one reasonable reply at a time.
The turn: the client talks in email, the work lives elsewhere
Keep the conversation where the client is. Keep the project where the team can find it. Most of the mess comes from letting one pretend to be the other.
You do not have to move the client into a new tool, and most clients would rather you did not. What you move is everything that happens after their email arrives.
Five habits that do it
One person talks to the client. Not the only person who ever speaks to them, but the one who owns the channel. Requests come to them, answers go out from them, and the rest of the team is off the CC. This is not about control. It is about there being one thread instead of five, and one voice the client learns to trust.
Every request becomes a task the day it arrives. When the client writes "can we try the logo bigger on mobile", that sentence becomes a task, with a link back to the email it came from, before anybody replies. Now it has an owner, a date, and a place where the work on it will happen. The email can go back to being an email.
The team talks on the task, not in the thread. The designer's question about the logo goes on the logo task, as a comment, naming the person who has to answer. The answer goes there too. Three weeks later, anyone who opens that task sees the whole story in order, without asking anyone and without scrolling through a client's out of office replies.
Write decisions down as one line, on the task. "Decided 12 March: blue logo, bigger on mobile, per Anna." One sentence, with a date and a name. This is the line you went looking for on Thursday, and it takes ten seconds to write when the decision is fresh, against twenty minutes to reconstruct when it is not.
Send one status email a week, same day, three parts. What got done. What happens next. What we are waiting on from you. That last part is the one clients value most, because it turns their silence into a visible item with a date, and it is the one that most quietly unblocks projects. A predictable Friday note also means fewer "just checking in" messages from them during the week.
- One owner on the client channel, the team off the CC.
- Request in, task out, the same day, with a link back to the email.
- Team questions on the task, naming who has to answer.
- Decisions as one dated line, where the work is.
- One weekly note: done, next, waiting on you.
The same Thursday, a month in
The client asks where the homepage is. You open the homepage task. The decision is the last comment: blue, bigger on mobile, 12 March, per Anna. The next step is on the calendar for Friday morning. You reply in two lines, and you are completely sure.
The thread with the client is still there, and it is still email. It is just much shorter now, because it only has to carry the conversation. The project is somewhere else, and it was never lost in the first place.
The bigger idea
Most client friction is not about the client. It is about a project that has no single place where its current state lives, so everyone keeps asking each other what that state is. Give the work one home and the conversation one owner, and the number of emails drops on its own. Nobody had to write fewer. There was just less to ask.