Skip to content
Subconscious

What to Test in Simulation Before You Burn Your First Ten Customer Calls

On this page

A pre-seed founder with no research budget has to decide, before the first customer call, which questions belong in that call and which ones can be resolved first. Get the split wrong and the cost shows up two ways: burn the first ten conversations on things a live human never needed to answer, or treat simulated enthusiasm for a pitch as proof that a real buyer will pay for it.

Why founders skip research instead of triaging it

Formal qualitative research can require recruitment, delivery, and analysis costs a pre-seed team cannot yet support. Get a quote for the actual method, geography, and criteria. Nielsen Norman Group’s interview guidance distinguishes exploratory interviews from observing use; early conversations can clarify needs without proving future purchases.

A founder may rely on personal experience, network conversations, and available user calls before commissioning formal research. Those sources can help frame the question, but check whom they cover and where prior beliefs or selection may distort the conclusion.

Some exploratory questions can benefit from simulated hypotheses before interviews. Real conversations clarify needs and constraints; payment, switching, and referral assumptions need the corresponding observed behavior. Keep both kinds of evidence in the early discovery plan.

What can a controlled comparison settle before the first call?

Subconscious can compare generated reactions or choices between assigned alternatives in a configured audience. Use that output to propose positioning questions or objections for discovery. Comparing customer-profile groups does not by itself establish that the profile caused a response, and a weak modeled result is not grounds to discard a critical hypothesis without a human check.

Before talking to a single customer, a founder can use this kind of controlled comparison to:

After real conversations, use the findings to refine simulated prompts and propose where to probe next. Generating fifty responses from three profiles does not establish the prevalence of an objection across buyers. Estimate prevalence from suitable human data when the decision requires it.

A fit worth being honest about

Assess fit from the decision, existing market context, available budget, and required evidence. Ask what a scoped study would deliver and what it would leave for real customer discovery; confirm eligibility, pricing, and deliverables for the actual study with the team.

As a discovery-planning example, name the customer profile and explore five questions: the current frustration, reaction to the pitch, first skeptical objection, comparison with a known alternative, and conditions for trying the product. Carry important assumptions into customer conversations, including rejected modeled options where a screening error would matter.

What can't a controlled comparison tell a founder?

A controlled comparison of hypothetical responses cannot tell a founder whether a real person will change behavior, pay money, or refer the product to someone else. Enthusiasm for a simulated pitch is not conversion evidence; treating it as such is the second way founders waste runway on this problem. Use the modeled comparison to prepare hypotheses for real validation.

For evidence beyond generated hypotheses, plan a human study of the same question with an aligned endpoint. Agree recruitment and instrument adaptations with the team. Existing interviews or behavior records may already address part of the question; determine what remains unresolved before commissioning another study.

Where does this fit for a founder before product-market fit?

Before product-market fit, a simulated comparison can propose ICP hypotheses for real interviews. Examine reactions from configured customer types without treating specificity or emotional language as validated demand. Preserve critical alternatives and confirm important needs in customer conversations.

Use the provisional result to prepare the first customer conversations. Decide which assumptions need interviews, which need behavior records, and which require an observed purchase or switching test.

Simulation: propose objections; Interviews: probe real pains and constraints; Records: check past behavior; Actions: observe purchase, switch, or referral
Prepare discovery without mistaking conversation for behavior Stated willingness does not confirm a future payment or referral.
Define the buyer and hypothesis; Explore modeled questions and objections; Identify calibration and uncertainty; Probe important assumptions with people; Test the relevant observed behavior
Keep critical assumptions in the discovery plan Rejected simulated options may still need a human check when screening error matters.

Next step

A founder deciding what belongs in the next ten customer conversations can see how Subconscious frames this in how we work, or look at case studies and the research library for examples of the same triage applied to a bigger decision. A demo walks through what this looks like end to end.