Small business CRM customer interviews: five prompts

Small business CRM customer interviews should reconstruct recent work before asking about products. The five prompts below are a prompt guide, not interview findings. Nobody was recruited or interviewed for this article, and it contains no quotation or claimed preference.

For an England-based small business, use this as a practical CRM software input. Before you compare packages or decide how to configure pipelines, use the prompts to map a real enquiry from first contact to record update.

The aim is not to sell a product or prove a preference. It is to gather neutral evidence about how a small team currently records enquiries, where ownership moves and which manual steps may be worth keeping.

That evidence can support a CRM software brief, a migration plan or a review of an existing system. The interview method remains research, not a product demonstration.

For a small business CRM software decision, these prompts turn real enquiry handling into requirements. They show which record updates, pipeline stages, ownership rules and manual steps the business actually needs. Use the answers to compare small business CRM options or to improve an existing CRM, not to run a generic research project.

Keep the focus on the CRM workflow: first contact, record update, hand-off and follow-up. That keeps the exercise useful for CRM software for small businesses in England.

What to take away

Method and boundaries

This five-prompt guide is intended for research with eligible participants working in England. Prompts were included when they could separate a concrete workflow event from opinion about CRM. The method excludes product demonstrations, sales qualification, leading feature questions and requests for confidential customer data. There was no sponsor, incentive or supplier involvement.

Before use, define the small-business rule, respondent role, England location rule, sampling frame, recruitment channel, field dates, interviewer, recording choice and analysis plan. Check the role again at the session opening in case responsibility moved after recruitment. The GOV.UK guide to in-depth interviews recommends open, neutral questions and real examples rather than general accounts of what should happen.

Sample size for England-based small businesses depends on the number of eligible roles and the variety of enquiry routes. Recruit through trade associations, local business networks and specialist research panels. Record the channel and date for each participant.

1. "Tell me about the latest relevant enquiry"

Name the workflow in the screener, then let the participant choose a recent eligible case. Ask when it started, who was involved and what made it complete. Record the prompt separately from the answer. Do not assume that delay or repetition needs software.

For the CRM brief, record candidate enquiry fields, the event that creates a record and what “complete” means. Treat each as a requirement to validate, not a feature recommendation.

2. "Show the route, using approved material"

Ask the participant to demonstrate the steps with synthetic or redacted data if privacy and security controls permit. Note only actions, screens and hand-offs directly observed. A participant's explanation of an unseen action remains a statement, not an observation. Stop screen sharing if personal or commercially sensitive information appears outside the agreed scope.

For software requirements, note which workflow actions need recording and whether information is entered manually or brought in through an import. Base any later CRM test on the route observed, not an assumed need.

3. "Where did the record change or become uncertain?"

Follow the chosen case through corrections, duplicates, ownership changes and exceptions. Neutral follow-ups include "What happened next?" and "How did you know?" Other examples are "Can you show that step on screen?" and "What did you record at that point?" Avoid "Would automation solve that?", which embeds the proposed answer.

Translate directly observed corrections, duplicates, ownership changes and exceptions into candidate requirements for record history, duplicate handling and ownership. Keep any unobserved need labelled as an inference or unknown.

4. "Who could approve a different process?"

Separate daily use from contract authority, data decisions and security review. Ask for the actual decision route and a recent comparable change. Do not translate influence into spending authority. A buyer's positive comment is not a purchase commitment.

Turn the decision route into role and access requirements: distinguish who updates records from who approves a process or handles data and security decisions.

5. "What would make you keep the present method?"

Explore the manual baseline, switching burden, training, inaccessible features, export needs and unacceptable risks. This prompt tests the proposition instead of inviting praise. Record unknowns when the participant cannot answer.

Record the constraints a CRM must preserve or address, such as switching burden, training and export needs. Use these as buyer-controlled acceptance checks later, not as claims about any product.

Protect the participant and the analysis

GOV.UK consent guidance for user research covers purpose, recording, data use, sharing, retention, withdrawal and complaint information. The actual organisation must choose its UK GDPR basis and obtain qualified privacy advice. Research agreement does not permit later promotion.

The ICO's direct marketing classification guidance distinguishes genuine research from surveys containing promotion or intended for later marketing. Keep recruitment and sales systems separate unless a reviewed, transparent route exists.

Use a five-column ledger: prompt, observed evidence, participant statement, editorial inference and unknown. A fictional worked row shows the format. It is not a finding.

Add participant code, eligible role, session date, interviewer, note-taker, guide version and deviations. GOV.UK analysis guidance advises teams to preserve what was seen or heard before deriving findings.

Report patterns only for the recruited cases and show the denominator. Stop fieldwork if consent cannot be matched to the data, the method excludes necessary access needs, or interviews have turned into disguised sales calls.

Before you act

Common questions

What should be defined before the interviews begin?

Before use, define the small-business rule, respondent role, England location rule, sampling frame, recruitment channel, field dates, interviewer, recording choice and analysis plan. Check the role again at the session opening in case responsibility moved after recruitment.

How should a participant demonstrate the route?

Ask the participant to demonstrate the steps with synthetic or redacted data if privacy and security controls permit. Note only actions, screens and hand-offs directly observed. A participant's explanation of an unseen action remains a statement, not an observation.

When should fieldwork stop?

Stop fieldwork if consent cannot be matched to the data, the method excludes necessary access needs, or interviews have turned into disguised sales calls. Research agreement does not permit later promotion, and the actual organisation must choose its UK GDPR basis.