Test a customer problem before building an offer

A convincing offer can be built around a problem that customers do not care enough to solve. The wording may be attractive, the website professional and the explanation technically correct. None of those things establishes that someone will change their behaviour or pay for the work.

Research is valuable when it changes a decision. Before speaking to customers, identify what you are uncertain about and how different answers would affect the offer. Otherwise the conversation can become a search for encouraging comments rather than a test of a business assumption.

For Fieldnote Studio, the initial assumption is that small service firms lose useful time explaining inconsistent package information. That sounds plausible. It still needs evidence about who experiences the problem, when it occurs and whether a document package is an appropriate response.

Write a claim that can be challenged

A broad statement such as “small businesses need clearer information” is difficult to disprove. Narrow it to a situation: “Firms with several service packages and more than one person answering enquiries repeatedly correct inconsistent explanations.” This defines a group, a circumstance and an observable behaviour.

Then identify alternatives. Perhaps enquiries are confusing because prices change too often, because the service itself is unclear or because staff have no authority to answer. A rewritten pack may help one cause and leave another intact. Research should be allowed to change the diagnosis.

The Australian Government’s market research guidance describes several sources of evidence, including existing customer records, interviews and feedback. For this book, the practical recommendation is to combine more than one kind of evidence rather than treating a single agreeable interview as a verdict.

Ask about events rather than approval

Questions about recent events tend to produce more useful detail than invitations to admire an idea. Ask the customer to describe a particular enquiry, what happened next and what information was missing. Explore the current workaround before introducing your solution.

For example, a Fieldnote interview might begin with: “Walk me through the last time a customer misunderstood what was included.” Useful follow-up questions concern who noticed, how it was corrected and whether the correction affected time, money or trust. Ask permission before viewing any actual document; a redacted example may be enough.

Compare this with “Would a clearer pack help?” A yes is easy and may be sincere, but it tells you little about priority. The person may like the concept while having no intention of changing anything this year.

Separate three things in your notes: what happened, what the customer believes caused it, and what you infer. A repeated correction is an observation. “Our old document causes it” is an explanation to test. “They will buy our package” is a further inference. Keeping these apart stops a short conversation from becoming a chain of unsupported conclusions.

Look for variation and disconfirming evidence

Interviewing only friendly contacts can produce a narrow picture. A customer who already trusts you may tolerate weaknesses that a new buyer would not. A person who rejected a similar service can explain obstacles that enthusiastic prospects overlook.

Fieldnote deliberately includes a firm that recently rewrote its information internally. It discovers that the firm had a capable writer but struggled to obtain a final approval from several managers. That finding changes the proposed service: the approval process matters as much as the writing.

A small sample is useful for discovering questions and failure modes. It does not establish the percentage of a whole market that will buy. Avoid converting a few interviews into a market-size forecast with precise-looking numbers. Record the composition of the sample and the missing perspectives.

Test the smallest meaningful commitment

The strength of a signal depends on what the person actually does. Agreeing to another conversation is different from supplying information, allocating staff time or accepting a paid pilot. These actions are not interchangeable, and none guarantees long-term demand.

A bounded pilot can test a delivery assumption as well as demand. Fieldnote offers to review one existing service page, identify inconsistencies and discuss a sample rewrite. The pilot has a defined fee, output and time limit. It does not pretend to deliver the full package for a token price.

Before running it, the team writes what it expects to learn: whether the customer can supply usable input, whether staff agree about the service, how long review takes and whether the result is useful enough to support a larger commission. A pilot that merely gives away extensive work may generate appreciation without testing a viable business.

Keep a compact evidence table

This is a working table, not proof that the opportunity is good. Update it when evidence changes. If a test contradicts a claim, change the offer or stop. Do not quietly replace the original success criterion after seeing the result.

Decide what the research permits

Evidence can support different next steps. Repeated, costly confusion with a willing owner may justify a scoped offer. A vague concern with no recent example may justify a lighter educational resource. Inconsistent service definitions may require internal decisions before a writing job can begin.

An honest conclusion can be “we do not know enough yet”. Attach that conclusion to a specific missing fact rather than making research endless. The amount of evidence should fit the reversibility and cost of the decision. Publishing a test description is easier to reverse than hiring staff around an untested service.

Exercise: challenge your preferred explanation

Write the explanation you currently favour for a customer’s problem. Then write two other explanations that could produce the same observation. Identify a question or small test that would distinguish them. Do not ask the customer to choose from your explanations until you have heard their account in their own terms.

The outcome of this chapter is a more credible problem definition and a bounded offer hypothesis. The next task is finding a repeatable way to meet suitable customers without confusing activity with demand.