We scan new podcasts and send you the top 5 insights daily.
Gusto and Rippling both saw users struggling with old payroll systems. Gusto interpreted the customer's "pull" as a desire for a delightful experience. Rippling saw it as a desire for total automation. This subtle distinction in understanding the core customer need led to fundamentally different product architectures and business trajectories.
Treat your startup not as separate departments (sales, product), but as one cohesive organism. The unifying force is customer "Pull," which acts as an evolutionary selection pressure, shaping every aspect of the business to fit what customers urgently need.
When searching for "blocked" demand, it's easy to invent problems from logical first principles (e.g., "all companies want to reduce costs"). This "wish-casting" ignores the customer's actual context and priorities. True pull is never generic; it must be a specific, top-of-mind problem for a user right now.
True product demand lies in the gap between what customers are currently doing (observable on their calendar) and their ultimate goals (their mental to-do list). A successful product closes this gap, better aligning a customer's actions with their underlying objectives. This mismatch is where "pull" is found.
Scribe started by building workflow automation, viewing documentation as a simple byproduct. Customers, however, found the automation only incrementally valuable but saw the documentation as a game-changing solution. Listening to this strong user pull led to the company's successful pivot.
Founders instinctively resort to "push" tactics: adding features, refining sales pitches, and highlighting benefits. This approach often fails because it ignores the fundamental concept of "pull"—the underlying project or motivation a customer already has. Successful products are built around this existing pull, not by trying to create it.
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.
A competitor may have a "better" product on paper, but buyers' demand is nuanced. A founder can win a deal against a well-funded rival by discovering the buyer's primary need is industry expertise, not more features. By aligning with this deeper "pull," the competitor's strengths become irrelevant.
A product has strong market pull when it aligns with the customer's true goal (their "to-do list") far better than their current action (their "calendar"). Automated note-taking app JMP had pull because it perfectly matched financial advisors' hidden goal to minimize time spent on compliance paperwork.
Pull isn't just a problem; it's a state of active struggle. Think of it as physics: the customer is applying force toward a project, but their existing options are applying a counter-force. Your product's role is to unblock this potential energy, which is often invisible until a viable new solution is presented.
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.