The most convincing proposal is not always the safest one
A bespoke software project can become central to how a business operates. Choosing a partner based solely on price, design samples or a persuasive sales presentation can leave important risks unexamined.
A good supplier should be willing to clarify the problem, explain trade-offs and distinguish what is known from what requires discovery.
Look for relevant problem-solving experience
Experience in your exact industry can be helpful, but the strongest evidence may be experience with similar technical complexity: ageing systems, unusual calculations, difficult integrations, multi-party permissions or staged migration.
Ask for examples and customer references that the supplier is authorised to share.
Test whether they understand your business
Do they ask about the process, people, exceptions and commercial consequences? Or do they immediately propose a technology stack and an application with generic features?
A supplier that recommends a standard product when appropriate may be more valuable than one that insists every problem requires custom coding.
Compare quotations on the same scope
Request clarity about deliverables, assumptions, exclusions, integrations, migration, testing, documentation, hosting and support. Two very different prices may describe two very different products.
Understand the discovery process
For complex work, an initial discussion is rarely enough to produce a reliable fixed-scope quote. Ask how requirements will be documented and whether you can retain the resulting plan.
Clarify ownership and future independence
Understand who owns customer-specific code, what components are licensed, which third-party services are required and how another developer could maintain the system in future.
Check communication and governance
Who is the main contact? Who decides priorities? How are demonstrations, risks, changes and acceptance managed? Agree reporting and decision-making processes before the project begins.
Look closely at delivery and testing
Ask about staging environments, quality assurance, security practices, data migration tests and handling of edge cases. A plan should include more than a sequence of coding milestones.
Discuss ongoing costs
Understand hosting, maintenance, licence dependencies, security updates and further enhancements. A low initial price can be undermined by expensive long-term commitments.
Warning signs worth investigating
- A fixed quote with almost no questions about the requirements.
- Unclear IP or access arrangements.
- Unrealistic promises on timing, cost or business savings.
- No transparent change process.
- No credible plan for data migration or testing.
- Pressure to commit before the scope is understood.
A practical selection process
Shortlist suppliers with credible experience, give them the same written requirements and ask them to explain their assumptions. Assess clarity, commercial fit and ability to support the resulting system, not only hourly rates.
InfoForte’s approach is to begin with a free commercial discussion, followed by separately agreed paid discovery for serious bespoke projects. Clients retain the development plan and may use it to compare providers.
