The difference between a sale amount and credit cost leaves out the work needed to help the customer. Record support time in sensible categories, then use a stated internal hourly-cost assumption if you want a cost estimate. The result is a planning calculation. It should not be presented as an audited profit figure or a guarantee of what the next customer will require.
Record the work that belongs to the order
Initial installation help, activation questions and later playback support can take different amounts of time. Keep them separate so one unusually complex setup does not disappear inside an average. Record elapsed handling time rather than the whole period a chat remained open. Waiting overnight for a customer response is different from spending an hour actively investigating a device problem.
State the cost assumption
Multiplying time by an hourly amount is useful only when the amount is labelled. It may represent staff cost, an internal planning value or the owner’s estimate of their own time. Those are different measures. Do not call the result a payroll expense if it is only an assumption. Include other actual costs separately so the same amount is not counted twice in the order calculation.
Read the pattern without judging the customer
A short series of orders can reveal repeated setup questions or unclear instructions. It does not establish a permanent support cost for every device or person. Look for improvements such as a clearer installation link or a better activation message. Keep the time record tied to task categories and order references, with minimal personal information and no customer credentials.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
Twenty minutes at an internal planning rate of$12 per hour represents$4 of time. An$8 gross difference after credit cost would leave$4 before other costs in this illustration. Neither figure establishes net profit.
