Generate Business Operational Plan

A strategy that lives in slide decks doesn't run the business. The work of running the business happens at a much smaller scale — the Monday standup, the customer onboarding checklist, the monthly financial review, the way a refund request moves through three people in 24 hours. When those mechanics are unclear or undocumented, the company runs on the founder's memory, and the founder becomes the bottleneck the business cannot scale past.

This prompt builds the operational layer that connects strategy to execution. It defines the core processes, assigns ownership, sets the metrics each function reports on, and lays out the meeting cadence that keeps the system calibrated. The result is the manual a new hire could read on day one to understand how the business actually works.

What It Does

Defines the core operating processes for each business function — sales, marketing, delivery, finance, support — with clear inputs, outputs, and ownership.
Establishes the KPI dashboard each function reports on weekly and monthly so performance is visible before it becomes a crisis.
Designs a meeting and review cadence that keeps the team aligned without descending into meeting overhead.

The Prompt

#CONTEXT:
I have a business strategy but no documented operational plan — most decisions live in my head, processes are inconsistent, and as we grow I am becoming the bottleneck. I want a complete operational plan that defines how each function runs day to day, who owns what, what gets measured, and which meetings keep the system on track. The output should be detailed enough that a new operations hire could read it and run the business.

#ROLE:
You are a chief operating officer with 15 years of experience scaling small businesses from founder-led chaos to systems-led growth. You understand that operational excellence is not bureaucracy — it is the smallest set of processes, metrics, and meetings that produces consistent output. You design lean systems that work for 5-person teams as well as 50-person ones, with explicit handoffs between functions and a measurement layer that catches problems early.

#RESPONSE GUIDELINES:
1. Start with a one-page operating model that names each function in the business, its purpose, and its main outputs.
2. For each function, document the 3–5 core processes with inputs, outputs, owner, frequency, and completion criteria.
3. Define a KPI dashboard for each function — 3–5 metrics with target ranges and a clear escalation rule when targets are missed.
4. Lay out a meeting cadence — daily, weekly, monthly, quarterly — with the purpose, attendees, and required inputs for each.
5. Identify the top 5 operational risks given my current setup and recommend specific mitigations.

#OPERATIONAL PLAN CRITERIA:
1. Every process has one named owner — accountability without a name decays to no accountability.
2. Every metric has a target range and an escalation rule. A metric without a threshold is a number, not a control.
3. Meetings are designed around decisions, not status. If a meeting could be replaced with a written update, it should be.
4. Processes scale on the team I have, not the team I might have in 18 months. Solve for the next 12 months of growth.
5. The plan must include a documentation and onboarding layer so processes survive personnel changes.

#INFORMATION ABOUT ME:
- My business and core offer: [BUSINESS]
- Current team size and roles: [TEAM]
- Revenue stage: [REVENUE_STAGE — e.g., pre-revenue, $50K MRR, $1M ARR]
- Biggest current operational pain: [PAIN]
- Tools I currently use: [TOOLS — e.g., HubSpot, Notion, QuickBooks, Slack]
- 12-month growth plan: [GROWTH_PLAN]

#RESPONSE FORMAT:
Operating Model:
- [Function 1]: [Purpose] | [Main outputs] | [Owner]
- [Function 2]: ...

Core Processes by Function:

[Function 1]:
- [Process name] — Trigger: [input] | Output: [deliverable] | Owner: [role] | Frequency: [cadence] | Completion: [definition of done]
- ...

[Function 2]:
- ...

KPI Dashboard:

[Function 1]:
- [Metric] — Target: [range] | Cadence: [reporting] | Escalation: [trigger and action]
- ...

Meeting Cadence:
- Daily: [meeting] — purpose, attendees, inputs, outputs
- Weekly: [meeting] — ...
- Monthly: [meeting] — ...
- Quarterly: [meeting] — ...

Top 5 Operational Risks and Mitigations:
1. [Risk] — [Mitigation]
2. ...

Documentation & Onboarding Plan:
- [Where processes are documented]
- [How a new hire is onboarded into the system]

How to Use

Be honest about your current team size — the plan should fit the people you actually have, not the hypothetical org chart you wish you had.
Name your biggest operational pain point. The plan calibrates around the bottleneck you're trying to solve, not generic best practices.
Implement the meeting cadence first. Cadence creates the surface area where the rest of the plan gets adopted; without it, written processes are ignored.
Roll out one function at a time. Trying to operationalize the entire business at once usually means none of it sticks.

Example Input

## Information about me

- My business: A boutique digital marketing agency offering SEO and content services to mid-market B2B SaaS clients
- Current team: 8 people — me (founder), 2 account managers, 3 SEO specialists, 1 content lead, 1 admin
- Revenue stage: $1.4M ARR, growing ~30% YoY
- Biggest pain: Inconsistent client experience — some accounts get great service, others slip through the cracks; I am constantly putting out fires
- Tools: HubSpot CRM, Notion docs, ClickUp project management, QuickBooks, Slack
- 12-month plan: Scale to $2.2M ARR, hire 1 more senior strategist and 2 specialists, productize a smaller-tier offering for early-stage SaaS

Tips

One owner per process — never two, never a team. Shared accountability is no accountability. If two roles need to coordinate, name one of them as the owner and the other as the contributor.
Set escalation rules before you need them. "If logo churn exceeds 6% in any 30-day window, the head of CS calls a review within 5 days" is an operational control. "Watch the churn rate" is not.
Kill any meeting that produces no decisions. Recurring meetings without a clear decision output are the easiest 10% of operational overhead to remove and will buy back hours of weekly capacity.
Document processes in the same place the work happens. If your team works in ClickUp, the SOP lives in ClickUp — not in a Notion doc no one opens. Friction kills documentation adoption faster than anything.
Re-run this prompt every 6 months. As headcount and revenue change, the right operational plan shifts. The plan that runs an 8-person agency will fail at 16, and vice versa.

What It Does

The Prompt

How to Use

Example Input

Tips

We use cookies