DesignJust4You / Project guide
Custom software development
-
01Process
Who does the work, with which data and business rules?
-
02Specification
Roles, features and delivery acceptance criteria.
-
03Development and testing
Testing individual parts with future users.
-
04Rollout
Data migration, training and agreed support.
Example workflow. The specific scope depends on the project.
Excel or custom software? If your team reconciles several spreadsheets every day, copies the same data and checks which version is the latest, it is time to reconsider how you work. The answer still depends on the process: sometimes an organised spreadsheet and clear rules are enough, sometimes an off-the-shelf business solution is suitable, and sometimes you need application development.
This guide helps you base your decision on specific tasks, the cost of manual work and employee needs. You can use it to prepare for a conversation about custom software development.
When is a spreadsheet still a good choice?
A spreadsheet is practical for records with a clear structure, occasional calculations and analyses managed by a small number of people. If you know who maintains the data, can easily check changes and do not have a complex approval workflow, first try improving your existing way of working.
Agree on consistent column names, required fields and a person responsible. Separate active data from the archive and check whether the same information is unnecessarily maintained in several places. Developing a new system will not resolve unclear business rules by itself: you need to clarify the same questions before programming begins.
5 signs that you need a different system
- You enter the same data several times. An email enquiry ends up in a spreadsheet, then in a quotation document and finally in another record. Every transfer means additional work.
- The status of a task is unclear. Employees have to ask a colleague whether a request has been processed, approved or is ready for the next step.
- Rules depend on the person. Deadlines, discounts or responsibilities exist only in someone’s memory, making it difficult for a new team member to take over.
- Different roles require different access. Sales, operations and management do not need the same data or the same editing permissions.
- Reports require manually combining data. Instead of seeing the current situation at a glance, the team spends time preparing figures from multiple sources.
These signs justify analysing the process. On their own, they do not yet mean you have to develop entirely new software.
Excel or custom software: where does an off-the-shelf CRM fit?
| Option | When to consider it | What to check |
|---|---|---|
| An organised spreadsheet | Simple records and a limited number of steps. | Data ownership, entry rules and change control. |
| An off-the-shelf business tool | A standard sales, task or support process. | Required features, data export, access permissions and the total cost of use. |
| Custom software | A specific workflow, several connected systems or requirements that an existing tool struggles to meet. | First-version scope, integrations, maintenance, security and how to retrieve your data. |
If the main problem is tracking customers and quotations, first consider a CRM solution. If data needs to connect to an existing store, accounting application or another service, check the options for API integration. Sometimes connecting existing tools is a smaller and more useful project than replacing them completely.
Example: from enquiry to approved quotation
The following example illustrates a process, not the results of a particular client. Imagine a company where a salesperson records an enquiry, a colleague prepares a calculation and a manager approves the quotation. All this information can be kept in spreadsheets, but it is important to have a clear answer to who is currently responsible.
The first version of an application for this process could cover recording enquiries, assigning a responsible person, status, deadlines and an approval record. Automatic messages, advanced reports and connections to other systems can be planned as later phases, according to actual need.
Before development, write down one typical request from beginning to end. Then add the exceptions: incomplete data, requests returned for revision and cancellations. These details determine how the system should work.
How do you assess whether the investment is worthwhile?
Start with the time the team actually spends repeating tasks. Multiply the number of hours per month by the internal hourly labour cost and add verifiable correction costs. This is an initial estimate of potential savings, not a promise that all those costs will disappear.
On the other side, add up development or subscription fees, data migration, training, hosting, maintenance and expected changes. Consider benefits that are harder to express financially as well: clear responsibilities, accessible information and easier onboarding of new employees.
What should you prepare for a software project estimate?
- A description of one process and the roles of the people who use it.
- An example of an existing spreadsheet’s structure, with personal and confidential data removed.
- A list of systems to connect and the available documentation.
- Three features without which the first version would not be useful.
- Access rules, the need for a change history and data export.
- An approximate budget, a preferred deadline and the person who approves decisions.
Include a trial with real users, validation of migrated data and a rollback procedure if something does not work as agreed. The transition should allow work to continue.
Want to check what suits your team? Send a brief description of your process through our free project estimate. If the system needs to run in a browser, also explore web application development.