Off-the-shelf software or custom development?

A ready-made service should be considered first if it closes the main process and the team can test it on real tasks. Custom development becomes reasonable when the limitations of the finished product prevent mandatory operations from being performed. Between them, there is a third option: use a ready-made kernel, and link individual steps with integration.

At a meeting with a supplier, it is easy to compare the number of functions and forget about daily work. Below we will look at how to check launch speed, restrictions, data access and cost of ownership before the team transfers clients and orders to the system.

1. Describe your business workflow

Take one typical enquiry and take it from the first request to completion. Who accepts the enquiry, where does it store the files, who changes the status and what does the client see? Also write down two complex cases: for example, transferring a record and an order that is served by several employees.

For each step, indicate a required result. “The manager is comfortable to work with” is difficult to verify. “The manager sees his requests, the manager sees the entire queue, the client receives a message when transferring” can be reproduced in the demonstration. An example of the sequence of operations is in the article about the path of an enquiry from the site to the manager.

2. Check the existing service

Ask for trial access and instruct the future user to complete the enquiry themselves. Let him perform the usual task and correct the error: cancel the action, change the owner, or find the lost attachment. Note where instructions, manual transfer, or support assistance will be needed.

Write restrictions next to the task they affect. If you don’t have the filter you want, see if you can replace it with a view or report. If employees can see documents from other people’s clients, check the rights settings before uploading work data. These restrictions have different weights when choosing.

3. Estimate launch time

A ready-made interface reduces the amount of development, but setting up roles, transferring directories, training and testing integrations remains. Consider the launch to be the moment when an employee can carry out a work scenario and get the expected result. Registering an account is usually just the first step.

To develop from scratch, divide the launch into stages. First, you can collect the queue, enquiry card and basic statuses. Add complex reports and bulk operations as clear requirements emerge. An example of such a division is in the material about the Telegram Mini App admin panel.

4. Calculate costs after launch

Compare solutions for the same period. For the finished product, take into account the subscription, the required number of users, connecting integrations, data transfer and employee work. In your development calculation, include design, implementation, hosting, support and future changes.

Add a second calculation scenario: for example, a branch will appear or the number of enquiries will increase. Check which costs change with volume. Separately appreciate manual labor. If the operator transfers data from one system to another daily, factor this time into the calculation even if the subscription cost is small.

5. Check data export

Before choosing, find out whether you can get tickets, associated files, statuses and change history in a form suitable for transfer. Upload test records and open it outside the service. Check that it is clear which enquiry each document belongs to and whether the records can be matched to clients.

For your system, set the person responsible for storage, copying and recovery. A custom-developed program also creates a dependency if access to the server and recovery procedures are known to only one person. How to check a set of files and databases is described in the article about website backups.

6. Consider integrations

If a ready-made service handles requests well, but clients need a separate recording interface, these parts can be linked. For example, Mini App collects data and shows status, and employees work with the queue in the existing system. First, check that its exchange interface allows you to perform the necessary operations.

Decide in advance where the current status is stored and what will happen if the exchange fails. Who will see the error? Is it possible to repeat the transfer without a second enquiry? Who will correct the record if there is a discrepancy? The cost of integration maintenance should be included in the comparison on a par with subscription and development.

7. Compare pilot results

Summarize your observations in a short table. For each required scenario, indicate the result of the test, the restrictions, who is responsible for the configuration, and the remaining costs. Separately write down what you have assumed so far. For example, the supplier promised to upload attachments, but no one has opened the trial file yet.

If all the required scenarios have been completed, you can start with the finished product and reconsider the decision after the pilot. If one step requires regular manual migration, evaluate a separate integration. If the audit reveals several limitations in the main process, these scenarios will become the basis of the requirements for your system.

8. Agree the launch conditions

Before paying or starting development, agree on what is included in the first stage and how the team will accept it. Write down the required scenarios, the timing of data transfer, access rules, the person responsible for support and the way to obtain data when changing the solution.

To get started, just reproduce several work tasks from start to finish. It is easier to compare options based on the results of such a check than using lists of functions from presentations. Describe working scenarios and limitations in the brief to evaluate the finished service, integration and development according to the same criteria.