Key Takeaways

  • Rob Snyder, author of The Power of Pull, warns that design partners create false positive signals because unpaid collaborators rarely convert into paying buyers.
  • Buyers facing an urgent, unavoidable project want immediate completion, not a seat on an advisory council helping shape a product road map.
  • Free design partnerships attract people looking to play Steve Jobs, offering architectural opinions rather than committing budget to solve a pressing problem.
  • Lenny Rachitsky admitted falling into this trap on early teams, building features based on prospect wishlists instead of what forced a commercial commitment.
  • Snyder recommends selling service-shaped offers early, such as an AI product manager delivered manually behind the scenes, to confirm real willingness to pay before writing platform code.

The Steve Jobs Trap in Early Discovery

Rob Snyder spent years studying how software companies uncover authentic product-market fit. His central warning in The Power of Pull challenges the standard playbook: signing up three to five design partners to steer early development.

Snyder argues this setup invites dangerous distortion. “You recruit a design partner who quote unquote buys into your vision for the product and they give a bunch of feedback and never buy from you,” Snyder explained. “They never buy and you realize that all of their feedback was just like them playing Steve Jobs and there's like I'm going to help this startup versus I have something I'm actually trying to get done.”

When a prospective user agrees to an unpaid or low-commitment pilot, their incentives detach from economic reality. They suggest roadmap items, critique wireframes, and enjoy advising an eager team. None of that engagement proves purchasing intent. Buyers with urgent operational fires do not want weekly feedback calls; they want the fire put out.

Why Design Partnerships Filter Out Your Best Buyers

Inviting prospective accounts into a design partnership does more than attract the wrong advisors. It actively repels the desperate customers who would otherwise pay you on the spot.

As Snyder noted, the offer itself dilutes urgency: “If they're like it it basically takes something from I need to to solve this right now to like okay now I'm helping you build your product... So it it's a negative signal to people who actually have pull and it's a positive signal to people who don't.”

Rachitsky saw this same dynamic playing out in his own zero-to-one builds. “We ran into the same zero to one traps Rob describes,” Rachitsky acknowledged, “building based on what prospects said they wanted rather than what actually got them to say yes.”

When you tell a buyer facing an immediate deadline that you want their feedback on an alpha, you reveal that your solution cannot fix their problem today. The buyer with cash and an urgent blocker leaves the call to find an imperfect tool that already exists. Meanwhile, the casual spectator remains on your calendar for months, offering suggestions that never translate into revenue.

Sell the Service Before Building the Platform

Founders often default to design partnerships because they believe they cannot bill clients for unfinished software. Snyder rejects that assumption. You do not need automated software to charge money; you need a defined outcome.

“You can sell something that's more service-shaped early on,” Snyder pointed out. “I've seen a bunch of startups do that where they sell, you know, okay, we're going to have an AI product manager who can do XYZ kind of thing. For now, it's delivered by us while this thing is working behind the scenes.”

Selling a manual service strips away ambiguity. If a customer pays thousands of dollars for your team to handle an operational task by hand, you have proven authentic pull. You uncover workflow bottlenecks while being paid to build the automation. A design partner hands you an unpaid backlog; a paying customer hands you their real constraints.

What to Do With This

Audit your active prospect pipeline before Friday. If you have pilot accounts or design partners who are not paying full price, send them a scope agreement with a cash price attached to deliver the finished outcome. If they refuse to pay, remove them from your weekly sprint planning immediately and redirect your development hours to prospects who will sign an invoice today.