What to Measure Before Your Business Has Much Data

Two people booked after seeing your offer. Was that two out of three qualified inquiries or two out of thirty? Keep the counts together. With little history, a record of who saw the offer and what they did next is more useful than a conversion rate on its own.

One editor’s weekly note (illustrative): Six inquiries, three from people who needed the short-report service I offer. Two of those three booked. Both jobs were delivered, but one took twice as long as quoted because the client sent a new draft halfway through.

What deserves attention first: finding more leads, changing the price, or clarifying what counts as a new draft? Two bookings cannot establish a dependable conversion rate. The extra revision, on the other hand, is a specific event the editor can ask about before quoting the next job.

Start with a decision, not a dashboard

Ask what you need to decide this week or month. Are you trying to learn whether the right people notice your offer, whether they take the next step, or whether you can deliver the work within the time and cost you expected? Choose measures that can change that decision. If a number will not affect what you do, you may not need to collect it yet.

Use a notebook or simple spreadsheet before buying an analytics tool. Write down what you count, the period, where the information came from, and any limits. Keep estimates separate from confirmed actions. This makes the numbers easier to interpret later and prevents a rough guess from becoming a business target by accident.

Track three parts of the work

Qualified interest: Count people who fit the intended audience and show a specific need, such as requesting details or asking for a quote. A page view or social reaction may show exposure, but it does not necessarily mean the visitor is a likely customer. Note how the person found you and what question they asked.

Next-step behavior: Record what happens after someone sees the offer. Depending on the business, that might be a completed booking, a request for a sample, or a decision to proceed after receiving a quote. Define the action before counting it. Do not combine casual inquiries with confirmed commitments if they mean different things.

Delivery effort: For each completed job or order, note the time and direct costs required to provide it, including follow-up and rework. This helps you see whether the offer can be delivered as described. A sale that takes far more work than expected may need a narrower scope even when the customer is satisfied.

Make the measures concrete

Imagine a solo editor offering a fixed-scope review of a short report. The editor could count requests from the intended customer group, the number of people who book after seeing the scope and price, and the hours needed to complete each review. Those measures answer different questions: Is the offer reaching relevant people? Do they understand enough to commit? Can the work be delivered within the planned time?

The editor should also record the period and what changed. If a new message or referral source brought in inquiries, note that. If the editor revised the scope, do not compare the new delivery time with earlier work as though nothing changed. A number without its conditions can tell the wrong story.

Keep definitions consistent. Decide whether a returning customer counts as a new inquiry, whether a quote request belongs in the qualified group, and when a job is considered complete. Write those rules beside the measure. Consistent definitions are more valuable than elaborate charts when only a few observations are available.

Be careful with small samples

Early counts are often small and uneven. One unusually large project, one referral, or a quiet week can shift a percentage dramatically. Show the raw count beside any rate: “2 of 5 requests booked” is more informative than a bare “40%.” Do not present a handful of observations as a stable conversion rate or a reliable estimate of next month’s sales.

Look for repeated behavior and useful explanations, not just movement in a chart. Ask what the people who did not proceed chose instead, and whether the same obstacle appeared more than once. Qualitative notes can help explain a count, but they should not be turned into unsupported claims about every customer. Different sources or customer types may behave differently, so preserve the distinctions that matter.

Review on a schedule

Pick a regular review date and ask three questions: What did we observe? What is still unknown? What decision follows? If the measure is not helping answer the original question, change it or stop tracking it. Add a new measure only when a new decision requires it, and keep a note when a definition changes so you do not compare unlike periods.

Useful measures are not the ones with the most impressive totals. They are the few observations that help you choose a realistic next test, improve delivery, or stop spending effort on an assumption that is not holding up. You can decide to gather more information before acting; that is also a useful result.

Keep customer information limited to what you need, store it appropriately, and avoid collecting sensitive details just because a tool makes them easy to gather. If you use an analytics service, check what it records and whether your privacy practices need to explain that collection. A measurement habit should be proportionate to the decision it supports.




A Weekly Cash-Flow Check-In for a Very Small Business

A client says they’ll pay next month. Your supplier wants payment on Friday. Even if the job was profitable, will there be enough money in the account on Friday morning? Put both dates next to your available balance. That’s the question a weekly cash-flow check should answer.

A practical example

You start Monday with $700 available. A customer owes you $900, so the week looks comfortable until you put the dates in order.

One week of expected cash movements (illustrative)
When Movement Projected balance
Monday Opening balance $700
Wednesday Supplier payment: $450 out $250
Thursday Rent: $400 out $150 short
Friday Customer payment expected: $900 in $750 if everything clears as planned

The $750 is the arithmetic end balance, not permission to spend it on Thursday. If the bank declines the rent payment, the rent is still due. And if the client pays late, the $900 never enters this week’s available cash. Contact the client to confirm timing and discuss any change with the party owed before the due date; don’t silently move a bill to make the sheet balance.

What to bring to the next check-in

Start with the balance you can actually use. Mark pending transactions so you neither miss them nor subtract them twice. Put each expected receipt and each bill on its likely date. For an uncertain payment, try the week without it. Your two most useful notes are the lowest projected balance and the first date it could happen.

Separate cash from profit

Cash and profit answer different questions. A sale may be recorded before the customer pays, while a cash payment for equipment may happen before that purchase is fully reflected as an expense. The U.S. Small Business Administration’s finance guidance discusses bookkeeping and cash-flow projections as part of managing business finances (SBA: Manage your finances). Use the records and accounting method appropriate to your business; a weekly cash check is not a replacement for financial statements or professional advice.

For a simple example, a consultant may finish work and send an invoice this week, but receive payment next month. The work may count as revenue in the records before cash arrives. Meanwhile, hosting and other bills may be due now. Tracking both the invoice and its expected payment date helps explain the timing without confusing a sale with available cash.

At the next review, replace estimates with actual dates. If the client regularly pays a week after the date on your sheet, change the next forecast. The point of keeping last week’s version is to spot that pattern before another rent payment comes due.

Use one consistent time for the review

Choose a day each week when you can review your bank activity and records without rushing. Use the same basic steps each time, and write down the date of the check. The goal is not to create a perfect forecast; it is to notice changes early enough to ask questions and make a plan.

Start with cash that is actually available, not sales you hope to make. Check posted transactions and any payments that are pending or uncleared. Keep business and personal records separate in your working view so that a balance does not hide money needed for another purpose.

List expected money in

Write down invoices, card settlements, customer payments, refunds, and other receipts you reasonably expect. For each item, note the amount, expected date, how certain it is, and what action remains. An unpaid invoice is not the same as cash in the bank. If a customer has not confirmed a payment date, mark the receipt as uncertain rather than counting it as guaranteed.

Follow up on overdue invoices using the terms you agreed to, and update the expected date when you learn more. For sales that vary, use a conservative estimate and label it as an estimate. Do not use a strong sales week as a reason to commit to recurring spending before you know whether the pattern is likely to continue.

List money out and due dates

Review rent, software, supplies, contractor invoices, debt payments, payroll, taxes, and other obligations that fall within the period you are tracking. Include one-time payments and annual or quarterly costs that are approaching; they can be missed if you only think month to month. Record the due date, amount, and whether the bill is already scheduled.

Sort items by date rather than only adding them into monthly totals. A business can expect to collect enough over a month and still face a cash gap if a large bill is due before customers pay. If amounts or due dates are unclear, check the invoice or agreement instead of guessing.

Look ahead and flag a shortfall

Put the starting balance, likely receipts, and planned payments in date order for the next few weeks. Carry the running balance forward after each item. A simple table can include date, description, money in, money out, certainty, and next action. The estimate does not need to predict every sale; it should make the timing of known obligations visible.

If a projected balance looks too low, identify the cause and the date. Confirm expected receipts, check for duplicate or unusual charges, and consider which discretionary costs can be delayed without creating a larger problem. Do not assume a payment will arrive early or that a supplier will extend a deadline. Contact the relevant party before a due date if you need to discuss options.




A Beginner-Friendly Break-Even Worksheet

Worked example: You charge $80 for a service that costs $30 to deliver. Each sale leaves $50 toward the month’s fixed costs. If those costs are $1,000, it takes 20 sales to cover them: $1,000 ÷ ($80 minus $30) = 20. At 19 sales you are $50 short. The twentieth covers the last $50; it is not $50 of profit.

Gather the numbers first

Choose one product or service and one time period, such as a month. Keep the units consistent. Write down the selling price per unit, the variable cost for each sale, and the fixed costs for that period. Variable costs change with the number of sales; fixed costs stay the same over the period you are analyzing, even if you make fewer sales.

Include costs that are easy to overlook: payment fees, packaging, delivery, materials, returns, and the time needed to fulfill an order. If you exclude your own labor, say so. The resulting break-even point will not show whether the business compensates you for that work. Avoid mixing a one-time startup purchase with monthly costs unless you state how you are treating it.

Use fixed costs ÷ (price per sale minus variable cost per sale) for a single product or service with positive contribution. If you can sell only whole units, round a fractional result up. For example, $1,010 divided by $50 is 20.2, so you need 21 sales. The SBA break-even resource provides more background.

Calculate contribution per sale

Subtract variable cost per unit from selling price per unit. The amount left is the contribution available to cover fixed costs. For example, if a service sells for $80 and its variable delivery costs are $30, the contribution is $50 per service. This does not mean $50 is profit; fixed expenses still need to be covered.

Then divide fixed costs for the period by contribution per unit. The SBA gives the break-even formula in units as fixed costs divided by selling price per unit minus variable cost per unit (SBA: Break-even point). In the example, with $1,000 in monthly fixed costs and $50 contribution per service, the result is 20 services for the month, before any costs omitted from the calculation.

Use a simple worksheet

  • Product or service and time period: ______
  • Price per unit: $______
  • Variable cost per unit: $______
  • Contribution per unit (price minus variable cost): $______
  • Fixed costs in the period: $______
  • Break-even units (fixed costs divided by contribution): ______

Check the result against capacity. Can you realistically deliver that many units in the chosen period? Can you reach enough customers? If the answer is no, the formula has not failed; it has shown that the assumptions need another look.

What if the result is zero or negative?

If price equals variable cost, each sale contributes nothing toward fixed costs. If variable cost is greater than price, each additional sale increases the shortfall under those assumptions. There is no positive sales volume that covers fixed costs until you change the price, reduce variable costs, change the offer, or reconsider the idea. Do not divide by zero or treat a negative contribution as a usable break-even number.

A zero or negative contribution is a prompt to investigate, not proof that a business can never work. Some costs may be misclassified, the offer may have several products, or a different service mix may change the result. Recalculate with clearly labeled assumptions rather than hiding the problem in an average.

Test a range instead of trusting one answer

Make a few versions of the worksheet with different prices, costs, or sales mixes. Label them as scenarios, not predictions. If a small change in the assumptions moves the break-even point sharply, that is a risk worth understanding before you spend. Compare the result with customer evidence and delivery capacity, then update the worksheet when actual costs become available.

For example, if variable delivery cost rises from $30 to $40 while price stays $80, contribution falls from $50 to $40. With $1,000 in fixed costs, the simple break-even estimate moves from 20 to 25 services. This is a sensitivity check, not a prediction that you will sell either quantity. It shows why measuring actual delivery costs matters.

The simple formula assumes one product or service and a consistent price and variable cost per unit. If you sell several items, calculate each one separately first; a blended break-even estimate depends on the sales mix, which may change. Do not hide that uncertainty in a single average.

Keep break-even separate from a financial plan

The break-even result says how many units cover the costs you included under those assumptions. It does not show whether customers will buy that quantity, whether you can deliver it, or whether cash will arrive before bills are due. It is also not a complete profit target if you have left out owner compensation, financing costs, taxes, or other relevant expenses. List exclusions beside the worksheet so a reader can see what the number does not include.

Use the result as a question for the next test: can you reach enough buyers, at this price, with these costs? If not, revisit the offer or assumptions instead of treating the calculated number as a sales goal. For a worked example focused on one digital product, see A Website Model That Makes Money. The SBA also offers broader startup-cost guidance; use a qualified bookkeeper or accountant when you need help deciding which costs belong in your own analysis.




How to Compare Your Offer with Alternatives Fairly

A customer comparing your service with a competitor may have a third option: do the job themselves. Include that option if it’s realistic. A useful comparison makes it easy to see who saves time, who saves money, and where each claim comes from, even if the reader doesn’t choose you.

A practical example

Imagine you run a print shop. You charge $48 for 50 booklets delivered on Friday. A nearby shop quotes $40 for the same print job, with pickup. Can you advertise that your service saves the customer money? Not from those two prices alone.

What the quotes actually tell you

Your quote costs $8 more and includes delivery. A customer already driving past the other shop may prefer pickup. Someone who cannot leave the event venue may gladly pay the difference. Neither choice makes one printer cheaper for everyone. If the buyer only needs guests to see a program, sending a digital copy is another real option; it does not supply printed booklets.

Before publishing a comparison, line up the quantity, page count, paper, finish, deadline, and any mandatory charges. Note when you checked each quote. If you know your own delivery time but not the competitor’s, write “not confirmed” rather than “slower.” Keep the quotes so you can explain the comparison and update it when a price changes.

A claim you could stand behind

“For this 50-booklet job, our quoted price is $48 including delivery. The other quote is $40 with pickup. Choose delivery if the trip is worth more than $8 to you.”

That wording identifies the job and leaves the value of the trip to the reader. In the U.S., the FTC policy on comparative advertising supports truthful, nondeceptive comparisons and calls for clarity about their basis. It does not turn this example into a general claim about either shop. Give the real buyer enough detail to choose the other offer when it suits them better.

Define the decision the reader is making

Start with the buyer’s situation. Which problem are they trying to solve, and what choices could they realistically make? Include more than named competitors: a customer may use an existing tool, do the work themselves, choose a different kind of service, or delay the decision. “Do nothing for now” can be a valid alternative when the cost or inconvenience of switching is greater than the benefit.

Keep the comparison narrow. Comparing every feature of every product can overwhelm the reader and make the page stale. Focus on the few criteria that could change the decision, such as total cost, time to use, required skill, support, or a specific capability.

Choose like-for-like criteria

Use the same criteria for each option. If you compare monthly price, include the same billing period and clarify whether fees, setup, shipping, or add-ons are included. If you compare service speed, define what “fast” means and use comparable conditions. Avoid pairing your strongest feature with a competitor’s weakest feature.

Ask what matters to the buyer rather than what makes your offer look best. A simple worksheet might include:

  • The customer’s must-have requirement.
  • The price and other costs to get the outcome.
  • What is included and what is not.
  • Time, effort, or expertise the customer must contribute.
  • Support, access, or terms that affect the experience.
  • The source and date for each fact.

Leave a criterion blank or label it “not confirmed” when you cannot verify it. A blank is more honest than a guess. When information is missing, ask the provider or omit that comparison rather than assuming the competitor does not offer a feature.

Use evidence you can explain

Prefer current, primary information: published prices, product documentation, service terms, or a direct demonstration under stated conditions. Record when you checked it because offers and terms can change. If you rely on a customer review or a third-party test, explain what it can and cannot show. Do not turn one user’s experience into a general claim about every buyer.

Comparisons in advertising should be clear and truthful. The Federal Trade Commission’s policy statement says truthful comparative advertising can help consumers, while clarity and substantiation matter (FTC: Comparative advertising policy). If you make a claim about a competitor’s product, keep the evidence for that specific claim and describe the conditions of the comparison.

Make the comparison easy to audit. Put the source and date beside each important figure, explain any test conditions, and keep factual specifications separate from your interpretation. If you use a score, explain the scale and why each criterion has that weight. A total score can create false precision when the inputs are estimates or when different buyers value different things.

Show trade-offs, including your own

Explain who each option may suit and where it may fall short. Your offer might cost more but include support; another option might be less expensive but require the customer to do more work. Say so plainly. If your offer is not the right fit for someone with a particular need, state that rather than pushing a sale.

Disclose relationships or incentives that could affect how readers interpret the comparison. If you receive compensation for a recommendation, say so clearly near the relevant links. Do not use words such as “best,” “cheapest,” or “guaranteed” unless you define the claim and can support it. A disclaimer at the end does not fix a misleading headline or an unfair table.




How to Run a Small, Low-Risk Test of a New Service

Interest is no longer the question: two clients want to try your report-editing service. What you don’t know is whether one review fits in a morning once you count correspondence, reading, and revisions. Here is a pilot invitation you could adapt.

“For this trial I’m taking two reports, each up to five pages. You’ll receive written comments and one follow-up call, not a rewritten report. I’ll confirm your price, delivery date, and cancellation terms before booking. Please send a sample you’re authorized to share so we can check that the report fits.”

That message sets the client’s expectations. Your own notes serve another purpose: record minutes spent on intake, reading, comments, and the call separately. If reading takes an hour but clarifying the assignment takes two, cutting the page limit may solve the wrong problem.

Choose one question for the pilot

Start with the uncertainty that requires real delivery to answer. Perhaps you need to learn how long a session takes, whether customers can follow the instructions, or which handoff causes confusion. Avoid trying to validate demand, price, marketing, staffing, and the full business model in one pilot. Decide what you want to observe and what would make you change the service.

If you are still deciding whether the idea is worth exploring at all, begin with a low-cost idea test instead. For a pilot, keep the service small enough that you can deliver it personally or with the resources you already have.

Set a clear scope and eligibility

Write down what the pilot includes and what it does not. Define who can take part, how many customers you can serve, when the service will happen, how long it will take, and what the customer needs to provide. For example, a plant-care visit might cover a short assessment and a written watering plan, but not ongoing maintenance or emergency plant replacement. Clear limits prevent a small test from quietly becoming a full service commitment.

Choose participants who resemble the intended customers and have the relevant need. Explain that this is a limited pilot and what you hope to learn. Do not describe experimental work as a polished, proven service. If participants pay, state the price, deliverables, timing, cancellation terms, and how you will handle a missed appointment or incomplete work before they agree.

Plan the work before recruiting

List the steps from first contact through follow-up. Include preparation, delivery, customer questions, and cleanup. Estimate the time and direct costs for each step, including travel, supplies, payment fees, and any outside help. Set a maximum amount of time and money for the pilot. If you cannot deliver it safely or responsibly within those limits, reduce the scope or wait until you can.

Prepare only the materials needed to run the test: a short description, a scheduling method, a checklist for consistent delivery, and a way to collect feedback. Do not build a full website, buy large amounts of equipment, or hire permanent help just to run a small pilot.

Deliver consistently and observe

Use the same core process with each participant so you can compare experiences. Keep a brief record of what was delivered, how long it took, what questions came up, and where the customer needed extra help. Note departures from the plan without hiding them; they may reveal a missing step or a service limit.

Prepare a short run sheet with the start and end of the service, the promised deliverable, and what to do if a common exception occurs. After each delivery, write down what actually happened while it is fresh. This helps distinguish a repeatable step from a one-time surprise and keeps the pilot from depending on memory alone.

Ask for feedback after the customer has had a chance to experience the service. Start with open questions: “What was most useful?” “Where did you have to stop and ask for help?” “What did you expect that was not included?” and “What would you do next time?” Avoid asking only whether the person liked it. A polite positive rating may not explain whether the service solved the problem or whether the customer would choose it again.

Review the result against the question

Compare what happened with the goal you wrote before recruiting. Did the service take the planned time? Did customers understand the scope? Could you deliver the promised result without unexpected work? Which parts were repeated problems, and which occurred only once? Separate direct observations from your explanation of them.

Consider the costs and capacity, not only customer reaction. If the pilot was popular but required twice the estimated hours, the service may need a narrower scope, a different price, or a simpler process. If customers were satisfied but did not use the key part, ask whether the service solves the right problem. A few participants can help you improve the process, but they cannot predict how a much larger audience will respond.

Choose whether to repeat, revise, or stop

Use the results to make one next decision. Repeat the pilot if it answered the first question and another small group could help you check a remaining assumption. Revise one part if the experience exposed a specific problem. Stop if the work cannot be delivered responsibly within your limits or if the service does not address a meaningful customer need.

Close the loop with participants: deliver what you promised, explain any next steps, and ask permission before using their comments publicly. Keep a short record of the test, costs, feedback, and decision.




Map the Customer Journey from Discovery to Repeat Purchase

A customer ordering a plant-care kit may leave the checkout page to find out whether the kit suits a shady apartment. Your sales report might show only an abandoned cart. A journey map gives you a place to record that detour, mark what you don’t yet know, and decide what to ask a customer.

A practical example

A customer ordering a plant-care kit may leave the checkout page to find out whether the kit suits a shady apartment. Your sales report might show only an abandoned cart. A journey map gives you a place to record that detour, mark what you don’t yet know, and decide what to ask a customer.

A map from the buyer’s side of the counter

These are illustrative entries, not findings about real customers. A useful map leaves room for “we don’t know.”

First order of a plant-care kit
Moment Evidence you might have Question still open
Discovery A buyer says a friend sent the product page. What did the friend say it would help with?
Choosing A visitor asks whether the kit suits a north-facing window. Could they find the light requirements before checkout?
First use A support email asks which packet to open first. Are the packet labels consistent with the instructions?
Reordering An existing customer asks for a refill rather than another kit. Is a refill available, and can they find it?

Don’t join four observations from different people into one supposedly typical buyer. Date each observation and keep the source with your working notes. Where you have only a theory, keep it in the question column.

Choose one improvement to test

After mapping the journey, pick the friction point that is important to customers and that you can reasonably change. Make the improvement specific: add a clear size guide to the product description, explain what happens after an order, or give staff a short response for a repeated question. Avoid redesigning every stage at once, because you will not know which change helped.

Decide what observation would indicate improvement. You might listen for fewer repeated questions about one detail, ask customers whether they found the instructions they needed, or compare the same step before and after a change. Use measures that fit the issue; do not treat a small change in a small sample as proof of a universal trend.

Keep the map alive

Customer behavior can change when products, channels, staff, or policies change. Date the map, note who contributed, and review it when you see a recurring problem or make a substantial change. Keep the working version simple enough that someone can update it after a conversation or support review.

A useful map is a tool for choosing the next improvement, not a promise that every customer follows one route. Start with one audience and one goal, make the uncertainties visible, and revisit the journey after you test a change.

Set a useful starting point

Choose one customer group and one goal for the map. A map for someone ordering a plant-care kit for the first time will differ from a map for a returning customer who needs a refill. Keep the scope narrow enough that you can describe real interactions rather than every possible path through the business.

Define where the map begins and ends. It might start when a person first notices a need and end after they have used the product and decided what to do next. Include the steps that happen before and after the sale; the checkout alone is not the whole journey.

Write the stages in the customer’s order

List the main stages in plain language. For a first-time online order, they could be: notice a problem, look for options, compare offers, place an order, receive and use it, and decide whether to contact support or buy again. The exact stages depend on the customer and the type of offer. Do not add a stage just because a marketing diagram usually includes it.

Under each stage, note what the customer does, where the interaction happens, what question they may have, and what could make the next step harder. For example, a reader comparing kits may want to know what is included and whether the instructions fit a beginner. If that information is missing, they may leave to search elsewhere or ask support. Record the observed behavior and the possible explanation separately.

A simple table is enough: stage, customer action, question, evidence, friction, and the person responsible for the next handoff. Make a separate map when a different customer group follows a meaningfully different path. Do not create dozens of hypothetical branches; include an alternate route only when you have evidence that it changes what the customer needs or what your team must do.

Use evidence instead of assumptions

Review actual customer questions, support conversations, order steps, feedback, and staff observations. Ask people to walk through a recent experience in their own words. Use notes that describe what happened: “The customer emailed to ask which pot size fits the kit” is more useful than “Customers are confused.” Protect private details when sharing examples and do not include personal information that the map does not need.

For each stage, label what is known, what is inferred, and what still needs checking. One complaint may reveal a problem worth investigating, but it does not automatically show that every customer has it. If you have analytics, use them to locate a point where people stop, then gather context to understand why. A drop-off alone does not explain the reason.