A personal-finance app I own end to end.

On Clempo there's no team to hand things off to. I'm the product engineer for every layer: authentication, multi-tenancy, the data model, and the interface people actually touch. The same person who designs how a household gets isolated in the database also designs how the empty state reads when that household first signs in.

That end-to-end ownership is the whole point. Decisions that usually get lost in the gap between a backend team and a frontend team (how an error surfaces, what a permission boundary means in the UI, where a piece of data is allowed to appear) are all made by one person who has to live with the consequences.

Multi-tenancy is the hardest promise Clempo makes. More than one household's financial data lives in the same system, and the one thing that can never happen is for a household to see (or affect) data that isn't theirs. There's no graceful degradation on that requirement. It's either correct or it's a breach of trust.

So tenant isolation is treated as a property of the architecture, not a filter someone has to remember to add to every query. Scoping a household's data is the default path, and stepping outside that scope has to be deliberate and visible: the inverse of the usual setup, where a forgotten condition quietly leaks rows.

The same judgment I bring to design systems goes into Clempo's interface. Money is stressful, and a finance app earns trust through clarity: legible numbers, recoverable forms, and states that tell you the truth about what's happening. Design and accessibility aren't a pass at the end. They're built in as the product takes shape.

Information is never carried by color alone. Status, errors, and confirmations are expressed through text and structure as well, so the interface stays legible to everyone, including keyboard and screen-reader users. The details most products skip (the empty state before there's data, the focus path through a form) are the ones I deliberately sweat.

Clempo isn't a portfolio mock-up. Real households use it to keep track of their money, which means it has to be correct, private, and dependable every single day, not just on the demo path. That's a different bar than a side project that only ever has to impress in a screenshot.

Running a multi-tenant product with live users is where full-stack ownership stops being a phrase and starts being a discipline. The person who modeled the data is the person who hears about it if the interface is confusing or a number looks off. That tight loop (own it, ship it, live with it) is exactly the kind of product engineering I want to do on a team.