Almost every business starts with a spreadsheet. It's free, anyone can use it and it adapts to whatever you need: one more column, a new tab, a color for what's reserved. For a while it works perfectly.
The problem is that a spreadsheet doesn't warn you when it stops being enough. It doesn't break overnight: it slowly fills up with versions, with the messages that travel alongside it and with people who depend on someone remembering to update it. A spreadsheet works until it doesn't, and you almost always notice too late.
This post is about deciding with judgment: when it makes sense to stay with the spreadsheet, when it makes sense to move to a web system and what that system should have to be worth it.
Five signs your spreadsheet is no longer enough
They don't all have to happen. If you recognize two or more, it's worth looking at the alternative:
- There are two versions of the truth. Two people edit it at the same time, someone downloads it to work in peace and ends up sending yesterday's. The file is called "final_v2 (1)".
- The client has yesterday's price. The price changed in the spreadsheet, but the PDF that went out on WhatsApp still says something else.
- Everything depends on someone remembering. Letting people know a reservation came in, asking for approval, sending the updated document, changing the status. If that person goes on vacation, the process stops.
- To know how you're doing, you have to ask for a report. How many units were sold, what's reserved, who sold what: the answer exists, but someone has to put it together by hand.
- Either everyone sees everything, or no one sees anything. A spreadsheet doesn't know who's looking at it. If an outside salesperson needs availability, they also see the costs, the margins and everyone else's reservations.
What changes with a web system
A management system is an application built around how your business works. It opens in the browser, with nothing to install, on a computer or a phone, and on the phone it can be added like any other app. Inside, it has four layers:
| Layer | What it solves |
|---|---|
| Your screens | What each person sees, on a computer or a phone |
| Your team | Users with roles: who enters data, who approves, who only views |
| Your rules | How an order moves, what expires, what needs approval |
| Your data | On your own server, with daily backups. If you ever leave, you take it with you |
The underlying difference comes down to one thing: the system keeps a single version of everything, and each person sees what's theirs to see. What used to be emails and messages traveling alongside the spreadsheet become part of the system: it asks for approval, sends the email, updates the link the client has and generates the PDF.
Note: A system doesn't replace anyone's judgment. It replaces the part of the job that's about remembering, copying and pasting, and letting people know.
A concrete example: a developer's availability
The clearest case is a real estate developer selling apartments off-plan. Availability lives in a spreadsheet: unit, type, square meters, price, status and who's holding it. That spreadsheet is used by the owner, the sales team, the real estate agencies selling the project and, through PDFs and screenshots, the buyers.
With the Sales Portal , the same information moves into a system where everyone has their place:
- The owner loads the projects and decides. No unit changes hands without their approval.
- El vendedor sees up-to-date availability and requests the reservation from the unit itself.
- The agency logs in with its own user and shares the projects under its own brand, following the owner's rules.
- The buyer gets a link that updates itself: when a price changes, the link already has it.
No new information was added. What got sorted out is who enters it, who approves it and who sees it. That's almost always the leap.
When it does NOT make sense to switch
A system has a build cost and an upkeep cost, so it isn't always the answer:
- If only one person uses the spreadsheet and no one else depends on it, it's probably enough.
- If the process still changes every week, it's better to wait until it settles: a system sets rules, and setting them too early is expensive.
- If the problem is the data, not the process (no one enters the information, or it's entered wrong), a system will make it more visible, but it won't fix it on its own.
The useful question isn't "spreadsheet or system?" but how much it costs you today, in time and in mistakes, to keep things as they are.
Off the shelf or custom-built
There are two paths, and it helps to know which one is yours before asking for a quote:
- An off-the-shelf product, with your brand. If your operation looks like that of other businesses in your industry, there are systems already running that get installed with your logo, your colors and your users. For example, the Fundraising Bingo for clubs, schools and parent associations, which you can try without signing up.
- A custom-built system. If the way you work is your own, it gets designed around it. There's no need to start from scratch: the pieces that repeat in almost every system (login with Face ID and two-step verification, users and invitations, approvals, shared links, PDFs and dashboards) are already proven in production, and that lowers both the timeline and the risk.
In both cases, the system is yours: it has its own database, on your domain, and it isn't shared with anyone.
Where to start
Before talking about screens, it helps to write down three things: which spreadsheets you use today, who touches them and which messages travel with them (the emails, the WhatsApp chats, the PDFs). That's the map of what a system would need to solve.
If you want to see what can be built for your industry, sistemas shows the ones already running and examples by type of business. And if you'd rather tell me about your case, a 30-minute call is enough to know whether it makes sense.