In short: an off-the-shelf product is the right choice when your process looks like most companies’ in your field. Custom software makes sense when the process is specific, data comes from several places or the team works differently from what a generic product imagines. The third way, often the fastest and cheapest, is to start from an existing platform (users, roles, forms, approvals, documents, integrations) and develop only what is truly specific to your company.
When an off-the-shelf product is enough
- Your process is common in your field: invoicing, accounting, payroll, e-mail, a simple CRM.
- You can adapt the team’s way of working to the software without real losses.
- You don’t need special integrations, or you only need the ones the product already offers.
- You want predictable costs, as a subscription, and fast implementation.
A simple rule: if during the first week of testing you haven’t said “it’s different for us” more than twice, the off-the-shelf product is probably enough.
When you need custom software
- The process is your differentiator: the way you receive orders, validate, produce or deliver is why customers choose you.
- Data comes from too many places (ERP, warehouse, website, spreadsheets, devices) and nobody sees it together.
- You have approval rules, documents or reports that no generic product covers without compromises.
- You have already tried a product forced to fit, and the team works in parallel spreadsheets to compensate.
The third way: a platform plus specific development
The common part of any business application is the same: users and roles, forms with validation, approval and signing workflows, document generation, audit log, import and export, API. In a project written from scratch, these components eat a large part of the budget before anything specific to your company appears.
When you start from a platform where the common part already exists and is used in production every day, development focuses on what is different: your process, your documents, your rules. The practical result:
- the first usable version appears after a few iterations, not after months of specifications;
- you pay for development around your process, not for generic features;
- security, backups and updates come as standard, like with a product.
Questions to ask the vendor
- What already exists and what is written from scratch? Ask for a concrete list. “Everything is custom” usually means everything is paid for.
- Who owns the code and the data? And what happens if you end the collaboration.
- Where does the application run? In the cloud, on a dedicated instance, or on your own server, including without internet access if you need that.
- How does it connect to the software I already use? API, database or files. A good vendor doesn’t ask you to change your invoicing software.
- What does the first version look like and when can I try it? Versions the team can try from the start, not just at the end.
- What happens after launch? Training, assistance, maintenance and development as the process changes.
- How is the code tested and reviewed? Automated tests written together with the code and review before production are good signs, whether the code was written by a person or proposed by an AI model.
How a well-run project goes
- Analysis. The vendor comes to see how you work today and you agree together on what the first version solves.
- Prototype. A first version with the main forms and workflows, which your people can open.
- Development in short iterations, with feedback after every step.
- Training on real data, with written and video guides.
- Support: the application stays maintained and changes along with your process.
The risks and how to avoid them
- Hundreds of pages of specifications before any code. Prefer a small first version in production and adjustments along the way.
- Dependence on a single person at the vendor. Ask about the team, documentation and typed code structured in modules.
- Integration left for the end. The connection to the ERP or the warehouse is tested early, in test mode.
- Security added at the end. Two-step authentication, roles, audit log and backups should exist from day one.
Frequently asked questions
How much does custom software cost?
It depends on how much of the application is written from scratch. On an existing platform you pay for the analysis, the development of the specific part, the integrations and support. Ask for a written estimate after analysis, not a price over the phone.
How long until the first version?
On an existing platform, the first usable version appears after a few iterations. In a project written from scratch, usually after months of specifications and development.
Can I start from an existing product and adapt it?
Yes, if your process resembles one already covered by a product. You start from that product and add only the differences.
What happens if the process changes in a year?
The application must be able to evolve. Ask from the start how changes are made, what they cost and who makes them.
At DataFlows we build custom applications on our own platform, the one our solutions for warehouses, pharmaceutical manufacturing, public institutions, documents and B2B sales already run on. See what we have already built or tell us what you want to solve.
