Validate ICP budget through interviews before building—if they have no budget, pivot to where money is
Having a real problem isn't enough—your ICP must have budget to solve it. Many startups waste months building for users who love the solution but cannot pay for it. The validation process should explicitly ask about budget authority and purchasing power, not just pain level. If you discover your initial ICP has no budget (like customer success managers often don't), immediately pivot to the department or role where budget exists for that category of solution (like marketing for customer communication tools). Budget location drives ICP definition more than problem severity.
When to use
Early stage when validating ICP through customer interviews. Before committing significant resources to building for a specific customer segment. When you have product-market fit for the problem but sales aren't happening despite interest. Particularly important for B2B products where buying authority is separated from user needs.
Don't do this
Assuming that if customers love your solution, they'll find budget to buy it. Building for end users without understanding who controls purchasing decisions in that organization. Continuing to sell to an ICP with no budget because they're enthusiastic about the product. Blaming sales execution when the real issue is targeting buyers with no authority.
2 Founders Who Did This
Interviewed dozens of customer success managers who loved the personalized video solution for customer communication. Problem was real, but Yosef discovered: 'We understood the main problem was there's no budget with customer success. When they said we had to go to marketing... there's no real budget there.' Had to pivot entire go-to-market from customer success to marketing where budget actually existed for communication tools.
Targeted college dining teams who had no budget allocated for student health analytics tools. Product didn't increase their bottom line