Running a SaaS solo: surviving your co-founder's paternity leave

Executive overview

When your co-founder goes on paternity leave, you lose more than a pair of hands — you lose the psychological buffer that keeps doubt in check. Tony ran Cloud Forecast alone for six weeks and discovered that managing your own psychology is the hardest part of being a founder, not the execution.

The episode covers three compounding setbacks — stalled pipeline, a failed SDR hire, and solo isolation — alongside two structural wins: a new engineer delivering real output and financial modelling that revealed the team had room to invest more aggressively.

Hiring a new engineer (Katya)

• Katya joined just before Francois left and exceeded expectations.
• Tasked with a front-end redesign using Tailwind, dependency updates, and test coverage.
• The project gave her a structured way to learn the app while delivering tangible output.
• Described as bringing good ideas and diversity of perspective to the team.

The psychology of solo founding

• August was the company's best month: crossed $200k ARR, doubled a key customer's contract, closed a net-new enterprise deal.
• September–October saw a sharp reversal: opportunities didn't close, pipeline stalled.
• Tony's hardest challenge wasn't execution — it was having no one to reality-check with.
• Mastermind group helped, but couldn't substitute for a co-founder saying "it's okay."
• Two mindset anchors that helped: think in years not months; shift from "I have to do this" to "I get to do this."

Why enterprise deals drag

• AWS cost management is rarely a day-zero priority for customers.
• Three patterns in stalled pipeline: non-response after sign-up, free trials ending without conversion, enterprise deals dragging past the 60-day target close.
• Product is more "vitamin" than "aspirin" — useful but not urgent for most prospects.
• Planned fix: expand beyond AWS cost into Kubernetes cost management (Barometer, in beta with 5 customers) and other cost areas like Datadog and Snowflake.

Product market fit as a continuum

• Rob draws on Drip's history: the product was "good enough" until automations and visual workflows made it a clear must-have.
• Product market fit isn't binary — it moves from 1 to 100; above a threshold, inbound demand accelerates.
• Unsolicited customer feedback about Kubernetes costs validated the Barometer bet.
• Barometer target: charging customers by early Q1 next year to generate expansion revenue.

SDR hiring: two failed attempts

• Part-time SDR (10 hrs/week) required too much of Tony's time to manage and left early for a better job.
• Full-time SDR candidate exaggerated experience; pressure tactics during negotiation confirmed the instinct to pass.
• Net result: money and time lost, but Tony reframes it as necessary learning.
• Next hire is being redefined — likely a sales/marketing generalist rather than a pure SDR.

Financial planning and spending the TinySeed money

• 2021 revenue covered all expenses, meaning TinySeed funds were untouched.
• Worst-case scenario modelling (2% growth) shows the business remains profitable even with salary increases.
• Realisation: the team has been too conservative; 2022 plan is to hire one or two people.
• Used Matt Wensing's Summit tool to model scenarios — credited with shifting Tony's mindset from conservation to calculated aggression.