Blog
Case Study

Case Study: A Startup Founder Sees 3 Months of Calendar Data for the First Time

April 12, 2026·5 min read

Nina had been building for 10 months. First-time founder, B2B SaaS, six people on the team. She was working constantly — evenings, weekends, the whole thing. But something felt off. The product wasn't moving as fast as it should. She kept saying 'I need to get back into the product' and then never quite getting there.

What the Data Showed

She connected three months of Google Calendar history to Tempo and set up five layers: Investor & BD / Team & Operations / Product & Engineering / Admin / Personal. After tagging her events, the distribution was unambiguous.

  • Investor & BD: 62%
  • Team & Operations: 14%
  • Product & Engineering: 9%
  • Admin: 8%
  • Personal: 7%

She was spending 62% of her working hours on investor relations and business development. Her product work — the thing she kept saying was the priority — was getting 9% of her time.

The Revelation

I was running the company like a fundraiser, not a product builder. And the worst part is I genuinely thought I was heads-down on the product. I felt like I was working on it constantly. But I wasn't. I was talking about it.

Nina, B2B SaaS founder

This is one of the most common founder patterns. Investor relations feels urgent and high-stakes. Product work feels like it can always happen tomorrow. The calendar reflects what actually gets protected — not what you intend to prioritize.

What She Changed

Nina set one rule for Q2: Product and Engineering gets a minimum of 30% of her week, every week. Not aspirational — enforced. She tracked it weekly using Tempo's layer distribution view. If the week was trending below 30% by Wednesday, she declined the next BD meeting that came in.

She also restructured her investor communication. Instead of one-off calls scattered throughout the week, she batched all investor and LP touchpoints into a single half-day on Thursdays. Everything else became async — email updates, loom videos, written answers.

The Outcome

By the end of Q2: the fundraising round closed, the product shipped the two features that had been 'almost ready' for three months, and the team described Nina as 'more present' in product reviews. The calendar shift preceded all of it. Not the other way around.

The lesson isn't that investor work is bad. It's that a calendar mismatch between stated priorities and actual time allocation is invisible until you measure it — and once you measure it, you can't unsee it.