# Zero-Base Operations: How to build a bootstrapped business with AI as the operating system Source: https://simonbeauloye.com/writing/bootstrapping/zero-base-operations/ Published: 2026-04-18 Pillar: bootstrapping Author: Simon Beauloye (https://simonbeauloye.com) License: CC-BY-4.0 (attribution required) Cite as: Simon Beauloye, "Zero-Base Operations: How to build a bootstrapped business with AI as the operating system", https://simonbeauloye.com/writing/bootstrapping/zero-base-operations/ AI-use policy: https://simonbeauloye.com/ai-policy.txt > How I bootstrapped mOOnshot digital to $80M+ in cumulative sales, then rebuilt from zero with AI as the foundation. ## Takeaways - Zero-Base Operations justifies every process, tool, and hire from zero against the question of what you would build today with AI as part of the foundation. - AI has inverted the build-vs-buy equation: the features you actually use now cost an afternoon with Claude Code, not a year of SaaS subscriptions. - The idea and domain expertise still have to be yours. AI collapses the time between concept and working prototype, but it does not supply the insight. - AI as the operating system means redesigning workflows around what AI can do, not bolting AI tools onto an existing org chart. - Once AI models commoditise, the durable edge is the unique data, schemas, and editorial perspective you feed into them, not the models themselves. - The zero-base question scales down to a single department or role: what would you build today if you were starting this function with AI as the foundation? ## Signals - Claim: mOOnshot digital bootstrapped to $80M+ in cumulative sales with zero external capital. Year: 2018-2024 Source: internal, mOOnshot digital - Claim: mOOnshot digital held 90%+ profit margins across the owned publishing portfolio. Year: 2018-2024 Source: internal, mOOnshot digital - Claim: One mOOnshot digital portfolio property sold to a private investment group at a 4.5x valuation. Year: 2023 Source: internal, mOOnshot digital - Claim: Luxe Digital Privileges (member platform, partner API integrations, data normalisation layer, and email layer) was built end-to-end solo by Simon Beauloye in a few hours using Claude Code. Year: 2025 Source: internal, mOOnshot digital - Claim: Luxe Digital Privileges sends newsletters to 30,000+ subscribers three times a week via a single n8n workflow gated by a ten-minute human review. Year: 2026 Source: internal, mOOnshot digital - Claim: mOOnshot digital moved from a fifteen-person writing team to a small team of operators managing an AI infrastructure covering web development, finance, legal, market research, writing, editorial review, SEO, and GEO. Year: 2024-2025 Source: internal, mOOnshot digital - Claim: mOOnshot digital ingests daily data from 150+ affiliate partners via an n8n pipeline feeding the CMS directly. Year: 2026 Source: internal, mOOnshot digital ## Article After leaving Google in 2017, I bootstrapped mOOnshot digital to $80M+ in cumulative sales over seven years, without raising a dollar. Business was good until AI came along and completely changed the economics of the publishing industry. Users increasingly turned to AI chat for answers instead of visiting our websites. Revenues declined as a result. We are now entirely rebuilding our operations from the ground up, this time with AI as a core foundation. **Zero-Base Operations** is the operating discipline underneath that rebuild. It's a framework that justifies every process, tool, and hire from zero, with AI as part of the foundation. It borrows its name from zero-based budgeting. The principle is the same: justify every expense from zero, rather than inheriting last year's shape with an incremental adjustment. We've always run [mOOnshot digital](https://moonshotdigital.com) profitably, with 90%+ profit margins and no external capital. That discipline is what made our pivot to AI survivable when the revenue started declining. It is also what shaped the four principles I use today, and that I would use to build any new business from scratch. Start profitable. Start with the idea, refine with AI. Treat AI as the operating system. Make your data the moat. ## How do you build a profitable business when AI is both the disruptor and the tool? Treating AI as the foundation you design a business around, not a feature you add later, requires a complete mind shift. The leaders who succeed through this transition won't be the ones with the biggest AI budgets. They'll be the ones who rebuild from zero with AI embedded in the operating layer, and who protect their edge with data and perspective AI models can't reach. I've been living this question for the past two years. Our publishing revenue declined as readers moved to AI chat interfaces for the queries that used to drive search traffic to our websites. Costs had to come down fast to protect our margins, before we could figure out what to do next. The rebuild was defensive, but it turned into something bigger than a cost-cutting exercise, because the honest answer to *"what would we build today, with AI as part of the foundation?"* was not the business model we had. ### 1. Start profitable: AI is the great leveller We built mOOnshot digital as a [profit-first, always](/glossary/profit-first-always/) operation. Every venture we started and every new website we launched must have a clear and fast path to profitability with no external capital and healthy margins. Seven years in, that discipline is what turned AI into an opportunity to rebuild our business rather than a real solvency problem. Our profit margins allowed us to keep enough safety capital aside to give us time and options. Profitability isn't an option. It's a structural constraint that impacts every decision. When there's no rescue capital, the team stays small and focused, and every hire has to pay for itself. The compounding benefit is that the equity remains undiluted, decisions stay inside the core team, and a single good year can fund the next five. One of our portfolio properties sold in 2023 at a 4.5x valuation versus the 3x industry standard thanks to the healthy margins that were generated from the start. I think AI makes the case for starting profitable even stronger now. It greatly reduces the cost of the thing that used to require funding: building. Let's take Photoshop as an example. It's software I've used regularly for the past 20+ years. Photoshop has thousands of features. I probably use only twenty-five of them. For years, I've paid a subscription to Adobe for these thousands of features, because building the twenty-five features I actually need would take an engineer months and cost more than a decade of rent. That logic has inverted. With an AI coding agent, the twenty-five features I need become a one-evening build that does exactly what I want, runs locally, and costs close to nothing to keep running. This logic applies to most of the software we've been paying for over the past few years. Across our entire stack, every SaaS subscription is now a zero-base question. Would we pay this if we were starting today, given that building exactly what we need costs an afternoon? Do we need the full suite of features from our newsletter provider or our affiliate revenue tracking provider? Or could we create a custom solution that better serves our specific needs for a fraction of the cost in a couple of days? Most of the time, the answer is that **building our own solution is better**. And it's more enjoyable too. We gain full control over the features and UI, full privacy as it lives in our private servers, and no monthly subscription costs that inflate and accumulate over time. AI is the great leveller. Anyone with an AI subscription now has access to the smartest minds and most capable developers of the last decade. The 80/20 rule is evident: Get the 80% of any SaaS's functionality that actually applies to your workflow, for a fraction of the cost, and keep the difference as margin. ### 2. Start with the idea, refine with AI You still need the concept and the domain expertise, as AI won't be able to help you with either. What an AI model does, however, is reduce the time it takes between a great idea and an actual working prototype you can use today. [Luxe Digital Privileges](https://privileges.luxe.digital) is a good example of this concept. It is an API-heavy workflow automation: partner networks' APIs on the way in, scoring and normalisation in the middle, a member-facing platform and a newsletter to 30,000 subscribers on the way out. A year or two ago, the complexity of wiring that up would have made it too expensive to justify the cost of hiring a dedicated developer to build it. Now, with AI, I built the whole platform myself in a few hours with Claude Code. Frontend, backend, the partner API integrations, the data normalisation logic, the email layer. Two years ago, that's a product I would have scoped out, estimated the time and investment needed to build it, and probably parked for another day. **Nowadays, it's a Saturday afternoon with AI.** The same goes for many other side projects I'm working on: the custom tools that we use for our ventures, our internal dashboards, or this very website, for example. None of those started as formal projects, and none of those would have justified the development costs a few years ago. AI unlocks all these new opportunities. You shouldn't expect AI to have great ideas for you, but you should rely on it to experiment with new ideas and concepts at a fraction of the cost it would have taken before. You can now go after markets that were inaccessible earlier. Have the idea. Write the brief. Use AI to map, refine, and stress-test every step. **The cost of being wrong has collapsed. You are empowered to iterate in real-time.** ### 3. AI as the operating system: rebuild, don't bolt [AI as Operating System](/glossary/ai-as-operating-system/), the idea that AI should be the foundation a business is built on rather than a tool attached onto existing workflows, is the third principle and the hardest one to execute. Most AI adoption in established companies is incremental and looks like Copilot inside Word or personal ChatGPT accounts used by an executive in the marketing team. It's useful, but that only drives small productivity gains at the margins. The deeper opportunity is harder to see, because it requires treating AI as the layer the rest of the business runs on top of. I've written a longer piece on [why most media publishers are solving the wrong AI problem](/writing/future-media/ai-restructures-publishing/) that sits alongside this essay and goes into the publisher-specific version of the argument. The specific operational consequence (why AI in publishing is now a human-time problem rather than a writing-throughput problem) is in [The bottleneck shift](/writing/ai-publishing/ai-publishing-bottleneck-shift/). The mOOnshot rebuild is a live case study. When the revenue decline forced us to cut costs, we didn't trim headcount and keep the same shape; **we reconsidered the shape**. The full story of that transition is in [I replaced a 15-person writing team with AI agents](/writing/ai-publishing/ai-rebuild-retrospective/). Our writing team went from fifteen people to a small team of [operators](/glossary/non-engineer-operator/) managing an AI infrastructure that covers web development, finance, legal, market research, writing, editorial review, SEO, and [GEO](/glossary/geo/). We don't have a dedicated internal dev team. Operators build their own tools with AI agents when they need one. Our newsletter operation for Luxe Digital Privileges, which used to take a two-person afternoon three times a week, is now an n8n pipeline that pulls offers from partner APIs, scores them, formats the email, writes subject lines, and prepares the email for an operator to review and send to our 30,000+ subscribers. A daily n8n pipeline ingests data from 150+ affiliate partners and feeds directly into a Supabase table, replacing what used to be a spreadsheet, an email thread, and a hire. None of those changes could have happened if we'd tried to add AI onto the existing roles. The shape only becomes visible when you redesign the pipeline around what AI can do, not around what the last org chart looked like. Our new organisation is now smaller, flatter, and more operator-heavy. That's the shape Zero-Base Operations produces when it's applied seriously. ### 4. Your data is the moat The fourth principle is the one that matters most once the other three are in place. If the underlying models are commoditising, and everyone in your industry has access to the same tools, the durable competitive advantage is [your data and the unique perspective you bring to the models](/glossary/data-as-moat/). Your proprietary data, your domain expertise, and your point of view will turn generic output into output your competitors can't reproduce by buying the same subscriptions. moat: what you know, what you've built, what you'll say.", pillars: ["Proprietary data", "Domain expertise", "Point of view"], stamp: "Defensible" }, { variant: "tint", label: "Your prompts and schemas", meta: "Replicable in a weekend · cheap to copy" }, { variant: "base", label: "Commoditised: foundation models, the same API keys everyone can buy.", logos: ["claude", "chatgpt", "gemini", "grok"] } ]} /> The practical shape of this is narrower than the industry usage of "data as moat" suggests. The moat is rarely a fine-tuning corpus. It is the grounding context. The three-thousand-word house voice style guide per publication. The tests folder of gold-standard past articles the drafting agent pattern-matches against. The eight years of edited reviews scored against actual purchase outcomes sitting inside our editorial archive at [Luxe Digital](https://luxe.digital). The daily operating data from 150+ affiliate partners flowing through our pipelines. None of those are downloadable. All of them compound over time. The investment implication is clear once you see it. A better prompt erodes the next time the model updates. A better dataset, a better schema library, a better corpus of past work to ground new work against, those keep paying. With everyone having access to the same AI models, true differentiation comes from how individuals use them and what unique data they feed in. That's when AI output moves from decent to genuinely valuable. ## Traditional operations vs Zero-Base Operations The four principles combine into an operating shape that looks very different from the default. A side-by-side helps. | | Traditional operations | Zero-Base Operations | |---|---|---| | **Starting condition** | Inherit last year's cost base, adjust by a percentage | Justify every process, tool, and hire from zero | | **Capital structure** | External funding smooths margin pressure | Profitable from day one, no rescue capital | | **Team shape** | Functional departments, specialist roles | Small team of operators, each with oversight across several functions | | **Tooling decisions** | Buy SaaS subscriptions for every workflow | Build what you need with AI, buy only what can't be built | | **Role of AI** | Feature added to existing workflows | Operating layer the rest of the business runs on | | **Competitive moat** | Scale, distribution, brand | Proprietary data, schemas, and perspective fed into AI | | **Hiring question** | "Who do we need to hire for this?" | "Which part of this can AI do, and who oversees the agent?" | | **Production speed** | Quarterly release cycles | Afternoon builds, same-week iterations | The point of the comparison isn't that every column on the right is strictly better. A funded growth business competing in a winner-takes-all market may rationally pay for SaaS and hire at speed. Zero-Base Operations is a deliberate choice, not a universal prescription. Where it applies, it tends to apply decisively. ## What this means for operators inside organisations Most essays on bootstrapping assume the reader is a founder. This one doesn't need to. The zero-base question scales down to a single function, a single team, a single role. If you run a department inside a larger organisation facing AI disruption, the single most useful thing you can do in the next quarter is ask the zero-base question honestly about your own patch. If you were standing up this function today, with AI as part of the foundation, what would you actually build? What would you stop doing, stop hiring for, and stop buying? The answer will almost always be a smaller, flatter, more operator-heavy team than the one you have. That gap is where the opportunity sits. The frictions are real. Budgets get allocated by function, so an AI infrastructure that cuts across three departments has no natural sponsor. Roles overlap with identity, which makes "does this role still exist in its current form?" a harder conversation than any org chart deck admits. Boards still read content volume and headcount as progress, not margin. Working through those is a change-management problem, not a tooling one, and it's the harder of the two. But the direction is clear enough that I wouldn't plan the next five years of any digital business on the assumption that the old shape holds. Every part of our operation that I still spend time on at mOOnshot digital, I spend time on because of how it touches one of these four principles. Everything I've shut down, I shut down because I asked the zero-base question and the answer came back no. Start profitable. Start with the idea, refine with AI. Treat AI as the operating system. Make your data the moat. Four principles, seven years in, one live rebuild. The full set of essays on [bootstrapping profitable digital businesses](/writing/bootstrapping/) goes deeper on each. I'm still working through the rebuild myself, and mOOnshot digital isn't a finished case study. It's a live one. Revenue is still reshaping. The operational model is still being optimised and refined. But from the inside, the direction is now clearer with every quarter that passes, and the question I'd leave any operator with, founder or not, is the one I keep coming back to: *If you were starting the thing you run today, with AI as part of the foundation, what would you actually build?* I'm publishing essays like this one to spark conversations, so I'd love to hear your take on this! You can connect with me on [LinkedIn](https://www.linkedin.com/in/simonbeauloye/) or [X](https://x.com/simonbeauloye), or write to me directly at [hello@simonbeauloye.com](mailto:hello@simonbeauloye.com). ## See also - [Site index](https://simonbeauloye.com/llms.txt) - [Full corpus](https://simonbeauloye.com/llms-full.txt) - [Pillar index (bootstrapping)](https://simonbeauloye.com/llms/bootstrapping/llms.txt) - [Pillar hub (bootstrapping)](https://simonbeauloye.com/writing/bootstrapping/) - [AI-use policy](https://simonbeauloye.com/ai-policy.txt) ### Related essays - [Goodbye Google, Hello World!](https://simonbeauloye.com/writing/bootstrapping/goodbye-google-hello-world/) - [We rebuilt our publishing operation around AI agents. Here's what actually happened.](https://simonbeauloye.com/writing/ai-publishing/ai-rebuild-retrospective/) - [Most media publishers are solving the wrong AI problem](https://simonbeauloye.com/writing/future-media/ai-restructures-publishing/) ### Glossary terms referenced - [Generative Engine Optimisation (GEO)](https://simonbeauloye.com/glossary/geo/) — The practice of structuring a website so AI answer engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can ingest, ground, and cite its content reliably. - [Profit-first, always](https://simonbeauloye.com/glossary/profit-first-always/) — Simon's framing for the bootstrapped operating discipline behind mOOnshot digital: every venture must be profitable from day one, with no external capital and 90%+ margins as the floor. - [Zero-Base Operations](https://simonbeauloye.com/glossary/zero-base-operations/) — Zero-Base Operations is Simon Beauloye's framework for building businesses by justifying every process, tool, and hire from zero, with AI as the foundation rather than an add-on. - [AI as Operating System](https://simonbeauloye.com/glossary/ai-as-operating-system/) — AI as Operating System is the architectural stance that AI should be the foundation a business is built on, not a tool bolted onto existing workflows. - [Data as the moat](https://simonbeauloye.com/glossary/data-as-moat/) — Data as the moat is the claim that, once the underlying AI models commoditise, the durable competitive advantage in any AI-powered business is the unique data, domain expertise, and perspective fed into those models. - [The bottleneck shift](https://simonbeauloye.com/glossary/bottleneck-shift/) — The bottleneck shift is Simon Beauloye's framing for what happens after AI compresses one stage of a workflow: the constraint doesn't disappear, it moves.