There is an old assumption in enterprise software that size must be answered with size. If a large business needs a commerce or booking platform, the thinking goes, it needs a large vendor and a large systems-integrator engagement to match — because only an organisation of comparable scale could possibly build and run something adequate. That assumption held for a long time because it was mostly true. It is quietly ceasing to be true, and the businesses that notice first stand to gain the most from it.
This is for two audiences at once: the digital studio wondering whether it could credibly serve clients far bigger than itself, and the enterprise leader wondering why the answer to every serious requirement is always another eighteen-month integrator contract.
The reason a small team historically couldn't stand up a serious commerce stack was never the interesting 20% — the part that makes a given business distinctive. It was the unglamorous 80%: identity and access, subscription and billing logic, tax, invoicing, refunds and retries, an admin surface someone can actually operate, a mobile presence on two platforms, and the integration plumbing tying it all together. That substrate is enormous, it is largely the same from business to business, and building it from scratch is what made "enterprise-grade" synonymous with "enterprise-sized budget."
Take that substrate off the table — deliver it already built, already wired together, already covering web and native mobile from one backend — and the equation inverts. The work that remains is the differentiated part, which was always the part a small sharp team was best at anyway. The barrier was never talent. It was the months of undifferentiated plumbing that only scale could amortise.
VBWD is a full-stack SDK built to be exactly that substrate: one self-hosted Python core, a Vue/TypeScript web front end, native iOS and Android SDKs, and a plugin system where payments, subscriptions, catalogue, CMS, booking and chat switch on without a restart. The core is agnostic on purpose; a studio's value goes into the plugins and the configuration, not into rebuilding identity for the fortieth time.
The performance envelope matters here more than it looks. When infrastructure imports a million complex products in the time it takes to drink a coffee rather than overnight, a two-person studio can operate a catalogue at a scale that used to demand a dedicated platform team. The heavy lifting is done by the software, not by headcount — which is precisely what lets a small operator credibly carry a large client's workload.
The interesting part for an agency is that reselling or hosting a licence is the least of it. The durable revenue is in the relationship the substrate makes possible:
None of these depend on being large. They depend on the substrate being good enough that a small team's time goes into value rather than plumbing.
This is leverage, not magic. A small studio taking on a large client's commerce stack still needs the operational discipline to run it — the on-call, the backups, the incident response, the account management a serious client expects. What has changed is that these are now the only hard parts, rather than being buried under months of rebuilding identity and billing first. The substrate removes the undifferentiated difficulty. It does not remove the responsibility of running a real business for a real client, and any studio pretending otherwise will get found out. The opportunity is genuine precisely because it still requires competence — which is what keeps it from being available to everyone at once.
If you're on the buying side, the implication is quietly liberating: your options are no longer bounded by the small set of vendors who could afford the old complexity. A focused studio running a modern, self-hosted substrate can deliver an outcome that used to require a marquee integrator — often faster, usually cheaper, and with a codebase and data you actually own at the end of it rather than a dependency you rent forever. The question worth asking your next vendor isn't "how big are you." It's "what do we own when this is done, and how fast can you move."
Whether you're a studio looking to serve above your weight or an enterprise looking past the usual vendor list, the useful next step is the same: see the substrate carry a real workload. Because VBWD is source-available under BSL 1.1 — free for commercial use while annual attributable sales stay below the value of 6.7 BTC per year — you can evaluate it against your actual requirements before any commercial conversation.
Request an enterprise installation → Tell us the workload — yours or your client's — and we'll help you stand it up, so the question of who can serve whom gets answered by the software, not by headcount.