How to pre-sell, scope, and staff an early-stage product

Executive overview

Most pre-revenue startups overbuild their product, take tainted market feedback, and hand control to investors too early. The fix is to compress the MVP to the single core promise, charge customers to fund development, and keep engineering in-house.

The fastest path to product-market fit is pre-selling access to something that barely works — then letting customer money, not investor conditions, drive what gets built next.

Investor red flags and cap-table discipline

• An investor demanding you hire a CEO before revenue is unusual for a three-person team — normal for Series B or C, not pre-revenue.
• Founder instincts matter: if the condition feels wrong, it probably is.
• Do diligence on investors the same way they do it on you — find the companies that failed and ask how the investor behaved.
• Create optionality across capital sources (friends and family, angels, VCs) so no single investor can dictate terms.
• Hiring a six-figure CEO into a three-person pre-revenue team destroys runway without adding early-stage value.

Defining the MVP correctly

• The MVP delivers the core promise in its most primitive working form — not a polished feature set.
• Use the scooter analogy: scooter → bike → motorbike → car. The goal is always "get from A to B," not "build a car."
• Identify three features that fulfil the promise. Cut everything else to a later release.
• Administrative and account-management features (e.g. password reset) are not MVP — handle them manually at first.
• If nobody will use what you built, you didn't build the MVP right — add the second wheel, don't redesign the car.
• Reid Hastings: if you're not embarrassed by your first release, you waited too long.

Getting feedback from the right people

• Feedback from non-early-adopters is the single biggest killer of early-stage companies.
• Geoffrey Moore's crossing the chasm framework: innovators and early adopters are the only valid feedback sources pre-chasm.
• The other 80% of the market (early majority, late majority, laggards) will give feedback that actively misleads product decisions.
• Always qualify respondents first — e.g. "do you rent or own?" before asking about a rental app.
• Going to the wrong restaurant to test a restaurant-tech innovation wastes developer hours on feedback that doesn't transfer.
• Unqualified feedback can send two engineers down a three-week build path at real cost — treat it as a financial decision.

Pre-selling to fund development

• Get customers to pay you to build the product; this beats raising capital and diluting equity.
• Show a clickable prototype or one-pager that explains the product and its roadmap.
• Customers will accept missing features if you're transparent about the release plan and they're aligned with it.
• Custom development and consulting happen every day — early adopter programs are the same model applied to your product.
• Pre-sales validate market demand before a single hour of engineering is spent.

In-house vs agency engineering

• Agency developers build whatever you tell them — their incentive is to maximise billable scope, not product-market fit.
• Agencies typically cost 40%+ more than market rate; you get fewer shots on goal before cash runs out.
• Prefer contract-to-hire or part-time freelancers you can convert to full-time — build the team, not the dependency.
• Short-term agency work is acceptable, but backfill in parallel with a dedicated in-house hire.
• Use clickable prototypes and reverse-engineer from customer feedback before committing any engineering resources.
• Measure twice, cut once: high confidence in what you're building before writing code.