What should a weekly opportunity report show? An executive decision memo, not another dashboard

Leadership receives plenty of numbers every Monday. Marketing sends form counts and cost per lead. Sales sends pipeline value and stage movement. Operations sends backlog and service SLAs. Each report is accurate within its silo and useless for the question that actually matters: of the demand we already attracted, how much became a measurable opportunity—and how much leaked before anyone could act? Weekly reporting fails when no single document connects source, first touch, follow-up rhythm, and outcome. Executives end up debating budget because the operating chain stays invisible. Customer acquisition loss measurement exists precisely because those silos hide early leakage; the weekly report is how leadership reads that chain without waiting for a quarterly post-mortem. The fix is not more dashboards—it is one memo with four blocks and three actions. Clinics, dealerships, and B2B service firms all fail the same way when phone, form, and follow-up data never meet in one narrative.

A second failure mode is vanity density. Reports that list thirty metrics train everyone to skim. Executives need contrast and trend, not exhaust. If last week and this week look identical except for a five percent form increase, the report wasted a meeting. A useful weekly opportunity report limits itself to decision-grade signals: volume of meaningful demand, on-time processing rate, channel-level delay, recurring loss themes, and explicit actions. Everything else belongs in an appendix or a monthly deep dive. When in doubt, cut a metric rather than add one. The test is simple: if removing a line would not change a decision this week, it does not belong on page one.

Reports also fail when they arrive without a shared definition of opportunity. A pricing inquiry, a same-day service request, and a high-ticket consultation are not the same class. Without a classification dictionary agreed by marketing, sales, and operations, weekly numbers mix noise with signal. Leadership cannot prioritize if every inbound touch counts equally. The report must state which intent classes it includes and exclude low-priority volume deliberately so the headline numbers mean something. That dictionary should change rarely; if categories shift every week, comparisons lie and teams learn to distrust the memo.

Finally, weekly reports become theater when they describe problems without owners. A paragraph about slow callbacks is not a report line item; it is a complaint. Executives tolerate one week of diagnosis. By week two they expect names, dates, and expected impact on on-time processing or outcome rate. The weekly opportunity report exists to close the loop between measurement and correction—the same loop customer acquisition loss analysis describes—not to rehearse that leakage exists. If the same bottleneck appears three weeks running with no action owner, the report itself has failed as a management instrument.

Block one is throughput of meaningful demand. State total inbound signals in the agreed opportunity classes for the week, then the percentage processed on time against your standard—first meaningful response within the SLA, assignment to a named owner, or callback completed, depending on channel. Show the prior week beside this week so leadership sees direction, not a snapshot. Include a single sentence on capacity: whether arrival volume exceeded staffed hours on any peak day. This block answers whether the business is keeping pace with demand it already paid to create. It replaces raw lead count as the opening headline because volume without processing rate is how acquisition loss hides in plain sight. Use the same opportunity dictionary as your acquisition loss model or the two reports will contradict each other in the same leadership meeting.

Block two is channel quality and delay. Break performance by phone, form, chat, marketplace, referral, and branded search landing paths—not to blame channels but to expose where high-intent demand waits. Include median and ninetieth percentile first-response time, not average alone. A channel can look healthy on volume while hiding peak-hour gaps that only appear when you slice by hour and day. Pair quantity with delay so executives see which paths need routing, staffing, or integration fixes before more spend flows there. One line on capture rate per channel belongs here too: what share of known arrivals created a timestamped record. Uncaptured demand is the fastest leak to fix once visible.

Block three is recurring themes: objections, misroutes, and silent drop-offs that appeared in more than one interaction sample during the week. These are strategic signals, not anecdote. If price timing, insurance acceptance, geographic coverage, or appointment availability surfaced repeatedly on calls and forms, product, pricing, or process may need adjustment—not another script tweak on the floor. Theme reporting connects frontline language to executive decisions. It also reveals acquisition loss that never reaches CRM because the conversation ended early or the form was never assigned. Sample ten interactions that illustrate the top theme and attach them as evidence; executives should not need to trust a label alone.

Block four is the action list: maximum three items, each with owner, due date, and expected impact on on-time processing or outcome rate. Without actions the report is a status email. With actions it becomes the agenda for a twenty-minute leadership review. Reducing opportunity loss is a measurement-and-correction loop, not a one-time software install. The same four-block structure should repeat weekly so data stays comparable and trends become credible. Language must stay executive: cost, risk, priority—not internal jargon. The goal is visibility and improvement, not blame. This mirrors the executive weekly section in customer acquisition loss measurement; here the focus is the standing cadence leadership uses to run that loop. If block four is empty two weeks in a row, stop sending the report until ownership is fixed.

Executive language means cost, risk, and priority—not jargon pulled from tooling. Translate delay into missed appointments, stalled quotes, emergency calls sent to voicemail, or marketplace messages answered next business day. Translate ownerless follow-up into revenue waiting without a named responsible party. Operators still need drill-down paths: shift-level delay for workforce decisions, capture gaps where signals never entered a system of record, and a linked sample of calls or forms that illustrate the theme block. The one-page memo stays clean; evidence sits one click away. If an executive asks how you know block two is true, the answer should take thirty seconds, not a new project.

Resist merging this report with financial close or marketing performance reviews. Opportunity reporting sits between demand creation and revenue outcome. Its cadence is weekly because routing, response, and follow-up problems move faster than monthly strategy cycles but slower than hourly alerts. Daily operational alerts can fire for missed SLAs; the weekly document summarizes whether those alerts represent noise or a structural leak. Monthly reviews then ask whether action items moved the on-time processing rate. Keeping cadences separate prevents the weekly memo from becoming a dumping ground for every function's favorite chart.

CRM exports alone cannot populate blocks one and two faithfully. Early signals—calls, forms, first-response timestamps—often live outside CRM until late funnel stages. The weekly report should pull from the same continuous chain acquisition loss measurement uses: source, touch, intent class, first action, follow-up state, outcome. Treat CRM as the outcome layer, not the only source. When leadership trusts the chain, debates shift from opinion to prioritized correction. If telephony and form data disagree with CRM counts, say so in block one; hidden disagreement erodes the report faster than a bad week of numbers.

Schedule one fixed slot—twenty to thirty minutes—with marketing, sales, and operations leads present. Walk the four blocks in order. Do not open channel dashboards unless block two flagged an anomaly. Ask for each action item: what changes for the customer if we complete this by the due date? If nobody can answer, the action is too vague. Close with confirmation of next week's owner for data assembly. Rotating authorship without a single accountable editor is how weekly reports lose format consistency. The meeting ends when action owners repeat their commitments aloud, not when everyone has had air time.

Track three trailing metrics across weeks: on-time processing rate, median first response on your highest-volume channel, and count of ownerless high-intent records older than forty-eight hours. When an action completes, note which metric it was meant to move and review movement four weeks later. Not every fix shows in seven days; the discipline prevents declaring victory on anecdote. If metrics flatline while actions multiply, the report has slid back into theater—narrow the action list until impact appears. Revisit the classification dictionary quarterly; do not rewrite it during a bad week.

The goal is visibility and improvement, not blame. When trust breaks, teams clean data before it reaches the memo and loss hides again. Frame the weekly opportunity report as shared operating intelligence: the business already invested to create demand, and this document shows whether internal capacity honors that investment. DAS Systems reads inbound opportunity as one flow from search and ads through call, form, follow-up, and close; this weekly format is how leadership keeps that flow legible without drowning in dashboards. Start with four blocks even if data is imperfect; imperfect visibility beats perfect silence.