A composite case study. Names, sectors and timelines are changed. The pattern is drawn from real Irish partnerships.
She did not call it burnout for almost a year. She called it 'a bad month'. Then 'a hard quarter'. Then, eventually, in the passenger seat of her partner's car at half past eleven on a Wednesday night outside St. James's, she called it something closer to the truth.
There were three of them on the cap table. One was a part-time advisor with a small stake. The other two were the operating founders — Niamh, who ran everything customer-facing, and Cillian, who ran the product and engineering. On paper they were 45/45/10. In practice, by month fourteen, Niamh was working roughly seventy hours a week and Cillian was working roughly forty.
How the asymmetry built up without anyone noticing
It did not start asymmetric. In the first six months they were both pulling the same hours. Then a major client onboarding pushed Niamh into a customer-success role she had not signed up for. Cillian, recognising the pressure, suggested she 'take it on for a quarter' while he focused on a platform rebuild. The platform rebuild took eight months. The customer-success workload never went back.
Neither of them had a framework for re-negotiating workload mid-flight. So they didn't.
- Month 0Incorporation. Roles defined loosely as 'commercial' and 'technical'.
- Month 6Major client signed. Onboarding workload absorbed by Niamh.
- Month 9Cillian begins a six-week platform rebuild that becomes an eight-month rebuild.
- Month 12Niamh starts skipping company social events. Cillian assumes she 'just doesn't enjoy them'.
- Month 14Niamh works through a viral infection she should have stayed home for.
- Month 15An ER visit. A conversation in the car park. Cillian learns most of what he should have known six months earlier.
The early warning signs
- One founder consistently sending Slack messages between 11pm and 1am without comment.
- Workload conversations being deflected with 'it's fine, it's just this week'.
- Holidays cancelled or shortened, framed as a personal choice rather than a workload symptom.
- Silent dropping of activities (gym, running, family dinners) that used to be load-bearing.
- The phrase 'I'll be okay once we get through this' used in three consecutive quarterly reviews.
The conversations they never had
- What is a sustainable working week for each of us, in numbers?
- When workload becomes structurally uneven, how do we re-balance — through hires, through equity, through pay, or through scope?
- What is the early-warning signal each of us would commit to raising?
- Are we comfortable telling each other when the other is doing too little?
"He didn't see it because I'd spent a year making sure he wouldn't have to. That's on me. But the structure that made that possible — that's on both of us."
What happened commercially
Niamh took eight weeks of partial leave. The company hired a customer-success lead it had been postponing for nine months. Cillian moved roughly thirty per cent of his time onto commercial work. Revenue dipped for one quarter and then recovered. The relationship took longer.
What PartnerReady would have flagged
- HIGH risk on Commitment: no agreed definition of full-time, no workload review cadence.
- HIGH risk on Decisions: no defined process for re-allocating roles when scope changes.
- MEDIUM risk on Money: no link between workload imbalance and compensation adjustment.
- A specific recommendation to schedule a quarterly 'capacity and load' review with written outputs.
Questions to ask yourself
- If your co-founder were burning out, would you know? What would the signal be?
- Have you defined, in numbers, what a sustainable working week looks like for each of you?
- When was the last time either of you said no to a piece of work and stuck with it?
- What would have to be true for either of you to take a real two weeks off?
The PartnerReady check will usually surface the underlying risk in under ten minutes.
Twenty questions across equity, exits, IP, decision-making and commitment. No account required. No data leaves your device until you choose to generate the report.