What to measure during a pre-launch besides how many people joined

Your waitlist has grown, but the product still feels oddly untested. You know how many people entered their email address. You do not yet know whether they understand the offer, would pay for it, or can describe the problem in their own words. That is the gap a useful pre-launch measurement plan should close.

Start with the decisions you need to make

Do not begin by collecting every available number. Begin with the decisions ahead of you. You may need to decide whether the promise is clear, which problem to prioritise, whether the format suits the buyer, or whether to launch now rather than keep polishing. Each decision needs a different signal.

For example, a sign-up can tell you that a message earned enough interest for someone to take a low-effort action. It cannot tell you why they joined. A reply can expose a use case or objection. A completed research conversation can show whether someone will give you time to explain their situation. A referral can indicate that the problem is easy for them to recognise in another person.

Measure replies, not just reach

A reply requires more effort than a click or sign-up, so it can give you richer evidence. Ask one narrow question at a time: “What are you trying to do at the moment?” or “What would make this worth buying?” Record the answer in the person’s words, then group similar answers rather than smoothing them into your preferred language.

Track reply rate as a checkable calculation: replies divided by delivered messages, multiplied by 100. Also record the number of replies that contain a concrete situation, question or objection. Ten vague compliments and three detailed objections are not equivalent evidence. The detailed replies give you material to investigate.

If you are using store.fan for a lead magnet or email list, email marketing can give you a place to send a focused question and organise the response process. Keep the question tied to a decision. A growing spreadsheet of interesting comments is not research until it changes the offer, format or launch plan.

Capture objections before launch week

Objections are not failed conversions. They are explanations of what is stopping someone. Tag each one by type: price, timing, trust, relevance, format, effort or a missing feature. Then count the tags. If most people ask whether the product applies to their situation, your positioning may be too broad or your examples too thin. If they ask when it will be available, timing may be the useful next message.

Separate a stated objection from an inferred one. “I do not know whether this works for freelancers” is stated. “They probably think it is too expensive” is an inference. You can keep both, but label them differently. This prevents you from writing launch copy around a concern nobody actually raised.

Use referrals as a clarity test

Ask people to forward the waitlist or name someone who might have the problem. Do not treat every share as equal. A useful referral has context: who they referred, what problem they thought that person had, or what sentence they used to explain the product.

You can track a simple referral rate as referred sign-ups divided by total sign-ups, multiplied by 100. More important than the percentage is the wording. If people describe the offer accurately, your message may be portable. If they say only “you should check this out”, the product may be interesting without being clear.

A creator storefront can make the next step easier to share. On store.fan, your storefront lives at store.fan/username, so you can send one stable address rather than several scattered links. If you need to collect interest before selling, the free plan is link-in-bio only; paid plans start with a 14-day trial. Choose the setup based on the action you need, not on the size of the waitlist.

Count completed conversations and changed assumptions

Set a small, explicit research target: for example, a number of completed conversations across the buyer types you believe you serve. The useful measure is completed conversations, not invitations sent. For each conversation, record the person’s current workaround, the consequence of the problem, what they have already tried, and what would make a solution credible.

At the end, write down one assumption that changed, stayed uncertain or gained support. This makes the research auditable. If five conversations all confirm that people want a result but dislike long video lessons, that may affect your format. If the conversations point to five unrelated problems, narrowing the product may be more useful than adding features.

Turn the signals into a launch decision

Review the signals together rather than searching for one magic threshold. Stronger evidence usually has three parts: people can explain the problem, they ask relevant questions about the solution, and they take a step that costs them time or reputation, such as a conversation or referral.

Weak evidence can still be useful. Many sign-ups with few replies may mean the call to action is attractive but the question is poorly designed. Many replies with repeated confusion may mean the audience is real but the offer is unclear. A quiet referral channel may mean the problem is private, niche or difficult to describe, not automatically that there is no demand.

Make the next action specific: rewrite one section, interview a different buyer type, run a private beta, or invite a small group to buy. If you sell a digital product, course or membership through store.fan, sales go directly to your Stripe account and store.fan takes 0% of sales; Stripe’s own processing fee still applies. That removes one platform fee, but it does not remove the work of making the offer worth buying.