A startup in Burgenland had a customer support problem and a content problem. Two problems. Two potential hires. Zero budget for either.
I asked them a question that changed both problems at once: What if your customer support conversations became your content?
They started recording support calls (with permission), transcribing the questions, and turning the answers into FAQ articles, blog posts, and social media snippets. Customer support volume dropped 35% because people found answers on their own. Content output tripled without adding a writer. One resource — support conversations — now served two functions.
That is Task Unification. Not adding new resources. Making existing resources do more than one thing. It comes from Systematic Inventive Thinking, a discipline that treats constraints as creative fuel rather than obstacles. I have used it across 40+ startups, and it is one of the most powerful frameworks in the entire Subtract to Ship system.
The Principle Behind the Framework
Most people solve problems by adding. Need marketing? Add a marketer. Need better data? Add a data tool. Need more leads? Add a lead generation platform.
Task Unification works in the opposite direction. Instead of asking “What should I add?”, it asks: “What do I already have that could serve an additional purpose?”
This is not compromise. It is not doing two things badly instead of one thing well. When done right, the unified task is often better than either task would have been separately — because the combination creates a feedback loop that standalone resources cannot.
The support-to-content example above is a perfect case. The content was better because it came from real customer questions, not guesses about what customers might want. And the support experience improved because the content reduced repetitive inquiries. Both functions benefited from the unification.
How to Apply Task Unification: The Four-Step Process
Step 1: List Your Internal Resources
Write down everything your business already has. Not what you wish you had. What exists right now.
Categories to consider:
- People: Your team, their skills, their daily activities, their interactions
- Data: Customer information, support tickets, sales calls, usage data, feedback
- Content: Existing articles, emails, presentations, proposals, documentation
- Processes: Onboarding, sales, delivery, support, billing
- Physical assets: Office space, equipment, packaging, printed materials
- Relationships: Customers, partners, vendors, community members
Be specific. Not “we have customers.” Instead: “We have 200 active customers, 45 of whom have been with us for more than 12 months, and we interact with an average of 30 per week through support.”
Step 2: List Your Unmet Needs
Now write down everything you need but do not have enough of. The gaps. The wishes. The things you would do “if only” you had the budget or the people.
Common needs for small businesses:
- More content
- Better customer insights
- More referrals
- Faster onboarding
- Stronger brand presence
- More proof and credibility
- Better documentation
Step 3: Cross-Match
This is where it gets interesting. Take each resource from Step 1 and ask: “Could this resource also serve one of the needs from Step 2?”
Go through every combination. Most will not work. Some will be obvious. A few will be surprising. You are looking for the surprising ones — the connections you have not made because you have been thinking about resources and needs as separate categories.
Real cross-matches I have seen work:
- Sales calls (resource) serving content creation (need). Record sales calls, extract the questions prospects ask, turn those into blog posts and social content. Now your sales team is also your content research team.
- Customer onboarding (resource) serving social proof (need). Add a step in onboarding where new customers share a screenshot of their first win. Collect these systematically. Now your onboarding process is also your testimonial engine.
- Product packaging (resource) serving referrals (need). Include a physical referral card in every shipment with a specific offer. The packaging is already going to the customer — it now also serves as a referral mechanism.
- Team meetings (resource) serving training (need). Record team problem-solving sessions and tag the discussions by topic. New hires can watch real problem-solving instead of reading a manual. Your meetings now serve double duty as training materials.
- Support documentation (resource) serving SEO (need). Your internal knowledge base answers the same questions your potential customers are Googling. Publish a version of it. Internal documentation becomes external content.
Step 4: Design the Unification
For each viable cross-match, design how the unification will actually work. This means answering:
- What is the specific mechanism? (How does the resource serve the additional function?)
- What needs to change in the current process? (Usually very little.)
- Who is responsible for the additional function?
- How do you measure whether the unification is working?
Keep the design simple. If the unification requires a major process overhaul, it is too complicated. The best task unifications add a small step to an existing process — not a new process entirely.
A Detailed Example: Task Unification at Vulpine Creations
At Vulpine Creations, we had a product development process: Adam and I would spend months testing and refining magic effects through hundreds of live performances before bringing them to production. This testing process was our core quality resource — the reason we could guarantee that every product worked reliably in paid professional settings.
Our unmet need was marketing content. We had almost no public-facing content beyond product listings. We knew content would build credibility and attract customers, but neither of us had time to create separate marketing materials.
The unification: we started treating our product testing and instruction filming as content sources. From each product’s development, we extracted:
- Performance principles that applied broadly to the magic community. These became discussion topics in online forums and social channels.
- Behind-the-scenes development insights that showed our testing rigor. These became credibility-building content.
- Clips from our eight-hour instructional videos that demonstrated the products in action. These became promotional material.
One production cycle — a process we were already doing — now generated weeks of content. We did not add a content creator. We did not add a marketing strategy. We unified the product development function with the content function.
The result: our content pipeline was sustained by work we were already doing. The quality of the content was higher than anything we could have produced from scratch because it came from real product development, not theoretical demonstrations.
Task Unification and the Closed World Principle
Task Unification is a subset of the Closed World Principle, which states that the best innovations use only what already exists within or near the problem space.
This matters because adding new resources creates new dependencies. Every new tool, hire, or system requires maintenance, management, and integration. Task Unification creates no new dependencies — it gets more from what you already maintain.
For founders with limited budgets, this distinction is critical. You are not making do with less. You are seeing more in what you already have. The constraint is not a limitation — it is a lens that reveals combinations you would have missed if you could afford to throw resources at every problem.
Five Starter Unifications You Can Implement This Week
If the framework feels abstract, start with one of these proven patterns:
1. Proposals become case studies. Every proposal you write contains your analysis of a problem and your proposed solution. Strip the client-specific details. What remains is a case study structure. Publish it (anonymized) as proof of how you think.
2. Customer emails become content topics. Every question a customer asks you is a signal that other people have the same question. Collect them. Answer them publicly. This is content creation with zero ideation effort.
3. Hiring interviews become market research. When you interview candidates, you learn about what other companies are doing, what tools people are using, and what skills are in demand. Capture those insights. They inform your strategy.
4. Product feedback becomes product roadmap. Not the feature requests — the patterns underneath them. When five customers ask for five different features, they might all be pointing at the same underlying need. Your feedback system is also your prioritization system.
5. Invoices become upsell touchpoints. You are already sending invoices. Add a single line: “Other clients at your stage also use [X service]. Want details?” Your billing process is now also a sales mechanism. Not aggressive. Just present.
Measuring the Impact
Task Unification is worth measuring because it shows you how efficiently your resources are working.
Track two things:
Functions per resource. How many business functions does each major resource serve? If your support team only does support, that is a 1:1 ratio. If your support team also generates content and qualifies leads, that is 1:3. Higher ratios mean more efficient resource use.
Cost per function. Without task unification, each function has its own cost. With it, the cost is shared. Measure the reduction. The support-to-content example above effectively cut content creation costs by 80% because the conversations were already happening.
Track these in your Sunday CEO Review to keep the unification working and spot new opportunities.
Common Mistakes
Overloading people. Task Unification adds a function to a resource, not extra hours to a person. If the unification requires someone to work more, you have not unified — you have just added work. The mechanism should be built into existing activities.
Forcing bad matches. Not every combination works. If the unification degrades the quality of either function, scrap it. A support team that also creates content should not be creating worse content or providing worse support. Both functions must benefit or remain neutral.
Unifying without measuring. If you do not track whether the additional function is producing results, you are just adding busywork. Every unification needs a metric.
Takeaways
Task Unification asks one question: What do I already have that could serve an additional purpose? The answer is almost always more than you think.
List your resources. List your needs. Cross-match them. Design the unification so it adds minimal overhead to existing processes. Measure the result.
The businesses that do the most with the least are not the ones with the biggest budgets. They are the ones that see the most possibilities in what they already have. Stop adding. Start unifying.
For the broader principle behind this framework, see the Closed World Principle. And if you want to apply constraint-based thinking to your product, the MVE approach shows you how to deliver maximum value with minimum features. The velocity principle pairs well here too — once you free up resources through unification, speed becomes your competitive advantage.
