You ask a simple question: how much does this customer owe us? Someone opens a sheet called "accounts FINAL 3", scrolls, checks a WhatsApp group to see if the last delivery went out, and comes back twenty minutes later with a number nobody fully trusts.
That's not a people problem. Spreadsheets and WhatsApp are brilliant tools for starting a business. They just weren't built to be its operating system. Once you have several staff, hundreds of orders and a few branches or delivery routes, they start costing you time, money and sleep.
This guide is for owners in that spot. It covers who actually needs a custom system, what it replaces, and how to build one in phases without betting the business on a single big launch.
Signs you've outgrown spreadsheets
Tick the ones that sound familiar:
- The same order is typed into a sheet, a WhatsApp message and an invoice
- Two people edit different copies of the same file
- You can't answer "what's our stock of X right now?" without calling someone
- Customer balances are checked by hand before every delivery
- An employee leaving means knowledge leaving with them
- There's no record of who changed what, or when
- Month-end reporting takes days and still needs corrections
- You avoid growing because the admin can't keep up
If you ticked three or more, a system will likely save more than it costs. If you ticked one, better spreadsheets may be enough for now.
Who doesn't need a custom system yet
Honesty first, because not every business should build software.
- Very small volume. If one person handles a few dozen transactions a month, a well-organised shared sheet is fine.
- A ready-made product fits. If a standard accounting or point-of-sale program covers almost everything you do, use it. Custom makes sense when your process is what makes you different, or when you're stitching several tools together by hand.
- Your process changes every week. Software freezes a process. Settle how you work first, then build around it.
What a custom system replaces
| Today | In a custom system |
|---|---|
| Orders sheet plus "is it done?" messages | Orders with a clear status that everyone sees live |
| Stock sheet updated at night, if at all | Stock deducted automatically when an order ships |
| Customer balances calculated by hand | A customer statement generated in one click |
| Daily numbers reported by phone | A dashboard with today's sales, open orders and collections |
| Files on personal laptops | One database, backed up, with user permissions |
| "Who changed this?" | An activity log: user, time, before and after |
| Reports built from scratch each month | Saved reports, exportable to Excel or PDF |
Notice the last line. Your accountant can still get Excel files. The difference is that Excel becomes an output of the system, not the place where the truth lives.
What a dashboard actually is
"Dashboard" sounds like charts. In practice, a business system is mostly a set of plain, fast screens:
- Lists of orders, customers, products or bookings, with filters and search.
- Record pages showing everything about one customer or order in one place.
- Forms for entering data once, with validation, so wrong phone numbers and missing fields get caught.
- Roles and permissions. Sales sees prices, the warehouse sees quantities, only the owner sees profit.
- The dashboard page itself, with the five or six numbers you check every morning.
Since it runs in the browser and is responsive, staff can use it on a phone or tablet without installing anything. A native mobile app can come later if field staff really need offline use or camera scanning. We cover that choice in app, website or both.
Build it in phases
The biggest risk in custom software isn't the code. It's trying to build everything at once, launching late, and discovering that half the features weren't needed.
| Phase | What gets built | Why this order |
|---|---|---|
| 0. Discovery | Map the real process, collect your current sheets, define roles | You can't automate what isn't written down |
| 1. Core workflow | The one process that costs the most time, plus users and permissions | Fastest visible return |
| 2. Visibility | Dashboard, reports, customer statements, stock | Built on real data from phase 1 |
| 3. Connections | Online payments, WhatsApp notifications, customer portal, e-invoicing | Only once the core is stable |
Each phase goes live and gets used before the next one starts. That way you pay for what you actually need, and phase 2 is designed around how your team really behaves, not how everyone guessed they would.
On integrations: sending automated WhatsApp messages at scale goes through the official WhatsApp Business Platform, which charges per message in ways that vary by country and message type, so check the current pricing. And if your company must issue e-invoices or e-receipts through Egypt's Tax Authority system, connecting to it can be part of phase 3. Confirm the exact requirements with your accountant first.
Moving your data out of Excel
Migration is where optimistic timelines go to die. Plan for it.
- Collect every sheet that's actually in use, including the "personal" ones.
- Clean it: the same customer spelled three ways, merged cells, notes typed in number columns.
- Decide what moves. Often only open orders, current stock and customer balances, plus a summary of history.
- Import once, check totals against the old sheets, and fix differences before going live.
- Run old and new side by side for a short, fixed period, then retire the sheet. Keep a read-only copy.
Cost and ownership
For a custom platform, dashboard or booking system in Egypt, an indicative range is 40,000 to 250,000+ EGP, depending on scope. Monthly maintenance typically runs 1,000 to 8,000 EGP. What moves the price:
- the number of workflows and user roles
- how many reports and how complex the calculations are
- integrations with payments, messaging, accounting or tax systems
- how much data needs cleaning and importing
- whether you need a native mobile app on top
Phasing also spreads the cost. Just as important: the code, the database and the hosting access should be yours. Read do you really own your website? before you sign anything, and use how to write a website brief to describe your process clearly. The same brief works for a system.
Common mistakes
- Copying the spreadsheet layout screen for screen instead of redesigning the process.
- Giving everyone admin access "for now".
- No automatic backups, or backups nobody has ever tested restoring.
- Skipping staff training and blaming the system when people fall back to WhatsApp.
- Choosing a developer on price alone instead of on how they handle discovery, ownership and support.
Questions people ask
Can my staff use the system on their phones?
Yes. A web-based system built responsively works in any modern phone browser, with no app store involved.
Will I still be able to get Excel files?
Yes, and you should. Any list or report can be exported to Excel or PDF for your accountant or your own analysis.
What happens when my process changes?
The system gets updated, which is part of the point of owning custom code. Small changes are usually covered under a maintenance plan, and larger ones are scoped as a new phase.
How is my data kept safe?
Encrypted connections, user permissions, an activity log, and regular automatic backups stored away from the main server. Ask any developer to show you how a restore works.
I run an education centre. Is this the same thing?
The principle is the same, but centres have specific needs like attendance, groups and parent follow-up. See running an education centre online and offline in one system.
Start with one workflow
You don't need to replace everything. Pick the process that costs your team the most time or causes the most expensive mistakes, and start there. Write down how it works today, step by step, including the WhatsApp parts.
If you'd like help turning that into a phased plan with an honest estimate, you can book a meeting with us.