Custom software no longer means what it used to
"Custom" used to be a warning label: expensive, slow, risky, forever dependent on whoever built it. The word survived. The economics behind it did not.
What the word used to price in
Say "custom software" to anyone who bought it before 2020 and watch their face. The word priced in a requirements phase measured in months, a build measured in years, a handover that never quite happened, and a future in which every changed field was a change request billed at consultant rates. Custom meant handcrafted from scratch — every screen, every table, every login form built again, for you alone, at your expense alone.
The risk was structural, not anecdotal. A from-scratch system is a bet that one team, on one budget, gets architecture, security, performance and usability right in a single attempt — while the standard-software competitor amortizes those same costs across thousands of customers. Most companies looked at that bet and, sensibly, declined.
Assembled, not handcrafted
The definition is obsolete because the method is. Authentication, permissions, workflows, document handling, reporting, integrations, audit trails — none of that is your business, and none of it needs building. It exists as proven, reusable components, hardened by every system that already runs on them. What gets made for you is the composition: which blocks, wired how, plus the thin layer of logic that is genuinely yours and nobody else's.
That inverts the old bet. Instead of one team getting everything right once, a shared platform absorbs the hard generic problems permanently, and the custom effort concentrates where it actually differentiates.
The price moved with the method
Assembly changes what a system costs, and — just as important — what a change costs. When adding a capability means composing existing blocks rather than constructing them, price stops tracking effort-from-zero and starts tracking what you actually run. That is why our pricing is a sum of capability weights rather than a per-seat license: the cost model follows the build model.
The after-delivery economics shift hardest. The old custom system froze because change was expensive; an assembled system keeps moving because change is the normal operation of the platform underneath it.
How the pricing follows the methodThe dependency objection
The old warning label had one more line: custom means married to whoever built it. Is a platform not the same marriage with better branding? The difference is what you hold. You own the code, the data and the business logic — the parts that are your business. The platform layer underneath is the part you want shared, because shared is what makes it improve without you paying for every improvement alone.
Depending on a platform that ships improvements is not the old dependency. The old dependency was a consultant who billed you to stand still.
AI replaced the easy part