If Vulc vanished tomorrow

Somewhere in your admin there is a list of subscriptions that reads like a payroll. Every tool on it almost fits. Every one of them bills you monthly for the privilege of bending your workflow around it. I think established businesses deserve a better deal than renting forever.

What renting actually costs

The subscription price is the visible part. The invisible part is the shape tax: your process bends to the tool, and your data lives in someone else's schema. The roadmap serves the vendor's average customer, never you specifically.

And when the vendor raises prices or sunsets the product, the function you built on top of it goes with them. You did not own a capability. You borrowed one.

What owning means, concretely

When I hand off a build, ownership is not a metaphor. You get the code, the credentials, the documentation and the runbooks, and the system runs in your environment on your accounts. If Vulc disappeared tomorrow, your system would not notice.

That sentence is the test I build against. Every architecture decision has to survive it.

The honest anchor

A custom build should be priced against the alternative you were actually considering: another hire, or another year of subscriptions stacked on subscriptions. A hire costs the same salary every year and leaves with the knowledge. A build is paid for once, and it gets sharper with every edge case you feed back into it.

Where a retainer fits

Some owners want the system extended and tuned every month, so there is an optional retainer for exactly that. It exists to improve the thing you own. It is not a way to rent it back to you, and the system keeps running if you stop paying. Ownership with an asterisk is not ownership.