top of page

BUSINESS SYSTEMS AND CAPACITY PLANNING

Build service business systems before taking on more clients.

When each new client adds more questions, approvals, and late work to your week, demand is growing faster than delivery capacity. This guide helps you find the bottleneck, make one client journey repeatable, and decide how much more work you can responsibly accept.

Bring a delivery bottleneck to a BOSS Call. We will identify the process or capacity decision to address before you add more demand.

capacity-workflow-planning.png

START WITH THE PRESSURE POINT

Find the bottleneck

More clients will expose the work that only you can hold together.

A service business can be busy and still lack a dependable delivery system. The warning sign is not simply a full calendar. It is a client waiting because nobody owns the next action, a team member searching for the current instructions, or a founder reviewing routine work that should already meet a clear standard.

Business systems are the decisions, owners, instructions, tools, and review habits that make delivery consistent. The goal is not to automate every human interaction. It is to keep quality and client trust from depending on one person’s memory and availability.

Clients ask for status repeatedly

Inspect milestones, communication ownership, and the point where work waits.

Every handoff returns to the founder

Inspect decision rights, examples of acceptable work, and exception rules​

The calendar says yes but delivery says no

Count preparation, coordination, revision, and quality review alongside client meetings.

This guide begins when the service is selling and delivery needs a stronger structure. If the problem is getting suitable inquiries, begin with Client Acquisition. If the problem occurs before a prospect books, see Funnels and Follow-Up. Here we are working in Scale, the delivery and improvement part of Cherished Investments’ Business ABCs.

FOLLOW ONE REAL CLIENT

Map the delivery

Map the work from agreement to renewal.

Choose one common service, not every process in the company. Follow a recent client from signed agreement to the end of the engagement. At each handoff, write down the trigger, the owner, what the client receives, and how the next person knows the step is complete.

Agreement

Payment and scope trigger delivery.

​

Review

Quality and exceptions are checked.

​

Setup

Intake, files, and kickoff have an owner.

Close or renew

Results, next work, and offboarding are clear.

Delivery

Milestones and client updates are visible.

If the request sits in an inbox until the founder notices it, the issue is bigger than a missing reminder. Name who records the request, who checks whether it is within scope, who completes it, and which exceptions require the founder. Those decisions form the process that a reminder can support.

What happens when a client requests a revision?

BUILT ONLY WHAT THE WORK NEEDS

Build the system

Turn one fragile handoff into a repeatable system.

If the request sits in an inbox until the founder notices it, the issue is bigger than a missing reminder. Name who records the request, who checks whether it is within scope, who completes it, and which exceptions require the founder. Those decisions form the process that a reminder can support.

Name the next action and decision rights

Ownership

Give the ordinary step an owner and a completion signal. Set a boundary for when that person can decide and when the founder or specialist must step in. A task can be delegated with instructions; a workflow needs context across several tasks; a judgment call needs explicit authority.

Document the process someone else must run

Instructions

Write the trigger, owner, steps, tools, quality standard, common exception, and definition of done. Add one example of acceptable output. Test it with the person who will use it. If they need to ask you to interpret each step, the document is not ready to carry the work.

A handoff note should answer

What starts the work? Who owns it? Where is the current information? What does done look like? Which exceptions need another person?

PROTECT AND DELIVERY QUALITY

Calculate capacity before promising a start date.

Plan capacity

Available hours are not the same as hours on your calendar. Reserve time for sales, administration, leadership, and unexpected work. Then compare the delivery hours left with the work already committed and the hours a new client will require.

Planned working hours

Minus sales, administration, and a buffer

Available delivery hours

Minus current client commitments​

Remaining capacity

Compare with the new client’s weekly work

Use your own delivery history for estimates. Count meetings, preparation, messages, revisions, and quality checks, not only the hours you bill. A shortfall may call for a later start, narrower scope, a price or delivery-model change, clearer ownership, or more support.

The founder has inquiries. Can she take one more client?

SEE THE FULL CONVERSATIONS

Planned working hours

The proposed client needs six hours.

She is four hours short if she accepts the new engagement as is. Rather than add another tool, she traces the approval handoff. The project lead receives revision requests, checks scope against a written standard, and sends only exceptions to the founder. A monthly quality review catches problems without requiring her approval on every item.

​

In this hypothetical week, that reduces routine founder handoff time from four hours to one. Her current commitments become 21 delivery hours, leaving five. She is still one hour short of the six-hour promise. She offers a later start or adjusts the scope before signing. The system made the constraint visible; it did not make capacity appear from nowhere.

Review actual hours after the change. If turnaround time or quality declines, revisit the plan before adding more work.

worked example

STRATEGY AND SUPPORT

Bring your delivery bottleneck to a BOSS Call.

We can examine where work waits, what still depends on you, and whether your current hours support another client. Bring a recent client journey or rough workload numbers if you have them. We will identify the first operating decision to make.

Boss Support

QUESTIONS AND ANSWERS 

Business systems and capacity questions

Faqs
bottom of page