01When it’s the right start

A first step when technology matters to the case

A Reset is the right start when technology carries part of the investment case, but nobody can yet say what it returns.

  • 01A new acquisition, and a 100-day agenda still to set
  • 02Technology costs rising faster than the business
  • 03Duplicated systems and vendors after a buy-and-build
  • 04An ERP, CRM or cloud programme without a clear economic case
  • 05Little visibility of the value technology delivers
  • 06An exit or refinancing where the technology story needs evidence

02What we examine

Five areas, using your own data

We look where value and risk concentrate, with the people who run each area.

01Spend
Where technology money goes, by vendor, function and business unit, reconciled to the general ledger.
02Contracts
Terms, renewal dates, notice periods and committed volumes, and the decisions they force.
03Applications
Overlap, usage and cost across the application estate.
04Delivery portfolio
Programmes in flight, their business cases and their real status.
05Data
What the numbers can support today, and where they cannot yet be relied on.

03What leadership receives

Seven deliverables

Each one is written for decisions, not for the file. Every figure carries its ledger state, so a forecast is never read as a result.

  1. 01

    Technology spend baseline

    One view of run and change spend, reconciled to the general ledger.

  2. 02

    Contract and renewal map

    Commitments, notice dates and the decisions they force, in date order.

  3. 03

    Application landscape

    Overlaps, gaps, and candidates to consolidate or retire.

  4. 04

    Delivery portfolio review

    Which programmes carry value, which carry risk, and which to stop.

  5. 05

    Value register

    Each opportunity with an owner, a forecast and its ledger state: identified or validated.

  6. 06

    90-day action plan

    Sequenced actions, owners and decision points for the first quarter.

  7. 07

    Leadership readout

    A working session on the findings with the leadership team, the board or the investment team.

04How it runs

Week by week

  1. Week 1

    Mobilise

    Kick-off, data request, and interviews with leadership and the owners of technology.

  2. Week 2

    Baseline

    Spend and contracts reconciled; the application landscape mapped.

  3. Week 3

    Assess

    The delivery portfolio reviewed; opportunities identified and validated with their owners.

  4. Week 4

    Plan and read out

    The 90-day plan drafted with leadership, then the readout.

Shown for a four-week Reset. The scope sets the length, from two to six weeks.

05What it isn’t

Clear about the limits

  • Not a full audit

    We look where value and risk concentrate, not at every system.

  • Not a certification

    The Reset gives no compliance or security attestation.

  • Not a guarantee

    We promise no result. Management keeps ownership of the outcomes.

  • Not savings

    An estimate stays an estimate until it is implemented and verified in the ledger.

06What happens next

The plan belongs to you

Three ways to carry it out. You decide once the plan exists.

  1. Your team executes

    The plan is written for your leadership to run with its own people.

  2. Your partners execute

    Existing vendors and delivery partners take the actions the plan assigns to them.

  3. Mirivis supports

    We help carry it out, under a separately scoped engagement.

    Execution & Integration

Considering a Reset?

Tell us about the business and the decision in front of you.

Start a conversation