Assess ongoing maintenance
Understand whether the application can be maintained with a manageable level of work.
CNSLT/006Application review
Look inside.
Decide what deserves to change.
We assess an existing application to decide whether to maintain, improve or replace it. We review available workflows, code and documentation and explain the options, limitations and dependencies.
What works.
What needs attention.
Before expanding or replacing a tool, it helps to understand its foundations. The review connects what the team needs with what the current system can support.
Prepare for improvements
Identify dependencies and boundaries before adding functions or changing the interface.
Take over a delivered application
Arrange a review of the delivered work, documentation and agreed user journeys.
Plan a replacement
Compare gradual improvements with rebuilding, taking data and continuity into account.
From the system you have
to an informed decision.
We define which code, documentation and user journeys we can review. Each conclusion states its supporting evidence and the limits of the checks performed.
Starting point
- Application
- Code
- Documentation
Technical reviewOutcome
- Findings
- Options
- Action plan
From questions
to a practical plan.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Define the review scope
We agree on the components, access, features and questions the review should cover.
/002Review the foundations
We examine the structure, dependencies and documentation in the materials available.
/003Check how it works
We review representative user journeys and how they meet the team's needs.
/004Conclusions and alternatives
We propose priorities and options for maintenance, improvement or replacement, with their assumptions.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
Review the application.
Decide with evidence.
(4)Define the review
We agree the questions to answer and the features, code and documentation we can inspect.
Compare use and technical foundations
We review representative workflows, structure and components within the available scope.
Organise the options
We relate findings to the team’s needs to assess maintenance, improvements or replacement.
Deliver the recommendation
We explain priorities and alternatives, stating what has been checked and what needs further review.
Clarity to decide.
Clarity to move forward.
Decisions with context
Recommendations start with how you work. A tool that suits another business may not fit your budget or processes.
Evidence and limitations
We state what has been reviewed, what is outside the scope and what needs further investigation. A focused review is not presented as a comprehensive audit.
No commitment to development
You can use the findings to decide with your team or another supplier. If you continue with SBI Digital, we define a separate implementation phase.
Before we start.
(5)Does this include a cybersecurity audit or penetration test?
No. A general application review is not a specialist audit or a penetration test. If that assessment is needed, it requires its own scope and suitably qualified professionals.
Can you check an application without access to the code?
We can assess the experience and visible behaviour, but conclusions about the technical foundations will be limited. We make clear what could not be verified.
Does the first conversation count as a consultation?
The first conversation helps us understand your needs and assess whether we can help. A detailed assessment or review has a scope, deliverable and price agreed before work begins.
Do I have to commission development afterwards?
No. You can use the analysis with your own team. Implementation, coordination with other suppliers or further support is quoted separately if you need it.
Do you need access to all our systems?
We request only what is needed for the agreed scope. We can start with interviews, documentation and demonstrations; any additional access is agreed with a clear purpose and permissions.
Engineering × Design.
For the next step.