Understand the current system
A map of modules, dependencies and deployment practices will help identify where to begin.
All projects
MODERNISATION / ARCHITECTURE / DEVELOPMENT
Rewinit RESTART
A new chapter for a proven system.
We are building a programme for modernising existing applications in stages. RESTART is intended to connect dependency discovery, prioritisation and delivery of a first improvement with a plan for continued system development.
Delivery preparation
A plan that leads to deployment.Delivery preparation
As of 28 October 2026Scope defined. Next step: delivery.
We have prepared the project identity, first-version scope and acceptance criteria. The next stage is to build and verify the described journey with a partner. Timing will be agreed for the selected deployment.
- Prepared
- Scope and identity
- 01 / Next stage
- A review of one application, a dependency map and a first change package with a rollback plan.
- 02 / Planned stage
- Partner pilot
Who are we building this for?
Businesses with working software that is becoming harder to maintain or develop.
Where do we begin?
The system still supports the business, but every change takes a long time and relies on several people’s knowledge. RESTART will begin with one application and an improvement to one important scenario.
What will the first version include?
Application modernisation programme / Rewinit RESTART
Reasoned priorities
The change list will connect user impact with technical risk and cost.
A first reviewable improvement
The selected change will have acceptance criteria, regression checks and a rollback procedure.
Explore the planned journey.
Choose successive steps to see how the project’s first application is intended to work.
Interactive delivery plan
Rewinit RESTART / 01
Understand the application
Example scenario
Example TEST system: modules, integrations and deployment path.
Planned outcome
Create a dependency map and identify development obstacles.
An example scenario using prepared data. This presentation illustrates the planned process; it does not operate external systems.
A plan that leads to deployment.
Each stage follows verification of the previous outcome. The pilot scope will be agreed with a partner.
Prepared
Scope and identity
Project mark, visual direction, audience, first-deployment scope and acceptance criteria.
- 01
Next stage
First version
A review of one application, a dependency map and a first change package with a rollback plan.
Acceptance criterionThe change passes its agreed scenario, key existing functions pass checks and rollback to the previous version is rehearsed.
- 02
Planned stage
Partner pilot
Run the programme on one partner application and assess timing, obstacles and the value of the improvement.
- 03
Planned stage
Preparation for availability
A repeatable application qualification, progress reporting and modernisation planning process.
Development journal
Rewinit RESTART / DEVELOPMENT
First-deployment scope and identity prepared.
We have prepared the project mark and visual identity and defined its audience, first scenario, milestones and acceptance criteria. The delivery plan describes the next outcome to verify.
Project identity
A distinct mark and colour within the shared Rewinit system. The identity accompanies the project from planning to first-deployment materials.
Download SVG logoRewinit RESTART / PARTNERS
Build the first deployment with us.
We are seeking a partner to adapt the scope to a specific process and evaluate the outcome in a pilot.
Discuss RESTARTA useful starting point
- Source and test environment access
- Key user scenarios
- An application owner and desired improvement