Excel for Business: From Spreadsheets to Decisions

I build the systems that replace spreadsheets. Which makes the first thing I will tell you

surprising:

**In most cases where I am called in to build a system, a well-built spreadsheet would have been

enough — at a fraction of the cost.**

This course is written from that angle: not to teach you five hundred functions, but to make your

spreadsheet work, and to tell you honestly when you have genuinely outgrown it.

A spreadsheet is not a weakness

There is a common feeling that relying on Excel is "primitive" and that a serious company buys a

system. That is an expensive mistake.

A spreadsheet wins in four situations:

1. The process has not settled. You are trying a new way of working. A system freezes the method;

a spreadsheet changes in a minute.

2. Transaction volume is small. Twenty movements a day does not need infrastructure.

3. You need analysis, not recording. Scenario maths, comparing quotes, pricing models — a

spreadsheet beats any system.

4. You are the only user. No team, no permissions, no audit trail required.

In those four, buying a system is paying for complexity you do not need.

Where it genuinely breaks

And it does break — with known, specific symptoms rather than impressions:

• More than one person edits the same file, and "final version 3 last edit" appears.
• You need to know who changed what and when and cannot.
• Permissions are needed: the salesperson must not see costs.
• The data passed tens of thousands of rows and it became slow.
• You need a link to other systems, a website, or a till.
• Errors pass silently — a broken cell producing a wrong number in a report you then decide on.

Three or more symptoms = you have outgrown it. One or two = the fix is repairing the spreadsheet

rather than replacing it, and that is the rest of this course.

The middle road everyone skips

Between "an ordinary spreadsheet" and "a system" lie several steps that usually get jumped over:

The rule: do not jump from a spreadsheet straight to a system. Try the step immediately after

yours.

What you leave with

This course is entirely practical. You will build one real model from your own work — sales,

inventory, expenses, or customer follow-up — across the eight lessons: a clean table, working

formulas, analysis with a pivot, a decision dashboard, and protection against breakage.

Its output is a file you actually use, not an attendance certificate.

Excel or Google Sheets?

A question always asked, and the practical answer:

The rule: if more than one person edits daily → Sheets. If the data is large or you need Power Query →

Excel.

And everything in this course applies to both except where I flag otherwise. The concepts are the same:

table shape, separating data from reports, linking by code, and pivots.

Three mistakes that cost real money

Before we start, these are the ones I have seen cost companies money rather than time:

1. A pricing decision built on a broken formula. A range that misses new rows, so the margin looks

higher than it is. You price on that for months.

2. Inventory built on a file that does not match reality. You sell what you do not have, or your money

freezes in dead stock you cannot see.

3. Receivables lost because the follow-up sheet was not updated, or because one customer split into two

records through a spelling difference, so their balance looked half what it was.

None of the three produces a single error message. The file works, the number looks plausible, and the

decision gets made. That is why this course exists.

A note before you start: the separator

Before your first formula, settle this or you will lose an hour:

In many Arabic regional settings, **the argument separator is a semicolon ; rather than a comma

,**.

=SUM(A1;A10) instead of =SUM(A1,A10)

If you copy a formula from the internet and Excel rejects it, that is the reason nine times out of

ten. Try swapping the separators before doubting the formula.

And function names are written in English in almost all cases, even in an Arabic interface.

Action steps

1. Pick one real process you will build a model for across this course. Write its name.
2. Review the six symptoms: how many apply to you today?
3. If three or more, read the middle-road table and identify the step immediately after yours.
4. Type =SUM(1;2) and =SUM(1,2) in a cell, find out which separator works for you, and write it

down.