Short answer
Choose a software company by how well it understands your problem before proposing a solution, not by the lowest quote. Check that you will own the code and data in writing, meet the people who will build it, agree how requirements, changes, security and support are handled, and compare what each quote actually includes. A short paid discovery phase is often the safest way to test a partner.
01Start with the problem, not the technology
A good partner asks how your work actually runs before proposing anything: who does what, where information gets lost, what a better week would look like. A detailed proposal that arrives before anyone has understood that is a template, not a plan.
02Questions to ask before you sign
| Ask | Why it matters |
|---|---|
| Who owns the code, designs and data? | You should, outright and in writing, with access to the code repository from the start. |
| Who will actually work on the project? | Meet the people who will build it, not only the people selling it. |
| How do you work out the requirements? | A structured discovery phase stops you paying twice for the same feature. |
| How do you handle changes? | Changes are certain. Agree how they are estimated, approved and priced before they happen. |
| How will we communicate? | A weekly rhythm, one point of contact and working hours that overlap with yours. |
| How do you handle security and access? | Access control, secrets, backups, and who can see your customers' data. |
| What happens after launch? | Maintenance, fixes, hosting and monitoring, described and priced in writing. |
| Can we see similar work? | Live examples or references you can call, not only screenshots. |
- Ask
- Who owns the code, designs and data?
- Why it matters
- You should, outright and in writing, with access to the code repository from the start.
- Ask
- Who will actually work on the project?
- Why it matters
- Meet the people who will build it, not only the people selling it.
- Ask
- How do you work out the requirements?
- Why it matters
- A structured discovery phase stops you paying twice for the same feature.
- Ask
- How do you handle changes?
- Why it matters
- Changes are certain. Agree how they are estimated, approved and priced before they happen.
- Ask
- How will we communicate?
- Why it matters
- A weekly rhythm, one point of contact and working hours that overlap with yours.
- Ask
- How do you handle security and access?
- Why it matters
- Access control, secrets, backups, and who can see your customers' data.
- Ask
- What happens after launch?
- Why it matters
- Maintenance, fixes, hosting and monitoring, described and priced in writing.
- Ask
- Can we see similar work?
- Why it matters
- Live examples or references you can call, not only screenshots.
03Simple checks that take an hour
- Is the company registered? A trade licence or registration with the RJSC shows a legal entity you can contract with.
- Is it a BASIS member? Membership of the Bangladesh Association of Software and Information Services shows a registered software company. It is a sign of legitimacy, not a guarantee of quality.
- Do the people exist? Look up the founders and team leads on LinkedIn and check that their experience matches the claims.
- Do references answer? Call two past clients and ask what went wrong and how it was handled. Every project has problems; how they were handled is what you are buying.
- Is the contract clear? Scope, deliverables, ownership, payment stages, warranty and exit terms.
04Fixed price, time and materials, or milestones
| Model | Works when | Watch for |
|---|---|---|
| Fixed price | The scope is small and clearly defined | Every change becomes a change request, and quality can be cut to protect the margin |
| Time and materials | The scope will evolve as you learn | Needs regular reporting and an agreed budget ceiling |
| Milestones | A larger project splits into stages that are each usable | Define what “done” means for every stage before it starts |
- Model
- Fixed price
- Works when
- The scope is small and clearly defined
- Watch for
- Every change becomes a change request, and quality can be cut to protect the margin
- Model
- Time and materials
- Works when
- The scope will evolve as you learn
- Watch for
- Needs regular reporting and an agreed budget ceiling
- Model
- Milestones
- Works when
- A larger project splits into stages that are each usable
- Watch for
- Define what “done” means for every stage before it starts
When comparing quotes, line up what each one includes: discovery, design, testing, security, documentation, handover, training and support after launch. The cheapest quote often leaves several of these out and costs more later.
05Red flags
- A detailed quote without a single question about how your business works.
- A price far below everyone else's, with no explanation of how.
- No written agreement on intellectual property or data.
- You cannot get access to the code, the hosting or the domain.
- Every answer is yes. Good partners say no, or not yet, when something is a bad idea.
06Test the partnership before the big commitment
The safest way to choose is to work together on something small first. A paid discovery phase, or a first usable piece of the system, shows you in a few weeks how a team thinks, communicates, handles disagreement and delivers. It costs far less than discovering the same things halfway through a large project.
07If you are hiring from outside Bangladesh
Bangladesh is on UTC+6, so a working day overlaps with the Gulf, with Europe's morning and with most of Asia. Agree the overlap hours and the language of written updates at the start, put the contract and payment terms in writing, and hold a video call with the actual team before you commit.
Questions
How much does custom software cost in Bangladesh?
It depends on the scope, the number of user roles, integrations with other systems, security needs and who maintains it after launch. A short discovery phase is the most reliable way to get an estimate you can trust.
How long does a typical project take?
A focused internal tool can take weeks; a larger platform takes months. Splitting the work into stages that are each usable gets something working sooner and lowers the risk.
Should I choose the cheapest quote?
Compare what each quote includes: discovery, testing, security, handover and support after launch. The cheapest often leaves these out and costs more later.
Is a BASIS member company always a good choice?
BASIS membership shows a registered software company, which is a useful first check. Quality still has to be judged from the team, references, the questions they ask and a small piece of work together.
Last updated