Stop Accepting Client Work Before You Check Delivery Capacity

Revenue can hide a delivery problem for a while

Small advisory firms are good at finding a way. The founder takes one more call. The account manager covers a supplier meeting. Somebody works late to rebuild the client update. The deadline gets met, barely, and everyone moves on.

That works until it does not. One more implementation starts. A supplier misses a milestone. Two client reviews land in the same week. The person who knows the account is already carrying four other promises.

The problem usually looks like a people shortage after it breaks. Before it breaks, it is a decision problem. The firm accepted work without seeing the delivery load it had already sold.

Capacity planning does not need to become a finance exercise with fake precision. A small firm needs enough evidence to answer one useful question: can we accept this work on the proposed terms without putting current client promises at risk?

Count commitments, not names on an org chart

Three people on the team does not equal three available people. One may own client escalations. Another may be waiting on five suppliers. The founder may have calendar space but still be the only person who can approve a recommendation or handle a difficult client conversation.

Start with the work that has already been promised. Pull active implementations, client reviews, renewal decisions, proposals that may convert, open escalations, and internal deadlines. For each item, record:

• The accountable owner
• The next commitment and its date
• The work required before that commitment
• Another person or supplier the work depends on
• The consequence if the date moves

Do not count a project as available capacity because it is "waiting on the supplier." Waiting creates follow-up, client communication, schedule risk, and usually more work when the answer arrives. A dependency still consumes attention.

Separate calendar time from decision capacity

A team member can have open hours and still lack the authority or context to move the work. This is where small firms fool themselves.

Delivery capacity has at least two limits. The first is execution time. Who can prepare the inventory, compare quotes, update the project, or organize the client review? The second is decision capacity. Who can approve the recommendation, negotiate a scope change, escalate a supplier, or reset a client expectation?

If every meaningful decision comes back to the founder, adding a coordinator may clear tasks without clearing the bottleneck. The firm needs explicit decision rights, not another place to assign work.

This is the next layer after delegating work without losing the client relationship. Delegation defines what another person can own. Capacity planning shows whether that ownership is working across the whole client portfolio.

Use four answers when new work arrives

Every opportunity does not need an immediate yes or no. Give the firm four honest options:

1. Accept. The owner, start date, required skill, decision authority, and supplier dependencies are clear. Current commitments remain defensible.
2. Delay. The work fits, but the proposed start date does not. Offer a date the team can support instead of quietly accepting a deadline it already expects to miss.
3. Reassign. Another person can own the work if context, authority, and client communication move with it. Naming a new owner without those things is calendar theater.
4. Renegotiate or decline. Reduce the scope, split the project into phases, use an outside specialist, or say no when the work does not fit the firm's capacity or operating model.

A vague "we will figure it out" is a fifth answer, but it is not a useful one. It transfers the decision from the sales conversation to the delivery crisis.

Put a capacity gate before the client promise

The best time to review capacity is before a proposal includes a start date or delivery commitment. By the time the client signs, your team may feel trapped by a promise nobody checked.

Add a short internal gate. The deal owner brings the proposed scope, target date, likely supplier path, client-side dependencies, and expected internal work. The delivery owner confirms who can take it and what must move. If the deal changes later, run the gate again.

This should take minutes for routine work. Complex projects deserve more thought. The point is not another approval meeting. The point is to make the tradeoff visible while the firm can still change the terms.

Connect the gate to your proposal decision brief. A recommendation is incomplete when the supplier and price make sense but your own delivery plan does not.

Review the next six weeks, not an imaginary perfect quarter

A long-range staffing model may help a larger firm. A small advisory team usually gets more value from a rolling six-week view.

Week one should be specific. You know the client calls, tasks, deadlines, and open issues. Weeks two through six will be less certain, so show ranges and assumptions. Include signed work, likely starts, major renewals, client reviews, and high-confidence proposals. Do not treat every pipeline opportunity as booked delivery.

Mark the weeks where one person, one approval, or one supplier carries too much of the plan. Those are concentration risks. Moving ten small tasks will not fix a week that still depends on one founder decision or one uncertain installation date.

Watch for early evidence that the plan is wrong

You do not need a utilization benchmark to know delivery is slipping. Your own operating records will tell you.

• Next actions keep moving without new external evidence
• Client updates are prepared at the last minute
• The same owner appears on most overdue work
• Supplier delays are not reflected in client dates
• Projects stay active because nobody has defined completion
• New opportunities receive dates before delivery owners review them

Bring these exceptions into the weekly advisor operating review. Do not turn that meeting into a tour of every task. Decide which promise needs a new owner, a new date, a supplier escalation, or a direct client conversation.

Tell the client early when the plan changes

Capacity planning will not prevent every miss. Suppliers change dates. Clients delay inputs. People get sick. The value is seeing the pressure soon enough to make a professional choice.

If a commitment is at risk, confirm what changed, what remains in your control, and which decision the client needs to make. Offer a revised date or scope with a named owner. Silence is not schedule management.

Clients can work with a reasonable constraint when you explain it early. They lose confidence when a date passes and the advisor starts reconstructing the story afterward.

Keep the capacity view connected to client work

A separate staffing spreadsheet gets stale because it is one more place to update. Capacity decisions should use the same client, project, task, activity, and pipeline records the team already touches.

Advisor OS gives technology advisory firms project visibility, task management with due dates, client and contact activity, and pipeline context in one system. That makes it easier to see who owns the work, which commitments are approaching, and where a new deal could collide with current delivery.

The software cannot tell you how much pressure your team should accept. That is your call. It can make the tradeoff harder to ignore.

Start with the next six weeks. List the client promises, owners, dependencies, and likely new work. Put every new commitment into accept, delay, reassign, or renegotiate. Then fix the first week where your plan depends on heroics.

If your workload still lives in private notes, inboxes, and memory, run the free Advisor OS agency scorecard. You may have a capacity problem, but the first fix is better operating visibility.