PIPELINEGuide
Custom software: comparing providers — what really matters
Quotes for custom software are hard to compare because everyone writes something different. The questions that reveal the differences — and the warning signs.
When comparing providers for custom software, what matters less is the quoted price and more the question of what happens afterward: who supports the system after it goes live, and what does a later modification cost. That's the difference that only shows up after a few months.
01 — Criteria
How quotes differ
- What exactly is included. Two quotes with the same total can cover completely different deliverables. Ask for scope as a list, not as running text.
- Who delivers what. Content, images, data, access — if it's not specified, it becomes a point of conflict later.
- What operation costs. Calculated over three years, including licenses, hosting, and support.
- What happens if you want to switch. Do you get access, data, and documentation? The answer to this question says more about a provider than any reference.
- Who actually does the work. With small providers this matters: who sits in the meeting, and who then does it.
02 — Questions
Questions you should ask
- What happens if the project becomes more expensive than estimated — who bears that?
- Who owns data, access, and, if developed, the source code?
- What does operation cost in the second and third year?
- What does the documentation we receive at the end look like?
- How would you measure whether the project was successful?
- Is there a case in which you would advise us against this?
03 — Warning signs
When to be skeptical
- Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
- No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
- Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
- Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
- No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.
04 — Scope
What's included
- Requirements gathering with the people who will be working with it
- Implementation in small, usable steps instead of as a large-scale project
- Migration of existing data from spreadsheets and legacy systems
- Roles and permissions, logging, and backup from the start
- Integration with your existing systems instead of creating another silo
- Documentation and source code that belongs to you
05 — Questions
Frequently asked questions
Does this run on our own servers or in the cloud?
Both are possible. For most businesses, a cloud solution is lower-maintenance; where data must not leave the premises, we set it up on your own infrastructure.
How many users can a system like this handle?
That depends on the architecture, which we plan according to your expected growth — from a few users in your own business to several hundred across multiple locations.
When does custom software pay off compared to standard software?
When your process is a genuine competitive advantage, when standard software only fits seventy percent and the rest ends up as manual work, or when license costs per user exceed the development cost over a few years. If it's only about convenience, standard software is cheaper.
What happens if we no longer work together?
You have the code, documentation, and access. We deliberately use widespread technologies so that a switch is possible without someone having to rebuild everything.
How do we avoid the project going off the rails?
Small steps with usable results, fixed budgets per step, and the option to exit after each step. Large fixed-price projects over twelve months are the most reliable path to disappointment — for both sides.
Can we start with a spreadsheet?
Often yes, and that's a good test. If the spreadsheet maps the process and only fails due to multi-user capability, permissions, or data volume, the requirement is clear and the project is calculable.
Who owns the source code?
You do, completely, upon payment. That's in the contract. You can take it to any other developer — that's the point.
06 — Next
Related pages
- Custom software — Overview
- Custom software — Costs
- Custom software — Risks
- Custom software — Measuring success
- Custom software — Alternatives
- Custom software — Do it yourself
- Custom software — Funding
- Custom software — Prerequisites
- Process automation
- CRM integration
- API Interfaces
- All guides
Custom software by region
Next step
Send us a few sentences about your project.
We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.