“Can we try one more direction?”
A new review round enters after the agreed feedback cycle.
A scope-decision concept for fixed-fee agency work
ScopeSignal explores a narrower way to handle scope change: turn every material request into a visible commercial choice before the team keeps delivering.
How margin disappears
It arrives inside normal delivery language. Each request appears small enough to keep moving. The commercial effect only becomes obvious after several decisions have already been made by default. The lines below are illustrative composites, not attributed customer quotations.
A new review round enters after the agreed feedback cycle.
A useful improvement appears without a matching scope decision.
The delivery mix changes, but the original cost assumption stays untouched.
The team protects momentum. The project quietly accepts the cost.
The expensive part is not the request. It is delivery continuing before the commercial decision.
The problem mechanism
Work can remain operationally “on track” while commercial control slips. The project plan records tasks; the missing object is the explicit choice attached to the deviation.
It appears in chat, email, feedback or a project-management task.
Someone estimates effort informally, or simply begins because the request feels reasonable.
The request is not explicitly absorbed, traded, re-scoped or charged.
Time and internal cost accumulate across requests that looked harmless in isolation.
The agency discovers the effect later—even though no one consciously approved it.
The solution object
Not another vague alert. A short record that connects what was agreed, what changed, the estimated commercial impact and the response an authorised person chose.
State the agreed fee, scope and planned delivery cost.
Capture the deviation in the client’s and team’s own words.
Estimate internal delivery cost and show cumulative exposure.
Choose to absorb, trade, re-scope or charge—deliberately.
Keep the rationale and prepare a clear client-ready summary.
The Margin Drift Timeline still has a role. It is a useful visual inside the trail, not a defensible category claim. Established agency systems already forecast project margins.
The intended distinction is the decision record. The concept focuses attention on whether the agency made a commercial choice—not merely whether a dashboard detected risk.
Interactive concept / Project Atlas
Select a response for each illustrative request. The model updates from the assumptions shown below; it does not predict savings or product performance.
Fixed-fee website redesign
Eight estimated hours at £70 internal cost.
Five estimated hours at £70 internal cost.
Three estimated hours at £110 internal cost.
Choose a response for each request to create the illustrative decision record.
Model: planned contribution = £24,000 − £12,600 = £11,400. Absorb adds delivery cost. Trade assumes equivalent planned work is removed. Re-scope remains unresolved. Charge assumes an added fee equal to estimated internal cost—only to make the demo arithmetic explicit, not as pricing advice.
Where the concept sits
Existing agency platforms already market forecasts, live margins and budget alerts. Dedicated scope tools already document requests, impact and approvals. ScopeSignal’s narrower hypothesis is the explicit four-way commercial decision. Whether that distinction is strong enough to support a standalone product would still need interviews and market testing.
PSA / agency operations
Projects, people, time, budgets, utilisation, forecasting and broader business reporting.
Typical centre of gravity: operational visibilityScope / change-order tools
Compare requests with scope, estimate impact, create change orders and retain approvals.
Typical centre of gravity: change controlScopeSignal concept
Connect the deviation to one of four explicit responses and preserve the decision rationale.
Working distinction: decision accountabilityThis is a positioning hypothesis, not a superiority claim. Public capability references used in the research include Productive, Teamwork, Docket and ScopeGuard.
Four valid responses
The useful outcome is a conscious choice appropriate to the relationship, the project and the economics.
Accept the delivery cost because the goodwill or strategic value justifies it.
Make the cost visible anyway.Add the request while removing something of comparable delivery cost.
Reset what “done” includes.Pause the request until timing, ownership or deliverables are agreed again.
Do not let ambiguity become approval.Price the additional work and obtain approval before delivery continues.
Make the client’s choice clear.A deliberately narrow hypothesis
The concept is designed around fixed-fee or capped agency work. It cannot rescue unclear scope, unreliable inputs or a culture where nobody owns commercial decisions.
Designed for
Not a substitute for
Product truth
The research, positioning decision, page architecture, copy, interface design and working browser interaction.
ScopeSignal as a product, Project Atlas, all project economics, interface states and decision logic.
Demand, willingness to pay, integration feasibility, detection accuracy, security requirements and user outcomes.
Fake trials, sample pricing presented as an offer, invented integrations, testimonials, ROI and availability claims.
Questions
No. Absorbing work can be the right commercial decision. The concept makes the choice and its estimated effect visible instead of allowing it to happen silently.
No. It is an independent product and conversion-copy concept created to demonstrate B2B SaaS research, positioning, page architecture and interactive execution.
That has not been established. A real product would need discovery around inputs, integrations, human review, accuracy and false positives. This concept deliberately avoids claiming an automated detection method.
No. The concept is framed as a focused decision workflow. Whether it should be a standalone tool, a feature or a process template is an unresolved product question.
The arithmetic is accurate for the assumptions displayed in the example. The assumptions themselves are fictional. A real forecast would only be as useful as its fee, scope, time and cost inputs.
Here, the page is a portfolio artifact. In a real venture, this kind of concept can help expose positioning and discovery questions—but it would not replace customer interviews, feasibility work or offer testing.
The decision before the next task
Open the sample trail again, or read the case study to see why the original “margin intelligence” position was rejected and how the narrower argument was built.