Call notes from a first conversation. Anonymised, shared with consent.
This call was with a second-line leader at a very early-stage, remote-first company. Small core team, global stakeholders, long deal cycles, high-touch relationships throughout.
She joined close to inception and over two years grew into a de facto Founder's Office role: investor relations, deal coordination, marketing oversight, events, hiring inputs, and the day-to-day glue that holds a distributed company together. On paper it reads like a dream role. It carries a cost almost nobody names.
Why she reached out
This wasn't a job-seeking call. It started as a connection, a curiosity-driven conversation, a way to talk to someone who understood how messy founder-adjacent roles get.
A pattern was forming underneath it. She was carrying a disproportionate share of context, responsibility and coordination, and she was starting to feel the edges of being the only person holding it together.
What she thought the situation was
She described her days as wearing multiple hats: investor and client coordination, sourcing and evaluating partners, end-to-end transaction ownership, marketing oversight and brand visibility, conference strategy and speaker placements, plus whatever caught fire that week.
She talked about the work with pride, and also with fatigue. The same concern surfaced several times in different words, and the plainest version was this: if two or three things need attention at once, her bandwidth doesn't allow it.
What I was listening for
I didn't interrupt the flow. I listened for structure, and ran five questions in my head while she talked. Who else can do what you do? What breaks if you step away? Which of these responsibilities is genuinely delegable? Where does the founder depend on you most? What actually happens when you're overloaded?
She never answered those directly. The answers were obvious anyway.
What became clear
She wasn't busy. She was structurally central, which is a different diagnosis with a different fix.
She held investor context nobody else had. She coordinated across functions with no backup. She absorbed urgency from every direction, and while she could step into other people's roles, nobody could step into hers.
This is the quiet failure mode of Founder's Office roles at very small companies. They scale responsibility much faster than they scale support, and the person in the seat usually notices last because the growth feels like trust.
The real issue
Not workload. Irreversibility.
Her role had become critical and fragile at the same time, valuable and unscalable, trusted and exhausting. When one person becomes the connective tissue for everything, delegation stops being possible without duplication, and duplication is expensive enough that nobody approves it.
At that point the system isn't resilient. It's dependent, and it will stay dependent until something forces the question.
What we talked through
Founder's Office cannot be a single point of failure. If the role can't be backed up, it will eventually burn out whoever holds it, and the company will call that a personal resilience problem rather than a design one.
Wearing multiple hats works up to a point. Past a certain scale it stops being versatility and starts being risk on the balance sheet, even though it never appears there.
Hiring a second Founder's Office person isn't automatically the answer. Often the real fix is pushing ownership back into the functions rather than stacking another layer on top of them.
Remote-first setups make this worse. Without informal context sharing, dependency concentrates even harder on the one person who knows everything, because there's no hallway where knowledge leaks out by accident.
And compensation conversations tend to expose the structural truth. When scope grows faster than budget, the misalignment surfaces eventually, usually at the worst possible moment.
How it ended
No dramatic resolution. What shifted was awareness.
Not "I need to do more," but "this setup cannot stay this way without consequences."
That realisation is usually the first step towards either redesigning the role or outgrowing it. Either is better than staying where she was.