Mail comes to the founder because the founder is who the client bought, because answering takes ninety seconds and explaining takes six minutes, and because the one person who routes everything is the only person with enough context to route it. None of that is a discipline problem, and trying harder has never once fixed it.
- A founder’s inbox is the company’s routing table, held in one head and readable by nobody else in the building.
- Answering is faster than handing over. That is true in every single instance, and it is still the thing doing the damage.
- Your team is not underused because they are idle. They are waiting behind the one person everything has to pass through.
- Software cannot decide what you should stop doing. What it can do is stop the eighty messages anyone could handle from competing with the three that genuinely need you.
How everything ended up coming to you
Nia founded a public relations firm six years ago and there are seven of them now, including two account leads who are, by any fair measure, very good. She is the founder, and on a Tuesday she will read and answer around ninety messages, of which perhaps six actually need her.
None of this was decided. It accumulated, and every path it runs on was correct at the moment it formed.
Her address is on the contract, because she signed it. It is on the proposal that won the account eighteen months ago, because she wrote that proposal. It is on the card she handed a journalist at a drinks thing in 2021, and that journalist, who has known her nine years and does not know the account leads at all, still writes to her when he wants a line by four o’clock. A client’s marketing director copies her on everything, mostly out of courtesy, which is a request wearing a coat. In year two she was the account lead on all of it and answering everything was not a bottleneck, it was the job.
So the firm grew and the routing did not. Seven people now do the work that one person used to do, while the question of who should handle any given message is still answered by the same person, in the same way, at the same speed, which is as fast as she can read.
Why answering is always faster than handing over
The best name anybody has given this belongs to William Oncken Jr. and Donald Wass, who called it the monkey, and whose opening question in Harvard Business Review is still the whole diagnosis: “Why is it that managers are typically running out of time while their subordinates are typically running out of work?” The next move on any piece of work is the monkey, and it climbs, one small and entirely sensible transfer at a time, from the person who should be carrying it onto the person who has just been asked about it.
That is an argument rather than a measurement, and it is worth treating as one. What makes it ring true in a small firm is the arithmetic underneath it, which anybody can do on their own week.
A journalist wants a comment by four. Nia knows the client, knows what they will and will not say, and can write the two sentences in ninety seconds. Handing it to the account lead means explaining who the journalist is, what the client’s board is nervous about this quarter, and why the phrase they used last spring cannot be used again, which is six or seven minutes if it goes well. Then it comes back for a check, which is another three, and there is a real chance of it coming back wrong, which is the whole afternoon.
Ninety seconds against ten minutes and a risk. She answers. Anybody would answer, and on that message answering is the correct decision. Do it forty times a week and the correct decision has quietly become the shape of the company: her capacity is the binding constraint on everything, and two good account leads are underneath her waiting for work they are perfectly able to do.
There is also the part nobody admits, which is that answering is satisfying. A handled message is a finished thing. Briefing somebody is an unfinished thing that will come back, and at half past five on a Tuesday, finished is what you want.
The routing table nobody else can read
Ask why the account leads cannot simply take it on and the honest answer is not that they are not ready. It is that routing this mail correctly needs context that exists in one place.
Which client is fragile this month. Which journalist is owed a favour and which one burned them in March. What was actually promised in a meeting eleven months ago that never made it into writing. Whether the marketing director copying her in is being polite or is quietly escalating something. None of that is in a document. It is in Nia, and it got there because she has been the one handling everything.
That is the loop, and it is why the problem is stable rather than temporary. She routes everything because she is the only one with the context, and she is the only one with the context because she routes everything. Six years of that is not a habit anybody can break by resolving to break it on Monday.
It also means the company has concentrated two different things in one person without ever writing either down. Its throughput, which is capped at how fast one person can read and decide. And its risk, which is that the day she is in a pitch, or ill, or on a plane, the routing simply does not happen and nothing tells anybody it did not.
What a bottleneck costs the people behind it
The cost is not that work gets dropped. It mostly does not, because Nia is conscientious and the work gets done. The cost is that it gets done by the wrong person, promptly, and three other things happen instead.
Clients wait. Not for the answer, which anybody in the firm could have given, but for the one person who gives it, who is in a pitch until three. A firm whose response times are set by its founder’s diary has a service level nobody chose and nobody can see.
The team stops forming judgements. This is the uncomfortable one. If every decision passes a founder’s desk, the people behind it learn, quite rationally, to bring questions rather than answers, because bringing an answer risks being wrong about context you were never given. Two account leads who could have made the call are, six years in, slightly less able to make it than they would have been in a firm that let them.
And the work that only the founder can do is the work that yields. The new business pitch, the hire, the decision about which of two directions the firm takes next: those are the items on Nia’s list with no external deadline, no client waiting on them, and nothing that will go wrong today if they slip. Everything else in her inbox has somebody at the other end of it. So the responsive work wins, every day, and it wins for the same reason it was right to answer the journalist.
What changes when the ranking is not yours
Nothing here reorganises a company, and anything claiming to would be lying. What changes is narrower and, for a founder, more useful than it sounds: which messages are in front of you, and how much you have to open before you know.
The feed leads with what genuinely needs Nia today, ranked on consequence and on how soon rather than on the minute it landed. The six sit at the top. The eighty-four are still there, in an order that makes sense, not competing with the six for the same ten minutes. Each thread carries a plain summary, which for a bottleneck is the load-bearing part: opening a message is the act that makes it yours, and a line telling you what a thing is before you open it is the difference between routing and absorbing. How that ranking is arrived at is a subject of its own, and so is naming the people whose mail must never sink.
Handing something over stops requiring her to remember it afterwards, which is most of why handing over is expensive. What she has passed on is tracked, and she is reminded to chase at the point it needs chasing rather than at three in the morning. Her mail and the firm’s own conversations sit in one live feed, so passing a thing to an account lead does not mean opening another app. A short briefing at a time she picks gathers what needs her, and outside it she says what deserves to reach her mid-morning, which is how ninety unbroken minutes for the pitch become possible at all. Meetings arrange themselves against a calendar already reconciled, which matters more than it sounds when the scarcest resource in a firm of seven is one person’s diary.
Her people sit under one roof with seats added as the firm grows, and if she runs a second company it stays sealed off from the first. All of it connects to the mail the firm already has, on Google or on Microsoft 365, with every address, contact and thread of history exactly where it was. Point is the product, benefits is the flat inventory, and what a calm inbox feels like is the version with a morning in it.
What no email client can do about this
Start with the three it cannot touch, because a founder who is told this solves the bottleneck will believe it for about a fortnight.
It cannot make a client write to somebody else. Your name is on the contract and the journalist has had your address for nine years. Mail addressed to you will go on being addressed to you, and the only things that change that are an introduction you make in person and an account lead the client comes to trust.
It will not decide what you should stop doing. Which of the eighty-four are genuinely yours is a judgement about your firm, your people and what you are prepared to have done slightly differently from how you would do it. Software has no view on that and should not pretend to.
And there is no shared mailbox here, which is worth stating plainly because it is the first thing founders ask for. Point does not offer one. Everyone signs in as themselves and their own mail stays their own; what is shared is the business, one organization with your people inside it. Letting the team read the founder’s inbox would not have fixed the routing anyway, because the routing was never a permissions problem.
On what it does do, the settings matter. Autonomy is set per kind of action, and a new account has all of them where Point prepares something and then waits on you. Move one up when you are ready to stop reading its previews, and it will stop checking with you on that class of work, which is the point of moving it at all. Everything done for you is listed with its timestamp, and most of it can be put back from that list. A message that has already left cannot be brought back, here or anywhere else.
The test to hold it to is not whether your inbox got faster. A faster bottleneck is still a bottleneck. It is whether, on a Tuesday in three months, the six messages that needed you got you, and the eighty-four went where they should have gone without passing through your head first.
Common questions
Is this a shared inbox for my team?
No, and that is deliberate rather than a gap. Everyone signs in to their own mail and keeps it, and what you share is the business itself, with your people in it. A shared mailbox answers a different question, which is how several people work one queue without colliding. The founder problem is not two people opening the same message. It is that everything arrives at one person in the first place.
How do I stop clients writing to me directly?
Mostly by introducing somebody, in person or on a call, and then visibly not being the one who replies for a while. That is an act of management rather than a setting, and no software does it for you. What software can do is stop the mail that still comes to you from all looking equally like it needs you, so the introduction is a decision you make on purpose instead of one you keep postponing because your inbox is full.
Will it reply to clients on my behalf?
It writes the draft, in the way you write, and by default the draft waits for you. The decision to send is yours until you raise the setting yourself for a particular kind of work, which most founders do first for the low-judgement traffic like arranging times. For anything a client would read as coming from you personally, that setting is worth leaving exactly where it is for a good while.
We are seven people. Are we too small for this?
Size is the wrong question, and the right one is whether one person is the route everything takes. That is often more true at seven people than at seventy, because a firm of seventy has usually been forced to build the routing and a firm of seven has not. What decides it is whether your day is spent being the switchboard rather than doing the work only you can do.
I run two companies out of one mailbox. Does that work?
Yes. The two are kept apart, each with its own mail, tasks and people, and switching from one to the other carries nothing across. The wall is between companies you own. It is not a way of partitioning clients from one another inside a single company, which would break half of what makes the ranking worth having anyway.
The short version
A founder ends up answering everything through a sequence of individually correct decisions: you are on the contract, you have the context, and answering is quicker than explaining every single time. The result is a company whose throughput and whose risk both sit inside one person’s reading speed, with capable people waiting behind them. No email client reorganises that, and any product suggesting otherwise is selling you a fortnight of optimism. What it can change is what reaches the top, whether you have to open a thing to find out what it is, and whether handing something over also means remembering it forever. The measure three months from now is not that your inbox is faster. It is that the messages which genuinely needed you got you, and the rest did not have to come through you at all. For the version written for your trade, there are PR firms, consultants and the other six.