A website, a third studio, and a goodbye
The studio looks a little different this week. One project has a new public home, another has joined the lineup, and the first one I ever built has reached the end of its life.
Fazon has a website
Fazon's website is live, with a waiting list for the iPhone app. Fazon is a time-limited weight-loss program built around walking, protein, and a coach that helps you adjust course. An active phase lasts 4, 8, or 12 weeks; everyday tracking continues for free afterward. The site explains that rhythm more clearly than a feature list could.
If you open it on a desktop, try scrolling through the story. A phone stays beside the text, moves as you go, and changes screens as the phase unfolds. I wanted the page to show what the transition from everyday tracking to a focused phase and back feels like. On smaller screens, or with reduced motion, the story works without that animation.
The waiting list is deliberately simple: send an email from the site and I will write when the beta opens and again when the app reaches the App Store. There is no app release to announce yet. This week also brought more work on iCloud sync, a way to delete your Fazon data, and the remaining beta gates. I would rather get those right than mistake a live website for a finished app.
Build, Launch, Run
Last week I introduced Launch Studio, which handles the work of reaching people after a product has been built. Run Studio now has its own project page. Together with Build Studio, the idea is clearer: build the product, launch it, then keep the business behind it running.
Run Studio starts with finances: seeing what the studio costs, which product a cost belongs to, and which decisions need a human review. It is a local macOS app in early development. The app foundation and product registry exist; the financial evidence and accounting handoffs are still being built. The images on its page are design previews, not screenshots of a finished finance tool. Each of the three Studios can stand on its own, even though I am designing them to work together.
Goodbye, Skrivhjälp
Skrivhjälp has reached end of life. It was my first project: a guided way to write formal Swedish letters without needing to know how to prompt an AI assistant. You chose the situation, filled in a few details, saw a preview, and paid once for the finished text.
It taught me more than how to generate a letter. I learned about SEO, Stripe checkout, payments, and all the work around getting a small product into the world. But it attracted very little traffic. Looking back, I think I was a couple of years too late with it, and keeping the service running no longer made sense. The service is retired; the project page stays as a record of what I built and what it taught me.
Elsewhere
Launch Studio has added a closer look at search: Google search data and the queries worth following now have a place alongside its existing planning and content work. Run Studio has also been building out its Home, cost views, and Settings. Both are moving quickly, but neither is being presented as a finished public product.
What's new in Build Studio
Build Studio has gained a work queue for planning the next pieces of work while I am at my computer. Later, when I am out, I can ask Codex to check Build Studio's read-only overview through its local API: what is running, what needs me, and what is next. When the current task has finished, I can ask Codex to start the next one from the queue. Nothing starts automatically; the queue gives me a way to keep work moving without being at the desk.
The execution flow has changed too. The leaner chain is now the default, there is a direct way to create a backlog story, and review findings that only I can resolve no longer send agents through pointless fix loops. Checks that require me to look at a screen or try an app are collected at the end of a run instead of masquerading as code defects. There have been smaller reliability fixes around stalled agents, QA reruns, project-server ports, and resuming Codex agents after a usage limit.
If you run Build Studio from source, some of these changes need a rebuild, restart, or a check that each project's configured port matches the one it uses. The changelog has the exact upgrade steps.
The common thread this week is less glamorous than a launch banner: a public page that explains a product honestly, a clearer place for the work after launch, and knowing when to let an old project end.