Stop Paying Rent on Features

Here’s an uncomfortable exercise for anyone running an online store: open your app admin and count the subscriptions.

A landing-page builder. A schema plugin. A survey tool. A subscription widget. Every one of them solved a real problem on the day you installed it. And every one of them is now rent, a small standing tax that never ends and never compounds in your favor. You are paying monthly, forever, for features.

I ran this exercise on my own company and then did something about it: an AI developer seat recoded seven paid apps native to the storefront, landing pages, schema, surveys, subscription widgets among them, and deleted the subscriptions, alongside a platform-tier downgrade worth $2,101 a month. That’s not a projection. That’s a bill that stopped arriving.

The vibe-coding platforms made the first half of this possible, and they deserve the credit. Lovable and Replit conclusively answered “can AI build software?” Yes. It’s commoditized. But there’s a second question they structurally can’t answer: can software be built INTO a company? Their output is an orphan at deploy, no company context, no maintenance owner, no measurement, no idea what your margins or policies or history are. It works beautifully on day one and then nobody owns it when the API changes or the edge case shows up.

The line I keep coming back to: Lovable builds you an app. I want my company to gain a capability. Software born wired, it reads the company record, it goes through the same approval gate as ad spend, it carries an owner and a health check, and it gets graded on outcomes like every other piece of work. Same prompt, different result, because the thing drafting it knows your business. They generate software. The point is to staff it.

Three rails make this sane instead of terrifying. Every build states, in advance, the metric it will move and the date it gets measured, “we shipped it” is not a verdict; “it’s used and it moved X” is. Nothing reaches production without a human clearing it. And every build carries an owner and a health check or it doesn’t ship, no orphan software, ever. The thing that wrote the code is also the thing that watches it.

None of this makes the generators enemies, by the way. They’re engines. Give them a chair and a report card too.

The missing integration you’ve wanted for a year isn’t a feature request on someone else’s roadmap anymore. That’s the shift.

Full write-up, scope, rails, honest caveats about which apps are actually worth keeping, at thinkfigaro.com/developer-seat.