Every new SaaS I start follows a rough 30/30/30 split. It's not a rigid formula, but it keeps me honest about where the time is actually going.
Days 1–30: Talk and prototype
I spend this month mostly not coding. Talking to potential users, sketching the smallest version of the product that could possibly be useful, and building just enough of a prototype to have a real conversation around.
Days 31–60: Build the core loop
Now the coding starts in earnest. I focus only on the one core loop that delivers value — everything else (settings, polish, edge cases) waits.
Days 61–90: Get it in front of real users
Launch small, watch closely, and fix what actually breaks instead of what I assumed would break. This is usually where the real roadmap gets written.