Even a marquee, hyper-growth customer can be a net negative. AppDynamics chose to part ways with Netflix when its scaling demands consumed the entire engineering roadmap, preventing the company from serving its other 199 customers and building new features.

The founder realized he had product-market fit not from praise, but from anger. When the system went down, his few early customers were furious because they had come to rely on it, even in its imperfect state. This is a powerful, non-obvious signal of true customer dependency.

When one customer represents a huge portion of your revenue, your product roadmap is at risk of "slow drift." Your team, eager to please, starts building features the customer "might like," not what they explicitly requested or what your broader market needs, subtly derailing your product strategy.

Pursuing large "whale" customers for early validation is risky because they often come with heavy demands that can derail the product vision. Instead, seek out innovative, mid-level companies who are early adopters. They provide better feedback, and building traction with them opens doors to larger clients later.

Serving customers outside your ICP isn't just about high churn; it disproportionately increases support load, generates negative public reviews, and distracts your team from the core product vision. These hidden costs can slowly poison a small business.

It's common to vet investors, but founders should apply the same rigor to their first customers, especially in enterprise. Early customers are not just revenue sources; they are innovation partners who shape your product. Choosing partners who share your vision and will collaborate deeply is crucial for success.

Customers frequently complain about their current tools (e.g., "We're struggling with Salesforce"). Founders mistakenly interpret this as a request for a direct alternative. This is a trap. The real demand is the underlying job they're trying to do, which the tool is failing to support.

Early in its journey, HubSpot secured a deal with Meta that would have doubled its quarterly revenue. However, founder Brian Halligan tore up the contract because Meta was far outside their ICP. Servicing them would have derailed the product roadmap and company focus, ultimately destroying the business.

Customers often suggest solutions (e.g., "add this feature") based on their limited understanding of what's possible. A founder's job is to look past the specific request and identify the core problem or desired outcome. Building exactly what the customer asks for verbatim is a mistake; solving their underlying goal is the key.