There's a job on every small team that never appears on an org chart. It has no title, no job description, and no backup. It's the job of being the glue — the person who connects the CRM to the inbox to the calendar to the docs to the group chat, entirely inside their own head.
On most teams, that person is the founder.
The invisible job
The glue job is easy to miss because each individual task is tiny. Checking whether the proposal went out. Nudging the designer about the asset. Remembering that this client prefers calls to emails. Reconstructing the context of a deal from four tools before a fifteen-minute meeting.
None of these tasks would justify a hire. Together, they consume the founder's most valuable hours — and worse, their attention.
The daily symptoms
You know you're the glue when:
- Your day starts with a checking round: inbox, CRM, bank, dashboard, chat — not to act, just to verify nothing fell through.
- You nudge more than you decide. Half your messages are "any update on this?"
- You're the only person who can reconstruct context: why this client got a discount, what was agreed on that call, where the latest version lives.
- Vacations are theoretical. Not because the work can't wait, but because the connections can't.
Why it creates anxiety, not just workload
Workload is bounded — you can see it, schedule it, finish it. The glue job is unbounded. It's a background process that never terminates, because its real function is vigilance: making sure nothing slips between tools that don't talk to each other.
That's why the glue job produces a specific kind of founder anxiety. It's not "I have too much to do." It's "something, somewhere, is quietly falling through, and I don't know what."
Why delegation fails
The obvious fix is to hand the glue job to someone else — an assistant, an ops hire, a chief of staff. And it helps, until it doesn't. Because the loop doesn't live in a system anyone can operate. It lives in the founder's head: the triggers, the exceptions, the context, the judgment calls.
Delegating a loop that only exists in your head doesn't transfer the loop. It transfers the symptoms — and adds a translation layer.
From memory to system
The way out is not a better assistant or a better memory. It's moving each loop out of your head and into a system that runs it:
- Name the loop. "After every sales call, the notes get summarized, the CRM gets updated, and the follow-up gets drafted."
- Give it a trigger. The calendar event ending. The email arriving. Monday at 9am.
- Write down the rules you've been applying implicitly for years.
- Mark the checkpoints — where you still want to review before anything goes out.
- Let it run. And let it come back to you only for the exceptions.
Every loop you move out of your head is attention you get back permanently. The glue job doesn't disappear all at once — it dissolves, one loop at a time.
The founder's real job was never holding the tools together. It was deciding what the business does next.