I tracked my productivity for 90 days while building a SaaS - here's what actually moved the needle

The thing I'd add from running my own version of this is that the act of tracking for 90 days probably moved your output more than any single finding inside the data did. You can't watch a number every day without the watching changing the thing being measured. So the honest version of "here's what moved the needle" is usually "here's what I could attribute," which is a smaller and different list than "here's what actually mattered."

What I found is that the legible inputs (hours logged, tasks closed, deep-work blocks) were the easy things to track and the weakest predictors of a good week. The thing that actually correlated was something I almost couldn't measure: whether I'd done the smallest version of the core work before touching any inputs at all. On the days I did that, the rest followed. On the days I optimized the inputs first, I'd end up with a beautiful spreadsheet and a hollow week.

The trap with a 90-day tracking retro is that the spreadsheet rewards what's countable, and the needle-mover is often a behavior that compounds quietly and never gets its own column. You end up crediting the metric that was easy to log instead of the habit that was hard to see.

Curious which of your needle-movers was something the tracking surfaced on its own versus something you already suspected and the tracking just confirmed. The first kind is rare and worth a lot more than the second.

The meta-lesson is as important as the findings: you could answer 'what actually moved the needle' only because you measured it. Most solo founders can't answer that after 90 days - they have a vague feeling but no data.

I've been building around this: a Notion OS for solopreneurs with a Weekly Review database that captures what got done, what got skipped, and what decision changed the week's trajectory. 12-16 weeks in, patterns surface that feel like luck when you're living through them.

What surprised you most - something you expected would move the needle that didn't?

90 days of honest tracking is rare - most founders abandon it after 2 weeks because the data makes uncomfortable things visible.

The pattern that typically emerges: the high-output days aren't the longest ones - they're the ones where you started with clarity about what you were actually optimizing for that week. The low-output days usually share one trait: no clear ops layer to orient from in the morning.

What was the biggest surprise from your data? I'd guess it either confirmed or completely disproved something you believed about yourself.

The 90-day tracking thing is interesting but I'm curious what you were measuring. "Productivity" for solo founders is slippery. Time worked? Features shipped? Revenue moved? All three can trend in opposite directions on the same week.

What I've found tracking my own work is that the useful metric isn't input (hours) or even output (features). It's momentum. Did today's work make tomorrow's work easier or harder? That's the signal that actually predicts whether you're building something sustainable or just accumulating technical debt disguised as progress.

What did you end up measuring, and did the metric itself change what you chose to work on?

Simple things have made a big difference for me. Block out specific times in my calendar every day / every week for deep work and productivity. Put those times in my calendar so that when I'm looking at my calendar, I have confidence that I have times that I can count on actually accomplishing specific things. It also helps me book meetings, calls, etc at times that don't throw off my productivity.

The pairing of 'runs locally' + 'no API keys' is undervalued positioning. It speaks to the technical buyer who has already been burned by SaaS tools that changed pricing, added rate limits, or went down at the wrong moment.

The one-time purchase model makes sense when the tool does a defined job well. What's the job this tool does?

Interesting breakdown.
One thing I’ve noticed working with teams is that productivity often improves not when people work more, but when the next decision is clear.
When ownership and the next step are obvious, execution speeds up almost automatically.