Skip to content

Learning series · Technology & AI · 7 lessons

From Spreadsheets to a System

Most Saudi businesses still run on spreadsheets, and there comes a point where the file stops being the solution and becomes the problem. A practical series on making the move: how to know the moment has arrived, how to inventory your files and clean your data, and what to migrate first so the business never stops for a day.

Start the series
From Spreadsheets to a System
7 of 7 published

Lessons in this series

  1. 01When the Spreadsheet Stops Being the Answer: Five SignalsThe spreadsheet is not the mistake, but it has a limit, and when your company passes it five clear signals appear. Copies multiply under near-identical names, one person knows how to update the file, the number changes depending on who you ask, nobody can say who changed what and when, and work stalls when the file owner travels. Part one of From Spreadsheets to a System names the five signals, explains what each one costs in practice, and closes with a five-minute exercise you can run today.Part 1 of 7 · 7 min read
  2. 02Inventory Your Files: Which Sheet Is the System?Before any migration, you need to know which file your company actually runs on, not which one you assume matters. Most companies hold dozens of sheets, but one or two carry the business and the rest are copies, reports and drafts. Part two of From Spreadsheets to a System gives you three questions that expose your real system of record, and ends with a single deliverable: a one-page list naming the file, its owner, what depends on it, and whether it has a backup.Part 2 of 7 · 7 min read
  3. 03Cleaning Data Before the Move: What Must Not Travel As-IsMoving unclean data into a new system moves the same mess into a more expensive place. Most of the sheets companies run on carry five recurring faults: one party recorded under several names, mixed date formats, numbers stored as text, columns nobody can define, and coloured cells holding unwritten meaning. Part three of the From Spreadsheets to a System series explains each fault and why it grows after the move, and ends with one rule: every meaning stored in a colour or in someone's head must become a written field before it travels.Part 3 of 7 · 7 min read
  4. 04What Moves First? A Migration Order That Keeps You TradingMoves from spreadsheets to a system rarely fail because the system is bad; they fail because a company tried to move everything at once while still trading. The order that protects the operation is simple: static data first — customers, items, suppliers — then transactional data like invoices and orders. Between them sits a parallel-running period with a declared end date, not an open one. Part four of From Spreadsheets to a System explains why that sequence and how to run the overlap without doubling your team's work forever.Part 4 of 7 · 7 min read
  5. 05Permissions: Who Sees What Once Data Leaves the FileA file has exactly one permission level: whoever opens it sees everything inside. Payroll, profit margins and customer data all sit in the same sheet in front of everyone who received a copy. The first thing a system gives you is not a prettier screen, but each person seeing only their own part. Part five of the From Spreadsheets to a System series covers how to set permissions without paralysing the work, and why customer data travelling as a file is a legal exposure rather than an untidy habit.Part 5 of 7 · 7 min read
  6. 06The Reports You Used to Build by Hand Every MonthA monthly report that takes two days to assemble is not a report, it is a collection exercise that finishes after the month it describes has gone. The time goes into gathering files, standardising their formats and reconciling numbers that disagree, not into analysis, and the decision that needed the number has passed before it arrives. Part six of the From Spreadsheets to a System series covers why a report inside a system becomes a view of the current moment, and which reports deserve automating first.Part 6 of 7 · 7 min read
  7. 07The First Thirty Days After the Move: What BreaksMost spreadsheet-to-system projects do not fail during the build; they fail in the first month of use. The data is migrated and the screens are ready, yet the team still keeps the old file open in the corner, gaps in the data surface at the first real transaction rather than before it, and training was delivered once on launch day and never repeated. Part seven of the From Spreadsheets to a System series covers what usually breaks in those thirty days, and a plan for getting through them.Part 7 of 7 · 7 min read

Want to apply this in your business?

In a free twenty-minute session we learn where you stand and suggest where to start.

Other series

Technology & AI7 lessons

How Do I Modernize My Legacy System with AI?

A practical series for every Saudi company that still depends on a legacy system that works but has become costly or risky: how to tell your system needs modernizing, how to inventory your systems before any decision, how AI extracts the business rules buried in old code, when to rewrite, migrate or replace, how to test and cut over without stopping the business, and where your data goes during modernization, with Amazon's AWS Transform as a live example.

Start the series

Technology & AI7 lessons

The AI Assistant for Your Business

A practical series for an owner considering an AI assistant to answer customers: what a slow WhatsApp reply actually costs, how an AI assistant really works without the jargon, how to build the company knowledge it answers from, how to stop it inventing prices and facts, where your employee's role begins and when they step in, what the Personal Data Protection Law requires of your customer conversations, and how to measure the return and roll it out in a week.

Start the series

Technology & AI9 lessons

ERP Systems: A Practical Guide

What an ERP actually is without the jargon, when you genuinely need one and when you don't, what it is made of with examples from Saudi sectors, how to choose between cloud and on-premise or off-the-shelf and custom, why ERP projects fail and how to make yours succeed, how to implement it successfully and manage the change, how to meet Saudi compliance from e-invoicing to Arabic localization, and where AI fits into modern systems.

Start the series