Wunderplanning

As a Product Owner running two products in parallel, my own planning was scattered across half a dozen tools — tasks in one app, notes in another, loose to-dos everywhere. Nothing kept them in one place, and nothing started from the question that actually matters each day: what am I focusing on now?

Heavy project tools were too much overhead for personal planning; plain notes were too loose to hold a real workflow. I wanted one opinionated place where tasks, notes and to-dos live together — and where my data stays mine.

One board, three building blocks. Instead of separate apps, I put tasks, notes and to-dos on a single synced board, so capturing a thought never means switching context — the whole board loads and saves as one unit per user.

Focus over firehose. The day starts with a short commitment — a few tasks you can realistically finish — while everything else stays one click away in an overflow. Smart automations pick the focus, boost what's genuinely urgent and keep the board tidy on their own.

Private by default, full-stack, solo. Personal planning is personal, so I treated privacy as a product decision: every account's data is stored separately and encrypted, with key rotation built in. I designed and built the whole thing myself — the React front end, the serverless API and the Postgres data model — to keep full control and learn by shipping end to end.

Wunderplanning is a real, account-based planning app: a unified board for tasks, notes and to-dos, per-user accounts with encrypted storage, file attachments, an onboarding flow, in-app feedback and import/backup of your own data.

Under the hood it's React, TypeScript and Tailwind on the front, serverless API routes backed by a Neon Postgres database on the back, and Vercel Blob for attachments — all deployed on Vercel. It's my personal SaaS testbed for product ideas and small, sharp tools I actually use every day.

Shipping a full product solo — from the first user story down to the database schema and the infrastructure — changed how I work as a Product Owner. Making the trade-offs and living with the consequences sharpened how I scope, estimate, prioritise and write tickets in my day job.

It is an ongoing project. I keep shaping it around how I actually plan, which is exactly the point.