
Rob SnyderFounder & CEO
In this interview, Rob Snyder, Founder and CEO of Reframe and author of The Power of Pull, reveals his counterintuitive zero-to-one methodology for uncovering genuine customer demand without forceful push sales. He outlines the practical PULL framework, explains why founders should reject polite design partnerships, and breaks down the unit economics of early customer conversion. Snyder shares actionable operational advice on navigating pivots, optimizing pricing, and systematically turning single successful customer outcomes into repeatable enterprise case study playbooks.
Founder Stats
- SaaS
- Started 2021
- Not Publicly Disclosed/mo
- 6–20 team
- Cambridge, Massachusetts, United States
About Rob Snyder
Rob Snyder is the Founder and CEO of Reframe, a fellow at the Harvard Innovation Labs, and the author of The Power of Pull. He earned his MBA from Harvard Business School and has spent over a decade leading product and go-to-market strategies for early-stage software companies. Through his advisory work and writing in The Physics of Startups newsletter, Snyder has guided more than fifty B2B startups from initial ideation to over one million USD in annual recurring revenue.
Interview
October 28, 2026
What fundamental mistake do founders make when attempting to create customer demand for a new product?

Founders routinely assume that market demand can be manufactured through persuasive sales pitches, polished marketing copy, or endless feature development. In reality, customer pull is discovered rather than created. You cannot convince an indifferent prospect to care about an abstract problem; you must search for a coiled spring of pent-up urgency where the customer is already actively looking for a way out of an untenable situation.
How does the PULL framework define the mechanics of why a customer actually buys?

The PULL acronym breaks down into four sequential components: Project, Unavoidable, List of options, and Limitations. First, there must be a concrete project currently on someone's active to-do list. Second, that project must carry an unavoidable deadline or severe penalty for inaction. Third, the buyer has an existing list of workarounds they are using. Fourth, those options have severe limitations that leave the buyer stuck and eager for an immediate alternative.
Why do you argue that founders should never sell to companies, but rather to specific individuals?

Companies do not buy software; individuals with specific job responsibilities and personal reputations do. If you say you are selling to a large enterprise like SpaceX, you will fail because the company itself has no single brain or unified priority. You must identify the specific human being, such as the head of legal compliance, who personally owns an urgent deliverable and is blocked from completing it.
Why do you advise early-stage founders against taking on conventional design partners?

Design partnerships often create a dangerous illusion of progress while delaying genuine market validation. Design partners are typically polite industry acquaintances who agree to weekly calls because they enjoy discussing ideas, but they have no real skin in the game. They request bespoke features that distract you from building a repeatable product, and when it comes time to pay, they vanish because they never had unavoidable pull.
How can a founder validate customer pull using only two slides before writing any code?

Instead of spending six months engineering software, create two simple presentation slides. The first slide articulates the exact high-stakes project the customer is attempting to execute, along with the brutal limitations of their current tools. The second slide describes your proposed workflow solution and its concrete deliverable. If the prospect leans forward and asks how quickly they can get started, you have pull; if they offer polite intellectual compliments, you do not.
What is the Hail Mary question, and how can founders use it during a dead-end sales conversation?

When a discovery call goes cold and you realize the customer has no interest in your pitch, throw the Hail Mary question: Is there anything currently on your to-do list that you would pay me right now to solve? This sudden pivot strips away the scripted dynamic and invites radical candor. Often, the prospect will immediately describe a painful, unglamorous problem that reveals the exact direction for a high-conviction company pivot.
How should a founder structure their initial sales calls to differentiate true buying intent from politeness?

Structure the conversation around uncovering the customer's existing behavior rather than presenting your product. Spend the first twenty minutes diagnosing their current projects, deadlines, and workaround tools. If you present your solution and they do not ask about pricing, deployment timelines, or implementation logistics, they are merely being polite. True buying intent looks like someone trying to pull the product out of your hands.
Does a new B2B product really need to be ten times better than existing market alternatives?

Not necessarily. The ten times better rule applies primarily when you are asking customers to replace an entrenched system that already works reasonably well. However, if a customer is facing an unavoidable project deadline and their current options completely fail to deliver the required output, your product only needs to be the first viable solution that actually gets the job done on time.
How should early-stage founders approach software pricing when they lack historical benchmarks?

Price your product based on the magnitude of the customer's unavoidable risk rather than the cost of your cloud hosting or development hours. When a buyer has an urgent corporate initiative with hundreds of thousands of dollars at stake, a low-cost tool signals amateur quality and introduces perceived risk. Pricing should reflect the economic value of unblocking the project immediately.
What does it mean for a founder to enter goblin mode when initial customer traction stalls?

Goblin mode is an intense operational posture where a founder strips away all vanity distractions—such as networking events, redesigning websites, or tweaking pitch decks—and focuses exclusively on running rapid, unglamorous demand experiments. You reach out directly to dozens of prospects every single day, test raw hypotheses, and iterate furiously until you hit an undeniable pulse of customer pull.
Why is manual customer onboarding crucial during the initial zero-to-one phase of a startup?

Automated self-serve onboarding is a trap for nascent startups. When you send new signups a login link and hope for the best, you miss the critical moments where users get confused and abandon your tool. Founders should manually onboard their first twenty customers personally, observing every point of friction and ensuring the customer achieves their breakthrough aha moment within the first forty-eight hours.
How can analyzing early customer churn provide the sharpest diagnostic insights for product-market fit?

Founders often view customer cancellations as an emotional failure and look away, but churn is your most valuable diagnostic mirror. When a customer churns, conduct a rigorous post-mortem to determine whether the problem was a product defect or improper qualification. More often than not, churn reveals that the user never had an unavoidable project in the first place, allowing you to tighten your ideal customer profile.
What is the concept of a case study factory, and how does it scale early B2B growth?

A case study factory is the systematic process of turning a single successful customer engagement into an undeniable sales asset. Instead of chasing disparate industries, you document the exact baseline metrics, implementation steps, and quantifiable ROI achieved by your first happy customer. You then distribute that exact blueprint to twenty identical peers who share the same unavoidable project, creating effortless reference-driven sales.
How can product teams inside large, established enterprises adopt the PULL methodology?

Internal corporate product leaders face the same traps as startup founders by building tools that colleagues politely praise but never adopt. To succeed inside an enterprise, internal teams must treat business unit leaders as paying clients, identifying their unavoidable quarterly mandates and building solutions that directly resolve their operational bottlenecks rather than mandating top-down software compliance.
Table Of Questions
Video Interviews with Rob Snyder
An 86-minute guide to finding PMF - Rob Snyder (Author, The Power of Pull)
Cite This Interview
Use this interview in your research, article, or academic work
Related Interviews

Jason Lemkin
Founder & CEO at SaaStr
In this interview, Jason Lemkin, Founder and CEO of SaaStr, assesses the structural shifts impacting late-stage venture capital, public cloud valuations, and artificial intelligence infrastructure…

Rahul Vohra
Founder & CEO at Superhuman
In this interview, Rahul Vohra, Founder and CEO of Superhuman, explores why superficial AI integrations fail to retain software users and outlines frameworks for embedding…

Mike Cannon-Brookes
Co-Founder & CEO at Atlassian
In this interview, Mike Cannon-Brookes, Co-Founder and CEO of Atlassian, discusses the practical integration of autonomous AI agents across modern enterprise collaborative workflows. He examines…

Aneel Bhusri
Co-Founder & CEO at Workday
In this interview, Aneel Bhusri, Co-Founder and CEO of Workday, unpacks the seismic impact of enterprise AI agents on global corporate labor and organizational architecture.…

Vikram Chalana
Founder & CEO at Pictory
In this interview, Vikram Chalana, founder and CEO of Pictory, sits down with Vlad Kachur to explore the transformation of corporate knowledge into automated video…

Guillermo Rauch
Founder & CEO at Vercel
In this interview, Vercel founder and CEO Guillermo Rauch discusses recursive founder mode, scaling product portfolio autonomy, and the transition toward agentic software factories. Rauch…