Concept, not live software. Product, interface and figures are illustrative; no customer or performance claims.

A scope-decision concept for fixed-fee agency work

The project is on track. The margin isn't.

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

Scope change rarely looks commercial when it arrives.

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.

01 / REVISION

“Can we try one more direction?”

A new review round enters after the agreed feedback cycle.

02 / ADDITION

“Could mobile have its own states?”

A useful improvement appears without a matching scope decision.

03 / ESCALATION

“Let's get senior eyes on it.”

The delivery mix changes, but the original cost assumption stays untouched.

04 / DEFAULT

“It's faster if we just do it.”

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

Decisionless Delivery

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.

01

A request enters a delivery channel

It appears in chat, email, feedback or a project-management task.

02

The team reads it as work

Someone estimates effort informally, or simply begins because the request feels reasonable.

03

No owner makes the commercial choice

The request is not explicitly absorbed, traded, re-scoped or charged.

04

Small exceptions become the delivery pattern

Time and internal cost accumulate across requests that looked harmless in isolation.

05

The margin changes by default

The agency discovers the effect later—even though no one consciously approved it.

The solution object

Give each material change a Scope Decision Trail.

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.

01

Baseline

State the agreed fee, scope and planned delivery cost.

02

Request

Capture the deviation in the client’s and team’s own words.

03

Impact

Estimate internal delivery cost and show cumulative exposure.

04

Decision

Choose to absorb, trade, re-scope or charge—deliberately.

05

Record

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

Make the decision. Watch the economics move.

Select a response for each illustrative request. The model updates from the assumptions shown below; it does not predict savings or product performance.

ScopeSignal / Decision trailIllustrative data only

Fixed-fee website redesign

Project Atlas

3 decisions open
Original fee£24,000
Planned delivery cost£12,600
Unresolved exposure£1,240
Projected contribution£11,400
Projected gross margin47.5%

Extra mobile states

Eight estimated hours at £70 internal cost.

£560

Third revision round

Five estimated hours at £70 internal cost.

£350

Senior QA added

Three estimated hours at £110 internal cost.

£330
Absorbed delivery cost£0
Assumed added fee£0
Margin change0.0 pts

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

The market does not need another “early warning” claim.

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

Run and forecast the operation

Projects, people, time, budgets, utilisation, forecasting and broader business reporting.

Typical centre of gravity: operational visibility

Scope / change-order tools

Detect and document change

Compare requests with scope, estimate impact, create change orders and retain approvals.

Typical centre of gravity: change control

This is a positioning hypothesis, not a superiority claim. Public capability references used in the research include Productive, Teamwork, Docket and ScopeGuard.

Four valid responses

Commercial control does not mean billing every exception.

The useful outcome is a conscious choice appropriate to the relationship, the project and the economics.

01 / ABSORB

Protect the relationship

Accept the delivery cost because the goodwill or strategic value justifies it.

Make the cost visible anyway.
02 / TRADE

Keep the fee, change the work

Add the request while removing something of comparable delivery cost.

Reset what “done” includes.
03 / RE-SCOPE

Change the plan

Pause the request until timing, ownership or deliverables are agreed again.

Do not let ambiguity become approval.
04 / CHARGE

Change the commercial terms

Price the additional work and obtain approval before delivery continues.

Make the client’s choice clear.

A deliberately narrow hypothesis

Useful only where the commercial baseline is real.

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

Teams with something concrete to protect.

+
A documented fee and agreed delivery scope
+
Reasonable internal cost assumptions
+
Material requests that arrive during delivery
+
A named person authorised to choose the response

Not a substitute for

The operating discipline underneath it.

Project management, time tracking or accounting
A clear statement of work and change process
Accurate cost and effort estimates
Human judgement about the client relationship

Product truth

What this is. And is not.

Real

The research, positioning decision, page architecture, copy, interface design and working browser interaction.

Illustrative

ScopeSignal as a product, Project Atlas, all project economics, interface states and decision logic.

Unknown

Demand, willingness to pay, integration feasibility, detection accuracy, security requirements and user outcomes.

Excluded

Fake trials, sample pricing presented as an offer, invented integrations, testimonials, ROI and availability claims.

Questions

Straight answers.

01Does every extra request need to be charged?

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.

02Is ScopeSignal available software?

No. It is an independent product and conversion-copy concept created to demonstrate B2B SaaS research, positioning, page architecture and interactive execution.

03How would it detect an out-of-scope request?

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.

04Would this replace a PSA or project-management platform?

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.

05Are the margin figures accurate?

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.

06Why build a page before the product exists?

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

Do not let delivery choose by default.

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.