Free field notes / Updated 2026-10-21
Validate a B2B Idea With Small Businesses
Talk to small-business owners, find the budget holder, and test a bounded paid pilot before building software or treating interest as a sale.
Validate a business-to-business idea with small businesses by learning a recent workflow, identifying who approves spending, and offering a tightly scoped pilot. A user liking the idea is not enough if someone else owns the budget or the team cannot adopt it. Test an actual buying and delivery decision before building a full system.
Choose one business type and one recurring task
"Software for small businesses" describes too many different operating environments. A one-person repair shop and a twenty-person event company have different workflows, budgets, and decision processes.
Start with a narrower situation. The hypothetical example here is a service that cleans up inventory entries for small secondhand shops. The initial audience is shops adding several batches of stock each month, with an owner who still checks the inventory records.
Keep the first problem administrative and bounded. Do not turn interviews into advice about financial, medical, or legal matters. If your proposed offer enters a regulated area, stop ordinary validation and seek qualified guidance first.
A useful starting question is: "How did you enter the last stock batch, and what went wrong, if anything?" It lets the owner describe the workflow without assuming they need your product.
Understand the buyer, user, and approver
In a small business, one person may fill all three roles, but do not assume it.
| Role | Question to ask | Why it matters |
|---|---|---|
| User | Who enters new stock into the inventory? | Finds the daily workflow |
| Buyer | Who would choose a different inventory workflow? | Finds ownership of the decision |
| Budget holder | Who can approve this expense? | Finds the spending decision |
| Reviewer | Who would need to check access or implementation? | Finds practical adoption constraints |
Ask about the most recent similar purchase. "How did you decide to pay for the last tool you added?" can reveal whether the owner acts alone, checks with a partner, or needs a team trial.
Do not pressure an employee to promise a purchase they cannot approve. Ask whether a conversation with the appropriate person would be useful, and let the employee choose whether to introduce you.
Interview around a real workflow
- Ask the owner to describe the last stock-entry task from start to finish.
- Identify the handoffs between people.
- Ask what information was missing or duplicated.
- Find out what they already use and what it costs in time or money.
- Ask what happens when the task goes badly.
- Learn when the problem will occur again.
A recent example is more useful than a general complaint that the business is busy. An owner might dislike the current stock sheet but still find changing it more disruptive than keeping it.
Avoid asking for private customer records. A blank inventory sheet, fictional example, or verbal description may answer the question without exposing anyone's information. Ask before viewing or keeping internal material.
Listen for existing satisfactory methods too. If the owner has a ten-minute stock-entry routine that works reliably, a polished replacement may not solve an important problem.
Use a relevant, permission-based outreach note
Approach owners through your own relationships, welcomed introductions, or business communities that permit relevant requests. Choose quiet times for local conversations and ask whether the person has a moment before explaining the idea.
A sample note for an existing contact or welcomed introduction is:
Hi, I am exploring how small secondhand shops record incoming stock. I am not selling a finished software product. Since you add new items regularly, would you be open to a 15-minute conversation about the last batch? No customer information needed, and no problem if the timing is wrong.
If you are ready to sell a manual pilot, say so rather than hiding the offer inside a research request. Keep the message personal because the context is real, not because you inserted a name into a mass template.
Do not repeatedly contact an owner who declines or does not respond. Respect the communication preferences of the business and any community rules.
Offer a pilot small enough to approve
After the research conversation, ask permission to explain the pilot. Specify what will happen, who must participate, the price, the duration, and what result you will review together.
For example: "For US$90, I will standardize inventory entries for your next three stock batches over two weeks. You supply item descriptions and check the final entries. I do the work manually; automated software is not built yet."
That pilot is different from a promise to transform all operations. It has a clear end and does not require a long commitment. Explain any input requirements before the owner agrees.
If the proposed product does not yet exist and you accept money in advance, make it refundable and explain the terms. Prefer a no-payment reservation if you cannot yet commit to a delivery scope and date.
Set both buying and delivery thresholds
A hypothetical buying threshold might be two paid pilots from eight suitable owner conversations by a fixed date. Define what counts as suitable and ensure each owner receives the same core offer.
A delivery threshold might be that the owner uses the cleaned entries for all three batches and requires no more than one revision per batch. If your promise concerns time saved, compare the owner's actual stock-entry process before and during the pilot. Do not infer savings from the number of entries you process.
Measure your own effort too. Suppose a US$90 pilot takes three hours to prepare and another hour for calls and revisions. That is US$22.50 per working hour before other costs. It may be useful learning, but it is not automatically a viable ongoing price.
Ask about a second purchase at a stated scope and price. A free extension can hide whether the original value was sufficient.
Understand letters of intent in plain terms
A letter of intent is a written statement of possible future interest or planned next steps. For an early test, it may record that a business wants to review a pilot once specified conditions are met.
Treat it as context, not completed revenue. The owner may still need approval, a working product, a date, or a satisfactory price. The document's meaning and obligations depend on its wording and circumstances; this guide is not legal advice. Ask a qualified professional if you need to understand its effect.
Do not draft documents that imply certainty you do not have. For validation, a clearly recorded pilot conversation or actual booking may be more informative than collecting impressive-looking paperwork.
Common mistakes
- Interviewing users without learning who approves spending.
- Offering a broad transformation instead of one bounded outcome.
- Asking owners to share unnecessary customer data.
- Treating a letter of intent as a purchase.
- Ignoring setup, staff time, and switching effort.
- Building features requested by a business that never accepts the pilot.
Use past-behavior questions to understand the workflow and manual delivery tests to examine value before automation.
Next step
Paste your idea into the free triage tool, then name one business type, one recurring task, and the person who can approve a small pilot. Make the first ask easy to understand and easy to decline.