Give day 30 a job. By then, do you want to know who needs your service, whether anyone will pay your price, or how long one order takes to deliver? Pick one question. You can have a productive first month without launching a website or making a sale if you settle something that matters to your next decision.
A month on one index card: “By day 30 I want to know whether one paid editing job will fit into the six hours a week I have available.” Week one finds the customer; week two defines the job; week three measures the work; week four decides what to change. Those six hours are a limit in this example, not a target for another business.
Before day one: choose one outcome
Decide what you want to know or accomplish by the end of the month. Examples include identifying a specific customer group, testing whether people understand an offer, or completing one small paid project. Pick one primary outcome rather than trying to create a brand, publish everywhere, build a full product, and reach a revenue target at once.
Set boundaries for the month: how many hours you can give the project, what amount you can afford to spend, and what you will not take on yet. Make a short list of assumptions that need attention. Keep a note of anything that must be checked with a local authority or qualified professional before you sell or provide a service; this plan does not replace that check.
Week 1: understand the customer and the work
Write a one-sentence description of the customer, the problem, and the offer you are considering. Review the alternatives customers already use, including doing nothing. Talk with a few people who have recently faced the problem and ask what they did, what was difficult, and what they paid or gave up to solve it. Do not treat friendly praise as a commitment to buy.
At the end of the week, summarize what you learned and list the two biggest unanswered questions. If the intended customer or problem still sounds vague, narrow it before creating more materials. A smaller, clearer audience is easier to learn from than a broad claim that the offer suits everyone.
Week 2: define a small offer and a test
Describe the smallest version of the product or service that could answer one important question. State what is included, who it is for, the expected timing, and any limits. Estimate the direct cost and the time it will take to deliver. Use assumptions openly; do not make a detailed forecast from numbers you have not observed.
Choose a test that is honest about what exists today. You might show a sample, invite people to join a clearly described waitlist, or offer a limited pilot you can fulfill. If you collect contact details, explain how you will use them. Do not advertise a product as ready, take payment under unclear terms, or imply that a test result is proof of broad demand.
Week 3: run the test at a manageable scale
Reach a defined group through a channel they already use, then record what they do. Track a small number of measures tied to your question, such as qualified replies, requests for a quote, completed bookings, or the time and cost needed to deliver one order. Note the context, such as who saw the offer and what they were asked to do. A raw count without that context can be misleading.
Keep the scope within your time and spending limits. If the test requires a bigger build, more inventory, or an audience you cannot reach, pause and redesign it. If people misunderstand the offer, change the wording before assuming that the underlying idea has failed.
Week 4: review evidence and choose the next step
Compare the result with the question and stop rule you set at the beginning. Which assumptions gained support? Which remain unknown? What did it cost in money and hours? Decide whether to continue with one more test, revise one part of the offer, or stop. Document the reason, including evidence that did not match your expectation.
Use the final days to close open loops: respond to participants, deliver what you promised, record expenses, and list the next two actions. Leave some time unassigned for delays and learning. If you spend the whole month executing a rigid checklist, there may be no room to respond to what the test actually showed.
At each weekly check-in, note the hours available, hours actually used, and what is still owed to a customer. If the work runs long, cut the scope of the next offer rather than hiding unpaid hours from your calculation. For a broader overview of setting up, see Creating and Starting an Online Business.
Use a short weekly check-in
At the same time each week, review the goal, the evidence collected, spending and hours, blockers, and the next decision. Keep the notes brief. If a task no longer helps answer the main question, remove or defer it. If you did not finish, ask whether the task was too large or the plan depended on something outside your control; do not simply add more hours by default.
A first month is a learning period, not proof that the business will succeed or fail. If the evidence supports continuing, the broader path from choosing a customer and offer to making a first sale is covered in Creating and Starting an Online Business. Recheck any location-specific obligations before operating, and adjust the next month to the evidence you have rather than an arbitrary launch date.







