A web app is a browser tool that finishes a job: a dealer order, a service case, an approval, a customer portal. The company website tells a buyer what the firm does. The app works with the people who sign in. Commissioning one because a website “should also have a panel” adds logins and care without a clearer enquiry.
When a custom tool is the right conversation
The same work moves every week through mail and spreadsheets, and the mistakes now have a cost. More than one role needs the same record. An ERP or CRM already holds part of the truth, and someone must say which fields are read and which are written back. That integration is the project, not a later extra.
If a standard product already carries the process, custom development should stay on the gap. Rebuilding a product the team could configure is a long way to the same screen.
When it is too early
If each customer is an exception and nobody will sign a single flow, write the process first. Code will preserve the argument. It will not settle it.
What the company should keep
Source, environment, access, and a named care scope. Users and data stay with the company. An application only one person can deploy is an operational risk. Care means defects, small changes, and a person who answers, with a boundary so the month does not become an open brief.