What you can use
Validate a one-person business idea with a seven-day buyer research and paid-pilot plan. Includes interview questions, an evidence checklist, and a worksheet.
SOLOHATCH FIELD GUIDE · BUSINESS VALIDATION
Before building a website or buying another AI tool, test one thing: will a specific person take a meaningful next step to solve a specific problem?
This seven-day plan turns a broad one-person business idea into a small, observable experiment. Your output is one buyer group, one recurring problem, one bounded offer, and a log of what people actually did. Seven days cannot prove that a business will succeed.
Define a buyer and a problem
“An AI business for small companies” is too broad to test. It does not tell you whom to contact, what they struggle with, or what they might buy. Start with this sentence:
I help [specific buyer] handle [recurring problem] by delivering [bounded result], so they can [practical benefit].
Illustrative example: a freelance designer is considering a service that turns a fitness coach’s scattered service descriptions into a one-page enquiry guide. The initial buyer group is independent coaches already receiving enquiries. The problem is repeatedly explaining the same services before a prospect can decide whether to book.
This is a hypothetical example, not a customer result. The assumption to test is whether that explanation work is frequent and frustrating enough for coaches to consider paying for help.
The seven-day validation plan
Day 1: Pick one reachable buyer group
List people you can realistically reach through existing contacts, suitable professional communities, or public business contact routes. Narrow the group by its situation: “independent coaches receiving weekly enquiries” is more useful than “all small businesses.”
Write down your riskiest assumption. In the example: “Coaches spend enough time explaining their offer that a reusable enquiry guide would be useful.” Keep this assumption visible throughout the week.
Day 2: Ask about the last real occurrence
Invite a few suitable people to a short conversation. Three to five conversations may reveal useful initial patterns, but they are not a representative market study. Ask permission, respect community rules, and make your commercial purpose clear.
- When did this problem last happen?
- What did you do to handle it?
- Which part took the most effort?
- What have you already tried?
- What happened when you left it unresolved?
Avoid leading with “Would you buy my AI service?” It invites speculation. A description of a recent event is more useful than encouragement about an idea.
Day 3: Compare the workarounds
Look for recurring problems in the conversations. Does the buyer use saved messages, a spreadsheet, an existing document, or extra time? Record differences as well as similarities.
One coach may already have an effective FAQ. Another may write a long explanation for every enquiry. Those are different starting points. Do not assume everyone in a job category has the same need.
Day 4: Define a small paid pilot
Write a short offer with a deliverable, required inputs, a deadline, a stated price, a revision boundary, and clear exclusions. Choose a price you can explain from the work involved; do not present an arbitrary number as a market benchmark.
Illustrative pilot: “I will turn your current service notes and five common enquiry questions into a one-page enquiry guide within three working days of receiving your inputs. The pilot includes one revision. It excludes website development, advertising, and a promise of more bookings.”
Keep fulfilment manual while learning what buyers need. AI may help draft the document, but check its accuracy and obtain permission before sharing private client material with an external tool.
Day 5: Make a relevant invitation
Offer the pilot only to people for whom the problem is relevant and through a permitted route. Connect your message to their stated problem. Avoid scraped contact lists and repeated promotion in unrelated communities.
You mentioned rewriting the same explanation for new enquiries. I am testing a small service that turns those answers into a reusable one-page guide. Here are the scope, price, and delivery time. Would you like to discuss whether a pilot fits your situation?
The next step should be clear. Asking someone to “check out my business” gives you less useful feedback than inviting a specific discussion about a defined deliverable.
Day 6: Observe the next action
Record what happened: no reply, a question, a refusal, a request for scope, an introduction to a decision-maker, or an agreed paid pilot. Follow up briefly only when appropriate. A refusal could reflect timing, trust, price, or lack of need; it does not automatically explain which one.
If someone agrees to a pilot, confirm scope and terms before taking payment or starting work. One paid pilot demonstrates one purchase decision. It does not establish repeatable demand.
Day 7: Review and change one variable
Compare your result with a decision rule written before outreach. For example: “Continue if at least two suitable people independently describe the problem and at least one asks to discuss the defined pilot.” This is a personal learning threshold, not an industry conversion benchmark.
If the problem is real but the offer is unclear, revise the offer. If people rarely experience the problem, reconsider the buyer or problem. If you could not reach suitable people, test a better access route before drawing a demand conclusion. Change one main variable so the next result is easier to interpret.
Separate interest from evidence
- Polite interest: likes, compliments, and “sounds useful.” Do not count these as purchase commitments.
- Problem evidence: a recent example, a recurring workaround, or a cost the buyer can describe.
- Action evidence: discussing concrete scope, sharing appropriate inputs, involving the buyer, or agreeing to a paid pilot.
- Delivery evidence: whether a completed pilot met its agreed purpose and what the customer would change.
Track suitable people contacted as well as responses. Two replies from four relevant invitations and two from forty tell different stories. Small samples remain uncertain. Record evidence against your idea as carefully as evidence supporting it.
Copy this validation worksheet
Buyer group:
Recurring problem:
Last real example:
Current workaround:
Riskiest assumption:
Pilot deliverable and exclusions:
Price and delivery boundary:
People contacted / replies:
Observed actions:
Evidence against the idea:
Decision rule:
Next test:
Keep personal details out of shared logs. A short anonymized note is usually enough to support your decision.
Choose the next action the evidence supports
You may be ready for another pilot, a narrower buyer group, or a clearer offer. You may also decide to stop. Avoid turning a weak signal into a large automation project.
For a structured starting point, choose your SoloHatch path. To shape an offer, review the One-Person Company Starter Kit. When delivery starts repeating, explore AI workflow planning to decide what is worth standardizing.
Editorial note: Produced with AI assistance for SoloHatch. Examples are illustrative; no customer results are claimed. This is a planning framework, not a guarantee of customers or revenue.