In October 2008, Lionhead Studios shipped Fable 2. It looked like a fantasy RPG. It was actually the closest thing games had to an honest model of how choices compound.
Your character aged in real time. Buying a house updated what you could earn. Helping one NPC closed off another storyline thirty hours later. Morality was not cosmetic — it changed the character model, the city around you, the endings that remained reachable. Players who hated the mechanic still walked away with the intuition: choices are not independent. They compound.
Businesses picked up the same intuition in 2026. The problem is that almost nobody is applying it to their software stack.
The way most companies buy tools
The Fable 1 move — isolated, reversible, low-stakes — has become the default purchase pattern.
A founder signs up for HubSpot because someone on LinkedIn mentioned it. Two months later they add Notion because hiring picked up. Then a scheduling tool, then a dialer, then a data provider, then an AI note-taker. Each purchase happened alone. Each one was reversible. Each one felt cheap because the subscription was twenty euros a month.
Stacked together they form what most B2B teams actually run on: eleven vendors, four logins per person, three overlapping calendars, and a Slack channel that exists only to translate between them. Fable 1 calls these quests. Fable 2 would call them the loading screens before the actual game starts.
The pattern is so common that entire agencies have monetized it. Buy a tool. Hire us to configure the tool. Leave with an invoice, a login, and a vague sense that something is integrated now. Nothing compounds. Six months later the founder buys another tool to patch what the first one missed.
What Fable 2 would tell you to build instead
The choice-architecture layer — the part of the game that decides what choices even appear next.
In Fable 2 the choice was the interface. The system behind it decided which future choices became available. Businesses have the same layer and almost no name for it. We call it the orchestration plane. It is the part of the stack that owns what data flows where, what gets prioritized, what feedback loops exist, and what gets deleted because it is not earning.
Without that layer every tool added makes coordination worse. With it every tool added makes compounding better. The difference does not show up as a line item. It shows up as the founder who can say which of the eleven vendors actually produces a sales conversation this week, versus the founder who cannot. One of them knows what is costing money.
The positioning we picked
Nordspike does not sell tools. Clients show up needing the layer above tools — so that is what we sell.
When Nordspike started, the obvious game was reselling. Retell AI, Hermes, Instantly, Vercel, Supabase — every one has a partner program, and every one has agencies earning fifteen percent to configure them. We deliberately picked the opposite.
The reason is a Fable 2 lesson. The tool vendors are the quests. The architecture that decides which quests are available is the layer we operate on. Once you are there, the tools become commodities you pick by price and switch costs. The value is not in the tool. It is in the infrastructure that makes any tool you pick earn more than it would alone.
That is why you will find tactical blog posts on this site about phone receptionists, invoice processing, lead enrichment. Each of those is a quest. Each one is reversible and cheap to try. The reason they are worth reading at all is that they are built on top of the layer we are actually selling. The layer is the product. The quests are its proof-of-work.
If this is the layer, what does an audit of it look like?
Three questions that separate founders who own the architecture from founders who are renting quests.
We run this on every new engagement. The point is not to catch a client out. The point is that nobody has ever asked them to look at the whole stack with these lenses.
- Can you name the tool that produced your last sales conversation? Most cannot. The founders who can have an owned layer. The founders who cannot have quests.
- If we deleted two vendors tomorrow, which two would your team not notice? The overlap is doing something. The question is whether you have the architecture to see it.
- When your best salesperson closes a deal, what does your tooling do that nobody else's does? If the answer is everything, great. If the answer is nothing in particular, that is the layer showing up as a missing choice.
Every one of those questions is solvable. None of them get solved by buying another tool. They get solved by building the layer above tools, then plugging tools into it once it can tell you whether they are earning.
Why a 2008 video game is the right lens for this
Software folk love to quote sci-fi. The better reference is Lionhead's morality engine.
Fable 2 was a flawed, buggy, at times absurd game. Peter Molyneux promised each acorn would grow into a tree. It did not. But it was one of the first mainstream games that modeled choice compounding in a way anybody could feel.
Most of the founders we work with played it as teenagers. We wrote this for them. The moment you read the line about helping one NPC closing another storyline, you already knew how your CRM should work too.
What to do with this
If you run a service business, the next time someone tries to sell you a tool, run the three questions above on your current stack first. The audit is free and it takes thirty minutes with us, or a day of quiet writing by yourself. If the audit reveals quests and no architecture, that is what Nordspike exists to build.
If you played Fable 2 when nobody was watching, you already know what is at stake. The rest of this site is the tactical version of the same argument. Start with the audit, or read the quests first and come back. Either way, the layer is the product.
