In short: Write down the problem before talking to anyone, pick the right kind of firm, and ask who does the work, what is in writing and who owns the code, accounts and data. Keep domains and hosting in your company's name and start with one small piece of work before a larger project.
Choosing an IT consultancy is easier once you know exactly what you want fixed. Start with the problem, decide which kind of firm handles that problem, then compare a few on how they work: who does the work, what is in writing, who owns the result and what happens after launch. Start with a small piece of work before committing to a large one.
This guide is written for small and mid-sized businesses in Singapore. We are an IT consultancy ourselves, so we have tried to keep it useful whichever firm you pick.
1. Write down the problem, not the solution
Before talking to anyone, describe in a few sentences what is going wrong and what good would look like. For example: “Quotations take two days because the estimator works from paper notes and retypes everything into a template.” That is more useful than “we need an app”, because it lets a good consultancy suggest a cheaper answer if one exists.
Note who does the work today, which tools they use, how often it happens and where it gets stuck.
2. Decide which kind of firm you need
“IT consultancy” covers very different businesses.
- Managed IT services providers keep devices, accounts, networks and security running and offer a helpdesk. Choose one if staff cannot work reliably day to day.
- Software and automation consultancies build tools, automate workflows and connect systems. Choose one if your processes are slow or manual.
- Large consulting firms run enterprise programmes, such as replacing a core system across a big organisation.
- Product resellers sell and set up a specific software product.
Our comparison of IT consultants and managed IT services explains the most common split in more detail.
3. Shortlist firms that have built something similar
Ask each firm for examples close to your problem, and ask what they built rather than how much it improved things. A firm that has built a quotation tool, an enquiry workflow or a document process before will understand your edge cases sooner. Look at their own website and customer stories, and ask to speak to a past client if the project is large.
4. Check whether they will tell you not to build
A good consultancy will sometimes recommend an existing product, or a connection between tools you already have, instead of custom work. If every firm you speak to proposes a large custom build straight away, ask what off-the-shelf options they considered and why they ruled them out.
5. Ask who will actually do the work
Find out whether the people you meet are the people who will build it, or whether the work is passed to a team you have not met or subcontracted. Neither is wrong, but you should know who to talk to when something needs changing.
6. Get the scope and price in writing
The proposal should say what will be delivered, what is not included, how changes are handled and priced, and what support is included after launch. Fixed-price works for well-defined pieces; time-based billing suits work that will change as you learn. Either way, you should understand what you are paying for.
7. Agree ownership, access and data handling
- Code and documentation. Who owns them, and will you receive them?
- Accounts. Domains, hosting and key software accounts should be in your business’s name, with your own admin access.
- Data. What personal data will the system hold, where will it be stored, and who can see it? PDPC’s overview of the data protection obligations is a good reference.
- AI. If the work uses AI, ask which providers will process your data and whether it is used for training.
8. Ask what happens after launch
Software needs updates, fixes and small changes. Ask whether the firm offers maintenance, what response times it commits to, and how you could move to another developer if you needed to.
9. Start with a small piece of work
Rather than signing a large project on day one, start with one workflow or the smallest useful version of the tool. You will learn how the firm communicates, how it handles feedback and whether it delivers what it said, before you commit more.
Questions to ask in the first meeting
- Can you show us something similar you have built?
- What would you do if you were us, including options that do not involve you?
- Who will build it, and who do we contact afterwards?
- What is included in the price, and what is extra?
- Who owns the code, accounts and documentation?
- How do you handle our data, including with AI providers?
- What does support look like after launch?
Where to look next
Our list of IT consultancies in Singapore groups firms by type. If your problem is mainly about software, custom software development and workflow automation explain how we would approach it.
Frequently asked questions
What should I look for in an IT consultancy?
Look for a firm that has built something similar to what you need, explains options plainly including when not to build, puts the scope and price in writing, and leaves you with ownership of your code, accounts and documentation.
Should I choose a large or a small IT consultancy?
A small firm suits focused projects where you want to work directly with the people building it. A larger firm suits big programmes that need many specialists, formal project management or round-the-clock support.
Do IT consultancies in Singapore offer grants?
Some vendors offer solutions that qualify for government support schemes for SMEs. Check the current scheme on GoBusiness and confirm with the vendor that the specific solution you are buying is covered before you commit.
How do I avoid being locked in to one consultancy?
Keep admin access to your domain, hosting and key accounts in your own name, ask for the code and documentation as part of the agreement, and prefer common, well-supported technologies over unusual ones.