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%).
Build · Operational Web System
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.
Why scoping
An Operational Web System is never quoted before its paid scoping stage is complete.
Paid scoping buys a defensible number instead of a guess: it maps who uses the system, what the rules and exceptions actually are, and what the first useful release should include.
I would rather spend a paid day getting the scope right than put a guess in a quote. I lead the scoping stage personally, and bring in specialists only where the scope genuinely calls for their expertise.
This route is for software several people will depend on day to day, not for a single process that needs joining up. If it is really one important workflow rather than a system people will live inside, Connected System is probably the smaller, more direct start, and it is entered without a separate paid stage.
If that is what your situation looks like, I will say so rather than start you on a scoping stage you do not need.
Stages
Nothing moves to the next stage until the one before it is properly agreed.
Users, steps, rules and dependencies are mapped into the scoping deliverable, and the first useful release is agreed. Nothing is priced yet.
The written agreement confirms scope, exclusions, checks, dates, price, VAT and any material third-party costs.
Root Delta builds in stages, shows progress against the agreed checks, and hands over the working system with documentation.
The deliverable
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
Operational Web Systems start from £15,000 net, or from £18,000 including VAT at 20%.
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
How hosting, ownership, aftercare and continuity are settled.
The system is deployed to a supported managed cloud service in your own account, which you own, pay for and administer. Root Delta does not provide hosting.
Your accounts and data stay under your control, including any account a delivered feature needs to run, such as an AI provider: it is set up in your name and its ongoing usage is billed to you, not to Root Delta, so the system is fully yours to run. The agreement also sets out ownership of the agreed business-specific work and the licence for any standard Root Delta components.
Root Delta hands over the agreed documentation and next steps once the system is accepted. A qualifying system may then be assessed for Delta Care, which starts only after the named system passes its agreed checks and the written care terms are in place; Delta Care itself is software-only monitoring, practical triage and planned improvements, with anything beyond that quoted separately.
Root Delta is founder-led, and the agreement covers what happens if a key person becomes unavailable: Root Delta must tell you promptly, and may provide a suitably qualified substitute or propose a revised timetable. If neither is possible within 30 days, either side may end the affected work on the stated payment and refund terms.
Get started
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
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.
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.
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.
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.
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.
Yes, where responsibilities, access and decisions are agreed before delivery begins. Root Delta remains accountable for the work in its scope.