Answer
What does a good week look like in a service business?
Every enquiry answered, every commitment met, and one thing done that only matters next quarter.
Every enquiry answered within your stated window, every commitment met or renegotiated in advance, and one piece of work done that pays off later. Revenue is a monthly measure and cannot describe a week.
Weekly performance in a service business is usually assessed by feel — busy, quiet, difficult — or by revenue, which arrives too late and describes decisions taken weeks earlier. A more useful definition is available and it is built from what did not fail, because the failures in this kind of business are silent and the successes are visible.
The first component is that every enquiry received a response within the window the business says it works to. Not every enquiry converted, which depends on things outside the week, but every one was answered. That is the single measure most predictive of the following month, it is entirely within the business's control, and it is the one most likely to have failed without anyone noticing.
The second is that every commitment was either met or renegotiated in advance. A promised callback that happened, a quote sent on the day it was promised, a job completed when it was said it would be, or a customer told before the date that it had moved. The renegotiated case counts as success — what fails is the commitment that passed silently, because that is the one the customer experiences as being let down.
The third is one piece of work that produces nothing this week. Something written, a relationship maintained, a system improved, a process written down, a measurement started. Weeks composed entirely of delivery feel productive and leave the business exactly where it started, and the absence of this is why businesses that are always busy do not compound. One item, done, is enough — the discipline is that it happens at all rather than its size.
What is deliberately not on the list is revenue, hours worked, or jobs completed. Revenue reflects work sold weeks ago and cannot be corrected within a week. Hours worked measures effort rather than result and rewards the wrong thing. Jobs completed depends on what was scheduled rather than on how the week was run. All three are worth knowing and none describes whether the week went well.
The value of a definition like this is that it can be checked in a few minutes on a Friday and acted on the following Monday. A week where enquiries went unanswered is a week with a specific fixable cause. A week where commitments slipped points at capacity or at scheduling. A run of weeks with no compounding work explains why the business feels stuck despite being busy. None of those is visible in a revenue figure, and all of them are actionable while the week is still recent.
A good week is one where nothing was silently dropped, which is a lower bar than most businesses set and a higher one than most clear.
Answer Production Engine, Context Theory
Related questions
Is this not too easy a standard?
It is a lower bar than most businesses set themselves and a higher one than most actually clear, which is the point. Businesses routinely aim at growth targets while enquiries go unanswered and commitments slip, and the second set of failures is what prevents the first target. Clearing the basics consistently produces the growth that the target was asking for.
How do we check these without a system?
Three counts on a Friday: enquiries received against enquiries answered, commitments made against commitments met or renegotiated, and whether the compounding item happened. That is a few minutes with a notebook, and the discipline of counting reveals more in the first month than any dashboard does, because it forces the enquiries to be counted at all.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
| Teams responding to an inbound lead within 5 minutes | 7% | Category-wide |
| Average B2B first-response time | 42 hrs | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · hours · 1.25M inbound leads across 2,241 US firms · verified
2026 speed-to-lead benchmark · range ~5% FinTech to ~15% RevOps · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Workflow | Failures in a service business are silent and successes are visible, so a weekly definition built from what did not fail is more informative than one built from what was delivered. | The business's own week, compared for which of its problems generated a record and which did not. |
| Workflow | Whether every enquiry received a response within the stated window is the weekly measure most predictive of the following month and the one most likely to have failed unnoticed. | Weekly enquiry response completeness against the following month's booked work. |
| Workflow | A commitment renegotiated in advance counts as success while one that passed silently does not, because the customer experiences only the second as being let down. | Customer complaints, classified by whether the underlying commitment was renegotiated before it lapsed. |
| Procurement | Weeks composed entirely of delivery leave the business where it started, so a single item of compounding work per week is what distinguishes a busy business from one that is progressing. | The business's own record of compounding work completed over a quarter against its delivery volume. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one