Signs that a file is no longer enough

A spreadsheet can remain a useful tool for calculations, one-off analysis or simple tracking. The question arises when a file becomes central to an entire activity, involving several people and rules that are difficult to follow.

• Versions keep multiplying. Several copies circulate, and the team is unsure which one to use.
• The same data is entered several times. Information moves from a file to an email, then into another tool.
• Approvals stay buried in messages. You have to search for who approved a request and when.
• Access rights become difficult to manage. Not everyone needs to view or edit the same information.
• Tracking depends on one person. Formulas, exceptions and working practices are poorly documented.

These signs do not automatically justify new software. They help identify what is actually getting in users’ way and what deserves closer analysis.

Choosing between three approaches

For sales and business management, a solution such as Dolibarr is worth considering before commissioning a complete development project. Custom business software serves a different need: adapting features to your organisation and the tools you need to connect.

An illustrative example: tracking field service visits

Imagine a company that schedules its service visits in a shared spreadsheet. Reports arrive by email, photos stay on phones and approvals are given verbally. This is an illustrative scenario, not a description of a client project.

The initial need may be limited: a shared service record, an assigned person, a status, documents and an approval step. If teams work in the field, mobile use and connection quality also need to be considered.

This first version lets you test a specific workflow. Advanced dashboards or further automation can then be considered based on user feedback.

Information to prepare before requesting a quote

You do not need a complete specification to start a conversation. Gather a few practical details:

1. Users: who carries out each task, in the office and in the field?
2. Steps: how does a request arrive, who handles it and who approves it?
3. Difficulties: where do repeated data entry, delays or errors occur?
4. Data: which files, documents and historical records need to be retained?
5. Existing tools: which software needs to remain in place or exchange information?
6. Access: who can view, edit, export or delete data?
7. Priorities: which problem should be solved first, and how will you verify the result?

Use anonymised examples to explain situations without unnecessarily sharing confidential data.

Start with a useful, manageable first version

A project benefits from starting with a specific workflow: creating a record, assigning a task, preparing a document or finding information. This makes it easier to define the screens, rules and tests to carry out with the team.

Data migration, training, hosting, backups and maintenance are part of project scoping. Their scope and everyone’s responsibilities should be agreed before the system goes live.

At DEV2PUB, we start with your business and your existing tools. Our consulting and requirements analysis services help you compare approaches, then prepare to integrate an existing solution or develop a custom tool.

Your questions before choosing

Can we keep some Excel files?

Yes. A project can retain useful files and focus the new tool on operations that need shared tracking. Imports, exports and integrations are assessed according to the available formats and access.

Do we have to replace all the company’s software?

No. Scoping identifies what should stay, what can be connected and which features are missing. Connecting tools can sometimes solve a problem without replacing the entire setup.

What budget should we plan for?

It depends on the features, users, data to migrate, interfaces and services to connect. An estimate is based on a clearly defined scope, including the planned ongoing support.