See how the system fits together
Understand where it supports the business, where it is fragile and what needs attention next.
Assure · Independent Software Review
Know what your software is really relying on.
Root Delta reviews architecture, secure code and technical due diligence on software it did not build, and gives you a written report, evidence-backed findings, practical priorities and a walkthrough.
Scoped to the decision in front of you and priced to the system, never to the size of a deal.
Assure · Independent Software Review
- reviews
- software Root Delta did not build
- priced
- to the system, not the deal
- delivers
- a written report and a walkthrough
- fee
- a stated figure, agreed before work starts
rootdelta.net
Stakes
This review is for before you own the system, not for keeping it running afterwards.
When software sits behind a real decision, the review has to answer to that decision, not to a generic checklist.
Understand practical software risk
Review the agreed software for risks that could affect the system and the business relying on it.
Support an important decision
Assess condition, maintainability, dependencies and priorities before you commit to a deal or plan.
1 of 3
If you already own the system and it just needs to keep working safely, that is Delta Steward’s assessment, not this review. An Independent Software Review is for the decision itself: before you own it, or wherever an independent, non-continuing view matters more than ongoing care.
Method
Everything starts with clarifying the decision.
Scope, evidence and depth are agreed before the work starts.
-
01
Clarify the decision
The free 15-minute call clarifies what you need to know, what software is in scope and which type of review fits.
-
02
Agree access and evidence
The material to review, the access available and how the work will be carried out are confirmed before it starts.
-
03
Review, report and walk through it
Root Delta writes the findings down, then walks you through what they mean before you decide.
The report
The report ties every finding to evidence.
What was examined, what was found, and what deserves attention next, in one document you can act on.
Written findings, rated by severity
The conclusion, relevant evidence and practical priorities in one document, with each finding rated by severity so you can see what needs action first.
Findings you can trace
Each finding connects what was seen to its likely business consequence and a practical response.
Room to ask questions
A working session for the people making or implementing the decision.
1 of 3
Independence
Independence is written into the terms, not asserted afterwards.
Two things make the review independent: what Root Delta will not review, and when the scope is fixed.
- Root Delta does not review software it built itself.
- What will be reviewed, and against what evidence, is agreed before the review starts, not adjusted afterwards to fit a conclusion.
Price
Priced to the system, never to the size of a deal.
The price reflects the system, access, evidence and depth of review in scope. A written quote confirms the scope, timing and total before you commit.
Independent Software Review
A written quote for the review you need
Priced to the system
The quote states the total including VAT at 20%
The quote is based on the system, access, evidence and depth of review agreed. Due diligence is never priced as a percentage of a transaction.
Get started
Describe the decision the review must support.
Say what is being reviewed and what decision it must support. We reply within two UK working days with times for a free 15-minute call.
Questions
Questions about Independent Software Review.
Which type of review fits your decision?
Architecture review looks at how the system fits together. A secure-code review looks at agreed code for practical security risks. Technical due diligence is an engineering and technical review for a purchase, investment or other important decision. The right combination is confirmed on the free 15-minute call.
What access or evidence does the review need?
It depends on the agreed review. The relevant code, documentation, environments, records or demonstrations, and the available access, are agreed before work starts. Do not send passwords through this form or ordinary email.
What happens after the findings?
The walkthrough covers the report and its priorities. You decide what to do next. If you want help acting on the findings, that is discussed as a separate, clearly scoped piece of work.
What does the review not cover?
Independent Software Review provides engineering evidence and analysis. It is not legal advice, regulatory certification or a penetration test, and it cannot guarantee that every future issue will be found.