Rollout

From prototype to the Monday morning habit

A beautiful prototype that nobody refreshes is a failed project. Implementation is the work of sources, permissions, training, and two real closes with us still in the room.

Colleagues working through printed charts during a finance workshop

How a rollout actually runs

We work beside the systems you already pay for. Ripping out a ledger to suit a dashboard is almost never the right first move.

Source map

We list every figure and the system that owns it. Common sources include Xero, Sage, QuickBooks, operational exports, and controlled spreadsheets. We are not affiliated with those vendors. Where a source is unreliable, we say so and design the tile to show its weakness rather than hide it.

Access model

Consolidated readers, entity readers, and preparers are different people. We write the matrix before accounts are created. A branch manager should not stumble into group treasury. A non-executive should not need a finance login to read the pack.

Three kinds of training

Preparers learn refresh, exceptions, and commentary. Reviewers learn what must be signed before a number is called final. Board readers learn how to move through the narrative without requesting a second pack by email.

A tidy server cabinet behind glass in a small British office

Hypercare across two closes

The first close after go-live finds the awkward mappings. The second close shows whether the habit holds when we are less present. We stay available through both, with a named contact and a written list of open items.

At handover you receive the measure dictionary, refresh notes, the access matrix, and the name of the owner of each front-page tile. If a tile has no owner, it does not ship.

Hosting choices are yours. Some clients keep the dashboard inside a tool they already license. Others want a private workspace. We document where data sits, who can export it, and how a leaver is removed. Security is part of the build, not a PDF at the end.

What we need from you

A single internal sponsor

Someone who can unlock a read-only extract and decide when two definitions conflict. Without that person, design meetings become taste debates.

A recent close, not a perfect one

We would rather prototype on last month’s imperfect file than wait for a fictional clean year. The imperfections are the design brief.

Time from preparers

Two working sessions during the close window. We schedule them so they do not collide with the filing deadline.

Permission to say no

Stakeholders will ask for extra tiles. The sponsor needs cover to refuse the ones that do not change a decision.

Tell us what the next close has to survive

We will sketch a rollout that respects the calendar you already have, whether you are in Devon or anywhere else in the UK.

Plan an implementation