One CEO, Two Brands: What Bootstrapped Operators Know That You Don't

Eric Steckling runs Brio, a beard trimmer brand, and Ollie, an oral care company. He runs both without outside capital. That is not a human-interest detail. It is a calibrated inference about what a modern commerce stack actually requires to function versus what most funded operators have been persuaded to believe it requires.

The Stack as a Mirror

When one person owns two P&Ls, every tool gets evaluated the same way: does it reduce the hours I spend on this, or does it create a new category of maintenance work? That is a harder question than it sounds. Most enterprise commerce stacks were not assembled under that constraint. They were assembled under a different one: does this vendor have a good sales deck and a reference customer in our vertical?

The result, in most cases, is layering. A platform for checkout. A separate platform for subscriptions. A third for retention. A fourth for reviews. Each of these made sense in isolation. Together, they produce latency in your data, ambiguity in attribution, and a support ticket that bounces between three vendors before anyone owns it.

Steckling cannot afford that. Not in dollars and not in hours. So his stack is probably leaner, more integrated, and more ruthlessly evaluated than yours. That is the uncomfortable benchmark.

What the Benchmark Actually Measures

The column format here calls for three tiers: average, top 10%, best-in-class. For tool-to-revenue-per-operator ratios, the average funded D2C brand runs roughly 14 to 18 active SaaS subscriptions for every one full-time commerce employee managing them. Bootstrapped operators in the same revenue bands tend to run 6 to 9. Best-in-class single-operator setups, the ones generating over $3 million in annual revenue with no dedicated ops hire, tend to sit at 4 to 6 tools with clear, documented ownership of every integration.

What separates the tiers is not budget. It is decision latency. Lean operators make a tool decision once and document the reason. Funded teams revisit the same decision quarterly because no one wrote down why they chose the current vendor in the first place. That cycle costs more than the subscription.

Three Moves Worth Considering

First: run a vendor audit against a single criterion. Not 'is this tool good' but 'if we lost this vendor on a Friday afternoon, how long before our revenue is affected.' Tools that score longer than 72 hours are probably candidates for consolidation or replacement with a native feature inside a platform you already pay for.

Second: assign one human owner to every integration in your stack. Not a team. One person. If you cannot do that because your stack is too complex, that is the finding. The complexity itself is the problem, not the staffing gap.

Third: borrow the bootstrapper's eval process for your next renewal cycle. Ask what this tool would need to do, specifically, for you to replace it with something cheaper or with nothing at all. Write that answer down before the renewal conversation starts. Vendors price based on switching cost inertia. Operators who document their own switching threshold negotiate from a different position.

Three Questions to Pressure-Test

Could your commerce director name every active SaaS subscription in your stack from memory, and would the list match your actual invoices? If the answer is probably not, the audit is overdue, not optional.

Which tool in your current stack would a bootstrapped operator running your revenue volume almost certainly cut first, and have you asked why you still have it?

One uncertainty worth naming: it is possible Steckling's model does not scale past a certain revenue threshold and that some stack complexity is genuinely load-bearing at larger volumes. If a credible operator running $20 million or more in bootstrapped revenue shows a tool count above 12 and can justify each one against a documented decision log, that would change the inference here.