Define customers, value and the business model (The Small Business Operating Handbook)

A business model is a statement about how value reaches a customer and how the business retains enough value to remain viable. It must be specific enough to be tested. ‘Sell more’ is not a model; ‘provide a defined product to a reachable group at a price that covers delivery costs’ is a useful start.

Create a one-page operating brief

Write one sentence for each: customer group, problem or desire, offer, delivery method, acquisition channel, revenue mechanism, principal costs, operational constraint and near-term goal. Treat unclear parts as hypotheses, not facts. A new business may have limited evidence; acknowledging that is better than manufacturing certainty.

Separate buyer, user and payer where relevant. An engineering supplier may satisfy a technical user while purchasing approval belongs to another role. A customer may say they like a concept but have no budget or urgency. The useful signal is observable behaviour: paid orders, repeat requests, authorised trials and referrals.

The economics of an offer

For each offer record the selling price excluding any applicable GST, direct costs of delivering one sale, time required, expected returns and other costs that change with volume. Subtract variable cost from revenue to obtain contribution. Contribution must support fixed expenses, the owner’s required compensation where relevant, reinvestment and a margin for uncertainty.

Do not hide the owner’s labour. Sole-trader drawings are not ordinarily a wage expense in the same way as employee wages, but the owner’s time still has an economic cost. A model that ‘profits’ only because the owner works unpaid may not be scalable or attractive to a purchaser.

Customer evidence ladder

At the lowest level is an opinion. More useful is a detailed interview about a past purchase and its constraints. Stronger evidence is a request for quotation, a trial with clear evaluation criteria, a paid pilot, repeat purchases and reliable contribution margins. No single indicator removes all uncertainty.

Before expanding into stock, software subscriptions or staff, write down the claim the expenditure depends on. Example: ‘At least eight organisations will buy this service at $X within Y days.’ Decide in advance what result would mean continue, adjust or stop.

Offer design worksheet

A realistic seven-day test

Day 1: interview existing customers about actual needs. Day 2: draft one limited offer. Day 3: define cost and fulfilment. Day 4: invite a small eligible group. Day 5: observe objections and purchase intent. Day 6: follow up without pressure. Day 7: count responses, paid conversions and costs; decide whether more testing is justified. Seek consent and respect marketing and privacy requirements.

Interpretation

A poor result is information, not a verdict on the founder. Distinguish demand problems from distribution, pricing, credibility and timing problems. Avoid changing all elements of an offer at once, because the cause of an improvement will be impossible to understand.

KEVOS educational guidance. Assess legal, product and customer obligations independently.

Extended study: applying the method

Segment by buying situation rather than vague demographics

A useful customer segment shares a recognisable reason to purchase, a procurement process and a willingness or ability to pay. Two customers who look similar may buy for different reasons: one needs fast turnaround for an urgent repair, another needs predictable documentation for an annual contract. Interview them separately. Capture the trigger that starts a purchase, the alternative they currently use, the person authorised to decide, the delay that causes the most cost and the evidence they need to trust a new supplier. Resist the temptation to describe everyone as a potential customer. A narrow segment enables a clearer test, simpler fulfilment and measurable communication.

Define the complete unit of value

Before costing an offer, specify precisely what the customer receives. Is it a physical product, installation, support period, report or access licence? Include revision limits, delivery timeframe, acceptance criteria, exclusions, warranty handling and responsibility for customer-supplied information. Ambiguous scope turns quoted contribution into unpaid rework. Write a sample order confirmation and imagine how the customer might reasonably interpret every sentence. If a promised result depends on customer approvals or data, show that dependency. Unit economics mean little if the unit itself changes between sales. Once the deliverable is consistent, costs, price and satisfaction can be compared between orders.

Customer conversations without leading the witness

Ask about the customer’s last relevant purchase, not what they hypothetically might do in an ideal future. Useful prompts are ‘What prompted you to look for a solution?’, ‘Which options did you compare?’, ‘What delayed the decision?’, ‘What happened when the solution failed?’ and ‘Who signed off?’ Avoid asking whether your new concept sounds exciting; politeness often inflates positive responses. Record observations separately from interpretation. A statement such as ‘delivery was delayed by two weeks’ is evidence. A conclusion such as ‘all customers value speed above price’ is a hypothesis requiring more data. Seek permission before recording conversations and store notes safely.

Design experiments around falsifiable claims

An experiment should be capable of disappointing you. Write the hypothesis, sample, intervention, observation, minimum threshold and decision rule before starting. Example: ‘At least three of twelve eligible prospects will request a priced trial within fourteen days.’ The threshold is illustrative, not an industry benchmark. Pre-registering the rule protects against retrofitting a positive story to weak results. Track the denominator: three enquiries out of twelve approached means something different from three out of four hundred impressions. If a trial fails, check whether the audience saw a credible offer, whether objections were consistent and whether another controlled test is justified.

Connect price to delivery economics

A high quoted price does not ensure attractive contribution if the work is custom, scope changes frequently or payment is late. Cost direct materials, labour time valued appropriately, subcontractors, packaging, freight, payment fees and expected rework. Add a capacity charge where scarce equipment or expert attention limits throughput. Then compare customer willingness to pay with the economics required to keep delivering safely. Do not copy a competitor’s price without knowing differences in quality, inclusions, scale or sales channels. Price is both a market proposition and an operating constraint, and the two views must reconcile.

A disciplined opportunity decision

Use a small decision register with columns for customer evidence, margin estimate, upfront investment, operational complexity, payback uncertainty and next experiment. Rate risk qualitatively if numerical evidence is weak rather than inventing precision. A promising opportunity might justify a prototype but not a lease. A request from a single vocal customer may justify a paid custom order but not a permanent product line. State which assumptions must be proved before each irreversible commitment. Continue only when evidence improves the expected outcome; pause when critical conditions remain unknown; stop when the offer repeatedly fails economic or customer tests.

Workbook and scenario

Imagine a service provider offering a $1,500 fixed-scope package. Delivery uses $350 in subcontractor expenses and 12 hours of specialist work. If those hours are worth $60 each for economic evaluation, the direct economic cost is $1,070 before overhead and rework. Apparent contribution of $1,150 when only subcontractor costs are counted is misleading: economic contribution is $430 before overhead. Now consider a typical two-hour unpaid revision: another $120 in time reduces it to $310. The exercise is to write clear inclusions and revision boundaries, then identify the customer evidence that could justify the price.

Primary learning references

Australian Government business guidance — official starting point for planning and small-business operations.
Business cash-flow guide — public information on forecasting, records and financing.

Study note: Examples are teaching illustrations, not actual customer data or guaranteed commercial outcomes.

Implementation laboratory: offer validation and customer discovery

Define a realistic starting point

Before changing anything, create a baseline record dated at the beginning of the exercise. State what is currently happening, who owns the process, what happens when it fails, and what evidence is available. For this topic, give special attention to positive interview feedback without paid demand. A single recent incident is not necessarily a representative trend, so look for several examples where available. If the process is entirely new, say that there is no observed baseline and use a synthetic rehearsal rather than describing assumptions as history.

Write a one-sentence objective in the form: “Over the next four weeks we want to improve [measurable outcome] while maintaining [quality or safety requirement].” Avoid using a vague outcome such as working harder, being more professional or creating growth. A useful objective contains an observable difference and a control that prevents apparent efficiency from concealing new problems.

Identify the people and decision boundaries

Consider the different responsibilities of the buyer, product owner, operations lead and financial reviewer. In a microbusiness one individual may hold several roles, but those roles should still be conceptually separated. Identify who prepares the information, who checks it, who approves a change, who carries it out and who records the result. If outside advice is required, identify the point at which the process must pause for that advice. Avoid giving software or an AI assistant implicit authority to make legal, financial or employment commitments.

Prepare a short responsibility table with the columns Input owner, Process owner, Independent check, Final approver and Backup contact. For a sole trader, the independent check may be a periodic external professional review instead of a second employee. The objective is accountability, not artificial complexity.

Build a small evidence package

An evidence package should contain the current procedure, one or more real or simulated examples, relevant figures, the expected output and a list of known exceptions. Remove confidential personal information from teaching materials. For a real business, store operational evidence in an approved private location with access limited to the people who need it. Link each figure to its source instead of copying it manually between documents without a reference.

Separate observed facts from forecasts and estimates. An observed payment date is a fact; a future customer’s payment is an assumption, even when it is a reasonable one. A change in accounting classification or business circumstances may alter which facts are comparable. Mark missing information explicitly and assign responsibility for collecting it.

Work through an exception rather than only the easy case

Normal scenarios are useful for learning the steps; exceptions test the quality of the process. Imagine that positive interview feedback without paid demand occurs just before an important customer or statutory deadline. Which facts would you need immediately? Which decisions can be made under the existing authority? Which tasks could be paused safely? How would the customer, supplier, employee or adviser be informed where appropriate? What written record would be necessary to explain the response later?

Run the situation twice. First follow the present procedure. Then follow the improved procedure and compare clarity, elapsed time, error risk and confidence in the information. Note where the new approach merely moves work to another person. An effective improvement should not reduce one person’s workload by hiding costs or risk elsewhere.

Choose a review metric and define it precisely

The principal indicator for this exercise is qualified conversion to a paid pilot and contribution per order. State the numerator, denominator, measurement period and data source where applicable. Decide what level of movement would be meaningful before seeing the results. Pair a speed or output measure with at least one quality indicator. For example, a process that closes actions more quickly but increases uncorrected mistakes has not clearly improved.

Review results using a small table: Period, Baseline or target, Actual, Difference, Reason, Corrective action and Owner. Do not infer causation from a single good week. Demand, seasonality, staff absence or unusual orders can affect outcomes independently of the process change.

Put an approval gate before an irreversible action

The major decision boundary is changing price or committing inventory before evidence. Before crossing it, prepare a concise decision note: the available options, evidence, total cash exposure, dependencies, legal or customer obligations, reversibility, downside risk and the person authorised to approve. If information is missing, a smaller pilot may be preferable to a permanent commitment. Refusing to invent an uncertain input is a sign of a trustworthy process.

Agree a review date and an exit rule. An exit rule might limit an experiment to a fixed amount of money, a defined sample size or a certain number of weeks. The rule should be proportionate to the risk rather than copied from another business. Keep written approval evidence for consequential commitments and use specialist advice where required.

Complete a four-week practice cycle

First week: Describe the present method and collect baseline evidence. Do not redesign everything at once. Check whether the records can support qualified conversion to a paid pilot and contribution per order and choose one narrow intervention.

Second week: Create the new procedure, checklist or template. Test it on a simple example and on a difficult exception. Document each correction and identify whether missing inputs or ambiguous responsibility caused the problem.

Third week: Conduct a limited live pilot where appropriate and authorised. An example of a suitably narrow outcome for this topic is an offer with documented scope and a small paid trial. Measure time, quality and unintended consequences. Keep the ability to return to the prior process if the pilot fails.

Fourth week: Compare results, collect feedback from the people affected and write a decision: adopt, refine, retest or stop. Assign an owner and future review date. If no clear benefit appears, keep the evidence but do not claim success. The purpose of a pilot is to learn accurately, not to defend the original idea.

Reflection and transfer

Explain the principle to someone who has not read the chapter, without using jargon. Ask them to reproduce the calculation, review or process from your instructions. Any point requiring your verbal rescue is an opportunity to improve the documentation. Then consider where the same logic applies in another process: setting clear inputs, acknowledging uncertainty, naming decision rights, measuring outcomes and checking the effect on both money and people.

Completion evidence: a dated baseline, one-page procedure, exception test, recorded results and approved next action. These five records convert general business advice into a verifiable operating improvement.