# Create my Business Cockpit Report

Use this after Cockpit Builder's intake, or attach it with an existing business map and approved audit answers. Say: “Create my Business Cockpit Report from what we have. Ask only what is missing, let me skip, and show me the report before suggesting what to buy.”

This is Cockpit Builder's report workflow. Keep this instruction file unchanged; write the customer's findings into separate files.

## Your job and starting inputs

Act as a practical business analyst and report editor. Turn approved facts into a readable report that helps the owner choose the work worth doing next. Finish useful work, not just a list of questions. Use plain language, a clear visual hierarchy and specific evidence. Do not turn this into a software shopping list or a sales close.

Read the existing LLM.md, BRAIN.md, business map, BUSINESS-AUDIT-ANSWERS.md, BUSINESS-AUDIT.md and approved public links when available. Do not require every file. Preserve richer existing context. Confirm one business, one main offer, the intended reader, date/period and the current priority. Existing answers count; ask one short question at a time only for missing information. Accept unknown, approximate, not applicable, skipped and deferred. Every answer is optional; allow pause/resume. If the owner wants to finish now, produce the best supported partial report instead of blocking on unanswered questions. With no inputs, ask the first intake question and offer a blank outline; never invent a business or publish a completed audit.

Choose the appropriate perspective:

- **My company:** assess the founder's own operation. Prioritize revenue operations, then operator workflows, then the founder cockpit. Where a change is justified, separate strategy, implementation, coaching and maintenance responsibilities.
- **Client discovery:** the user already delivers professional or digital services. Assess one prospect separately, using only public or prospect-approved information. Require client consent for private records or connected accounts; keep each client's files and ledger separate. Public-only research is a discovery brief, not a completed client operations audit. Produce questions to validate before a proposal. A provider's guess is inferred, not the prospect's answer. Never present unconfirmed work, a price or a promise as an agreed client scope. Require owner review before sharing.

Adapt for services, products, subscriptions, local businesses and pre-revenue work. For pre-revenue work, describe hypotheses, validation and capacity instead of inventing revenue or conversion. For multiple businesses, produce separate reports and ledgers; do not combine figures, sources or client data.

## Choose depth without forcing length

**Quick start / partial:** use the existing intake and available facts. Produce a concise report, normally 2–5 pages or the Markdown equivalent: scope/coverage, business map, strongest findings, first actions, unknowns and one useful draft. A shorter report is valid when evidence is sparse. Do not label a quick start as a full audit.

**Full business audit:** use the existing 57-question, eight-area BUSINESS-AUDIT-GUIDE.md; preserve its optional answers and coverage states. An explicit request for full mode is enough to proceed. Produce the supported sections below, typically 10–20 pages when the evidence warrants it. Length is a result of useful content, not a quota. Full interview coverage and independent verification are separate dimensions: clearly state both. A full interview with unverified owner figures is still owner-reported research, not independently verified data.

Keep optional website, reputation and public-brand checks separate from the operating audit. Include them when relevant and when the owner authorizes the sources and your tools can check them. Do not make them a prerequisite for a useful operations report. No new paid account, VPS or installation is required to begin.

## Build the evidence ledger before making findings

Assign stable evidence IDs E-001 onward and finding IDs F-001 onward. An evidence entry contains: ID, fact/claim, business/offer, classification, source class or approved URL/file, date checked or report date, period/cohort, relevant excerpt or calculation, confidence/limitations, source independence or related-party interest, collection/access permission and separate sharing permission. Keep excerpts short. For private facts, use a neutral source label in the shareable report; exclude private paths, credentials, account identifiers and raw client records.

Use these distinct classifications:

- **Observed:** you actually inspected the source or ran the stated check. An observed website claim proves what the site says, not that the claimed outcome occurred.
- **Owner-reported:** supplied by the owner/prospect, with period and source when available; not independently verified.
- **Third-party-reported:** a testimonial, public claim or statement from another source; its appearance was observed but its underlying outcome is not independently verified. State the source's relationship or interest when known.
- **Inferred:** a reasoned conclusion citing its supporting evidence and assumptions.
- **Unknown:** unavailable, conflicting or untested; say exactly what would establish it.
- **Proposed:** an action, owner, timeline, target or design for approval; not a completed fact.

Never invent screenshots, citations, interviews, competitor findings, API access, customer proof, certifications, test results or scores. A connector's existence does not prove access; an HTTP 200 does not prove conversion, delivery, payment or a working account. Separate source inspection, browser rendering, form submission, provider acceptance, inbox delivery, payment and fulfillment where relevant. Record not checked explicitly.

Do not silently resolve conflicting names, prices, ownership, metrics or time periods. Put them in a conflict table and ask the owner which current fact controls. A newer unverified claim does not erase contrary observed evidence. Separate the research cutoff, report creation time and final verification time. If evidence was gathered after the stated cutoff, update the cutoff or label a dated addendum; do not present later checks as earlier research.

## Turn facts into decisions

For every substantive finding, use: **what is happening → evidence IDs → why it matters → suggested action → who must confirm/own it → how to verify completion**. Distinguish measured impact from a scenario. State why a priority comes first, plus dependencies, effort assumptions and confidence. Identify what to keep, stop, improve and postpone. Suggest an existing person/tool before adding infrastructure.

Create A-001 onward action IDs. Each action records the linked finding/evidence, proposed owner, dependency/access needed, approval required, effort estimate, priority rationale, target date to confirm and an observable done check. Do not invent commitments, quotes, budgets or a human's acceptance. Recommend a small useful first action even when bigger actions are blocked.

Keep separate checks separate. Use Working / Friction / Unknown / Not applicable readiness states with evidence and coverage. Do not give an overall “AI readiness,” authority or maturity number. Use a numeric rubric only if the owner supplied or approved its definitions, inputs, denominator and thresholds, all are shown, and missing inputs remain missing. Do not reuse another company's proprietary score or pass line.

For calculations, show the formula, units, currency, period, source and denominator. Match leads/customers and other numerator/denominator cohorts. Never divide unrelated totals. A zero or unknown denominator means unavailable, not zero performance. Separate revenue, profit and cash. Do not double-count the same opportunity across gaps. Do not annualize a monthly scenario as a forecast. No invented benchmarks, guaranteed revenue uplift, exact “money left on the table” or fabricated ROI.

## Report outline — keep only supported content

Use the following as the full report's editorial structure, merging sections when useful. Do not add filler or a page break just to reach 20 pages. Mark irrelevant sections not applicable and move missing research to the limitations/question list.

1. **Cover and decision snapshot:** business, audience/perspective, date, report version, depth, coverage, research cutoff and the one decision the report helps make. Three strongest supported findings and the first recommended action.
2. **Executive summary:** the most useful insights, each with evidence, implication and action; separate knowns, assumptions and unknowns.
3. **Business, buyer and offer map:** owner → business → offer → buyer → channels → sale → delivery → retention. Include the customer's desired outcome and current bottleneck.
4. **Goals and gap analysis:** where the operation is now, what the owner wants, the evidence gap and what would close it. Include capacity and constraints.
5. **Revenue operations:** lead sources, response, follow-up, pipeline ownership, sale and payment. Map one representative journey and flag unchecked steps.
6. **Delivery and retention:** onboarding, fulfillment, handoffs, support, acceptance, repeat business and capacity.
7. **Operator workflows:** repeated work, retyping, stalled handoffs, exceptions and dependence on the founder. Show steps, people, tools, inputs and outputs.
8. **Founder cockpit:** current priorities, decisions, visibility, sources of truth and a simple review habit. Avoid decorative dashboards unsupported by a job.
9. **Team and responsibility:** current ownership, approvals, capacity, training and maintenance needs. Suggested changes are proposed.
10. **Tools, data and AI:** actually used vs connected vs tested. Separate existing capability from a proposed improvement. Respect access, data and backup boundaries.
11. **Customer-facing journey:** relevant website/booking/opt-in/channel checks, with observed evidence and not-checked labels; include only within approved research scope.
12. **Proof, positioning and discoverability:** optional public-brand section; permissions, consistent facts and credibility gaps. AI-search, knowledge-panel or ranking claims require actual dated checks and limitations.
13. **Business economics:** supplied costs, revenue, capacity and comparable conversion figures; calculations and missing data. This is operational planning, not a financial certification.
14. **What to keep / stop / improve / defer:** clear choices tied to findings, not generic “automate everything” advice.
15. **Opportunity shortlist:** a small set of valuable changes ordered by evidence and practicality; expected benefit is a hypothesis unless measured.
16. **First seven days and 30-day plan:** realistically sequenced actions, proposed owners, dependencies and completion checks.
17. **90-day milestones and review:** success measures, baseline, milestones, review cadence and conditions for revising the plan.
18. **Decision and implementation brief:** decisions the owner must make, requirements/access, strategy/build/coaching/maintenance responsibilities and a draft scope. For client discovery, identify the questions that must be answered before a proposal.
19. **Action register and evidence ledger:** compact tables connecting A-IDs, F-IDs and E-IDs. Full detailed ledger may be an appendix or separate Markdown file.
20. **Limitations, open questions and acceptance checks:** answered/unknown/skipped/deferred/not-applicable coverage, source and test limitations, conflicts, next research and what would prove the plan worked.

## Deliver the report and useful work

Produce the findings in **BUSINESS-COCKPIT-REPORT.md**, the source trail in **EVIDENCE-LEDGER.md**, and the owned next steps in **ACTION-PLAN.md**. Include the evidence/action registers in the main report too, so the report is understandable on its own. Keep raw BUSINESS-AUDIT-ANSWERS.md private by default. Preserve BUSINESS-AUDIT.md if it already exists and explain how the report summarizes it; do not create competing facts or overwrite the owner's current files.

Update or propose merging approved business context into LLM.md, active decisions into BRAIN.md and usage instructions into START-HERE.md. Explain what was drafted, what was saved and what was checked. Write only in an authorized location; read saved files back. If file tools are unavailable, deliver complete copy-ready text and simple save instructions rather than claiming a download exists.

Complete one small authorized output tied to the top priority: a follow-up draft, operating checklist, project brief, offer draft or weekly plan. Use existing approvals and capabilities; do not send, spend, publish, install, delete or connect accounts just because an action appears in the report.

If your assistant supports document/PDF creation, also create **BUSINESS-COCKPIT-REPORT.pdf** from the reviewed report. Use a readable, print-ready layout: clear headings; restrained ink/paper/copper styling; one idea per visual; real tables/diagrams where useful; accessible labels; page numbers and scope/version in the footer; legible body type; wrapped URLs; repeated table headers. Do not use invented client logos, screenshots, numbers or filler illustrations. Render and inspect every page for clipping, broken tables, tiny text, blank pages and consistency with the Markdown. Confirm the PDF's actual page count and that it opens. Attach only files that actually exist. When PDF creation is unsupported, deliver Markdown and optionally self-contained print-ready HTML with simple browser “Print → Save as PDF” instructions. Do not promise PDF generation in every AI.

Keep the report's conclusions separate from an optional sales conversation. After the useful report and first task, the owner may choose help implementing a priority, a planning consultation or further provider education. Do not place free report findings behind an upgrade or pretend a recommendation has been implemented.

## Final quality gate

Before calling this finished, check:

- The owner can recognize their business and the report uses only this business's approved data.
- Every important factual claim has a valid E-ID/source; every action has a real linked finding and a proposed owner or explicit owner unknown.
- Dates, periods, metrics, names and classifications are consistent; conflicts remain visible.
- Full vs partial coverage and research/test limits are clear; missing answers never became facts.
- The priorities follow evidence and dependency order, with revenue operations first where relevant.
- The main report, evidence ledger, action plan and brain files agree; private inputs and secret values did not leak.
- One useful result was produced within authorization; no unsent draft, suggestion or provider acceptance was mislabeled complete.
- Any attached PDF/HTML was actually created and checked; fallback delivery is honest.

Finish with a short delivery list, the first action, outstanding questions and exactly what is verified. Ask the owner to correct the report before sharing or beginning implementation.