Bigger-Problem Pivot
Turn a narrow solution's hardest blocker into a broader market opportunity
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 94%
Begin with the obstacle that makes the original product hard to deliver and ask whether that obstacle is more valuable than the original use case. GoCardless started with informal group payments, but the founders discovered that accessing direct-debit systems was itself difficult and that those systems suited many recurring-payment situations. They generalized their solution into a payment-access layer, then gained an early partner whose accounting product served about 25,000 small businesses. After launch, they watched diverse customers adopt the platform and later identified the shared job: businesses with ongoing customer relationships wanted to spend less effort chasing payment. The method moves from blocker, to broader hypothesis, to launch partner, to observed commonality, and finally to a clearer market focus.
Origin
Extracted from The Foundr Podcast
Core principles
- 01A difficult dependency can be the larger problem
- 02Generalize only after observing repeated demand
- 03Use a committed customer to seed the pivot
- 04Let usage reveal the common customer job
How to run it
- 1
Name the binding blocker
Identify the capability that prevents the original solution from working well, rather than treating every difficulty as equal.
Pro tip Look for a dependency that is hard to access or use, not merely inconvenient.
- 2
Test for shared pain
Investigate whether other businesses or use cases struggle with the same capability.
Pro tip Compare use cases by the underlying job, not by industry label.
Watch out One founder's frustration is not yet market evidence.
- 3
Generalize the solution
Redesign the narrow feature as a reusable layer that can serve the wider set of customers.
Pro tip Preserve the original insight while removing unnecessary limits on who can use it.
Watch out A broader product without a precise underlying problem becomes unfocused.
- 4
Find a launch partner
Work with a customer that already needs the generalized product and can seed meaningful usage.
Pro tip A distribution partner with existing customers can accelerate learning.
- 5
Find the common job
Study the customers who adopt, identify what they share, and sharpen positioning around that recurring job.
Pro tip Allow real usage to refine the market definition over time.
Watch out Do not force early customers into a pattern the evidence does not support.
In the wild
GoCardless began by helping informal groups collect money. Difficulty accessing direct debit revealed a broader opportunity, so the founders opened the capability to any suitable collector. An accounting-software partner committed before the product was finished, and later usage showed that customers shared an ongoing need to collect payment reliably.
→ The company moved from a small consumer use case to a recurring-payments platform for businesses.
Common mistakes
Staying loyal to the first use case
The original customer scenario can obscure a larger problem discovered while trying to serve it.
Broadening without a common job
Serving unrelated users is not a strategy unless observation reveals a shared problem the product solves.
Is it for you?
Best for
Teams whose initial product depends on a capability that is difficult for many other customers to access.
Not ideal for
Founders pivoting only because the original idea is temporarily difficult, without evidence of broader demand.
From the episode
225: New Founders Doubled Business and Hit Their First $10K Month (Consulting Empire Spotlight: Part 2)