Digital Transformation Program

From diagnosis to a finished solution design – and support all the way through implementation

We design a digital ecosystem that works for the whole organisation – and the requirements your chosen implementation partner will build it from.

Design phase

8–12 weeks

from kick-off to the board’s decision

Engagement model

Design → Partner → Validation

three stages of working together

For

Board, CEO, CTO, CMO

organisations about to invest in technology

An ecosystem for the whole organisation

We design it by bringing three things together: goals, the current situation and the resources available

Goals

What the company must be able to do to deliver its plan for the coming years

Current situation

How systems, data and processes between departments really work

Resources

The people, skills, budget and time that are genuinely available

Why us

There are three ways to do this work – they differ in how much they cost you in time and risk

On your own

It can be done. But it is one of the hardest tasks in an organisation and needs experience of how large companies operate digitally

With a vendor only

A software house will design and price its own proposal. Coordinating the whole thing still stays with your product owner

With Savren

We have run programmes like this many times. We know what to look for in the design, in choosing a partner and during implementation

Let’s talk about how we can tailor this to your organisation

What you get

01

Agreed organisational needs

One list of requirements distilled from conversations with all stakeholders – instead of a separate wish list from every department

02

Priorities

What we do first, what comes later and what we don’t do at all – with a business rationale for every decision

03

Ecosystem and data-flow design

How systems should connect and how data flows between departments – a target architecture rather than individual tools

04

A roadmap

The sequence of changes, the dependencies between them and decision gates – including the scope of a pilot

05

Requirements and acceptance criteria

A scope ready for the partner to price, and the yardstick that tells you they have delivered what was designed

06

A product owner ready for the role

Mentoring for the person who takes ownership of the programme. If that person isn’t in place yet, support with recruitment and onboarding

Who is responsible for what

We design the solution and safeguard its quality – ownership of the programme stays with you

Savren

Diagnosis and solution design
Priorities, roadmap and data flow
Requirements and acceptance criteria
Partner selection and support in negotiations
Product owner mentoring
Milestone validation

Your team

Decisions and budget
Product owner and contact with the partner
Contract with the partner
Acceptance of implementation stages
Ownership after the programme ends

Implementation partner

Building the solution
Schedule and pricing of the work
Quality and delivery dates
Licences and maintenance
Submitting stages for acceptance

How we work together

Design phase

8–12 weeks

Once it is complete, we support you in choosing a partner and during implementation, at the pace set by the partner’s schedule.

The design phase is a fixed price agreed after the diagnosis. Implementation support is billed as a subscription.

Choosing an implementation partner

Three scenarios to choose from – they differ in how much of the selection process we take on

Scenario A – partner recommendation

We recommend a partner matched to the scope and scale of the programme, with the reasons for our choice. You run the rest of the process yourselves

Scenario B – full selection process

We research the market, issue a request for proposal based on the requirements, review the offers and compare them. It ends with a recommendation

Scenario C – you already have a partner

We work with the vendor you have already chosen. We design the solution and requirements around them, and the selection process falls away

In every scenario we take part in conversations and negotiations with the vendor – checking the scope of work, schedule and acceptance criteria before they go into the contract.

Three scenarios to choose from – they differ in how much of the selection process we take on

FAQ

The questions we hear most often in a first meeting

Do you carry out the implementation?

No. We design the solution and the requirements, and your chosen implementation partner builds it. During the build we check at agreed checkpoints that what is being built matches the design.

We have a product owner – why do we need you?

The product owner runs the programme day to day and knows the organisation from the inside – we can’t replace that. We bring what availability alone can’t make up for: experience from similar programmes in other organisations, patterns that have proved durable, and an outside view when assessing the vendor. That gives the product owner someone to test decisions against before they become expensive.

Do you have your own software house?

No, and we take no fees from implementation partners. That keeps our recommendation of a vendor independent, and the requirements aren’t written around anyone’s offer.

What if we already have a partner?

The programme runs as normal, with one exception: the selection process drops out of the scope. We design the solution and requirements around your vendor’s capabilities, and we can take part in negotiating the scope and acceptance criteria just as we would with a new partner.

What doesn’t the programme cover?

Development work, system configuration, licences and maintenance – these are the implementation partner’s scope. We also don’t take over day-to-day coordination of their work or the formal acceptance of stages; these stay within your organisation.

What it looks like in practice

Every organisation starts from a different place.

Before we propose working together, we want to understand where you are and what is actually needed. Sometimes it’s an audit. Sometimes a strategy. Sometimes a conversation is enough.

This website uses cookies

We use cookies to analyse traffic and personalise content; some data is shared with our analytics partners. You can change your consent at any time – see our Privacy Policy and Cookie Policy for details.