Blog

Notes on development, design, and the decisions behind them.

Monitoring dashboard of a SaaS in production with real-time metrics
4 min read

Building and running a SaaS: what changes once customers are paying

There's a huge difference between building a product and keeping it running on a Tuesday at 3am when a payment webhook fails. What I learned taking GymSmartAccess from idea to a real business.

Read note →
Diagram of business decisions preceding a product's technical architecture
4 min read

The decisions behind a SaaS that have nothing to do with code

The framework you pick matters less than you think. The decisions that actually determine whether a product survives happen earlier, and they're business decisions, not architecture ones.

Read note →
Comparison between a small working product and an incomplete version
4 min read

What an MVP is and isn't (almost everyone defines it wrong)

The acronym gets used to justify two opposite things: shipping little and shipping badly. The difference matters, especially if you're the one paying for the build.

Read note →
Product scope diagram showing features inside and outside the first version
5 min read

From idea to MVP: how I decide what to build and what to leave out

The hard part of an MVP isn't building it, it's cutting it. The method I use to decide what goes into the first version, with the real decisions behind the SaaS I run in production.

Read note →
Checklist for hiring a custom software development project
4 min read

How to hire custom development without it spiraling out of control

Most custom projects don't fail because of bad technology. They fail over decisions made in the first week that nobody revisits until it's already expensive to fix. The guide I'd give a client before the first meeting.

Read note →
Résumé comparing a generic description with a specific decision description
3 min read

My résumé stopped being a list of technologies, and conversations changed

React, Node, TypeScript — anyone can write that list. What I changed was telling what decision I made and what happened, not which tool I used to make it.

Read note →