Notes from building products end to end: AI-assisted workflow, design systems, and what shipping solo actually takes.
Some content is global, some is regional. Putting that in a filter menu means the one person who most needs it never sees it — because they never opened the menu.
AI made producing screens almost free. That moved the bottleneck from making things to deciding which ones to throw away — and no model will do that part for you.
Getting two strangers to agree to meet at a park is easy. Getting them to feel fine about it's the entire product — and it's not something you bolt on near the end.
A price of 67¢ tells you the odds are 67%. Almost nobody works that out in their head, and the ones who try get it wrong. Do the arithmetic for them.
An analyst searches for revenue and gets forty results. The search worked. The next twenty minutes — deciding which table to trust — is the part nobody designed.
Most directories let anyone list, then put a badge on whoever checked out. Flipping that — nobody is visible until they're verified — gives you a smaller catalogue and a far more honest one.
A bank was running multi-million-dollar loan deals in spreadsheets. The software that replaces that has to lose to Excel on flexibility and win on the thing Excel can't do at all.
Easy apps hide complexity and charge for it. Pro apps expose everything and assume confidence you may not have. The split is a business decision dressed up as a design one.
Most “I built this with AI” portfolios pick something safe. Safe projects hide the only question worth answering: can you ship something that has to feel right?
A pharma email takes two weeks and touches five teams in five tools. The AI's job is the work between the humans, not the work the humans are legally required to do.
Recording your screen is free. Sending it to someone is what everybody charges for — with watermarks, five-minute caps, and a sign-in wall in front of the person you sent it to.
A demo is the happy path with data you chose. Everything that made my products hard was in the part nobody demos — dates, permissions, empty screens, and the jobs that run while you sleep.
I have four products live that I built by myself. The useful version of that story is the one that includes where solo stops working, which is not where people expect.
Both came out of Stips, both looked perfectly correct, and neither was something the model could have caught on its own. One was about time. One was about permissions.
Most software fails softly. Some of it fails into someone's health, money, or safety. When being wrong has consequences, trust stops being a layer and becomes the product.
Your real competitor is not the other vendor in the bake-off. It is a spreadsheet one person built, everyone trusts, and nobody can be forced to abandon.
Producing options was never the bottleneck. Ring-Rival got good because I deleted things a model would have been happy to keep building.
Engineering cost used to do your prioritization for you. It stopped. Deciding what not to ship is now the only constraint holding a product together.
Every portfolio is polished and every candidate has a shipped demo. What I would ask to find out whether there is judgment behind the artifacts.
Not because everyone won the debate, but because the gap between a design and a running product collapsed. Here's what that changes in practice.
A working demo used to be evidence. Now anyone can produce one in a weekend, and the design job market is still figuring out what to screen for instead.
Polish stopped being a signal the moment it became free. What's left is the stuff a model can't produce for you: constraints, deletions, and decisions you can defend.
Two years of building products solo with AI. The changes are real and specific, and so is the list of things that are exactly as hard as they always were.