On Day 1, you started thinking about the foundations a small business needs to protect itself. Today, the focus shifts to an earlier decision: deciding what your business should help with in the first place.
When you’re starting with $100, it’s tempting to begin with a product idea, a name, or a logo. But those are answers to a question you haven’t yet asked: What problem does someone need solved?
A clear problem gives you something specific to investigate. It can help you decide what to offer, who to speak with, and what not to spend your limited resources building. It doesn’t guarantee a business will work. It gives you a stronger starting point than guessing at a product and hoping people want it.
Start with the problem, not the product
A business idea often arrives as a proposed solution: “I should build an app,” “I could sell a course,” or “I’ll start an online store.”
Those ideas may be worth exploring, but they are not evidence that a customer has a problem. First, find out what people are trying to do, where they get stuck, and what they do about it now. The answers might point toward a service, a simple resource, a process improvement, a physical product, or no offer at all.
That distinction matters when money is tight. Building takes time and may involve costs, even for a small experiment. Learning about a problem can begin with observation and conversations. The first decision is not “What can I make?” but “Which problem is specific enough to understand and important enough for someone to address?”
Four clues that a problem may be worth investigating
A problem doesn’t have to be dramatic to matter. Look for several of these clues together rather than treating any one as proof.
1. It happens repeatedly
A recurring issue may be more important than an occasional annoyance, especially when the same person has to deal with it every week or whenever a predictable event occurs.
Ask: How often does it happen? What triggers it? Does the person have to solve it again and again?
Frequency alone is not enough. A task can happen daily and still be easy or unimportant. But repetition helps you understand how often the friction appears and whether it has a place in someone’s routine.
2. It creates meaningful friction
Pain can show up in many ways: wasted time, avoidable errors, stress, delays, missed opportunities, or difficulty completing a necessary task. Try to learn what the person experiences, not what you imagine they must be experiencing.
Instead of asking, “Would a faster version be useful?” ask, “Tell me about the last time you did this. What was difficult?” Concrete details are more useful than a general expression of interest.
3. It has a consequence
A problem may be more compelling when the person can describe what happens if it remains unresolved. The consequence might be extra work, a delayed customer response, repeated corrections, or a task that gets pushed aside.
Avoid inventing a dollar amount or assuming that a frustration translates into a budget. If money is part of the issue, ask how the person currently accounts for it and treat their answer as information to investigate, not as a guarantee that they will buy a solution.
4. People already do something about it
Pay attention to current behavior. Someone might use a spreadsheet, keep personal reminders, hire help, ask colleagues to handle part of a task, or rely on an awkward process they’ve assembled over time.
A workaround doesn’t prove that a new business will be viable, but it gives you something concrete to understand. Ask what they have tried, what they still do manually, and what remains difficult. Compare that evidence with compliments about a hypothetical idea. “That sounds cool” is encouragement; actual behavior can tell you more about the problem.
Must-have or nice-to-have?
A must-have problem is not necessarily an emergency. It’s a problem people have a reason to address: perhaps it interrupts an important task, recurs at a predictable time, or creates a consequence they want to avoid.
A nice-to-have can still be a worthwhile idea. It may make something more enjoyable or convenient. But it may be easier for someone to postpone, especially when other needs compete for their attention or resources. For a founder starting with $100, it can be useful to investigate problems with clearer urgency and existing effort before committing to a solution.
Try these questions:
- What does the person do now when this happens?
- How often does it come up?
- What makes it frustrating or difficult?
- What happens if they leave it as it is?
- Have they already spent time, effort, or money trying to address it?
- Can you reach and learn from people who experience it?
If the answers remain vague, that’s not a failure. It’s a signal to ask better questions or choose a narrower audience. Avoid trying to convince someone that a problem matters. Your job at this stage is to learn how they see it.
Write a simple problem statement
A short problem statement can keep your research focused. Use this template:
[Specific person or group] struggles to [task] when [situation or trigger]. They currently [workaround], which leads to [specific consequence].
For example, imagine a solo event photographer who describes difficulty sending consistent client follow-ups after a busy weekend. A first draft might be:
Solo event photographers struggle to follow up with new inquiries after a busy weekend. They currently rely on memory and scattered notes, which can make follow-up feel inconsistent and difficult to manage.
This is an illustrative example, not a real customer story or evidence of demand. It deliberately describes the problem without proposing an app, service, or automation. That keeps the question open: Is this a recurring problem? How do photographers handle it today? What does “difficult” mean to them? Does it matter enough for them to seek a different approach?
If your statement includes a solution (“They need an automated follow-up app”) rewrite it. You’re still investigating the problem, not choosing the product.
Ask about real experiences
When you speak with someone, ask about a recent example rather than a prediction. Questions like these can help:
- “When did this last happen?”
- “Can you walk me through what you did?”
- “What part took the most effort?”
- “How often does it come up?”
- “What happens if you don’t get to it?”
- “What have you tried so far?”
Listen without pitching your idea. If someone says they would use a product you haven’t built, that’s useful feedback, but it is not the same as observing how they handle the problem today. Keep notes on the person’s words, actions, and uncertainties. Look for patterns across conversations, while remembering that a handful of conversations is only an early indication, not proof that a market exists.
You can also learn from public customer discussions, reviews, and industry conversations. Treat them as clues, not a substitute for understanding your intended customers directly. The same complaint may have different causes for different people.
Keep your first step small
Choosing a problem does not mean you need to build a product right away. Once you’ve written a clear problem statement, you can explore what a useful response might look like. In Day 4, the course will connect this work to a practical next step: turning a skill you already have into a service and exploring it before building something bigger.
That sequence matters. First understand the problem. Then consider whether your existing skills can help address it. An early offer can be simple and delivered manually; it does not need to start as software or a fully developed brand. Keep any scope, cost, and commitments clear, and learn what is appropriate for your situation.
ACORP’s AI employees are one example of how AI can support business operations, but an AI system is not automatically the right answer to every problem. The useful question is always whether a specific approach fits the people, task, and circumstances you have learned about.
For more on the course’s educational scope, see the Course Terms of Use. You can also read a further perspective on identifying important customer problems; use it as one viewpoint, not a formula or promise.
Today’s Action
Choose one group of people you can reach without spending money. Write down five recurring tasks they have to complete. Ask at least one person about a recent time one of those tasks was frustrating: what happened, what they did, and what made it difficult.
Then write one solution-free problem statement using the template above. Mark anything you still need to verify with a question mark. Your goal today is not to prove that a business will work. It is to leave with a clearer problem to investigate.
This lesson is general educational information, not legal, tax, financial, or professional advice, and it is not a substitute for advice from a qualified professional. ACORP makes no promises or guarantees about income, profit, or any business result; results depend on your own decisions, effort, and circumstances. Examples are illustrative, not typical outcomes. You are responsible for your own business decisions. Learn more in our Course Terms of Use.