Offer boundary
What is included, what is excluded, and where does custom work enter?
Field Note
Pricing is not always the bottleneck
Pricing can be a real issue. It can also be downstream of scope confusion, weak qualification, delivery drag, or unclear offer boundaries.
Changing price can be necessary. It can also ask price to compensate for operating drag the business has not inspected yet. The fix may be right. The sequence may be wrong.
Visible symptom
The work feels heavier than the price supports.
Margin feels tight. Clients ask for extras. Sales calls feel custom. Delivery expands after the sale. The founder thinks price is too low because the business keeps absorbing work that was not cleanly bounded.
That can be a pricing issue. The offer may be underpriced, too broad, or poorly packaged. But pricing pressure can also sit downstream of how the business qualifies, scopes, hands off, and controls changes after the sale.
Fix founders usually consider
Raise price, repackage, or rewrite the offer.
The usual fix is to increase rates, create tiers, tighten the proposal, reframe the offer, or shift to a higher-value package. Those moves can be useful when the offer boundary and delivery model are already clear enough to support a pricing decision.
But price is often asked to solve more than price. It may be absorbing unclear scope, weak qualification, inconsistent sales promises, delivery rework, custom requests, unclear change rules, or clients who should have been routed differently before the sale.
Sequence risk
A price change can hide the operating surface that created the pressure.
If scope expands after sale, a higher price may not fix the expansion rule. If sales calls stay custom, packaging may still be hard to enforce. If qualification is weak, the business may keep accepting work that creates delivery strain. If the change-request path is unclear, client extras can continue to appear even after price changes.
The risk is not that pricing work is wrong. The risk is changing price before inspecting what price is being asked to absorb. The sequence should separate true pricing pressure from scope, qualification, handoff, and delivery drag.
Fictional example
A price-increase request points to scope creep.
Fictional example: A founder wants to raise prices because delivery feels too heavy. Projects start within a quoted scope, then expand through extra requests, unclear revision expectations, and client questions that were not handled before kickoff. The founder believes higher pricing will make the work feel more balanced.
In this fictional sample review, price may need review. But the immediate pressure is scope creep after sale and unclear rules for what is included. The business does not have a visible change-request rule, and delivery receives work with fuzzy boundaries. Raising price before inspecting those boundaries could leave the same operating pattern in place.
What to inspect first
Before changing price, inspect what price is absorbing.
Qualification
Which clients or projects fit the offer, and which ones create predictable delivery drag?
Scope handoff
What expectations move from sales into delivery, and where do they become vague?
Change-request rule
What happens when the client asks for something outside the agreed scope?
Delivery load by client type
Which types of work expand, stall, or require extra founder involvement?
Price compensation
What is pricing being asked to compensate for: value, complexity, uncertainty, rework, or weak boundaries?
How a Bottleneck Audit maps it
The audit maps pricing pressure against scope and delivery pressure.
A Bottleneck Audit would inspect the offer boundary, qualification rule, sales expectations, scope handoff, change-request path, delivery load, and where founder judgment still fills gaps. It would treat the pricing change as a hypothesis, not the conclusion.
The output can show whether price should be reviewed now, whether scope boundaries need work first, whether qualification is the pressure point, or whether delivery drag needs to be mapped before pricing changes become the plan.
Manual route review