Concept · Set of pages
From a forty-tab workbook to an application three teams can open
A conversion engagement takes a spreadsheet that one person understands and returns an application that three teams can open.
Page 1 of 4
By Ade Fashola · Head of conversion services · 22 July 2026 · 9 min read
The workbook works. That is what makes these engagements different from a data migration: nobody is replacing something broken. Forty tabs of formulae that produce the right answer every month are a genuine achievement, and the person who built them is usually the best analyst in the building.
The problem is everything around it. One person can open it. Nobody can say what changed between last month's copy and this one. The inputs are pasted, so the provenance of any number is a memory rather than a record. And the whole arrangement has a single point of failure who is entitled to take a job somewhere else.
What we take from it
The first week of an engagement is reading, not building. What we are extracting is the analysis, not the spreadsheet: the sequence of things that happen, the rules that decide each one, and the handful of judgements that are genuinely judgements.
- The inputs, and where they really come from — which system, at what point in the month, in whose hands.
- The sequence — what has to be true before the next tab can be filled in. Most workbooks encode a dependency graph in tab order and nobody has ever drawn it.
- The rules that are actually rules — the ones that would be written the same way by any competent person doing this job.
- The judgements — the cells where somebody types a number because they know something. These do not become logic. They become inputs the application asks for.
That last figure is the one worth arguing about in the room. A conversion that produces zero judgement inputs has either found a genuinely mechanical process or has quietly hard-coded somebody's opinion, and it is almost always the second.