← back to all work ← volver a todo el trabajo

Building a 12 week year planner that I actually wanted to use

I was frustrated with clunky spreadsheets and an overpriced official app, so I built my own planning tool. Then hundreds of other people started using it too.

solo builder b2c web app react next.js supabase

The problem

Planning in 12-week cycles shouldn’t require a spreadsheet degree

I’ve followed the 12 week year system for a while. The idea is simple: instead of setting annual goals, you plan in focused 12-week sprints. But the tools available to actually do this were all frustrating in different ways.

Spreadsheets meant duplicating tabs every single week — one tab per week, times 12 weeks, times multiple goals. It was tedious busywork that pulled me away from the actual planning. Notion templates were better but still felt like wrestling a general-purpose tool into a specific workflow. And the official 12 week year app was expensive and, honestly, confusing to navigate.

I didn’t set out to build a product. I set out to build the tool I wished existed for my own planning — something clean, focused, and purpose-built for the 12-week cycle.


What I built

A purpose-built planner that gets out of your way

The core idea was radical simplicity. The 12 week year system already gives you the structure — goals, tactics, weekly plans, a scoring system. The tool just needed to make that structure effortless to follow, not add complexity on top of it.

You set your 12-week goals, break them into weekly tactics, and track your execution score each week. No dashboards full of charts. No feature bloat. Just your plan, your progress, and a clean interface that keeps you focused on the tasks at hand.


Key decisions

What I chose — and what I left out

Clean over clever. Every design decision was filtered through one question: does this help the user focus on their plan, or does it distract? If it distracted, it didn’t ship. No gamification, no social features, no AI suggestions.

Supabase for speed. As a solo builder, I needed auth, database, and real-time sync without managing infrastructure. Supabase let me go from idea to working app fast, with room to scale later.

Free, on purpose. I built this for myself first. Keeping it free removed the pressure to add features for monetization and let me focus on making the core experience great. The product is the portfolio piece — not the revenue stream.


Results

From personal tool to hundreds of users

I launched it quietly — no big marketing push, just shared it in a few communities of people who follow the 12 week year system. It grew through word of mouth.


Reflection

What this project taught me

The biggest lesson was that the best product decisions come from being your own user. I didn’t need user research or A/B tests to know what the right experience felt like — I lived the frustration every week. That empathy for the end user shaped every detail.

It also reinforced something I believe about software: simplicity is a feature. The app doesn’t try to do everything. It does one thing — 12-week planning — and it does it cleanly. That constraint is what makes it useful.

If I were starting over, I’d invest in a simple landing page earlier. The product grew despite having almost no web presence, which makes me think it could have reached more people with even a small effort on distribution.

← back to all work ← volver a todo el trabajo