sergio@arzani.it
Business software and web apps

When Excel starts feeling restrictive: deciding whether you need a web app.

Duplicate files and manual steps can reveal a process problem. Before developing software, let us identify it.

Studio Arzani · 10 November 2026 · 2 minute read

The Studio Arzani character organises sheets and tables into a simple dashboard, without showing real business data.

A spreadsheet can be a valuable tool. Problems arise when it becomes the meeting point for orders, customers, appointments and several people’s responsibilities, without shared rules. That does not mean it needs replacing immediately: it means it is worth observing how it is used and where it wastes time.

Let us find the steps that keep repeating

Is the same information copied into three files? Does a colleague have to ask which version to open every time? Do you need to reconstruct a conversation to find out how a job is progressing? These are signs worth noting, together with their frequency and consequences.

A hypothetical example: an enquiry arrives by email, is copied into a spreadsheet and then forwarded to the person responsible. The problem could be a lack of shared status information, rather than a lack of new software.

The first version should solve one specific problem

A web app can bring data and operations together in an environment accessible through a browser. We define users, permissions, fields, notifications and search around the actual work. The first version might simply record enquiries and show their progress.

Adding every imaginable feature immediately makes it harder to tell whether the system really helps. I prefer to agree on an initial scope we can evaluate, test it with the people who will use it and gather feedback before further development.

Let us consider what happens afterwards too

Importing existing data, exporting it, backups and maintenance should be part of the initial discussion. We also need to clarify who manages access when someone changes role or leaves the company.

Not every requirement calls for custom development: existing software or a review of the files may be enough. The discussion helps distinguish a particular requirement from a problem that simpler tools can solve.

Let us discuss the practical details

Tell me about a task that currently involves too many manual steps. We can map its workflow and decide together whether to improve the existing tools or design a dedicated management application.

Was it useful to you? Share it.

Let's talk about your project.

The request is sent directly from the site to Sergio Arzani. Privacy

Your project, in focus.

A few questions to understand what you need and prepare a tailor-made quote. If a detail is not yet clear, we define it together.

  1. 1. The project
  2. 2. Objectives and times
  3. 3. Your contacts
What kind of work do you have in mind?