50 questions a small business command center should answer
A useful command center begins with decisions, not charts. Select the questions that change action, identify the authoritative source, and define when an uncertain answer must stop for review.
How to use this library: choose five to ten questions that recur weekly. For each, name the source system, owner, refresh expectation, filters, and decision it supports. Do not connect a field merely because it is available.
Sales and pipeline
How many new leads arrived this week, and from which sources?Required data: lead created date and source. Authority: CRM.
Which leads have not received a first response?Required data: lead ID, created time, first activity. Authority: CRM activity log.
Which open opportunities have gone quiet?Required data: stage, last activity, agreed quiet threshold. Authority: CRM.
How much quoted work is open by salesperson, service, and stage?Required data: quote amount, owner, service, status. Authority: approved quoting system.
What is lead-to-quote and quote-to-booked conversion?Required data: stable lead, quote, and booking IDs with outcome dates. Authority: CRM plus quoting/scheduling sources.
Which products or services sold most in the selected period?Required data: item, amount, transaction date. Authority: accounting or approved sales ledger.
Which customer segments produce the highest sales?Required data: customer segment, sales amount, date. Authority: CRM segment plus accounting sales.
Which quotes expire soon or need a decision?Required data: expiration date, status, approval state. Authority: quoting system.
How does booked revenue compare with the same period last year?Required data: booking dates, values, comparison window. Authority: scheduling/booking source.
Which lost opportunities have a recorded reason?Required data: closed-lost status and reason. Authority: CRM.
Cash and profit
How much was invoiced, collected, and left outstanding?Required data: invoices, payments, balances, dates. Authority: accounting ledger.
Which invoices are overdue, by age and owner?Required data: due date, open balance, customer, owner. Authority: accounting ledger.
What does the P&L show for this range and basis?Required data: account totals, exact dates, cash/accrual basis. Authority: accounting P&L report.
How do actual income and expenses compare with budget?Required data: actual and budget amounts by account/period. Authority: accounting and approved budget source.
Which product or service lines generated sales?Required data: item-level sales and dates. Authority: accounting sales report.
Which direct costs can be tied reliably to those sales?Required data: documented cost mapping and transactions. Authority: accounting ledger plus approved mapping.
What completed work has not been invoiced?Required data: completed job IDs and invoice linkage. Authority: operating system plus accounting ledger.
Which credits, refunds, or write-offs need review?Required data: adjustment type, amount, status, approver. Authority: accounting ledger.
What cash obligations are due in 7, 30, and 60 days?Required data: approved bills, due dates, open balances. Authority: accounting accounts-payable report.
Which totals fail to reconcile to the approved report?Required data: displayed and source totals with identical filters. Authority: accounting source report.
Scheduling and capacity
What is booked today, this week, and next week?Required data: confirmed bookings, start/end, status. Authority: scheduling system.
Where is open capacity by team, skill, location, or equipment?Required data: availability rules, assignments, qualifications. Authority: scheduling and workforce sources.
Which appointments are unconfirmed or incomplete?Required data: confirmation and required-field states. Authority: scheduling system.
Where are double bookings or impossible travel windows?Required data: resource, time, location, travel rule. Authority: scheduling system plus approved rule.
Which jobs wait on parts, permits, access, or customer action?Required data: job status, blocker type, owner. Authority: work-order system.
Which work lacks an assigned qualified person?Required data: job requirement, assignment, qualification. Authority: scheduling/workforce systems.
What was rescheduled or canceled, and why?Required data: status history, timestamp, reason. Authority: scheduling audit log.
Which promised dates are at risk?Required data: promised date, current state, blocker rule. Authority: operating system.
How much booked work belongs to each service category?Required data: booking value, category, date. Authority: scheduling/booking source.
Which constraints repeatedly block new work?Required data: capacity exceptions and causes over time. Authority: scheduling exception log.
Customers and service
What is the complete timeline for this customer?Required data: stable customer crosswalk and dated events. Authority: each originating CRM, operating, and accounting source.
Which system owns the billing name and service address?Required data: field-level authority policy. Authority: accounting for billing; approved customer source for service address.
What did this customer buy, and when?Required data: customer ID, items, amounts, dates. Authority: accounting sales report.
What work, quotes, invoices, payments, and messages remain open?Required data: open states linked by stable IDs. Authority: each transactional source.
Which customers have repeated service issues?Required data: service cases, issue codes, dates. Authority: service/work-order system.
Which promised follow-ups have not happened?Required data: due follow-up and completed activity. Authority: CRM.
Which customer records are duplicated or ambiguous?Required data: source IDs and reviewed matching rules. Authority: identity crosswalk; sources remain unchanged.
Which contact preferences and consent requirements apply?Required data: channel preference, consent state, timestamp. Authority: approved consent/customer record.
Which high-value customers show declining activity?Required data: approved value definition and comparable activity periods. Authority: accounting plus CRM activity.
Who owns the next action for this customer?Required data: action, due date, assigned person. Authority: CRM or operating task system.
Exceptions and approvals
What needs a person’s approval now?Required data: pending item, type, approver, created time. Authority: workflow approval queue.
How long has each exception been waiting?Required data: exception created and resolved timestamps. Authority: workflow audit log.
What is the consequence if nobody acts today?Required data: approved severity and due rule. Authority: written operating policy.
Which workflow runs failed, stopped partially, or remain uncertain?Required data: run state, validation result, error. Authority: workflow execution log.
Which source connection is stale or unavailable?Required data: last successful refresh and expected frequency. Authority: integration monitor.
Which records violate a deterministic business rule?Required data: record, rule version, validation output. Authority: rules engine and source record.
Which proposed changes would write to a live system?Required data: destination, operation, before/after draft. Authority: workflow plan and destination source.
Who may approve each type of action?Required data: action type, role, current authorization. Authority: access-control policy.
What changed after approval, and who changed it?Required data: versioned before/after values, actor, time. Authority: immutable audit trail.
Which repeated exceptions signal a process or system-fit problem?Required data: categorized exceptions, frequency, consequence. Authority: workflow log plus reviewed classification.
Turn questions into a responsible specification
For every selected question, record: decision owner, authoritative source and field, identity key, allowed filters, refresh target, permission boundary, reconciliation rule, failure state, and next action. If one of those is unknown, label it rather than guessing.