Three months of work, grouped by the problem each piece actually solves for you.
We ship continuously — small improvements land most days, and you'd go cross-eyed reading a raw commit log. So every quarter we step back and tell the story behind the changelog instead: not what changed, but what got easier. This past quarter came down to two themes — making billing something you never have to think about, and making the admin fast enough that you forget you're using software at all.
Billing you don't have to babysit
The largest piece of work this quarter is also the most invisible: a central billing system that handles plans, upgrades, downgrades, and recurring subscriptions in one place. If you're on a paid plan, or you sell subscription products of your own, this is the engine quietly keeping everything in sync underneath you.
We'll write more about why we rebuilt billing from the ground up in a separate post, because it deserves one. The short version: billing is the part of a platform that's invisible when it works and catastrophic when it doesn't, and the old approach was starting to creak. Centralising it means there's now a single, well-tested place where all the money logic lives — which is exactly what you want for the part that touches money.
- Central admin now manages plans and subscriptions from a single screen.
- Self-service plan upgrades and downgrades, with proration handled automatically.
- Subscription products with flexible billing intervals for your own customers.
- A faster admin — the screens you use most now load in a fraction of the time.
- Dozens of smaller fixes across inventory sync, search, and the order timeline.
An admin that keeps up with you
Speed is a feature people only notice in its absence. When a screen takes three seconds to load, you feel it every single time — and over a working day, those seconds add up to real friction and real frustration. So we spent a good chunk of the quarter making the admin quicker, focusing on the screens you actually live in: orders, products, and the dashboard.
The result isn't a dramatic new feature you can screenshot. It's the absence of waiting. The admin should feel like it's keeping up with your thinking, not making you pause while it catches its breath. That's the bar we're aiming for, and we moved meaningfully closer to it this quarter.
“A changelog tells you what changed. We'd rather tell you what got easier.”
Why we group releases by benefit
A raw changelog is a list of commits. That's useful for us and almost useless for you. So we deliberately organise what we ship around the outcome — 'billing you don't have to babysit', 'an admin that keeps up with you' — because that's how you actually decide whether an update is worth your attention. You don't care that we refactored a service; you care that upgrades now just work.
It's also a small accountability mechanism for us. If we can't describe a release in terms of a problem it solves for a real merchant, that's a sign we built something for ourselves and dressed it up. Forcing every update into a benefit sentence keeps us honest about what's worth shipping.
What's next
Next quarter we're focused on deepening the analytics layer and pushing even more of our internal operations onto AI agents — which, indirectly, is what lets a small team ship this much in the first place. Everything above is live in your admin right now. If something here solves a problem you've been working around, you don't need to wait for anything — go and use it.
