Give the work a clear home
Bring important steps, information and decisions into one working experience.
Build · operational web system
Give a larger operation a clearer way to run. Start with the right shape.
For substantial operational software with several users, rules and moving parts. We start with paid scoping so the route, boundaries and build cost are clear before a larger commitment.
A larger working system, shaped around the operation it needs to support. See the price and scoping rule.
Substantial operation
- larger operation
- paid scope first
- several users
- one working view
- growing process
- staged delivery
- business control
- handover included
rootdelta.net
01 · Why
When the process is part of the business, a quick fix is not enough.
An Operational Web System is for a substantial internal or customer-facing operation where the work needs a durable home.
Shape it around how people work
Consider roles, rules and exceptions before the build is priced.
Build a path forward
Start with an agreed first release and a clear route for later stages.
1 of 3
02 · How
Understand the operation first, then build what it needs.
Paid scoping gives a larger piece of work the attention it needs before the build is agreed.
-
01
Scope the operation
We map users, journeys, rules, dependencies and the first useful release.
-
02
Agree the build
The written agreement confirms scope, exclusions, checks, dates, price, VAT and any material third-party costs.
-
03
Deliver in stages
We build, show progress, check the agreed outcomes and hand over the working system with documentation.
03 · What
A substantial working system, shaped around the outcome.
The final shape depends on the operation. The useful result is a clearer way for people to do important work.
Help people move through the work
People see the right information at each step and know what needs to happen next.
Keep the important detail together
The operation has a dependable place to record what happened and what happens next.
Make responsibility visible
Responsibilities and approvals are clear rather than hidden across inboxes and spreadsheets.
Keep control of the result
Your team receives the agreed system, documentation and control of its accounts and data.
1 of 4
Typical scopeIllustrative examples only
- Customer-facing service journeyGive customers a clear way to submit information, see progress and take the next step.
- A growing internal operationBring people, roles, decisions and records into one working view as the operation grows.
- A shared job or service recordKeep what was requested, what happened and what needs to happen next in one dependable record.
1 of 3
Illustrative examples only, not client work. The fit call helps identify the boundary, and the written quote confirms the actual scope.
This route starts with paid scoping, so the first release, boundaries and build can be agreed before a larger commitment.
04 · Price
Start with a proper view of the work, then agree the 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 full agreed scoping fee is credited against a matching build commissioned within 90 days of receiving the scoping deliverable. A prior Bottleneck Review counts towards that one credit rather than adding a second one.
05 · Get started
Start with the operation you need to run.
Tell us what the system must help people do, who uses it and what needs to improve. We will check whether this route fits and what scoping would need to cover. We reply within two UK working days with times for a free 15-minute call.
06 · Questions
Questions people ask before a larger build.
Clear answers before the first conversation.
Why is paid scoping required?
A larger operation has more users, journeys, rules and dependencies to understand. Paid scoping gives those questions proper attention before the build, price and boundaries are agreed.
What does the scoping stage cover?
It covers the operation, users, journeys, rules, dependencies, risks, the first useful release and the information needed to estimate the build. The scoping deliverable states what was agreed and what remains uncertain.
Can the system be delivered in stages?
Yes, where the first stage is useful by itself. The written scope and quote will say 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 the people using it, the outcome required and the responsibilities that need to be agreed before work begins.
Where does the system run?
It is deployed to a supported managed cloud service in your own account. You own, pay for and administer that account and provider service; Root Delta does not provide hosting.
Who keeps control of the accounts, data and work?
Your accounts and data stay under your control. The agreement sets out ownership of the agreed business-specific work and the licence for any standard Root Delta components.
What happens after the system is in use?
After acceptance, we hand over the agreed documentation and next steps. A qualifying accepted system may then be assessed for Delta Care, which starts only after the named system passes the agreed checks and the written care terms are in place. Delta Care provides software-only monitoring, practical triage and planned improvements; other work is quoted separately.
What happens if the delivered work has a fault?
We check each deliverable against the agreed result and the agreed way of checking it. During the agreed defect period, we correct reproducible material failures of the accepted deliverable to meet that result. New requirements or further features are separate written changes.
Can you work alongside our 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.