The answer is not "as soon as people seem excited."
That is exactly how founders trap themselves into shipping promises that were never operationally real.
The move from reservation interest to full pre-sale is one of the most sensitive decisions in early hardware. Done well, it validates demand and funds the next step. Done badly, it turns a promising project into a support, refund, and credibility problem.
Start here: Use Haitch to turn concept direction into validation-ready prototype outputs
A hardware startup should move to full pre-sale only when five things are true:
If those conditions are not true yet, you are still in waitlist, lead capture, or reservation territory.
This guide is for:
Founders often mix up three different signals:
1. Interest
Someone gave you an email address or liked the concept.
2. Reservation intent
Someone took a meaningful step that shows stronger intent, such as joining a priority list or paying a small deposit.
3. Full pre-sale intent
Someone is ready to pay most or all of the product price before delivery.
These are not interchangeable.
An email signup is not the same as a reservation. A reservation is not the same as a pre-sale. And a pre-sale is not safe just because a reservation campaign looked strong.
Reservation-style demand capture is useful when you still need answers on:
At this stage, your job is to learn whether the market pull is real enough to justify the next level of execution.
It is not yet to maximize collected cash.
The minute you ask for full payment, the conversation changes.
You are no longer saying, "Help us gauge demand."
You are saying, "We believe this product, this price, and this delivery path are credible enough that we are comfortable taking your money now."
That requires a much higher bar.
These are the signals that should be present before you move to full pre-sale.
For hardware, trust rises when buyers can see evidence that the product is real.
That does not always mean mass-production hardware. It does mean you have something more convincing than a concept illustration.
If your landing page still sounds like a future vision instead of a defined product, you are early.
Buyers should be able to answer:
You do not need perfect manufacturing certainty.
You do need enough clarity around BOM, assembly approach, packaging, shipping, and contingency that your pre-sale price is not a guess.
This is where many teams fail.
If the only way your promised ship date works is that nothing goes wrong, the date is not real. Hardware timelines need slack.
If buyers are still asking, "What is this?" or "Why would I want it?" you are not ready.
If the questions become, "When does it ship?" "What version will I get?" or "What happens if the date moves?" that is a healthier sign.
Stay in reservation or waitlist mode if:
A lot of founders call this caution "moving slowly."
It is actually avoiding an avoidable trust collapse.
For most early hardware teams, the safer path looks like this:
Use this when you are still refining message, segment, and feature priorities.
Use this when the concept is strong but the execution path still needs learning. This can be a priority list, application list, or small commitment mechanism on your own site.
One up-to-date note: Indiegogo's October 16, 2025 platform upgrade discontinued the older reservation feature, so teams should not base their plan around that legacy workflow anymore.
Use this only when the prototype, offer, cost assumptions, and delivery window are strong enough to defend publicly.
Do not confuse successful pre-sale collection with production readiness. You still need release discipline.
Kickstarter can help with trust and discovery, but it does not lower the execution bar for hardware.
Direct pre-sales can work well if your audience is already warm and your launch page is strong, but they place even more pressure on your own communication and support systems.
What matters is not which checkout surface you use.
What matters is whether your readiness state matches the promises you are making.
This is where connected execution matters.
To move responsibly from interest to pre-sale, you need one aligned view across:
Haitch helps founder-led teams keep those threads connected so they can tell the difference between market excitement and actual pre-sale readiness.
You need a believable prototype and enough execution clarity to make responsible promises. The exact bar depends on the product, but pure concept art is usually too weak.
Usually no. A waitlist is useful directional data, but it is a weaker signal than reservation behavior or actual pre-sale conversion.
Often yes. A lighter-weight commitment can help validate intent and sharpen messaging before you raise the promise level.
The main risk is not just refunds. It is losing trust with the exact early customers you needed to build momentum.
Move to full pre-sale only when the question has shifted from "Do people like this idea?" to "Can we now make a narrow, credible promise and execute against it?"
If you are still learning the product, use reservation-style signals. If the product and execution path are both becoming concrete, that is when full pre-sale starts to make sense.
Next step: Use Haitch to align prototype work, readiness, and customer-facing launch output before you ask buyers to commit