Choosing a software development company is easier when you stop comparing logos and start comparing evidence. Every shortlisted firm will show a polished portfolio and promise communication. Fewer will show you the commit history, the test suite, the handover document or the clause that gives you the source code when the relationship ends.
This guide is for a business owner or manager in Bangladesh who needs a system built, replaced or maintained. It covers vendor types, delivery criteria, a scorecard and the terms that prevent an expensive exit.
Know which problem you are buying
Before you talk to vendors, write one page covering the business problem, the users, the process today, the outcome you want and the constraints on budget and time. A new product, an integration and an augmented team are different purchases with different contracts. A firm that excels at building a new customer portal may be a poor fit for maintaining a ten-year-old ERP.
The five vendor types
Freelancer or small specialist team
Best for: a well-defined module, a short engagement or a specialised skill. Strength: direct access and lower overhead. Risk: key-person dependency, limited cover during illness or leave, and variable process maturity. Ask who else can access the repository and what happens if the freelancer is unavailable for a month.
Local boutique agency
Best for: business systems that need local context, on-site workshops and ongoing support. Strength: communication, time-zone alignment and knowledge of local payment, logistics and regulatory realities. Risk: capacity limits and uneven engineering depth. Ask how many people are full-time and who actually writes the code.
Offshore or nearshore agency
Best for: larger builds or access to specialised skills at a different cost base. Strength: scale and process. Risk: communication overhead, time-zone friction and handover complexity. Test written communication during the sales process, not after signing.
In-house team
Best for: software that is core to the business and needs continuous iteration. Strength: context, control and retention of knowledge. Risk: hiring time, management burden and the cost of covering specialised roles.
Product or platform vendor
Best for: a standard need such as accounting, HR or ecommerce where configuration beats custom code. Strength: faster start and a maintained product. Risk: limited differentiation, licensing escalation and difficult exit. Check the roadmap, data export and integration options before you commit.
Criteria that predict delivery
Relevant evidence, not a logo wall
Ask for two projects similar in complexity and domain, then ask the client reference three questions: what changed from the original plan, how the vendor handled a missed deadline, and whether they would hire the firm again. A portfolio image proves that a screen exists; a reference conversation proves how the firm behaves under pressure.
Team continuity
Meet the people who will do the work, not only the sales lead. Ask how long the proposed tech lead has been with the firm, what percentage of the team is full-time, and how knowledge is documented. High staff turnover is a delivery risk, especially in a long build.
Engineering practice
Look for version control, code review, automated tests, staging environments, issue tracking and a release process. Ask to see a sanitised pull request and a test report. A firm that cannot describe its definition of done is unlikely to produce maintainable code. NIST SP 800-218 and OWASP ASVS are useful references for the security expectations you can put in a contract.
Security and data handling
Ask where source code, test data and production data live, who has access, and how access is removed when a project ends. If the vendor claims ISO 27001 or another certification, verify it with the issuing body and confirm the scope covers the services you are buying. Do not treat a certificate as a substitute for contractual security obligations.
Commercial model
Fixed price suits a stable, well-specified scope. Time and materials suits discovery and evolving products. A monthly retainer suits maintenance and continuous improvement. Each model creates different incentives. Ask what happens when scope changes, how change requests are priced, and whether the estimate includes project management, testing and deployment.
IP, source code and exit
The contract should state that you own the custom code, documentation and data, and that you receive the repository, credentials, infrastructure configuration and third-party account ownership at handover. Avoid a clause that ties your application to the vendor's private framework unless you accept the lock-in. Ask for a knowledge-transfer period and a named exit checklist.
A weighted vendor scorecard
Score each vendor from 1 to 5, multiply by the weight and compare totals. Adjust weights to your context, but do not let price dominate.
- Relevant delivery evidence — 25%. Similar scope, verified references, measurable outcomes.
- Team and continuity — 20%. Named team, retention, local availability, clear ownership.
- Engineering and security practice — 20%. Code review, testing, documentation, access control.
- Commercial clarity — 15%. Transparent estimate, change process, total cost, payment milestones.
- Support and warranty — 10%. Response times, bug-fix period, maintenance options.
- Exit and IP terms — 10%. Code ownership, export, handover, no hidden lock-in.
Questions to ask about price
- What exactly is included: discovery, design, development, testing, deployment, training, warranty?
- Is the estimate based on a written scope, and what assumptions could change it?
- How are change requests priced and approved?
- Who pays for third-party licences, hosting, SMS and payment gateway fees?
- What happens if a milestone is late because of the vendor?
- What does support cost after the warranty, and what is excluded?
Our custom software team works on fixed-scope and retained engagements, and our pricing page explains how discovery, build and support are separated. For API-heavy builds, review our REST API design checklist during technical due diligence.
Run a paid pilot before the full build
A two-to-four week paid discovery or a thin vertical slice is the cheapest way to test a vendor. Give the same problem to two shortlisted firms and compare their questions, plan and working increment. Pay for the pilot; free proofs of concept are sales artefacts.
Red flags
- A proposal with no assumptions, no exclusions and no acceptance criteria.
- Reluctance to name the team or allow direct contact with a technical lead.
- No code repository access for your own organisation.
- A guarantee that the first version will be perfect and need no maintenance.
- Pressure to sign before you have spoken to a reference.
- A contract that assigns ownership of custom code to the vendor.
Metrics for the first 90 days
- Requirements agreed and changes logged.
- Working software demonstrated at each increment.
- Defects found in testing versus after release.
- Deployment frequency and time to restore a failed release.
- Documentation and handover items completed.
Sources
- International Organization for Standardization. ISO 9001:2015 Quality management systems — Requirements. Accessed 17 November 2026.
- CMMI Institute. CMMI Appraisal and Maturity Models. Accessed 17 November 2026.
- National Institute of Standards and Technology. NIST SP 800-218: Secure Software Development Framework. Accessed 17 November 2026.
- OWASP. Application Security Verification Standard. Accessed 17 November 2026.
- International Organization for Standardization. ISO/IEC 27001 Information security management systems. Accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.