Guide
Keep Most Spreadsheets, and Replace the Few That Have Become Systems With One Focused Application
A spreadsheet becomes a system when other people act on its output without being able to check it. Most files can stay, and we replace the few that carry weight with one focused application.
4-minute read5 November 2026
In Brief
- The test is dependency and consequence. A small file that feeds a regulatory return, a payment or a shutdown plan is a system, and it needs an owner, a change record and a test.
- We see four actions: find the files others act on unseen, keep the rest, put simple controls on those that matter, and build a small tool where several people write to a file with real consequences.
- Thinqmesh builds one application for the single job, with logins, roles and an activity record, connected to your existing tools, and deployed on your own account.
Walk through a plant, mine or utility and ask how the shutdown plan is built, how critical spares are tracked or where the monthly energy figures come from. The answer is often a file on a shared drive, maintained by one competent person, and it is working. It began as one engineer's calculation, proved useful, and gained dependants until it carried weight its author never designed it for. Our view is that most of these files should stay, and a small number have become systems that deserve a proper home.
The Test Is Who Depends on the Output
A forty-tab cost model used by one analyst who checks it is a personal tool. A single sheet of tank dips, feeding a stock valuation, may be a system. What separates them is whether other people act on the output without being able to verify it, and what happens if it is wrong.
The cost of leaving a system in a spreadsheet is several versions of the same figures, an unclear record of who changed what, and a reconciliation that someone rebuilds by hand each month. One focused application changes that at proportionate scale, and the files that are fine can stay as they are.
Four Actions to Find the Spreadsheets That Matter
Each narrows the work to the few files that carry weight, so the effort of replacing anything goes where it pays back.
Find the Files Others Act on Unseen
A maintenance planner, a buyer or a shift supervisor uses the result and has never opened the formulas.
Size matters little. A single sheet of tank dips that feeds a stock valuation can be a system, while a forty-tab model used by one analyst who understands it is a personal tool. We ask who acts on each file's output, whether they can check it, and what happens if it is wrong.
Get started
- List the files your planning, purchasing and reporting rely on.
- For each, ask who uses the result and whether they have seen the formulas.
Look for the Signs That Appear Together
Several together mean the organisation runs a system with no owner, no change record and no test.
The signs are familiar: the file stops when one person is away, copies travel by email with final in the name, someone pastes an export into a tab each week, and its figures leave the building in a return, an invoice or a safety decision. One sign is unremarkable, while several, especially the last, mark a system.
Get started
- Score each key file against the five signs.
- Pick the two that show the most signs together.
Put Simple Controls on the Files That Stay
An owner, a locked copy of the formulas and a dated version go a long way.
Most files are doing what they should, and replacing them wastes effort. For those that matter but can stay, we suggest a named owner, protected formulas, a dated version history and a second person who checks the result. These cost little and reduce the dependence on one person.
Get started
- Name an owner and a deputy for each key file.
- Keep one dated copy per month in a shared place.
Build a Small Tool Where It Is Shared and Consequential
One application that does a single job well, with clear permissions and an activity record.
Where several people write to a file and the consequences are real, a focused application serves better. We build the screens for the exact job, with logins, roles and a record of who changed what, and connect them to the accounting, CRM, payment and messaging tools you already use.
Get started
- Pick the file where several people type and others depend on the result.
- Write the one job it does in a single sentence.
How Thinqmesh Solves This
We build screens for the exact job your team does and connect them to the tools you already use. A first working version arrives within four weeks, and the full engagement runs to six.
- Week 1
The One Job, Agreed
We choose the spreadsheet that has become a system, watch how it is used and agree in writing the single job the application must do.
- Week 2
Screens, Logins and Roles
Screens are built for the exact job, with logins and roles so each person sees and changes only what they should.
- Week 3
An Activity Record and Connections
Every action is recorded, and the application is connected to your accounting, CRM, payment and messaging tools.
- Week 4
A First Working Version
Your team uses a first working version on your own account. The remaining weeks add integrations and polish.
You finish with a working application on your own account, logins and roles, an activity record, integrations with your tools, and source code and documentation you own.
