Build · Operational Web System

Substantial operational software starts with a paid scoping stage.

For software several people will run their day on: several users, rules and moving parts. Paid scoping settles the route, boundaries and build cost before a larger commitment begins.

Entered through paid scoping, not directly. See the scoping fee.

Substantial operation
larger operation
paid scope first
several users
one working view
growing process
staged delivery
business control
handover included
rootdelta.net

Why scoping

Why does the build start with paid scoping?

An Operational Web System is never quoted before its paid scoping stage is complete.

Stages

Three stages, each with its own gate.

Nothing moves to the next stage until the one before it is properly agreed.

  1. 1

    Scope the operation

    Users, steps, rules and dependencies are mapped into the scoping deliverable, and the first useful release is agreed. Nothing is priced yet.

  2. 2

    Agree the build

    The written agreement confirms scope, exclusions, checks, dates, price, VAT and any material third-party costs.

  3. 3

    Deliver in stages

    Root Delta builds in stages, shows progress against the agreed checks, and hands over the working system with documentation.

The deliverable

What the scoping deliverable gives you.

The deliverable states what was agreed, what is estimated and what remains uncertain, sized to the operation in front of it.

Illustrative examples only, not client work. The fit call helps identify the boundary, and the written quote confirms the actual scope.

Price

Price: paid scoping, then the agreed build.

Operational Web Systems start from £15,000 net, or from £18,000 including VAT at 20%.

Build

Operational Web System

From £15,000 net

From £18,000 including VAT at 20%

The build starts with paid scoping at 10% to 15% of the estimated build, with a minimum business price of £2,500 net (£3,000 including VAT at 20%).

The scoping fee is credited in full against a build commissioned within 90 days of receiving the scoping deliverable. A prior Bottleneck Review counts towards that credit rather than adding a second one.

Boundaries

Where control and hosting sit.

How hosting, ownership, aftercare and continuity are settled.

Get started

Describe the system your operation needs.

Say what the business needs the system to do and who will rely on it. We reply within two UK working days with times for a free 15-minute call.

Questions

Questions about a larger build.

What does the scoping stage actually cover?

The operation, its users, steps, rules, dependencies and risks, the first useful release, and what is needed to estimate the build. The scoping deliverable states what was agreed and what remains uncertain.

Can the system include AI?

Yes: for example extracting information from documents, drafting content for review, or routing work to the right person. Scoping identifies where it would help and where it would not, and any such step keeps a person checking the result.

Can the system be delivered in stages?

Yes, where the first stage is useful by itself. The written scope and quote state what that stage achieves, what remains for later, and what would need to change before a later stage.

Is this for internal or customer-facing work?

Either can be considered. The right route depends on who uses it, the outcome required, and the responsibilities that need to be agreed before work begins.

What happens if a delivered stage has a defect?

Root Delta checks each deliverable against the agreed result and the agreed way of checking it. During the agreed defect period, Root Delta corrects reproducible material failures of the accepted deliverable to meet that result. New requirements or further features are separate written changes.

Can Root Delta work alongside your team or another supplier?

Yes, where responsibilities, access and decisions are agreed before delivery begins. Root Delta remains accountable for the work in its scope.

Request a free 15-minute call