Excel, Notion, or a custom app: which should you choose?

Recognise the real switch signals

Row count is not the best indicator. Useful signals are competing copies, formulas nobody dares to change, double entry, the absence of history, and access shared too widely. In Notion, the equivalent is pages that contradict one another, fragile linked databases, or no clear rule about which information is authoritative.

The need also appears when a business rule depends on one person. If their explanation is required to understand a cell colour, a tab name, or a page status, the process is no longer transferable. Custom software becomes relevant when it secures that knowledge and removes a measurable daily cost.

• Several files claim to be the current version.
• A formula error can change an operational decision.
• The same data is re-entered in several tools.
• Roles and validations cannot be applied clearly.

Build or buy: start from the business gap

An existing product remains the right choice when it covers the central process, integrates with tools already in place, and keeps an acceptable cost at the scale of the team. Building what already exists without a useful difference is wasted spend.

Custom development is justified when the rule that distinguishes the activity cannot be expressed, when licences grow with no relation to value, or when double entry persists despite the tool. A web application is often the simplest format for a shared desk; SaaS adds isolation across organisations and billing.

Treat data takeover as a project

Migrating does not mean importing every cell. Duplicates, implicit formats, invalid values, and the mapping between the old vocabulary and the new model have to be identified.

Takeover is repeated dry before cutover. Totals, relations, and sensitive samples are checked, then a rollback procedure is written. The new product can be correct and still fail if its starting data is not.

• Keep a frozen, readable copy of the source.
• Document transformations and rejects.
• Compare volumes and relations after import.
• Have a sample validated by the people who use the data.

Put rights, history, and backups in the core

A shared file rarely offers the fine-grained rights a business process needs. The new tool must distinguish read, edit, validation, and administration, then log the actions that commit.

Backups only count if a restore has been tested. Infrastructure and security therefore do not come after the screens: they are part of the first usable perimeter.

Ship by use and organise the handoff

The first lot must remove a complete friction, not reproduce half of the spreadsheet. A team adopts a journey that actually solves a problem more readily than a large product still incomplete.

The people concerned test early on their real cases. Gaps are recorded, useful old habits are kept, and a clear date ends dual systems. Stellary illustrates a product where roles, data, agents, and supervision share the same state. An estimate then lets the perimeter be set against a budget.