The custom application should simplify the specific process. See how to assess the need, describe the user's scenario and choose the scope of the first version.
Name the problem that comes back at work
An individual web application is justified when solving an identified problem. It can order applications, help in product configuration or share information with customers. The idea of “we need our own system” requires clarification of what does not work today and who bears the cost of this limitation.
Describe the current process, even if it uses sheets and e-mails. Select where the information is prescribed, where the responsibility is lost and at what stage the user is waiting for the decision. This allows to assess whether an application, integration of existing tools or a simpler change in the organisation of work.
Run one scenario from start to finish
Choose a typical task and set out the next steps. Who enters the data? Who verifies it? What result does the customer receive? Add emergency situations such as no attachment, withdrawal of the notification or the need to correct.
Do not start with a long list of screens. Views are based on tasks and permissions. If two people see the same data, but can perform other actions, the project should take this difference into account. This affects the application range more than the button color.
Example: Valuation configurator
Suppose the company wants to reduce the number of incomplete queries. The prototype can collect several parameters and show what information is still missing. It does not have to automatically set prices if the final valuation requires an expert assessment.
Test such a model on examples of applications. Check whether users understand fields, whether the team receives the necessary data and if there is a way for an unusual case. Only then it is worth deciding which actions to automate in the next version.
Establish the conditions of maintenance
Your own application requires care, documentation and how to develop your function. Ask for data copies, access management and transferability before you start. If the solution connects with external services, take into account their limitations and changes.
- One main problem and a measurable result of the first version.
- Description of users, data and responsibility.
- The prototype of the most important path, also with incorrect data.
- Maintenance plan and owner of further decisions.
You can read about the requirements in the text custom software, and the differences between service types — in the material web pages and applications.
