Commerce Software for the Many
Follow the architecture forward and the merchant’s relationship with software changes shape. Today, adopting a capability means adopting a company: another vendor, another data copy, another connector, another dashboard, another line of tax. On one core, adopting a capability means something closer to flipping a switch. Installation becomes activation. The new capability does not arrive as a stranger to be introduced to the business over weeks of configuration; it arrives already knowing the customers, the catalogue, the orders, the permissions and the workflows — because the core knew them before the capability existed.
The difference between adopting a company and adopting a capability.
That changes the merchant’s arithmetic in both directions. Adding becomes cheap: minutes to first value, no integration project, no new tax lines. And — this matters just as much — removing becomes possible: because capabilities are thin and the data lives in the core, no capability holds the business hostage, and the switching tax that locked the old stack together loses its grip. The merchant regains the thing the app economy quietly took from her: the ability to change her mind.
Now widen the lens, because every affordability revolution creates two markets, and the second is usually larger. The first market is visible: the switchers, merchants already paying the tax — stacks assembled, bills rising with their own growth, held in place by the fear of leaving. For them the revolution is substitution and consolidation: most of the utility they built from eight applications, on one core, at a fraction of the combined bill, with one version of the truth and the freedom to leave any part of it. That alone justifies everything above. But the second market never appears in any vendor’s win-loss report, because it was never in the market at all. The starters are the majority of the world’s sellers: the storefront is a social profile, the catalogue is a folder of photographs, the customer database is a phone’s contact list, orders arrive through conversations, payments are confirmed in messages, and follow-up depends on memory. The business is digital without being software-operated.
The affordability revolution serves the switchers — and, more importantly, the starters.
Conventional software cannot serve the starters, and the reason is arithmetic, not neglect: the revenue per merchant cannot carry conventional product development, sales, onboarding and support. The foundry changes all four terms at once. When the components already exist, a product can be adapted to a language, a category or a local practice without building a company around it. When onboarding and support are AI-native, a seller can begin without a consultant. When the interface is conversational, the product meets the business where it already operates. And when the price reflects the useful core rather than the accumulated feature set, serious software becomes possible for very small businesses for the first time. They do not need a cheaper version of the stack. They need to never build one — what they receive is not a consolidation but a beginning: the first complete software memory their business has ever had.
Two honesty notes keep the claim disciplined. First, not every category of commerce software becomes cheap: payments, mission-critical order records, fraud systems and regulated infrastructure hold value that sits beyond code — as the first essay put it, that world stays expensive and deserves to; the foundry attacks repeated engineering and fragmented utility, not trust and risk. Second, success carries its own trap: a thriving core will face pressure to add every requested feature, drift upmarket, and slowly rebuild the bloated suite it was born to replace. The discipline is permanent — products thin, core strong, boundaries clear. The foundry does not need to serve every requirement to transform the market. It needs to serve the common jobs extraordinarily well, and make the uncommon ones easier to add.
And the tax, remember, is not a commerce phenomenon. The clinic runs a stack. The school runs a stack. The professional firm, the local manufacturer, the twenty-person logistics company — all of them are unpaid systems integrators for their own software, all paying five taxes for one utility. Commerce is simply where the fragmentation, the repeated foundations and the unmet affordability are all visible at once — where the primitives repeat, the daily utility is concentrated, and millions of sellers wait outside the market entirely. What ends the tax for the merchant ends it, in the same order, for everyone else: foundations once, capabilities on top, the price of the stack falling to the price of an app.
Closing: The End of the Tax
The first era of commerce software gave merchants access to specialist applications. The second assembled those applications into stacks — and quietly billed the assembly to the merchant. The next era must remove the tax the stack created, and for the first time, it can: AI lowers the cost of producing software; a shared core lowers the cost of producing the next software; the double cut concentrates on useful jobs and eliminates repeated foundations; intelligent surfaces make sophisticated capability ordinary; and falling prices bring in the businesses that were never in the market at all.
The companies that do this will not be recognised by the number of applications they announce. They will be recognised by a curve: product two taking less time than product one, product three reusing more than product two, every connector strengthening the portfolio, every price reduction admitting another class of business into software’s reach. The real proof is the economics of repetition. That is the moment a metaphor becomes a production system — and affordable software becomes abundance.
**
The next era of business software will not be won by the vendor with the largest suite, nor by the buyer with the tallest stack. It will be won by a production system that builds the foundations once and manufactures focused capabilities on top — most of the stack’s utility, at a fraction of the stack’s cost, for businesses that could never have assembled today’s stack at all.
The first essay named the revolution: the software foundry. This one names what it abolishes. The app-stack tax is the AdWaste of software — the money every growing business pays for machinery it already bought. Its collection ends when the foundations are built once.
Not more applications for businesses that already have too many. Better software for many more businesses.
