Consulting scope capacity: price the work the team can actually deliver

Translate expertise into a bounded service

A consulting offer becomes operable when it names the result, deliverables, acceptance evidence, schedule, client inputs, exclusions, and change path. “Strategic support” is not enough to schedule or price. A bounded offer might include one diagnostic, two workshops, a recommendation memo, and one revision round, with named dates and required access to data and stakeholders.

The U.S. Federal Acquisition Regulation's performance-work-statement section is a procurement-specific example, not a universal rule. It calls for required results in clear, specific, objective terms and measurable performance standards, along with relevant scope, period, place, objectives, and constraints. A small publisher can borrow that discipline while using an agreement appropriate to its own client and jurisdiction.

• Define what the client receives and what counts as acceptance.
• Name inputs and decision deadlines the client must supply.
• List exclusions and route new work through a written change decision.

Build the delivery map before the price

Estimate work by role and phase, including sales handoff, preparation, meetings, analysis, production, revision, administration, and closeout. Add direct cash costs and a contingency for known uncertainty. Then place the hours on the actual calendar. Ninety hours in a month is different from ninety hours spread across a quarter, especially when editorial deadlines are fixed.

Make the change cost visible

The following example is hypothetical. A fixed-price project is $9,000. Planned delivery is 90 hours valued internally at $60 per hour, or $5,400, plus $600 of direct cash costs. Planned operating contribution is $3,000: $9,000 − $5,400 − $600. These internal labor values are planning inputs, not employee pay claims or accounting classifications.

The client requests a new analysis requiring 18 hours. At the same internal value, that adds $1,080 of delivery cost. If absorbed at the same price, contribution falls to $1,920. The publisher can price a change, exchange it for an existing deliverable, move the date, or decline it. “Small request” should not be a scope category.

Protect portfolio capacity

Create a weekly capacity view by person or role: total workable hours, fixed editorial and operating commitments, already-sold consulting hours, contingency, and genuinely available hours. Do not count the same hour in a newsroom plan and a client plan. When a dependency slips, reforecast the calendar instead of assuming the work will compress harmlessly.

Keep a small buffer for editorial incidents, illness, and client rescheduling. A buffer is capacity withheld from sale, so show it explicitly. If several projects depend on the same editor, designer, or analyst, test that shared role rather than trusting the total team-hour number. The bottleneck role sets the feasible schedule.

At closeout, compare planned and actual hours by phase, revision count, client delays, cash costs, and acceptance cycle. Keep the completed-project data separate from the next estimate so the reason for a price change is visible. A profitable engagement can still be strategically poor if it repeatedly displaces the publication's core work. The decision is therefore both unit economics and opportunity cost: what the project contributes, what capacity it consumes, and which committed work loses that capacity.