What an Entrepreneur Does and How to Start Well

Before day one: define the constraint

Begin with the runway and responsibility you actually have. Write down the hours and money you can risk, income you still need, caring or health constraints, and the date you will review the commitment. The Australian Government starting guide treats personal readiness, business definition and planning as separate steps for good reason: enthusiasm does not remove practical obligations.

Then write one sentence that can be disproved:

We believe [specific customer] experiences [specific problem] often enough to commit [money, time, access or behaviour] to [proposed outcome].

“Everyone needs this” cannot be tested. “Independent allied-health clinics with more than five practitioners lose at least three hours a week reconciling referrals” can be investigated.

Days 1–10: investigate the problem, not your pitch

Recruit people who have recently experienced the workflow. Ask about a specific occasion: what triggered it, what they did, what it cost, what they tried and who controls a purchase. Avoid explaining your solution until you understand the current behaviour.

Summarise repeated facts, contradictions and unknowns. Do not turn three similar conversations into a market statistic. The output of this phase is a narrower assumption and a list of people willing to continue—not proof of demand.

Days 11–30: test a commitment before a build

Choose the smallest test that exposes the riskiest assumption. That could be a paid diagnostic, manually delivered service, letter of intent, prototype review with the actual decision-maker, or a time-boxed pilot. Set the success signal before running it so the result cannot be rewritten afterwards.

Two illustrative experiment designs

These examples show the structure; they are not MLAI case-study results.

Days 31–60: deliver the outcome manually and measure it

A manual or partly manual service can expose missing permissions, edge cases, support work and adoption friction before software hides them. Define the baseline, target, test period, owner and failure condition. Record both the claimed outcome and the independently verified outcome.

For an AI workflow, this is also when to map the data, integrations, human approval points and recovery path. If the output affects people, money, access or reputation, decide who can challenge and override it. Do not put real personal or confidential information into an unapproved public AI tool.

A proposed weekly operating rhythm

This is a planning template, not a measurement of how successful founders spend their time:

• Monday: choose one decision and the evidence needed.
• Tuesday–Thursday: talk, sell, deliver and observe.
• Friday: reconcile cash, review evidence, record risks and make the continue/change/stop decision.

Protect time for customer work. A week filled entirely with tooling, branding and internal planning can feel productive while leaving the main assumption untouched.

Days 61–90: decide what becomes a business

By day 90, aim to answer four questions honestly:

1. Does a defined customer experience the problem with enough consequence and frequency?
2. Have customers made a meaningful commitment to the proposed outcome?
3. Can you deliver that outcome safely, repeatedly and within a viable cost envelope?
4. Do the founders still want to pursue it under the actual constraints?

“Stop” is a valid evidence-based decision. “Change” should specify which assumption changed. “Continue” should name the next risk rather than simply authorise more building.

Australian setup: use decision gates, not a generic checklist

Formal steps depend on what you are doing. The official guide to starting a business covers readiness, structure, planning, registration, finances, customers, hiring and protection. Use it as the source of truth, then get legal, accounting or other professional advice where the choice depends on your circumstances.

What to record each month

Keep one evidence trail rather than rebuilding the story for each investor, adviser or teammate:

• customer problem and segment changes;
• experiments, pre-set signals, results and decisions;
• revenue, cash, runway and material commitments;
• product usage and verified customer outcomes;
• risks, incidents, assumptions and help needed; and
• the next milestone and accountable owner.

This is the foundation for a useful company plan and stakeholder update. For a deeper customer-acquisition sequence, continue with how to get your first customers.