Market research with AI works when the model is treated as an assistant, not as the market. Start with the decision you may take, define acceptable evidence, collect official data and direct customer evidence, and retain a source for every material claim. Use AI to expand queries, extract fields, cluster notes and challenge contradictions. Never let it invent market size, respondents, competitor facts or demand. The output should be a decision record with confidence and limits, not a persuasive summary.
Operating rule
A model response without a retrievable primary source is a search lead or hypothesis, not market evidence.
Start with the decision, not the AI tool
A useful brief names one decision: enter a region, choose a segment, revise an offer, test a price range, or stop a launch. It also states what evidence would change that decision. Without this boundary, AI produces broad categories and polished prose while the team collects material it cannot act on.
Visual slot: Add a real market-research decision brief here: decision, target customer, geography, time period, evidence threshold, owner and stop condition. Replace this block with the final visual later.
| Brief field | Strong question | Required evidence | Decision rule | Do not accept |
|---|---|---|---|---|
| Customer | Which UK field-service firms lose time at job handoff? | Role-specific interviews plus workflow evidence | Proceed only if the same costly job recurs and a buyer owns it | Generic SMB pain lists |
| Geography | Is the first market UK, one US state, or neither? | Comparable official units and local access constraints | Choose only after definitions and routes to market align | Global totals without geography |
| Alternative | What do teams do instead today? | Direct product pages, process observations and interviews | Build only if switching friction is understood | AI-generated competitor profiles |
| Timing | Is the problem urgent in this buying cycle? | Trigger events, budgets and decision process | Test now only if a real trigger and owner exist | Search interest as purchase intent |
| Stop | What evidence would end the project? | Named threshold and disconfirming questions | Stop or narrow when the assumption fails | Research designed only to confirm |
Use an evidence hierarchy before synthesis
Evidence rule
Separate published facts, direct observations, respondent statements, estimates and model suggestions before asking AI to summarize anything.
The U.S. Small Business Administration’s market-research guidance distinguishes existing sources from direct research such as surveys, questionnaires, focus groups and interviews. That is a useful operating boundary: secondary data frames the market; primary research tests language, workflow, objections and buying process. Neither source type automatically proves demand for your offer.
| Evidence class | What it can support | Required record | Primary limitation | AI role |
|---|---|---|---|---|
| Official statistics | Population, business counts or labor measures under published definitions | Publisher, table, unit, geography, period and retrieval date | May not match the intended segment | Find tables and explain definitions for human review |
| Direct competitor evidence | Observable offer, price page, claim, terms or route to purchase | URL, captured date and exact observation | Does not prove market share or customer satisfaction | Extract comparable fields without filling blanks |
| Interview | Language, workflow, trigger, objection and decision process | Consent, role, context, notes and verbatim evidence | Small purposive sample cannot estimate prevalence | Code notes and surface contradictory cases |
| Survey | Responses from a defined sampling process | Population, invitation, question, response and non-response notes | Bias and wording can distort percentages | Draft and quality-check, never fabricate responses |
| Planning estimate | A scenario for resource or launch decisions | Formula, sourced inputs, assumptions and range | Not an audited market fact | Recalculate scenarios and test sensitivity |
A six-part research operating loop
The following six-part loop is an editorial workflow for SMB decisions, not a universal research law: define the decision; establish the evidence ledger; map official and direct secondary evidence; conduct interviews; test a survey or proposition; synthesize contradictions and decide. Teams may revisit earlier stages whenever definitions fail.
| Stage | Input | Work | Output | Stop condition |
|---|---|---|---|---|
| Decision brief | Business choice and uncertainty | Define segment, geography, period and threshold | One-page brief | No accountable decision owner |
| Evidence ledger | Source requirements | Record provenance and definitions | Auditable claim register | Material source cannot be retrieved |
| Secondary scan | Official data and direct market pages | Compare units, dates and observable alternatives | Market boundary and gaps | Definitions cannot be aligned |
| Interviews | Recruitment and guide | Explore jobs, triggers, current behavior and objections | Coded evidence with exceptions | Sensitive data handling is unapproved |
| Survey or test | Qualified hypotheses | Test wording, sampling and proposition | Bounded response evidence | Sample cannot support intended inference |
| Synthesis | All evidence classes | Resolve contradictions and rate confidence | Decision, next test or stop | Summary hides source conflict |
Build a source ledger that AI cannot silently rewrite
NIST’s Generative AI Profile identifies confabulation as confidently presented false or erroneous content and recommends verifying sources and citations in outputs. In practice, keep the source outside the chat: store the URL, publisher, title, date, geography, unit, quoted field, extraction and reviewer. AI may propose a row, but it cannot approve its own evidence.
Visual slot: Add a real evidence ledger here: claim, source URL, publisher, date, geography, unit, definition, excerpt, AI extraction, human check, confidence and decision use. Replace this block with the final visual later.
| Ledger field | Why it matters | Human check | Reject when | Decision use |
|---|---|---|---|---|
| Publisher and URL | Makes the evidence retrievable | Open the primary page or table | Citation is invented, circular or inaccessible | Source authority |
| Date and period | Separates current publication from data period | Record both explicitly | Period is missing or stale for the decision | Recency risk |
| Geography and unit | Prevents false market comparisons | Match country, region, firm and person units | Units are mixed without conversion | Scope |
| Definition | Shows what the number actually counts | Read metadata and footnotes | AI inferred a definition from a label | Comparability |
| Confidence and contradiction | Prevents smooth summaries hiding conflict | Name competing evidence and owner | Only confirming evidence is retained | Next test |
Use official data to bound the market
For U.S. questions, Census Business Builder and Bureau of Labor Statistics data can provide primary public evidence under their own definitions. A UK or U.S. team should record the exact table and period rather than transferring one country’s ratio to another. Official counts can bound a population; they do not tell you which firms feel the problem, will switch, qualify or buy.
| Question | Suitable evidence | Definition check | What remains unknown | Next primary research |
|---|---|---|---|---|
| How many candidate firms exist? | Official business count by industry and geography | Industry code, establishment versus enterprise, period | Problem prevalence and buyer access | Screened interviews |
| Where are they concentrated? | Regional official table | Location of establishment versus customer | Serviceability and channel access | Route-to-market interviews |
| Is employment changing? | Labor series under a stated period | Occupation, industry and seasonal adjustment | Cause and budget impact | Buyer and workforce interviews |
| What is an observable price? | Current direct vendor price or terms page | Plan, billing period, tax and conditions | Discounting and realized price | Buyer budget discussion |
| Is the segment reachable? | Owned list, channel inventory or partnership evidence | Duplicate and qualification rules | Attention and response | Small recruitment test |
Map competitors and alternatives without inventing market share
Competitor rule
Record what a buyer can directly observe and what respondents actually use; do not turn page copy into market performance.
A competitor set includes direct products, manual workarounds, internal processes and the choice to do nothing. Capture the same fields at the same date: target role, problem, proof, pricing visibility, onboarding, constraints and destination. Mark missing information as unknown. AI can normalize wording, but it must not infer adoption, customer satisfaction or revenue.
Visual slot: Add a real competitor and alternative map here: buyer job, direct vendor, spreadsheet or manual workaround, do-nothing cost, observable proof, switching friction and unknowns. Replace this block with the final visual later.
| Alternative | Observable evidence | Question for buyers | Useful conclusion | Unsafe conclusion |
|---|---|---|---|---|
| Direct product | Offer, documentation, public price and terms | Why was it shortlisted or rejected? | Positioning and feature boundary | It leads the market |
| Spreadsheet or manual process | Observed workflow and respondent description | Where does rework occur? | Job and friction hypothesis | Every firm has this problem |
| Agency or consultant | Public scope plus buyer account | What expertise or accountability is purchased? | Service substitute and trust need | Service always costs more |
| Internal build | Interviewed workflow, owner and maintenance | Why keep control internally? | Switching and governance barrier | Build is inefficient |
| Do nothing | Trigger, consequences and deferred action | What would make the issue urgent? | Real competing priority | No action means no demand |
Interview for decisions, not compliments
Interview rule
Ask for the last real event, artifact and decision path before asking for opinions about a future product.
Recruit against the defined population and include disconfirming cases. Ask what happened last time, what artifact moved between roles, what failed, who approved spend and what alternative won. Separate a respondent’s statement from your interpretation. Do not upload identifying transcripts, customer lists or confidential documents to an AI service without approved handling; the ICO’s AI and data-protection guidance is a UK-oriented review input, not a global legal ruling.
Visual slot: Add a real interview evidence sheet here: screening basis, role, last event, artifact, trigger, current alternative, objection, decision path, quote, interpretation and follow-up. Replace this block with the final visual later.
| Weak question | Stronger question | Evidence sought | Probe | Do not infer |
|---|---|---|---|---|
| Would you use this? | Tell me about the last time this happened | Recent behavior | What document or screen did you use? | Positive intent equals purchase |
| Is this a big problem? | What happened next and who was affected? | Consequence and ownership | What was delayed, repeated or abandoned? | Emotion equals economic value |
| Which feature do you want? | How do you complete the job today? | Workflow and workaround | Where does responsibility change hands? | Feature request is the solution |
| What would you pay? | How is this category budgeted now? | Budget source and comparison | Who can approve and what competes? | Quoted price is willingness to pay |
| Do others agree? | Who has a different workflow? | Boundary and counterexample | What makes their case different? | Interview prevalence |
Design surveys after the hypotheses are specific
The UK Government Analysis Function’s questionnaire guidance emphasizes early question-quality work, clear language and appropriate open or closed formats. Its survey-testing guidance supports cognitive and usability testing before wider fielding. Start with target population and sampling path; test comprehension; then document invitations, responses, exclusions and non-response. A convenient audience is not automatically the market.
Visual slot: Add a real survey QA board here: target population, sampling frame, invitation, tested question, answer options, exclusion, response status, non-response risk and permitted inference. Replace this block with the final visual later.
| Survey risk | Diagnostic question | Repair | Evidence to keep | Claim limit |
|---|---|---|---|---|
| Leading wording | Does the question imply the desired answer? | Use neutral language and balanced options | Old and tested wording | No causal conclusion |
| Double-barrelled item | Could one respondent answer each part differently? | Split into one idea per question | Cognitive-test note | Do not merge distinct attitudes |
| Undefined population | Who exactly could have received the invitation? | Define frame, eligibility and exclusions | Recruitment record | No market percentage |
| Non-response | How do responders differ from non-responders? | Record response path and known differences | Invitation and response counts | Do not assume missing at random |
| Small subgroup | Is the base adequate for the decision? | Show base and suppress overinterpretation | Unweighted count and caveat | No precise segment ranking |
Use AI for bounded research work
AI boundary
Use the model to transform material you can inspect, not to manufacture facts you cannot retrieve.
| Task | Good AI instruction | Required control | Human decision | Never allow |
|---|---|---|---|---|
| Query expansion | Generate synonyms, industry codes and disconfirming queries | Reviewer selects and logs searches | Which sources enter the ledger | Treat generated terms as evidence |
| Structured extraction | Extract only stated fields; return unknown for missing values | Compare sample rows with source pages | Approve schema and corrections | Fill gaps from model memory |
| Interview coding | Cluster de-identified notes and retain evidence IDs | Double-code material and review exceptions | Name themes and boundaries | Invent quotes or respondents |
| Contradiction check | List claims with incompatible unit, date or definition | Open every referenced source | Choose whether comparison is valid | Smooth conflict into one number |
| Scenario drafting | Recalculate supplied assumptions and sensitivity ranges | Lock inputs and formulas | Approve planning case | Present scenario as market fact |
Size a market as a transparent scenario
A bottom-up planning scenario can use reachable_accounts × eligible_share × expected_annual_units × planning_price. Every input needs a source or an explicit hypothesis, and the output must remain a scenario. Do not call it total addressable market when the population, eligibility, unit or price definitions differ. Recalculate low, base and high cases only to see which assumption drives the decision.
Visual slot: Add a real market-sizing worksheet here: source population, eligibility hypothesis, reachable accounts, annual units, planning price, range, sensitivity, confidence and validation owner. Replace this block with the final visual later.
| Input | Evidence type | Quality question | Sensitivity test | Do not claim |
|---|---|---|---|---|
| Source population | Official table | Does it count the same firm unit and geography? | Replace with adjacent definition | Every record is a buyer |
| Eligible share | Screened primary evidence or explicit hypothesis | Which rule includes or excludes an account? | Vary the rule and range | Estimated share is measured prevalence |
| Reachability | Owned or partner channel evidence | Can the team identify and contact the segment lawfully? | Reduce accessible population | Reach equals demand |
| Annual units | Observed workflow or labelled assumption | What event creates a unit? | Change frequency range | Frequency is stable |
| Planning price | Current offer or explicit scenario | Does tax, discount and service scope align? | Test price and margin separately | Scenario is realized revenue |
Treat search interest as one signal, not demand
Google’s official Trends FAQ says Trends uses sampled, anonymized, categorized and aggregated searches, normalizes values by time and place, and is not scientific polling. A value from zero to one hundred is relative interest, not search volume, buyer count or sales. Use it to compare query language and direction within a defined setup; retain the query, topic choice, geography, period, category and retrieval date.
| Trends observation | What it may support | Required comparison | What it cannot prove | Next evidence |
|---|---|---|---|---|
| Term A exceeds term B | Relative search interest under the selected setup | Same geography, period and term/topic logic | Larger market or more revenue | Official population and buyer interviews |
| Regional difference | Relative concentration within Trends normalization | Comparable regions and time | Absolute demand by region | Local official and channel data |
| Seasonal pattern | Recurring relative interest pattern | Multiple periods and event notes | Purchasing season or causality | Sales, inventory and interviews |
| Low-volume zero | Term did not meet display threshold in setup | Synonyms and broader topic | No customer need | Direct research |
| Sudden spike | An event may have changed search interest | News and longer baseline | Sustained opportunity | Follow-up evidence over time |
Visualize the decision, not the decoration
Visualization rule
Choose the chart after naming the comparison and denominator; show unknowns and source notes beside the figure.
A bar chart can compare categories with aligned units; a line can show time under a consistent series; a distribution can reveal variation; and a decision matrix can combine qualitative evidence without pretending it is a statistic. Do not merge incompatible definitions because the chart looks clean. Every visual needs title, unit, geography, period, source and caveat.
Visual slot: Add a real research synthesis board here: decision, evidence streams, contradictions, confidence, chart choice, source note, owner and next experiment. Replace this block with the final visual later.
| Question | Suitable display | Must show | Misleading choice | Decision output |
|---|---|---|---|---|
| How do official counts differ by region? | Sorted bars or map with aligned units | Unit, year and definition | Three-dimensional chart without base | Priority regions for further research |
| How does interest change over time? | Line with annotated events | Period and normalized nature | Treating index as volume | Timing hypothesis |
| Which interview themes recur? | Evidence matrix with case IDs | Base, exceptions and quotes | Pie chart implying prevalence | Guide revision |
| Where do sources conflict? | Contradiction table | Source, definition and reviewer | Average incompatible numbers | Verification task |
| Which decision is supported? | Threshold scorecard | Evidence class, confidence and limit | Decorative dashboard total | Proceed, test, narrow or stop |
Weak research plan versus stronger research plan
| Layer | Weak plan | Stronger plan | Why stronger | Evidence needed |
|---|---|---|---|---|
| Decision | Research the AI software market | Choose whether to test UK field-service coordinators this quarter | Creates an accountable choice | Owner and stop condition |
| Secondary data | Ask AI for market size | Retrieve official business counts and definitions | Preserves provenance | Table, metadata and date |
| Competitors | Generate ten competitor summaries | Capture direct offer pages and unknown fields | Avoids invented market claims | URL and capture date |
| Customers | Ask whether they like the idea | Study last handoff, trigger, workaround and budget path | Grounds the problem in behavior | Screening and notes |
| Synthesis | Produce an executive summary | Maintain claim ledger, contradictions and confidence | Makes disagreement visible | Reviewer and decision record |
Detailed operational example
Assume a small UK software team is considering a scheduling product for field-service companies and a U.S. expansion later. The team has broad search interest, several vendor pages and enthusiastic internal opinions, but no aligned industry definition, buyer workflow or evidence that coordinators can be reached. This is a hypothetical operating example, not a case study, market benchmark or forecast.
The team writes a UK-first decision brief, retrieves official business and labor tables with definitions, records direct competitor pages, and recruits operations coordinators plus disconfirming owner-managed firms. AI extracts only specified fields, codes de-identified interview notes and lists contradictions. A tested survey is used only after the job and population are clear. The launch decision depends on repeated workflow evidence, accessible buyers and a viable small test, not a generated market total.
| Finding | First repair | Owner | Change-log entry | Watch | Do not claim |
|---|---|---|---|---|---|
| Industry counts use different units | Choose one enterprise or establishment definition | Research lead | Table, unit, period and exclusion | Eligible population range | Official count equals customers |
| Competitor pages omit onboarding effort | Mark unknown and ask recent evaluators | Product marketing | URL, missing field and interview prompt | Switching friction | Competitor is easy to adopt |
| Interview language conflicts with internal segment | Revise screening and recruit counterexamples | Research owner | Old/new segment rule and reason | Job recurrence and buyer role | Sample represents all firms |
| Survey question implies benefit | Rewrite neutrally and test comprehension | Research operations | Version, test note and exclusion | Completion and item interpretation | Agreement proves demand |
| Decision depends on one estimate | Run sensitivity and define a low-cost test | Founder and finance | Assumption range and stop rule | Recruitment and workflow evidence | Scenario predicts revenue |
Need an evidence-led market research audit?
Bring the decision brief, source ledger, interview plan and current market assumptions into one review. The audit identifies missing evidence and the next bounded test; it does not guarantee demand, launch success, leads or revenue.
Measure research quality without fake certainty
Decision rule
Measure whether evidence became more traceable, comparable and decision-relevant; do not score research by the amount of AI output.
Track unresolved source gaps, definition conflicts, recruitment coverage, disconfirming cases, survey-test failures, assumption sensitivity and decisions changed. Set a date and owner for each gap. A decision may still remain uncertain; the value of the process is that the uncertainty is named and priced. Do not claim that research caused subsequent growth, conversion or revenue without an appropriate design and competing explanations.
Visual slot: Add a real research change log here: date, claim, evidence added, definition changed, contradiction, confidence, decision impact, owner and next test. Replace this block with the final visual later.
| Signal | What it supports | Minimum evidence | Limit | Next action |
|---|---|---|---|---|
| Source coverage | Material claims are retrievable | Ledger links and reviewer state | More sources can still be redundant | Close critical gaps |
| Definition alignment | Comparisons use compatible units | Metadata and explicit transformation | Alignment does not prove relevance | Review segment fit |
| Disconfirming cases | The team tested its boundary | Recruitment and case evidence | Small sample does not estimate prevalence | Refine or stop |
| Survey comprehension | Questions are interpreted as intended | Cognitive or usability test notes | Does not remove sampling bias | Field a bounded test |
| Decision movement | Evidence changed proceed, narrow, test or stop choice | Dated decision record | Does not guarantee commercial outcome | Run the next controlled test |
What to remove, rewrite or keep audit-only
| Action | Claim or practice | Reason | Safer replacement |
|---|---|---|---|
| Remove | AI makes market research ten times faster | No approved source or stable definition | Describe the bounded task and review burden |
| Remove | This five-step method is the standard | The workflow is editorial, not universal fact | Name the operating loop and its limits |
| Rewrite | Google Trends proves demand | Trends reports normalized search interest | Use it as one query-language signal |
| Rewrite | Interviews show that most buyers agree | Purposive interviews do not estimate prevalence | Report themes, base and counterexamples |
| Keep audit-only | Private customer quote or commercial estimate | Consent, confidentiality or method is incomplete | Publish only with approval and full context |
Common market research mistakes with AI
- Starting with a tool instead of a decision and stop condition.
- Letting AI cite secondary summaries when a primary table exists.
- Mixing country, period, enterprise and establishment definitions.
- Treating search interest, interview enthusiasm or survey convenience as demand.
- Uploading identifying transcripts or confidential documents without approved handling.
- Filling unknown competitor fields with plausible model output.
- Presenting a planning scenario as market size or revenue forecast.
- Visualizing incompatible evidence without source notes and uncertainty.
FAQ
Can AI conduct market research on its own?
No. AI can help generate search queries, structure source fields, cluster de-identified notes, compare definitions and draft questions. It cannot establish whether a source is genuine, recruit a defensible sample, obtain valid consent, observe an unrecorded workflow or approve a business decision. A human owner must verify material claims against retrievable evidence and keep model suggestions separate from facts, assumptions and respondent statements.
Which sources should an SMB use first?
Begin with the source closest to the decision. Use official statistical agencies for population and economic definitions, direct vendor pages for observable offers, and interviews or tested surveys for customer workflow and language. Record geography, period, unit and retrieval date. A blog or AI summary may suggest where to look, but it should not replace a primary table, current product documentation or direct research evidence.
Can Google Trends estimate market size?
No. Google describes Trends as sampled, normalized search-interest data rather than scientific polling. Its zero-to-one-hundred values are relative within the chosen time, place and query setup; they are not search volume, buyer counts, revenue or total market size. Use Trends to explore language, timing and regional hypotheses, then compare those signals with official populations, channel evidence and primary customer research before making a market decision.
How many interviews are enough?
There is no universal number that makes an interview sample representative. Recruit according to the roles, use cases and disconfirming segments in the decision brief, then monitor whether new interviews change the workflow model or reveal important exceptions. Report the actual base and recruitment method. If you need prevalence or a market percentage, design an appropriate sampling study rather than converting repeated interview themes into statistics.
Should I upload interview transcripts to an AI tool?
Only when the organization’s approved privacy, security, contractual and research process permits it. Remove unnecessary identifiers, restrict access, understand vendor handling, and retain a secure source record outside the model. Sensitive customer, employee, health, financial or commercially confidential material may require stricter controls or no upload. AI convenience does not replace consent, purpose limitation, data minimization, retention decisions or professional legal review.
How do I know when research is sufficient to act?
Define the action threshold before collecting evidence. A practical threshold may require compatible official definitions, repeated workflow evidence across relevant roles, a reachable audience, no unresolved critical risk and a bounded test the team can afford. Research rarely removes all uncertainty. The decision record should show what is known, assumed, contradicted and still unknown, then choose to proceed, narrow, test further or stop without claiming guaranteed results.
What I would do first
First action
Write one reversible decision and one piece of evidence that would make you stop; then build the source ledger before opening an AI chat.
I would choose one segment, geography and buying situation, retrieve the best official population definition, capture the current alternatives, and conduct a few carefully screened interviews focused on the last real event. AI would receive a fixed extraction schema and de-identified material only. I would not field a survey or publish a market-size figure until definitions, sampling and contradictions were visible. The first deliverable is a decision brief, not a report deck.
Turn scattered research into a decision record
A market research audit separates sourced facts, customer evidence, assumptions and model suggestions, then assigns the next verification task. It creates a practical research plan without promises of market demand, leads, sales, launch success or revenue.