7 signs your business needs a custom app
A business app is not justified by headcount or a wish to look modern. It becomes useful when important work relies on workarounds, scattered data, and decisions that are hard to follow.
06 chapters
The first sign: company size is not what blocks the work
Two people can already lose time if they send different versions of the same file back and forth, or if each interprets a rule differently. Conversely, a larger team can work well with an existing tool when the process remains simple and clear. The real signal is the daily cost of workarounds.
Before talking about software, count what comes back: re-entered information, manual reminders, calls to find a file status, searching emails, or corrections after an error. These are not isolated small irritations when they affect the journey used to sell, produce, deliver, or follow up with a client.
Signs 1 and 2: competing versions of the truth and duplicate data entry
The first signal is the question “which file is the right one?”. It appears when a spreadsheet circulates by email, one copy sits in a shared folder, and another tool holds different information. Nobody is trying to do poor work: the system simply does not provide a shared source.
The second signal is duplicate entry. A request arrives in an inbox, is copied into a spreadsheet, then into invoicing or tracking software. Every copy takes time and can drift. The Excel, Notion, or custom app guide helps separate what can stay a table from what should become shared data.
The irritants group into three system problems
Competing files, unclear approvals, and manual searches are not seven isolated accidents. They affect data, decisions, or shared knowledge.
- 01–02Data
Truth is scattered
Competing versions, re-entry, and repeated corrections make information drift.
- 03–04Decision
Control disappears
Approvals, permissions, and history no longer show clearly who may do what.
- 05–07Knowledge
The process stops transferring
Exceptions, rules, and indicators depend on people or manual reconciliation.
This is an editorial synthesis. France Num recommends choosing software by covered needs and real team use.
- Two people do not always see the same status.
- Information is copied between email, spreadsheet, and software.
- A correction must be repeated in several places.
Signs 3 and 4: approvals and permissions are no longer visible
Some stages need approval from a specific person: accepting a quote, checking a document, triggering an order, changing a price, or closing a file. When that decision is lost in an email, cell colour, or conversation, it becomes difficult to know who did what and what may move forward.
The fourth signal appears when everyone can access too much information, or must constantly ask someone for an export. A business tool can give each person the view they need, without multiplying files or exposing data unrelated to their work.
- An important stage depends on an untracked approval.
- Permissions are managed by sharing links or passwords.
- It is hard to see who changed a piece of information.
Signs 5 and 6: the process depends on one person and exceptions keep growing
The fifth signal is a business rule that exists only in one person’s head. They know why a column is red, which client needs different treatment, or which document is missing before moving on. While they are available, everything seems to work. When they are away, work slows down or errors appear.
The sixth signal is an accumulation of exceptions: “for this client, we do it differently”, “this file goes in another spreadsheet”, “we check manually before”. An application should not set every old habit in stone, but it can make rules explicit, separate them from rare cases, and prevent the most expensive omissions.
Sign 7: nobody can simply answer “where are we?”
When following activity means assembling several exports, asking the team for updates, or counting by hand, the business is always steering late. It does not necessarily need a large dashboard. First, statuses, deadlines, and responsibilities need to be recorded at the time work is done.
Custom software does not turn every task into a form. It gives a reliable view of progress and retains the history needed to understand a blockage. Indicators come afterwards, from data clean enough not to tell a different story each week.
Start with one complete friction, not a giant new system
Seeing these signs does not mean every tool must be replaced. The best first delivery is often one journey: receive a request, prepare a quote, track a file, schedule an intervention, or centralise an approval. It should remove one friction end to end and remain testable with the people who actually do the work.
The next version is built from real cases, not an imagined feature list. The guide to turning a business process into a tool gives a simple way to observe that first step, set rules, and decide what should wait for a later version.
Move from an observed pain point to a tested journey
Public-service design guidance starts by understanding the problem and uses, then tests an answer before broadening the product.
- 01
Explore
Observe the work, people, data, and consequences of the problem.
- 02
Prioritise
Choose a complete friction whose outcome and current cost are visible.
- 03
Prototype
Make the journey testable without pretending to cover the whole future product.
- 04
Test
Let the people involved try simple cases and exceptions.
- 05
Measure
Compare time, errors, and backtracking before deciding what comes next.
Business, product, design, technical, and accessibility skills should remain involved through the lifecycle.
- Choose one priority journey with a beginning and an end.
- Have the first delivery tested by the people involved.
- Measure time, backtracking, and errors before and after.
- Keep a way to work manually if the tool is unavailable.
The remaining decisions
How many people justify a business app?
There is no threshold. Two people can already be blocked by competing versions or unclear approvals. The useful criterion is the cost of the workaround and the risk when information is wrong or missing.
Must every existing tool be replaced?
No. A custom tool can focus on the part that really causes trouble and connect to an existing CRM, accounting tool, or messaging service. Replacing what works is not the goal.
Does a business app need to be complex?
No. A useful first version may cover only one precise journey. Complexity often comes from a process that was never made clear, not from the number of screens needed.
Put the guide against a real project.
A few lines are enough: context, the main constraint, and the expected result.