A spreadsheet should become an app when the work around each row matters more than the data inside it: who can act, what must happen next, what evidence is required, and who approved the result. If the sheet mainly supports flexible analysis by a small, trusted group, keep it.
Score the workflow, not the file
A large workbook can still be the right tool. A small one can already be carrying a process that needs named owners, permission boundaries, and a reliable history. Row count does not settle the decision.
Score one recurring workflow from 0 to 2 on each dimension below. Use what people actually do today, including the side messages, reminders, and exceptions that never made it into the sheet.
- 0–3: keep the spreadsheet and improve it.
- 4–6: repair the sheet, then test one narrow workflow before committing to a move.
- 7–10: the workflow deserves a scoped app pilot.
| Dimension | 0 | 1 | 2 |
|---|---|---|---|
| Hand-offs | One person works alone | Several people update, but ownership is informal | Named owners, approvals, deadlines, or escalations matter |
| Access | Everyone can see and edit the same information | A few ranges or tabs need care | Different people must see or change different records or actions |
| Rules | The sheet mainly analyses or reports | Validation and formulas guide entry | The process must block invalid states or require evidence before proceeding |
| Accountability | Changes are disposable or easy to check | File version history is usually enough | The team must know who changed, approved, or released something |
| Working interface | The grid works for the people doing the task | Some users need a cleaner form or better mobile view | People need role-specific queues, forms, status views, or customer access |
Keep the spreadsheet when the grid still fits the job
Collaboration alone is not a reason to replace a spreadsheet. Modern spreadsheet tools already handle shared editing, history, validation, and controlled editing well enough for many teams.
Microsoft documents co-authoring and version history in current Excel. The experience depends on supported Microsoft 365 clients, sign-in, cloud storage, and AutoSave. Google Sheets can restrict who edits a sheet or range. Those are useful controls, and they may be all a small trusted group needs.
Keep the sheet for one-off analysis, modelling, reporting, or a process where the same people can safely see and change the same data. A replacement app creates another system to own, test, pay for, and maintain. That cost should solve a real operating problem.
If the difficulty is inconsistent headings, merged cells, unclear file names, or copied versions, repair the workbook first. GOV.UK guidance recommends consistent column names and deliberate versioning, especially for business-critical spreadsheets. Those changes also make a later migration easier if the workflow grows.
An app should change the rules around the data
Moving columns into fields is not enough. The useful change is what happens between those fields: who owns the next step, which condition blocks progress, which evidence must be attached, and which person is allowed to approve the result.
Google explicitly warns that protected Sheets ranges should not be treated as a security measure. People with file access may still be able to copy or export content. Where different people need different records or actions, a well-designed application can enforce those decisions on the server instead of relying on hidden tabs or careful behaviour.
OWASP recommends least privilege, denial by default, permission checks on every request, appropriate logging, and tests for authorization logic. These are design requirements, not benefits that appear merely because a spreadsheet was imported. Ask any app provider how those controls are enforced and tested.
A renewal tracker shows where the threshold moves
A renewal tracker with one owner and a shared status column is a sensible spreadsheet. The owner can sort by renewal date, filter by status, and label overdue records. The workflow scores near the bottom of the table.
Now add assigned account owners, evidence checks, manager approval, restricted commission fields, ageing queues, and a record of who approved each renewal. That version scores near the top. The number of rows may be unchanged; the organisation now cares about the order of decisions, permission boundaries, and accountable hand-offs.
This distinction prevents an expensive mistake. You are not replacing Excel because it looks untidy. You are testing an app because the business process now needs rules that the grid should not be expected to enforce.
Move one workflow without copying every spreadsheet habit
Start with one real record and follow it from entry to completion. Note who touches it, the decision each person makes, the information they need, the exceptions they handle, and the point at which the work is truly finished.
Bring the spreadsheet as evidence, not as the finished design. Its columns reveal useful data. Its formulas may reveal rules. Colour, comments, and side messages often reveal gaps that need a proper status, reminder, or approval step. Some layout choices exist only because a grid had to serve every role at once; an app does not need to preserve them.
Build a private working version before changing live work. Use realistic test records, include awkward exceptions, and let the people who do the task try it. The pilot should answer a narrow question: does this version make ownership, access, rules, and next actions clearer than the repaired spreadsheet?
- Name the event that starts the workflow and the result that finishes it.
- List each role and the records or actions that role may access.
- Write down the conditions that must block progress or require approval.
- Test a normal record, an incomplete record, and a difficult exception.
- Choose who approves the live release and what happens if the new version fails.
KasiLabs builds the workflow, not a workbook clone
With KasiLabs, you describe the work in plain language and shape tailored software around it. A spreadsheet can supply sample records and business rules, but KasiLabs does not claim to convert every formula, macro, layout, or exception automatically.
Work begins in a private version that selected people can review. Customers choose access roles and spending limits, approve the version that goes live, and keep earlier releases available if they need to step back. The point is deliberate control over the workflow, not a one-click file conversion.
KasiLabs is not the right move when the score is low, when a team mainly needs Excel formula parity or pivot-driven analysis, or when nobody can own testing and future changes. In those cases, improve the spreadsheet and keep using the tool that already fits.
Make the decision with one real record
Pick a recurring workflow, document one record from start to finish, and score it. If the score is low, fix the workbook. If it is high, describe that single workflow and create a private working version before anything goes live.