blog details

How to Find Problems People Will Pay You to Solve

A research-led method for observing friction, tracing consequences, studying workarounds and validating value before you build a product, service or business.

Amara Stops Searching for “Business Ideas”

The guests are leaving a small Saturday event. Decorations are being packed into boxes, the venue manager is checking the room, and the client looks exhausted. During the week, Amara—the freelance event coordinator—has heard the same family of sentences again and again: “I forgot to confirm the photographer.” “Who is collecting the cake?” “Did anyone send the location?” “I thought she was handling the chairs.” “Where is the final guest list?” “Who still needs to be paid?”

At first, each sentence sounds like a separate annoyance. Then Amara notices the pattern. The work is being coordinated through memory, scattered notes, calls and long chat threads. The problem is not that people need “another event ebook.” The problem may be that small event organizers have too many responsibilities without one dependable coordination system.

AMARA DID NOT DISCOVER AN IDEA. SHE DISCOVERED A REPEATED PROBLEM.

That distinction changes how you look for opportunities. Instead of asking What should I sell?, ask What are people already struggling to do—and what evidence tells me that solving it matters?

Quick Answer: How do I find problems people will pay me to solve?

Observe a specific group of people and look for repeated loss of time, money, opportunity, convenience or confidence: complaints, recurring questions, manual workarounds, delays, mistakes, bottlenecks, repeated spending, jobs people already hire others to do, confusing decisions and fragmented tools. Then investigate who has the problem, how often it occurs, what happens if it remains unsolved, what people do now, what they have already tried, who controls the budget and why current alternatives are insufficient.

OBSERVATION → PROBLEM → PERSON → CONSEQUENCE → CURRENT SOLUTION → VALUE → PAYMENT EVIDENCE → SOLUTION HYPOTHESIS → VALIDATION

Market research is meant to reduce guessing. The U.S. Small Business Administration recommends examining demand, alternatives, pricing and direct customer research; Harvard Business School guidance similarly emphasizes problem discovery before falling in love with a solution. A repeated problem is a reason to investigate—not proof of a profitable opportunity.

Problem ≠ Paid Problem

A problem can be real and still be commercially weak. Someone whose phone battery occasionally dies may carry a charger, use a power bank, charge at work or simply tolerate the inconvenience. The existence of the annoyance does not prove that person wants a 40-page battery-management guide.

Now compare that with a delivery company repeatedly losing customer orders because dispatch information is copied manually between three systems. The consequences might include refunds, staff time, delivery delays and customer complaints. That still does not prove your proposed software will sell—but it gives you more concrete consequences to investigate.

DO NOT LOOK ONLY FOR PROBLEMS. LOOK FOR PROBLEMS WITH CONSEQUENCES.

The bigger question is not merely “Does this problem exist?” It is “What happens if this problem is not solved?”

PROBLEM ≠ PAID PROBLEMPROBLEM EXISTS↓WHO CARES?↓CONSEQUENCE↓CURRENT SOLUTION↓DISSATISFACTION↓VALUE↓PAYMENT EVIDENCEDO NOT LOOK ONLY FOR PROBLEMS. LOOK FOR PROBLEMS WITH CONSEQUENCES.

The VEZILL Problem Value Map

Run every opportunity through this sequence before deciding what to build.

Problem
Describe the observable situation without embedding your solution. Who has it?
Name the person, role or business precisely. When?
Identify the moment and context in which it appears. How often?
Frequency can change the economics dramatically. What does it cost?
Trace time, money, risk and missed opportunity. What do they do now?
The real competitor may be a spreadsheet, employee, habit or “do nothing.” What is wrong now?
Do not assume dissatisfaction; find evidence. Who decides?
The user may not control the purchase. Who pays?
Identify the budget owner and buying process. Better outcome
Describe the improvement, not your preferred format. Evidence of value
Look for behavior, spending, switching, repeated effort or validated tests. A PROBLEM BECOMES MORE INTERESTING WHEN YOU CAN TRACE ITS CONSEQUENCES.

Where Real Problems Hide

Problem discovery is observational. Useful sources include customer questions, complaints, reviews, support tickets, sales calls, refund reasons, search queries, community discussions, forums, YouTube comments, workplaces, manual spreadsheets, WhatsApp workflows, email chains, repeated copy-paste work, freelance briefs, job posts, onboarding, business processes and homemade workarounds. VEZILL’s guide to turning customer questions into digital products makes an important related point: a question is a signal of a possible knowledge gap, not automatic purchase evidence.

Online discussions can help you generate hypotheses, especially when the same situation appears in different places. But an angry review, a viral post or a Reddit thread does not equal a market. Ask: How common is this? Who experiences it? What do they do about it? What does it cost? What would they switch from?

ONLINE COMPLAINT ≠ CUSTOMER DEMAND.

The 8 Types of Valuable Problems

1. Money
Loss, waste, leakage or avoidable cost. Value may come from reducing waste or improving a process—never promise financial results you cannot control. 2. Time
Repeated work consumes meaningful hours. A faster workflow, template, service or automation may help. 3. Risk
People want to reduce mistakes or uncertainty. High-stakes fields require qualified expertise and current authoritative guidance. 4. Complexity
A task is difficult to understand or perform. Structure, simplification and guided workflows can create value. 5. Convenience
People can do it themselves but prefer less effort. Done-for-you work, tools or automation may compete with DIY. 6. Knowledge
People do not know how to complete a bounded task. A guide, tutorial, checklist or other Quick Knowledge format may fit. 7. Coordination
People, tasks and information must stay synchronized. Planners, SOPs, dashboards and workflows can help. 8. Confidence friction
Uncertainty or overwhelm blocks action. Ethical decision support and preparation can help without exploiting insecurity. PEOPLE DO NOT PAY FOR “PAIN POINTS.” THEY PAY FOR OUTCOMES THEY VALUE.

The Four Consequences Test

For each problem, ask whether leaving it unsolved costs meaningful time, money, creates risk, or blocks an opportunity. A problem does not need all four. The test simply forces you to move from vague annoyance to consequences you can investigate.

THE FOUR CONSEQUENCESTIME — hours or effort wasted↓MONEY — cost, waste or lost revenue↓RISK — mistakes, failure or uncertainty↓OPPORTUNITY — valuable work blockedWHAT HAPPENS IF THIS IS NOT SOLVED?

The VEZILL Problem Signal Score

Score each dimension from 1 (weak evidence) to 5 (strong evidence): frequency, severity, consequence, urgency, existing spend, workarounds, search/question activity, dissatisfaction with alternatives, accessibility of the audience, your ability to solve it responsibly, clarity of the budget owner and quality of evidence. Do not turn the total into a magical cutoff. Use it to compare hypotheses and expose what you still do not know.

HIGH SCORE ≠ GUARANTEED BUSINESS · IT MEANS WORTH INVESTIGATING FURTHER.

50 Problem Opportunities to Investigate

These are hypotheses, not claims of proven demand. Notice that the proposed solutions vary: services, workflows, templates, software, guides and process changes. The goal is to train your eye to connect observation to evidence.

Small Retail

1. Neighbourhood clothing shop
Observed problem: Sizing and availability questions repeat across WhatsApp and Instagram.
Consequence: Staff time is consumed and serious enquiries can disappear in chat.
Current workaround: Copy old replies and check stock manually.
What the signal may mean: Product information or stock visibility may be weak.
Possible solution hypothesis: Product-page cleanup, approved response library and stock-status workflow.
What must be validated: Frequency, stock accuracy, return reasons and whether clearer listings reduce questions. 2. Small hardware store
Observed problem: Popular items are discovered out of stock only when a customer asks.
Consequence: Lost sales opportunities and rushed supplier calls.
Current workaround: Memory, shelf checks and supplier messages.
What the signal may mean: Replenishment visibility may be weak.
Possible solution hypothesis: Reorder-point sheet or weekly stock routine.
What must be validated: Stockout frequency, lead times, records and staff adoption. 3. Cosmetics retailer
Observed problem: Customers repeatedly need help choosing among variants.
Consequence: Long consultations and inconsistent staff guidance.
Current workaround: Ask one experienced colleague.
What the signal may mean: A safe structured selection aid may help.
Possible solution hypothesis: Non-medical comparison guide or staff decision aid.
What must be validated: Question types, safety boundaries, returns and customer preference for human help. 4. Gift shop
Observed problem: Custom-order specifications are scattered across chats.
Consequence: Rework, missed dates and disputes.
Current workaround: Screenshots and handwritten notes.
What the signal may mean: Order capture and handoff may be the issue.
Possible solution hypothesis: Custom-order intake form and production tracker.
What must be validated: Delay causes, form completion and existing POS capability. 5. Electronics accessories kiosk
Observed problem: Customers sometimes buy incompatible cables or accessories.
Consequence: Returns and lost trust.
Current workaround: Visual inspection and customer descriptions.
What the signal may mean: Compatibility identification may be a meaningful decision problem.
Possible solution hypothesis: Compatibility lookup workflow and labeled catalog.
What must be validated: Return reasons, device range, supplier data and accuracy needs.

Restaurants / Food Businesses

6. Small café
Observed problem: Ingredients run out during busy service.
Consequence: Unavailable menu items, emergency purchases and slower service.
Current workaround: A cook messages the owner, who sends someone to a shop.
What the signal may mean: Replenishment may be weak, but supplier reliability or menu planning could be the cause.
Possible solution hypothesis: Closing-stock checklist, par-level sheet or inventory setup.
What must be validated: Incident frequency, waste, lead times and ordering ownership. 7. Home baker
Observed problem: Customers change cake specifications after ordering.
Consequence: Rework, pricing confusion and deadline pressure.
Current workaround: Search old messages for the latest request.
What the signal may mean: Specification approval may be the real problem.
Possible solution hypothesis: Order brief, change-request process and final approval sheet.
What must be validated: Change frequency, causes, deposit policy and approval behavior. 8. Meal-prep business
Observed problem: Delivery-window and storage questions repeat after purchase.
Consequence: Support load grows and instructions vary.
Current workaround: Individual voice notes.
What the signal may mean: Post-purchase guidance may be missing.
Possible solution hypothesis: Delivery/storage information card and approved automated messages.
What must be validated: Food-safety requirements, reading behavior and delivery communication. 9. Small restaurant
Observed problem: Waiters repeatedly ask whether menu items are available.
Consequence: Ordering slows and customers wait.
Current workaround: Verbal checks or staff chat.
What the signal may mean: Availability communication may be the bottleneck.
Possible solution hypothesis: Sold-out board, shared status process or POS configuration.
What must be validated: Change frequency, team size and current POS features. 10. Caterer
Observed problem: Event quantities are recalculated from scratch.
Consequence: Quotation time and inconsistent assumptions increase.
Current workaround: Copy old spreadsheets and quotes.
What the signal may mean: A repeatable estimating workflow may save time.
Possible solution hypothesis: Controlled costing/quantity worksheet with documented assumptions.
What must be validated: Event variation, accuracy, food-safety and professional judgment.

Freelancers

11. Freelance web designer
Observed problem: Projects stall because clients do not send copy and assets.
Consequence: Deadlines slip and project-management time grows.
Current workaround: Repeated email and WhatsApp reminders.
What the signal may mean: Client preparation is part of the delivery problem.
Possible solution hypothesis: Website content preparation workbook, portal or paid organization add-on.
What must be validated: Missing inputs, client completion and whether assistance beats a template. 12. Graphic designer
Observed problem: Feedback arrives across several channels.
Consequence: Revision cycles expand and requests conflict.
Current workaround: Manually consolidate email, chat and voice notes.
What the signal may mean: Feedback collection and approval may be the problem.
Possible solution hypothesis: Review workflow or client approval system.
What must be validated: Revision causes, client preferences and project size. 13. Virtual assistant
Observed problem: Client follow-ups get lost in the inbox.
Consequence: Enquiries go cold and owner time is wasted.
Current workaround: Flags, stars and handwritten reminders.
What the signal may mean: Lead-state visibility may be the issue.
Possible solution hypothesis: Inbox-to-follow-up workflow or simple CRM setup.
What must be validated: Lead volume, privacy, lost-follow-up evidence and habit change. 14. Video editor
Observed problem: Clients send badly named files and omit assets.
Consequence: Editing starts late and files are misplaced.
Current workaround: Editor reorganizes everything manually.
What the signal may mean: Client handoff quality may be weak.
Possible solution hypothesis: Upload structure, naming template and intake checklist.
What must be validated: Client compliance, missing-asset frequency and storage-tool features. 15. Bookkeeper serving microbusinesses
Observed problem: Clients submit records late and in mixed formats.
Consequence: Month-end work slows and corrections multiply.
Current workaround: Chase screenshots, statements and receipts.
What the signal may mean: Document collection may need structure.
Possible solution hypothesis: Secure monthly records checklist and collection workflow.
What must be validated: Confidentiality, local compliance, secure storage and software integrations.

Content Creators

16. YouTube creator
Observed problem: Research links and footage references are scattered.
Consequence: Scripting takes longer and sources are hard to retrace.
Current workaround: Tabs, screenshots and notes apps.
What the signal may mean: Research organization may be a repeated workflow problem.
Possible solution hypothesis: Research capture template or database setup.
What must be validated: Research volume, current tools and collaboration needs. 17. Newsletter writer
Observed problem: Every issue starts from a blank page despite recurring sections.
Consequence: Publishing is inconsistent and planning takes too long.
Current workaround: Copy and strip down old newsletters.
What the signal may mean: A repeatable editorial structure may reduce friction.
Possible solution hypothesis: Editorial planning system or issue template.
What must be validated: Whether the real issue is structure, ideas, research time or motivation. 18. Podcast host
Observed problem: Guests arrive without understanding recording expectations.
Consequence: Setup time is wasted and quality varies.
Current workaround: Ad-hoc reminder messages.
What the signal may mean: Guest preparation may be insufficient.
Possible solution hypothesis: Guest preparation pack and pre-recording sequence.
What must be validated: Recurring problems, guest compliance and platform constraints. 19. Short-form creator
Observed problem: Brand deliverables are tracked through screenshots and DMs.
Consequence: Deadlines and usage obligations become hard to monitor.
Current workaround: Calendar reminders plus message searches.
What the signal may mean: Campaign tracking may matter for creators with enough deals.
Possible solution hypothesis: Brand-campaign tracker or management service.
What must be validated: Deal frequency, contracts, confidentiality and agency support. 20. Online educator
Observed problem: Learners repeatedly ask where lesson resources are.
Consequence: Support burden grows and learners lose momentum.
Current workaround: Teacher replies with links manually.
What the signal may mean: Course navigation may be weak.
Possible solution hypothesis: Searchable resource index or navigation redesign.
What must be validated: Question frequency and platform search capability.

Events

21. Freelance event coordinator
Observed problem: Responsibilities are scattered across chats, memory and notes.
Consequence: Missed confirmations, duplicated work and stress.
Current workaround: WhatsApp threads, notebook pages and calls.
What the signal may mean: Coordination ownership may be a repeatable problem.
Possible solution hypothesis: Small Event Coordination Workbook or coordination service.
What must be validated: Frequency, organizer type, tools, free alternatives and buyer. 22. Wedding photographer
Observed problem: Couples repeatedly arrive unsure what to prepare.
Consequence: Lost shooting time and avoidable confusion.
Current workaround: Different voice notes to each couple.
What the signal may mean: Preparation knowledge may be reusable.
Possible solution hypothesis: Wedding photo preparation planner.
What must be validated: Common questions, cultural variation, venues and whether free guidance is enough. 23. Community-event organizer
Observed problem: Volunteer duties are unclear until event morning.
Consequence: Tasks are duplicated or forgotten.
Current workaround: Last-minute group-chat assignments.
What the signal may mean: Role clarity and handoff may be the issue.
Possible solution hypothesis: Responsibility matrix and run sheet.
What must be validated: Event frequency, volunteer turnover and adoption. 24. Small corporate-event planner
Observed problem: Vendor payment status is tracked across messages and notifications.
Consequence: Duplicate follow-ups and uncertainty.
Current workaround: Spreadsheet updated manually.
What the signal may mean: Payment-status organization may matter.
Possible solution hypothesis: Non-accounting vendor tracker and approval workflow.
What must be validated: Finance ownership, privacy and existing accounting tools. 25. Birthday-party decorator
Observed problem: Clients change theme details after materials are purchased.
Consequence: Waste and disputes about extra costs.
Current workaround: Chat history and informal confirmation.
What the signal may mean: Change control may be the need.
Possible solution hypothesis: Design approval form and change-request workflow.
What must be validated: Frequency, client acceptance and deposit policy.

Property / Hospitality

26. Small guesthouse
Observed problem: Guests repeat check-in, Wi-Fi and transport questions.
Consequence: Front-desk time is consumed and answers vary.
Current workaround: Individual messages.
What the signal may mean: Guest information may be fragmented.
Possible solution hypothesis: Mobile guest guide and approved message sequence.
What must be validated: Top questions, languages and platform rules. 27. Independent landlord
Observed problem: Maintenance reports arrive without enough detail.
Consequence: Diagnosis and contractor scheduling are delayed.
Current workaround: Back-and-forth requests for photos and location.
What the signal may mean: Issue intake quality may be weak.
Possible solution hypothesis: Maintenance request form and triage workflow.
What must be validated: Emergency escalation, privacy, obligations and tenant adoption. 28. Short-stay host
Observed problem: Cleaners sometimes miss restocking items.
Consequence: Guest complaints and emergency deliveries occur.
Current workaround: Paper checklist or memory.
What the signal may mean: Turnover verification may be a repeated need.
Possible solution hypothesis: Turnover checklist with photo confirmation.
What must be validated: Property count, staff turnover and whether compliance is the cause. 29. Property agent
Observed problem: Prospects request listings that do not match budget or location.
Consequence: Agent time goes to poor-fit conversations.
Current workaround: Manual questioning in chat.
What the signal may mean: Qualification may be inefficient.
Possible solution hypothesis: Property-needs intake form and matching workflow.
What must be validated: Lead volume, privacy and whether forms deter good leads. 30. Small tour operator
Observed problem: Guests misunderstand what a day trip includes.
Consequence: Disputes and last-minute purchases arise.
Current workaround: Staff explain inclusions after booking.
What the signal may mean: Offer clarity may be the root problem.
Possible solution hypothesis: Rewritten booking page and pre-trip checklist.
What must be validated: Complaint frequency, seasonality and safety requirements.

Ecommerce / Online Sellers

31. Instagram clothing seller
Observed problem: Sizing, delivery and exchange questions repeat.
Consequence: Seller spends hours on repetitive support.
Current workaround: Saved replies and story highlights.
What the signal may mean: Information architecture may be weak.
Possible solution hypothesis: Better listings, size guide, FAQ and approved replies.
What must be validated: Question frequency, return reasons and reading behavior. 32. Handmade-product seller
Observed problem: Custom specifications are misunderstood after payment.
Consequence: Remakes and unhappy customers result.
Current workaround: Screenshots of chat approvals.
What the signal may mean: Specification confirmation may need structure.
Possible solution hypothesis: Configuration form and final proof approval.
What must be validated: Error rate, variability and customer effort. 33. Small online grocery
Observed problem: Orders arrive through several channels and are retyped.
Consequence: Items are omitted and fulfillment slows.
Current workaround: Copy-paste from chats into spreadsheets.
What the signal may mean: Order consolidation may have measurable value.
Possible solution hypothesis: Central order form or integration service.
What must be validated: Order volume, errors, channel preference and payment flow. 34. Digital download seller
Observed problem: Buyers cannot locate purchased files.
Consequence: Refund requests and support messages increase.
Current workaround: Manual resend by email.
What the signal may mean: Delivery UX may be failing.
Possible solution hypothesis: Post-purchase instructions or delivery automation.
What must be validated: Support volume, email issues and platform features. 35. Beauty-products seller
Observed problem: Customers ask usage questions that cross into medical concerns.
Consequence: Support is difficult and inappropriate advice creates risk.
Current workaround: Ad-hoc chat answers.
What the signal may mean: Clear boundaries and safe product information may be needed.
Possible solution hypothesis: Approved usage guide with professional escalation.
What must be validated: Manufacturer instructions, regulation, allowed claims and professional review.

Professional Services

36. Small law office
Observed problem: Prospects send incomplete information before consultations.
Consequence: Staff spend time requesting basic context.
Current workaround: Email chains and phone calls.
What the signal may mean: Intake structure may be inefficient.
Possible solution hypothesis: Secure firm-reviewed intake workflow.
What must be validated: Jurisdiction, confidentiality, professional rules and data security. 37. Accounting firm
Observed problem: Clients ask which records to prepare for routine meetings.
Consequence: Meeting time is spent assembling missing documents.
Current workaround: Individual reminder emails.
What the signal may mean: Preparation guidance may be reusable.
Possible solution hypothesis: Professionally reviewed preparation checklist and secure collection workflow.
What must be validated: Current rules, firm process and data protection. 38. Consultant
Observed problem: Every project starts with the same lengthy discovery explanation.
Consequence: Unpaid setup time and inconsistent expectations.
Current workaround: Copy old proposals.
What the signal may mean: A standardized discovery experience may improve clarity.
Possible solution hypothesis: Paid discovery package or intake workbook.
What must be validated: Client variation, acceptance and scope boundaries. 39. Recruitment agency
Observed problem: Hiring managers submit vague role requirements.
Consequence: Searches restart when expectations change.
Current workaround: Repeated manager interviews.
What the signal may mean: Role-definition quality may be the root problem.
Possible solution hypothesis: Hiring-manager role brief and kickoff workshop.
What must be validated: Missing details, decision-maker alignment and employment rules. 40. Architecture/design studio
Observed problem: Approvals are buried in email.
Consequence: Schedules slip and teams use outdated feedback.
Current workaround: Manual email summaries.
What the signal may mean: Decision tracking may be a coordination problem.
Possible solution hypothesis: Decision register and approval workflow.
What must be validated: Project scale, contractual controls and existing software use.

Students / Learners

41. University student
Observed problem: Deadlines are spread across portals and chats.
Consequence: Deadlines are missed and planning becomes reactive.
Current workaround: Screenshots and phone reminders.
What the signal may mean: Deadline consolidation may be the issue.
Possible solution hypothesis: Personal deadline dashboard or calendar setup guide.
What must be validated: Export options, student habits and whether free tools suffice. 42. Online learner
Observed problem: Tutorials are watched but practice is postponed.
Consequence: Knowledge is consumed without application.
Current workaround: Bookmarks and long playlists.
What the signal may mean: Practice structure may help, but motivation or course quality could be causes.
Possible solution hypothesis: Practice planner or accountability service.
What must be validated: Why practice is skipped and whether reminders change behavior. 43. Exam candidate
Observed problem: Revision materials are abundant but priorities are unclear.
Consequence: Time is lost switching resources.
Current workaround: Multiple PDFs, notes and videos.
What the signal may mean: Resource overload may create a planning problem.
Possible solution hypothesis: Current-syllabus revision planner.
What must be validated: Official syllabus, learner level and teaching-support needs. 44. New software learner
Observed problem: Setup errors prevent starting beginner exercises.
Consequence: Learning stalls before core concepts.
Current workaround: Repeated reinstalls and forum searches.
What the signal may mean: Environment setup may be a bounded knowledge problem.
Possible solution hypothesis: Version-specific setup checklist.
What must be validated: Versions, operating systems, official docs and maintenance burden. 45. Group-project team
Observed problem: Members do not know who owns each deliverable.
Consequence: Work is duplicated and integration happens late.
Current workaround: Group chat plus verbal agreements.
What the signal may mean: Coordination may be the issue.
Possible solution hypothesis: Responsibility matrix and milestone template.
What must be validated: Team size, assignment rules and adoption.

Local / Small Businesses

46. Salon
Observed problem: Appointments across DMs, calls and WhatsApp occasionally clash.
Consequence: Customers wait or slots are double-booked.
Current workaround: Paper diary plus chat search.
What the signal may mean: Scheduling may be worth improving if clashes are frequent.
Possible solution hypothesis: Calendar workflow, booking setup or service.
What must be validated: Clash frequency, walk-ins, staff schedules and customer channel preference. 47. Barbershop
Observed problem: Customers repeatedly ask expected waiting time.
Consequence: Walk-ins leave or call repeatedly.
Current workaround: Verbal estimates.
What the signal may mean: Queue visibility may matter at peak periods.
Possible solution hypothesis: Queue board, messaging workflow or booking option.
What must be validated: Peak patterns and whether estimates are reliable. 48. Church/community office
Observed problem: Registrations and volunteer details arrive through group chats.
Consequence: Names duplicate and coordinators lack a clean list.
Current workaround: Manual copy-paste into spreadsheets.
What the signal may mean: Information collection may be the problem.
Possible solution hypothesis: Registration form, roster and communication workflow.
What must be validated: Consent, data minimization, access and organizer capacity. 49. Small distributor
Observed problem: Retailers send orders in inconsistent WhatsApp formats.
Consequence: Sales staff retype orders and make clarification calls.
Current workaround: Chat copied into spreadsheets.
What the signal may mean: Order standardization may reduce friction without replacing WhatsApp.
Possible solution hypothesis: Structured order format, form link or capture system.
What must be validated: Retailer adoption, volume, errors, connectivity and integration. 50. Tourism microbusiness
Observed problem: Enquiries repeat itinerary, pickup and payment questions.
Consequence: Owner spends evenings answering basics.
Current workaround: Voice notes and copied messages.
What the signal may mean: Offer clarity and qualification may be weak.
Possible solution hypothesis: Clear enquiry page, itinerary template, FAQ and booking intake.
What must be validated: Seasonality, platform policies, payment safety and information accuracy.

Watch What People Do, Not Only What They Say

“I would definitely buy that” is easy to say when no money, time or switching cost is involved. Research on hypothetical bias in stated willingness-to-pay shows why hypothetical choices can diverge from actual purchasing behavior. In customer discovery, that means future-intent questions should not carry the same weight as concrete history.

Ask about the last time the problem happened. Did the person pay someone? Spend three hours fixing it? Build an ugly spreadsheet? Try four tools? Change suppliers? Cancel a service? Repeatedly search for help? These behaviors are imperfect but more grounded evidence than politeness.

A COMPLIMENT IS NOT A PURCHASE. A LIKE IS NOT A PURCHASE. A SURVEY “YES” IS NOT A PURCHASE. BEHAVIOR IS STRONGER EVIDENCE THAN POLITENESS.

The Workaround Principle

A workaround is what people create when the problem matters enough to require action but the available solution is absent, inconvenient, expensive or poorly matched. Spreadsheet + WhatsApp + notebook, manual copy-paste, screenshots, sticky notes, repeated Google searches, manual reminders and employees doing repetitive admin are all clues.

But ask why the workaround survives. Perhaps it is cheap, familiar, flexible and “good enough.” Switching itself has a cost. Measure how painful the workaround is, how often it is used, what it costs and what would justify change.

UGLY WORKAROUNDS ARE CLUES. THEY ARE NOT PURCHASE ORDERS. THE WORKAROUND SIGNALPROBLEM↓MANUAL WORK↓SPREADSHEETS / WHATSAPP↓COPY-PASTE↓MULTIPLE TOOLS↓EXTRA TIMEUGLY WORKAROUNDS ARE CLUES. THEY ARE NOT PURCHASE ORDERS.

The Existing-Spend Signal

Look beyond direct purchases. A business may already allocate employee hours, freelancer fees, software subscriptions, consultants, equipment, training, outsourcing or emergency labor to an outcome. That can establish that the outcome receives resources today.

A restaurant paying for repeated emergency deliveries because stock planning fails, a creator repeatedly hiring someone to format documents, or a business assigning five staff-hours each week to reconcile data all reveal economic behavior. Existing spend still does not mean they will pay you. Your alternative must be trusted, usable and valuable enough to justify switching.

B2B and Consumer Problems Are Not the Same Buying System

Consumer
The person experiencing the problem often decides and pays. Convenience, identity, confidence and personal time can matter strongly, while budgets may be smaller. B2B
An employee may experience the problem, a manager may evaluate the solution, and an owner or procurement function may approve payment. Economic consequences, integration, security and trust may dominate. USER ≠ BUYER ≠ DECISION MAKER — SOMETIMES.

A receptionist may struggle with repetitive scheduling, an operations manager may evaluate a new workflow, and the business owner may control the budget. Finding the person with the problem is not always the same as finding the person with the budget.

Five Deeper Case Studies

1. Amara / Events

Responsibilities live across WhatsApp, memory and notes. The consequence is missed confirmations and duplicated work; the workaround is more messages and calls. A Small Event Coordination Workbook is only a hypothesis. Amara must test frequency, organizer type, existing tools, free alternatives, who pays and whether a central planner actually improves coordination.

2. Small Restaurant

Staff discover missing ingredients during service. Do not jump to “inventory app.” Investigate ordering, supplier reliability, stock counting, menu changes, waste and responsibility. The right answer could be a closing checklist, spreadsheet, workflow redesign, training or software. THE FIRST SOLUTION IDEA MAY BE WRONG.

3. Freelance Web Designer

Projects stall because clients fail to provide website content. Repeated reminders are the workaround. A content-preparation workbook, onboarding service, template or portal could help, but the designer must learn which inputs cause delay and whether clients want self-service or hands-on support.

4. Small Online Seller

Pre-purchase questions repeat. The cause could be poor descriptions, unclear delivery rules, weak FAQs, trust concerns or a complex product. A chatbot might automate the symptom while leaving the cause untouched. Sometimes rewriting the product page is the better solution.

5. Student

A learner repeatedly misses assignment deadlines. The cause might be poor planning, too many platforms, work obligations, unclear instructions or missing reminders. A planner is only one hypothesis. Research the context before prescribing the format.

Symptom vs Root Problem

“Customers keep asking where their orders are” is a symptom. Possible causes include poor tracking, slow delivery, unclear communication, unrealistic promises or incorrect contact details. Building 100 customer-service reply templates may make staff faster at answering the same preventable question.

Likewise, repeated data-entry mistakes can come from a confusing interface, duplicate entry, weak instructions, insufficient training or a process that should not be manual at all. Root-cause work matters because fixing a visible symptom can preserve the system that creates it.

DO NOT BUILD A BETTER BANDAGE BEFORE CHECKING WHETHER YOU CAN REMOVE THE SOURCE OF THE PROBLEM.

The 5 Whys—Useful, but Not Magic

ASQ describes Five Whys as a questioning technique for drilling beneath symptoms, and explicitly notes that reaching a cause may take fewer or more than five questions. Complex problems can also have multiple causes, so do not force one neat chain.

Amara can ask: Why was the photographer not confirmed? Responsibility was unclear. Why? Tasks were distributed through chat. Why? There was no central responsibility list. That points toward a coordination-system hypothesis—but she should still verify it across events instead of treating the third “why” as proof.

How to Interview People About Problems

Weak question: “Would you buy an app that solves this?” Better questions reconstruct reality: “Tell me about the last time this happened.” “What were you trying to do?” “What happened?” “How did you solve it?” “How long did it take?” “Who was involved?” “What did it cost?” “What have you tried?” “What do you use now?” “What is frustrating about it?” “How often does this happen?” “What happens if you ignore it?” “Who decides how it gets solved?” “Have you ever paid to solve it?” “What would make you switch?”

Harvard Business School’s user-interview guidance emphasizes understanding the customer’s circumstances, challenges and decision process. The principle here is simple: ask about the past before asking about the future.

The VEZILL Problem Interview

PERSON / BUSINESS: ________
WHAT ARE THEY TRYING TO DO? ________
WHAT HAPPENED LAST TIME? ________
WHERE DID THEY GET STUCK? ________
HOW OFTEN? ________
CURRENT SOLUTION: ________
WHAT IS WRONG WITH IT? ________
TIME COST: ________
MONEY COST: ________
RISK: ________
OPPORTUNITY COST: ________
WHO EXPERIENCES IT? ________
WHO DECIDES? ________
WHO PAYS? ________
WHAT HAVE THEY TRIED? ________
WHAT HAVE THEY PAID FOR? ________
WHAT WOULD A BETTER OUTCOME LOOK LIKE? ________
WHAT EVIDENCE DO I HAVE? ________
WHAT AM I ONLY ASSUMING? ________

How to Use AI to Find Patterns in Problems

Do not begin with “Give me profitable problems.” Begin with real observations. AI can cluster complaints, normalize wording, categorize questions, summarize interviews, surface repeated themes, distinguish symptoms from possible causes, identify missing research and organize evidence. It must not invent interviews, customers, frequency, market size, budgets, spending or willingness to pay.

USE AI TO ORGANIZE EVIDENCE. DO NOT USE AI TO MANUFACTURE A MARKET.

VEZILL Problem Discovery AI Prompt

I am researching real problems experienced by [AUDIENCE]. Below is raw research collected from real interviews, reviews, customer questions, support messages, observations or workflow notes. Do NOT suggest businesses or products yet. 1. Normalize similar problems without changing meaning. 2. Group them into themes. 3. Count recurrence using ONLY the information supplied. 4. Separate: OBSERVED FACT / DIRECT CUSTOMER STATEMENT / BEHAVIORAL EVIDENCE / MY INTERPRETATION / UNKNOWN. 5. For each recurring problem identify: who experiences it; when it happens; what they are trying to accomplish; current workaround; time, money, risk and opportunity consequences; evidence of existing spending; evidence of dissatisfaction. 6. Identify possible symptoms versus possible root causes. 7. List questions that still require research. Do not invent demand, customers, budgets or willingness to pay. PHASE 2 — Generate solution hypotheses only for problems supported by evidence. For each include: PROBLEM / AUDIENCE / EVIDENCE / CURRENT ALTERNATIVE / WHY IT MAY BE INSUFFICIENT / DESIRED OUTCOME / POSSIBLE SOLUTION TYPES / WHO MAY PAY / WHAT MUST BE VALIDATED / RISKS & ASSUMPTIONS. Do not claim the opportunity is profitable.

Build a Problem Research Database

DATE · SOURCE · AUDIENCE · OBSERVED PROBLEM · EXACT WORDING · CONTEXT · FREQUENCY · CURRENT WORKAROUND · TIME CONSEQUENCE · MONEY CONSEQUENCE · RISK · OPPORTUNITY COST · EXISTING SPEND · WHO EXPERIENCES IT · WHO DECIDES · WHO PAYS · CURRENT ALTERNATIVES · DISSATISFACTION · POSSIBLE ROOT CAUSE · EVIDENCE STRENGTH · FOLLOW-UP QUESTION · SOLUTION HYPOTHESIS · VALIDATION STATUS

Keep observation separate from interpretation. “Three customers asked where delivery was this week” is evidence. “Customers desperately need my tracking app” is an inference. That separation makes your research harder to fool.

The “100 Problems” Exercise

Use 100 observations as a research exercise, not a magic threshold. You might collect 20 conversations, 20 reviews, 20 online discussions, 20 workflow observations and 20 search/question patterns. Remove duplicates, group patterns, identify the audience, trace consequences, study current solutions, look for spending, interview, prioritize and validate.

100 RAW OBSERVATIONS → DEDUPLICATE → GROUP → AUDIENCE → CONSEQUENCES → CURRENT SOLUTIONS → SPEND → INTERVIEW → PRIORITIZE → VALIDATE

You may discover a strong problem with fewer observations. You may collect 500 weak observations and still have no viable opportunity.

THE GOAL IS NOT TO COLLECT 100 PROBLEMS. THE GOAL IS TO STOP GUESSING.

Kenya and Africa: Study Local Friction Without Assuming It Is Broken

Useful research areas can include M-PESA-related business workflows, WhatsApp ordering, delivery coordination, retail inventory, salons and barbers, events, church/community administration, chama administration, property communication, tourism, hospitality, freelancing, education and professional services. But a manual process is not automatically a bad process. A shop taking orders through WhatsApp may be perfectly satisfied.

Investigate volume, errors, time, cost, satisfaction, alternatives and ability to pay. When research contains personal customer data, apply data minimization and privacy safeguards. Kenya’s Office of the Data Protection Commissioner states principles including lawful, fair and transparent processing, purpose limitation and limiting data to what is necessary. Anonymize research where practical and avoid dumping private customer conversations into public AI tools.

LOCAL FRICTION CAN CREATE LOCAL OPPORTUNITY. BUT OBSERVE BEFORE YOU “SOLVE.”

What People May Pay For

People may allocate money or other resources to save time, reduce waste, support revenue-generating work, reduce risk, reduce effort, gain convenience, get clarity, make a decision, learn a task, avoid a mistake, organize complexity, coordinate people, access specialized knowledge, have work done for them or improve an experience. None of these labels guarantees demand. The value lives in the outcome for a specific person in a specific context.

Problems That May Not Be Good Opportunities

A problem can be weak when it happens extremely rarely, has trivial consequences, is already solved well for free, belongs to an audience you cannot reach economically, has no realistic budget, requires expertise you do not have, creates unacceptable legal or safety risk, is merely a symptom, depends on users changing behavior they have repeatedly refused to change, or costs more to solve than the problem is worth. Avoid opportunities that depend on fear, misinformation, exploitation or pretending to hold professional competence you do not have.

A GOOD ENTREPRENEURIAL DECISION IS SOMETIMES: DO NOT BUILD THIS.

From Real Problem to Practical Knowledge

Not every validated problem should become a digital product. Sometimes the right answer is software, a service, professional help, process redesign, a physical product, automation, training, policy change—or no new solution at all. VEZILL becomes relevant when the useful solution is practical knowledge that can be responsibly packaged for someone to apply.

This is consistent with identifying valuable knowledge you already have, turning what you know into a digital product, and turning a hobby into a digital product: usefulness comes before format. If the problem is better served by a service, package the freelance service around the specific problem and supported outcome. For more examples, see problems small businesses pay freelancers to solve and problems you can solve online.

REAL PROBLEM → KNOWLEDGE GAP → PRACTICAL KNOWLEDGE → PACKAGE → VEZILL → ACCESS → LEARN → APPLY

Amara’s Final Discovery

After several events, Amara stops writing “business ideas” at the top of her notebook. She starts recording observations. The same clusters appear: task ownership, vendor confirmation, payment tracking, guest communication, event-day responsibilities and final checks.

Her hypothesis becomes more precise: small event organizers often coordinate many responsibilities across chats, memory and scattered notes. She asks how often this creates errors, who normally organizes, what tools they already use, whether a central planner helps, whether free alternatives are enough and who would actually pay.

Only then does she sketch a Small Event Coordination Workbook. It is still a hypothesis. She tests it before polishing it.

AMARA STOPPED SEARCHING FOR BUSINESS IDEAS. SHE STARTED STUDYING HOW PEOPLE WORK.

The VEZILL Problem-to-Solution Engine

Use this as the final operating sequence. At every step, preserve the option to revise or drop the idea.

THE VEZILL PROBLEM-TO-SOLUTION ENGINEOBSERVE↓DOCUMENT↓PATTERN↓PROBLEM↓CONSEQUENCE↓BUYER↓VALUE EVIDENCE↓SOLUTION HYPOTHESIS↓VALIDATEPROBLEM FIRST. EVIDENCE SECOND. SOLUTION THIRD. PROBLEM FIRST. EVIDENCE SECOND. SOLUTION THIRD.

Frequently Asked Questions

How do I find problems people will pay me to solve?

Observe a specific audience, document repeated friction, trace consequences, study current workarounds and spending, identify the buyer, then validate a small solution. Do not treat a complaint or idea as proof of payment.

What types of problems are people willing to pay for?

Problems tied to valuable outcomes can attract spending: saving time, reducing waste or risk, improving convenience, organizing complexity, learning a task or getting work done. The outcome, audience, alternatives and budget matter more than the category label.

How do I know if a problem is worth solving?

Look at frequency, severity, consequences, urgency, existing spend, workarounds, dissatisfaction, audience accessibility, solvability, budget ownership and evidence quality. A strong pattern deserves testing, not automatic building.

Where can I find real customer problems?

Customer conversations, support logs, reviews, returns, sales calls, workflow observation, job posts, search behavior, community discussions and manual workarounds can all reveal hypotheses. Respect privacy and verify patterns.

Do customer complaints make good business ideas?

Sometimes they reveal friction, but complaints alone are not demand. Investigate how often the problem occurs, what customers do now, whether they switch or spend, and whether the complaint reflects a root cause you can responsibly address.

How do I validate that people will pay for a solution?

Use increasingly strong evidence: past purchases, current spend, paid pilots, deposits or actual purchases where appropriate. Hypothetical “yes” answers are weaker than behavior that requires real commitment.

What is the difference between a problem and a pain point?

“Pain point” is business shorthand for a difficulty or frustration. This article prefers a concrete problem statement that names the person, context, consequence and current alternative, because that is easier to research.

How do I find problems businesses will pay to solve?

Observe costly delays, repetitive administration, errors, customer-service friction, manual handoffs and outsourced work. Then identify who experiences the problem, who decides and who controls the budget.

Can Reddit and online communities help me find business problems?

Yes, as research inputs. Repeated discussions can reveal language and hypotheses, but online posts are not representative demand data by themselves. Cross-check them with interviews, behavior, spending and other evidence.

Can AI help me find problems people have?

AI is useful for clustering and organizing real observations. It should not invent customers, frequency, budgets, market size or willingness to pay. Feed it anonymized evidence and require it to separate facts from inference.

What should I ask during a customer problem interview?

Ask about the last time the problem happened, what the person tried, time and cost, current tools, who was involved, what happens if ignored, who decides, what they have paid for and what would make them switch.

How do I turn a validated problem into a product or service?

Define the desired outcome first, then choose the smallest responsible solution format that fits the problem. Test it with real users before expanding. If practical knowledge is the solution, a guide, checklist, template, spreadsheet or toolkit may fit; other problems need services or software.

The Best Business Idea May Begin as Something You Notice

Amara began with “What business should I start?” She ends with a better question: Where are people repeatedly struggling, and what evidence tells me that solving it matters?

Her notebook changes from BUSINESS IDEAS to OBSERVATIONS · PROBLEMS · CONSEQUENCES · WORKAROUNDS · SPENDING · PEOPLE · EVIDENCE · QUESTIONS.

THE BEST BUSINESS IDEA MAY NOT BEGIN AS AN IDEA. IT MAY BEGIN AS SOMETHING YOU NOTICE. OBSERVE → UNDERSTAND → VERIFY → SOLVE

Find a real problem. Package the knowledge that helps solve it.

When practical knowledge is the right solution, explore focused guides, templates, tools and other Quick Knowledge on VEZILL.

EXPLORE VEZILL →   ·   Browse VEZILL Products →

VEZILL — Practical Knowledge, Packaged for Action.