A startup at Startup Burgenland needed user testing but had no budget for it. Zero. They were three founders with a prototype and an empty bank account.
I told them they already had everything they needed. They looked at me like I was being unhelpful.
Their product was for restaurant managers. They lived in a town with forty-seven restaurants. The testing lab was every restaurant within walking distance. The test subjects were the managers they could talk to this afternoon. The incentive was a free coffee and the promise of a product built specifically for people like them.
They tested with twelve restaurant managers in ten days. Cost: EUR 36 in coffee. Insight generated: more than any formal usability study could have produced, because the conversations happened in the actual environment where the product would be used.
That is the Closed World Principle. The best solutions use only what already exists within or near the problem. Not because adding resources is wrong, but because the constraint of using what you have forces a creativity that addition never produces.
Where the Principle Comes From
The Closed World Principle originates from Systematic Inventive Thinking (SIT), a discipline developed from the study of patents and inventions. Researchers found a consistent pattern: the most elegant innovations did not add new components. They reconfigured existing ones.
The classic example is Gutenberg’s printing press. He did not invent new technology. He combined the wine press (existing in every vineyard), movable type (existing in Asian printing), and oil-based ink (existing in painting) into something that changed civilization. Every component existed. The innovation was the combination.
For business founders, the implication is direct: before you buy a new tool, hire a new person, or build a new system, look at what you already have. The solution might be a recombination, not an addition.
How to Apply It: The Four-Step Process
Step 1: Define the Problem Specifically
Not “we need more customers.” Instead: “We need 20 qualified conversations per month with restaurant managers in the Graz metropolitan area who are frustrated with their current reservation system.”
Specificity constrains the problem — and constrained problems have constrained solutions, which are easier to find within your existing resources.
Most founders define their problems too broadly, which makes the solution space infinitely large. Narrow the problem. The narrower it gets, the more likely the answer is already within reach.
Step 2: Inventory Your Closed World
List everything within your immediate environment:
- People: Who do you know? Who do your contacts know? What skills does your team have that are underutilized?
- Assets: What tools, content, data, and physical resources do you already own?
- Relationships: What partnerships, customer relationships, or community connections exist?
- Processes: What activities are you already doing that could serve an additional purpose?
- Knowledge: What do you know from previous experience that applies to this problem?
The task unification framework extends this step by asking which existing resources could serve double duty.
Step 3: Force-Fit Solutions from Within
This is the creative step. Take each resource from your inventory and ask: “How could this resource help solve the defined problem?”
The key word is “force.” Not “could this resource solve the problem?” — that question will produce “no” for most resources. Instead: “If I had to solve this problem using only this resource, how would I do it?”
Force-fitting produces bad ideas at first. Push through them. The third or fourth forced connection is usually where the interesting solutions emerge.
Examples from my work:
- Problem: Need customer testimonials. Closed world resource: Existing customer support conversations. Solution: Extract praise from support tickets and, with permission, turn them into testimonials. No separate request needed.
- Problem: Need market research. Closed world resource: Sales call recordings. Solution: Analyze the questions prospects ask during sales calls. Each question is a data point about what the market cares about.
- Problem: Need a content strategy. Closed world resource: Internal documentation. Solution: Adapt internal SOPs and training materials into public-facing educational content. The content engine can distribute it.
Step 4: Test Before You Add
If the Closed World solution works — even partially — refine it before considering external additions. You might find that the internal solution handles 80% of the problem, and only a small external addition is needed for the remaining 20%.
This is drastically cheaper than the default approach of buying a full external solution. And it is faster, because you are working with resources you already understand.
The Closed World Principle in Product Development
The principle applies powerfully to product development. Instead of adding features, reconfigure existing ones.
A SaaS startup wanted to add a reporting feature. Building it from scratch would have taken six weeks. Using the Closed World Principle, they looked at what already existed: they had an export function that generated CSV files, and their customers already used Google Sheets. Instead of building a reporting dashboard, they created an automated Google Sheets template that pulled from the export and auto-generated the reports customers needed.
Development time: one week. Customer satisfaction: higher than a built-in dashboard would have been, because customers could customize the reports in an environment they already knew.
The instinct to build new features is strong. The discipline to recombine existing capabilities is rare. But it almost always produces faster, cheaper, and often better results.
When the Closed World Is Not Enough
The principle is not absolute. Sometimes you genuinely need something new. The signals:
- You have exhausted every recombination within your closed world and the problem persists.
- The problem requires a capability that does not exist in any form within your environment.
- The cost of the internal solution exceeds the cost of the external one (yes, this happens — forcing internal solutions can sometimes be more expensive than buying external ones).
When you do add something external, add the smallest possible thing. Not a full platform — one feature. Not a full-time hire — a freelancer for a specific task. Keep the addition minimal and reassess whether the closed world can absorb the new element into additional functions.
A Real Example: Closed World Innovation at Vulpine Creations
At Vulpine Creations, we faced a classic growth challenge: we needed more visibility in the magic community but had no marketing budget. Adam and I were fully allocated to product development and fulfillment. Hiring a marketer was not an option.
Closed World inventory:
- We had a growing catalog of products with video demonstrations already filmed for instruction sets.
- We had relationships with performers and reviewers who used our products.
- We had trade show experience and a reputation built at events like the Blackpool Magic Convention.
The solution combined all three. We repurposed clips from our existing instructional videos as promotional content for social media. We asked performers who already used our products to share their experiences in online magic communities. And we leveraged our trade show presence — where we were already demonstrating products — to generate pre-orders and word-of-mouth.
Cost: near zero. Effort: repurposing what already existed rather than creating new marketing assets. The visibility we gained came from recombining resources we already had — instructional footage, performer relationships, and live demonstration opportunities.
Nothing new was added to the system. Everything came from recombining what we already had.
The Closed World as a Default Setting
I recommend treating the Closed World Principle as your default before any resource decision. Before you buy a tool, hire a person, or add a system, spend 30 minutes asking: “Can I solve this with what I already have?”
Most of the time, the answer is yes — or at least “partially, which is enough for now.”
This is not about being cheap. It is about being resourceful. Resourcefulness builds stronger businesses because it creates fewer dependencies, lower costs, and a deeper understanding of what you already own.
The EAOS framework starts with elimination for the same reason: subtraction before addition. The velocity principle benefits from the Closed World Principle because recombining existing resources is always faster than acquiring new ones.
Takeaways
The Closed World Principle says: look inside before you look outside. The best solutions recombine existing resources — people, assets, relationships, processes, knowledge — rather than adding new ones.
Define the problem specifically. Inventory your closed world. Force-fit solutions from within. Test before you add.
The founders who build the most with the least are not lucky. They are disciplined about seeing possibilities in what they already have. That discipline starts with one question: What do I already have that I am not using?
Ask it before every resource decision. The answer will surprise you more often than not.
