← All field notes

Money · PRACTICAL FIELD NOTE

The profitable sale that quietly steals your whole afternoon

A candid, practical field note for small-business owners about the profitable sale that quietly steals your whole afternoon, with a clear next step.

A repair-shop cat compares a small coin pile with the hidden hours behind a profitable-looking job.

An invoice can make a sale look worthwhile while the afternoon tells another story. Work may extend beyond delivery: explaining the offer, setup, questions, and fixes. Yet those hours are not automatically waste. Hands-on guidance can build trust and help customers get the result they paid for; repeated confusion or preventable fixes may instead point to friction in the offer or process. The useful question is not whether a sale took extra time, but what that time did. Count the whole job before deciding whether to change its price, scope, or process.

What to know

Consider a fictional studio that sells a custom package for $600. The owner counts three hours making it and concludes the sale earned $200 per working hour. But suppose setup took one hour, customer questions took another hour and a half, and correcting a preventable mistake took half an hour. The six hours total reduce the revenue to $100 per hour before expenses, taxes, or other unpaid work. These figures are illustrative, not a benchmark: the point is how easily a delivery-only estimate can mislead.

For your next few similar sales, record time spent on delivery, setup, support, and rework separately. Compare the total with what the sale brought in, then look for a pattern. If support dominates, clarify what is included; if setup repeats, standardize it; if fixes recur, investigate the cause before simply raising the price.

Put it into practice

Count the whole sale, not just the delivery

Reconstruct one demanding recent sale from first contact through follow-up. Include qualifying the request, preparing a proposal, gathering materials, setup, questions, changes, and corrections. Looking only at delivery time can hide the labor around it.

Divide revenue by total work hours for a rough revenue-per-hour figure, then subtract direct costs to see what remains before overhead, taxes, and other expenses. This is not profit; it is a quick check on whether apparent efficiency depends on uncounted work. For each task, ask whether it delivers promised value, protects the result, or compensates for a process problem.

Separate service from friction

Not every extra hour is a problem. An onboarding call may help a customer use what they bought or make a complex service feel worthwhile. Repeated explanations of basic requirements, by contrast, may point to an unclear offer. The distinction is whether the work supports the promised result or repeatedly compensates for avoidable confusion.

Imagine a fictional design studio whose customers often ask questions after buying a package. If the questions concern important creative choices, the owner might keep a scheduled consultation as part of the offer. If they concern deadlines or file formats, a short welcome guide may help clarify expectations. Either way, check whether customers still get the help they need and whether the nature or amount of follow-up changes.

Choose a fix that matches the cause

If setup repeats, standardize only genuinely similar steps. A checklist or reusable template may improve consistency, but forcing a custom job through a generic process could create more rework. After trying a change, check both the time saved and whether errors or confusion increased.

If support consumes more time than expected, make its boundaries visible before purchase: what is included, how customers can ask for help, and what falls outside the package. A defined support period or separately priced session may fit some businesses. Consider whether the boundary is clear to customers and whether work simply shifts to another channel, such as after-hours messages.

If corrections recur, identify their source before treating a higher price as the only solution. Customer inputs, handoffs, rushed reviews, or an open-ended promise may contribute. Addressing a removable cause may protect both the customer experience and your time. If it cannot reasonably be removed, consider pricing for the risk or narrowing the promise.

Run a small, reversible test

Try one change on the next three to five comparable sales, or a small batch that suits your sales volume. For example, add an intake checklist or define one revision round, then compare the results with your recent experience. Consider customer responses and any new work the change creates, not just hours saved.

One unusual customer or quiet week is not a verdict. If a change saves time but creates confusion, revise it rather than removing needed support. If the sale still takes more effort than its return justifies, consider adjusting the price, narrowing the offer, or declining that work. Choose based on the cause you found, not on delivery time alone.