How to reach one million users by staying customer-first

Executive overview

Spending $1M building something nobody wants is a brutal teacher. After burning that on a failed email-marketing tool, the team pivoted by asking customers what they actually needed — and built Hauldrop.com, a product-discovery site, instead.

The lesson: get customers before you build anything. Validate demand first, then build the minimum needed to get paid.

The right metric of success determines everything you build — choose it wrong and you'll optimise toward users who never come back.

From failure to idea

• MeetFam.com cost ~$1M and 6 months; it made $25K
• Customers didn't want another email platform — they wanted customers
• A single affiliate email about the Oura Ring generated $3K unprompted, signalling real demand
• Hauldrop launched as a Product Hunt-style site for curated products

Getting first customers

• Promoted to an existing email list (OKDork.com) rather than buying traffic
• Made it trivially easy for users to contact the team — live chat, email, forms
• Set a 3-month goal of 10K signups as the success metric

First iteration: giveaways

• Growth was too slow; the team looked for what was already working
• Giveaways for Yeti coolers, cameras, and drones drove signups sharply up
• Switched to a daily giveaway and added social sharing buttons
• Homepage was simplified to a single email signup CTA

Wrong metric, wrong customers

• Signups spiked but users never returned — the "giveaway crowd" wanted free stuff, not products
• Attracting the wrong audience is a dead end regardless of volume
• The goal of "get users" pulled the product in the wrong direction

Second iteration: engagement over growth

• Changed the success metric from signups to engagement
• Shifted to sending one curated product email per day
• Customised the homepage around product discovery, not giveaways
• Metric change drove a completely different feature roadmap

The customer-first framework

1. Customer-first mindset — find customers before building anything
2. Use yourself — only build what you'd use regularly
3. Metric of success — pick one aligned with real customer value, not vanity numbers
4. Limitations — cap time and money spent before validating; minimum viable customer, not MVP
5. Date, not marry — change the implementation freely; never change the core problem or vision