digest
Short Summary
Main recommendation: Test a software idea by pre-selling it with a clickable prototype shown to early adopters, rather than building the product first. Dan Martell argues that asking for money (even $1) changes customer feedback from polite encouragement into real validation of what they need.
Key Points
- Customer financing: Dan describes getting customers to fund development through pre-sales, rather than relying on venture capital, angel investors, or friends and family.
- Fake-product validation at Flowtown: The team built three screens (upload emails, show analysis of social data, prompt for payment) and, at payment, said servers were overcapacity while collecting emails, measuring real conversion without building the product.
- Pricing-dynamics test at Clarity: Dan checked what experts charged (Neil Patel quoted $2,000 for SEO advice, which was too expensive) and then found another expert willing to charge $500/hour, and confirmed startup founders would pay that before writing any software.
- Early adopters matter: Feedback from non-early adopters (such as small-town restaurant owners rejecting an iPad ordering app) can wrongly kill a good idea.
- Enterprise evidence: Dan's consulting company, Spheric Technologies, worked with Procter & Gamble, Dole Foods, and Johnson & Johnson innovation teams, who paid for custom software, which he cites as proof that "my situation is different" objections do not hold.
Details Worth Noting
- Concrete instructions:
- Step 1, build a clickable prototype: Use Keynote or PowerPoint, or a tool like Keynotopia, to draw screens and link them so the user flow can be clicked through. Dan says that if you can draw a square box, you can do it. He mentions Balsamiq, UXPin, and InVision as more polished options but does not recommend them, because customers may hesitate to criticize a finished-looking design. He also recommends drawing on paper with a big marker and showing it at places where your ideal customers gather, such as a mall or farmers market.
- Step 2, find early adopters and innovators: Use the technology adoption curve by Jeffrey Moore. Identify traits of early adopters for your specific market (for example, a restaurant using Snapchat or Facebook messaging for marketing) and validate the prototype with those people, not with the early or late majority.
- Step 3, pre-sell: Ask for a financial or major time commitment (even $1) before building. Once money is requested, customers start asking concrete questions (team invites, collaboration, reporting, ROI) that reveal true needs.
- Offer co-creation: Show mockups to prospective buyers, invite them to a customer advisory board, and build with their input.
- Test with a tool stack: Dan's Clarity test used Google Calendar, a 1-800-Free Conference Call line, and PayPal to coordinate and collect payment manually.
- Caveat: Dan's examples come from his own companies and consulting work; he does not provide outcome data across many projects.
Bottom Line
Before writing code, get someone to commit money or significant time to a prototype from the right early adopters; their willingness to pay, not polite feedback, is the real validation.
