selected work · tools, dashboards, maps
lab22 builds the tools, dashboards, and maps that sit between an organisation's data and its decisions. The part of the work where the right question is already known — but nobody can answer it cleanly.
A commercial team tracked actions, commitments, and follow-ups across personal inboxes and overlapping spreadsheets. Nothing was wrong with the data — it just lived in six places and surfaced in none.
The work started with the process, not the output. We mapped the cycle, defined the categories, and agreed on what "done" looks like for each action type — then built a structure that lived inside the team's existing habits. Pipeline funnel, win/loss, account health, individual performance. One file. No new software to learn.
The team adopted it because it fit. Management adopted it because it talked.
Each program manager ran their own workbook. Finance ran a consolidated model that was always three weeks behind. Reviews were mostly about whose numbers were right.
A drag-and-drop interface where any manager loads their standard workbook and sees — immediately — where the program stands against budget, by category, by site, by week. Net position, cash flow, recovery, warranty. No manual consolidation. The source file stays as it was; the clarity is new.
Reviews became about decisions, not reconciliation.
A business development team was pitching new accounts across Europe and North America. The question was always the same: who is operating near us, what do they build, and where are our access points? The answer lived in scattered press releases, databases, and institutional memory.
An interactive map — EU and NA coverage — with every relevant site plotted, filterable by segment, type, and proximity to existing accounts. Built to the team's specific targets and updated as the picture changes.
Intelligence that moves with the conversation.
Everything lab22 delivers is built to be maintained by your team without us. If the engagement ends, nothing breaks. The logic is readable. The process is written down. Any competent analyst can continue from where we stopped.
That's not a selling point — it's a design constraint from the start.
If something in your operation is consuming time that should go to decisions — that's the conversation.
hello@lab22.studio →