Products are cheap now. Running them isn't.
Artur Sabirov3 min readThe best day of building a product is the one where you ship the thing the moment you think of it. You have the idea at breakfast; by evening it's live and someone is using it. That's the feeling that made you start — and lately, fewer days feel like it.
Not because the ideas got slower. Because everything around the idea got heavier. You write the feature by lunch, then lose the afternoon to the parts that aren't the feature: a database to stand up, a domain to point, a secret to rotate, an agent to let in — each on its own service, its own dashboard, its own bill.
The building half got its revolution
Building genuinely changed, and you can feel it at your own desk. A coding agent turns what used to be a week into an afternoon — the studies put the speed-up near 80%, though you don't need the number to believe it. The tools finally got out of the way, and for a while it felt like the whole job had gotten easier.
Two curves that stopped moving together
The running half didn't move
Running what you built got none of that. The product still has to stay up at 3am. The database still needs the backups nobody thinks about until they're gone, the keys still have to rotate, and someone still has to decide who — and now what — gets to touch production. Most days you write code for an hour or two; the rest goes to keeping it all standing.
If anything, cheap building made that weight heavier. You ship more, so there's more to keep alive. And a new keyholder showed up that you never hired: every agent session is one more thing reaching into production, holding a credential that lives in a config file and appears on no list you keep. There are more of these now than there are people, many times over, and most of us still say "user" and picture a human. The pile was survivable when you added a teammate twice a year. It isn't, when every working day mints keyholders nobody wrote down.
Who holds the keys now
The pile grows faster than the product
Count it up sometime. A three-person team runs deploy on one service, email on another, analytics on a third, then bolts on a tool for compliance, one for publishing, one for support. Five at the start, ten by month six, somewhere around €380–580 a month across six separate bills.
The product, and everything around it
The money was never really the problem; the budget was already spent. The problem is that six bills are six dashboards, six permission models, and six places you have to remember the day a teammate leaves. Onboarding your third hire eats an afternoon of pasting them into accounts. Offboarding eats another, revoking access across ten places and hoping you didn't miss one.
None of this was a decision. It happened one integration at a time, until the job you loved — making the product — had quietly become a second job: keeping the things it runs on in order.
The bet
So here's the bet we're making. The running half deserves what the building half already got: one place, one model. Vercel sells you deploy. Supabase sells you data. Linear sells you tasks. Lessly is one account for the whole stack around your product, so the answer to "where does this live, and who can touch it" is one login instead of ten.
What that actually is today: you push and it deploys, with logs and a one-command way back. Your Postgres is managed, backed up, and stays in the EU; your domains run through Cloudflare. Around that sit the things a product needs early — memory your agents can share, a consent banner, a waitlist, first-party tracking. You run all of it from one console, and so do the agents you build with, over the same API, MCP, and CLI, with the same permissions. Keys, not root: every action named and revocable in one motion, which is what makes one account safe to hand an agent.
How to hold us to it
One honest limit: Lessly is in private beta. The way in is the waitlist, with no self-serve signup and no SSO or roles yet; those land with the public launch, and we'll say they're here only when you can use them.
Related posts
Building Lessly in the open
Follow along, and get early access to the private beta.