All questions

When a custom management platform beats Excel or off-the-shelf software

Excel and off-the-shelf software solve a lot, and you do not always need to build something of your own. The useful question is not which one is better, but when the tool you use starts costing you more work than it saves.

Signs that Excel is no longer enough

Operations live in spreadsheets and scattered messages, with no single reliable record. There are several versions of the same file and nobody knows which one is right.

Nobody can tell who approved, withdrew or changed something, or when. In a spreadsheet anyone can change a cell and the history is gone.

Everyone sees everything, or nobody sees what they need. Per-person or per-role permissions are hard to keep up in a shared file.

Systems do not talk to each other and the team duplicates work: what gets written down in one place has to be copied into another.

When off-the-shelf software is the right call

If your process is standard, off-the-shelf software is usually the best option: many companies have already tested it and you do not have to maintain it. A well-known CRM for a common sales process or an accounting system for your books are good examples.

The trouble starts when your process has its own rules that the tool does not cover: multi-stage approvals, lot-level traceability or steps that only certain roles can take. Then the team ends up adapting to the tool, with side spreadsheets to cover what is missing.

A custom platform makes sense when those rules are central to your business. It does not replace everything: it connects to what already works, like your CRM or corporate sign-in.

A real case: Atlas

Atlas is the clinical inventory platform I built for OmniStem. It is a single system of record for clinical supplies: what is in stock, which lot expires first and who withdrew each item.

The business rules sit at the center of the design. Allocation follows FEFO, meaning whatever expires first goes out first. Withdrawals are recorded with a QR code from a phone, right on site. Every movement is confirmed by a person with their role and a PIN, and it goes into an append-only ledger, where the balance is always derived from the history and never edited by hand.

Access uses Microsoft 365 corporate sign-in, so nobody manages yet another password. Inside, it follows a hexagonal architecture, which keeps the rules separate from the interface and the database so the platform can grow without turning messy.

How to decide

List the rules your process cannot break and check whether your current tool follows them without workarounds. If it does, keep it.

If following them depends on someone remembering or on a side spreadsheet, a platform of your own is worth discussing. In that case I start by writing down the expected behavior with Spec-Driven Development and build in stages, so the team sees working progress from the start.

Do you have a similar case?

Tell me how you work today and what you want to solve. Native Spanish; English (B2).

Custom Management Platform vs. Excel or Off-the-Shelf