Skip to main content
Legia

IT Support & Consulting

How to Evaluate an IT Vendor Proposal: Questions Worth Asking

A neat IT vendor proposal is not necessarily a complete one. This list of questions helps you assess scope, total cost, team, security, and ownership before you sign.

SEO and Content Specialist

6 min read

IT staff working at rows of office desks

Short answer: assess IT vendor proposals against criteria you set before opening them, then ask every vendor the same questions on five things: scope and deliverables, total cost over the system’s life, who does the work, security and data, and ownership and exit. Ask for the answers in writing. A proposal that cannot answer clearly usually hides costs or risks that only surface later.

The way most companies choose an IT vendor is by comparing the figure on the last page of each proposal. It is easy, but misleading: two proposals with similar figures can cover very different work, and the lowest one often leaves out licenses, maintenance, or integration. This guide lists questions you can put to vendors directly, written to be read alongside the proposal you are holding.

Before opening the proposals: set the criteria

The evaluation criteria should be agreed before the first proposal is read. Otherwise, the criteria tend to bend toward the most convincing vendor presentation. The US cybersecurity agency CISA, in its guidance for customers of IT service providers, advises procurement to collect a list of requirements from every unit that will use the service at the start of the process, and to make it the baseline for the decision. The NIST Cybersecurity Framework (CSF 2.0) also lists planning and due diligence before entering a supplier relationship as an outcome organizations should achieve.

In practice, three steps are enough:

  1. Write the requirements in one list, separating must-haves from nice-to-haves.
  2. Set weights for each group of criteria, for example scope, total cost, team, security, and ownership.
  3. Send the same list of questions to all vendors, so the answers can be compared side by side.
Illustration: IT support

Questions about scope and deliverables

Scope is the part of a proposal most often written vaguely. Ask:

  1. What is included, and what is not? Ask for a written list of exclusions, not only a list of work.
  2. What is the final deliverable? A running application, a document, installed equipment, or an ongoing service. Each needs handover criteria.
  3. How is the result tested and accepted? Who tests it, how, and what happens if the result is not yet right.
  4. How are mid-project changes handled? A good proposal explains that changes are logged separately, assessed for time and cost impact, and approved before the work proceeds.
  5. What is needed from your side? Access, data, team time for interviews, or decisions at certain stages. These dependencies are often why schedules slip.

Questions about total cost

The figure in the proposal rarely matches what you pay over the life of the system. Ask:

ComponentQuestion to ask
Licenses and subscriptionsWhich licenses are needed, in whose name, and what do they cost per year?
MaintenanceWhat does maintenance cover after the warranty period, and how is it priced?
IntegrationIs connecting to existing systems already included?
InfrastructureWhich servers, cloud services, or equipment must be provided, and who pays the bills?
Price increasesHow can the subscription price change in later years?
ExitAre there costs when the contract ends, for example for data export or handover?

If the vendor also buys equipment or licenses for you, ask whether the purchase is in your company’s name and whether the vendor receives a commission from the supplier. The answer shows whether its equipment recommendations are not driven by other interests.

Questions about the team and way of working

Proposals often show a company name, not the people who will do the work. Ask:

  • Who does the work, and whether part of it is handed to subcontractors.
  • How results are delivered in stages, so you can check progress before the end of the project.
  • Who is accountable on the vendor’s side, and how escalation works when there is a problem.
  • What happens if a key team member leaves mid-project.

Also ask for examples of similar work you can check and, where possible, contacts of clients willing to talk.

Questions about security and data

A vendor with access to your systems or data shapes your company’s level of risk. CISA advises customers to request several things before a contract is signed, including service level agreements that separate operational services from security services, incident handling guidelines that include compensation for outages, and an explanation of how data from different customers is separated. For software products, the Secure by Demand guide from CISA and the FBI adds questions such as:

  • Are multi-factor authentication and single sign-on available in the base product, not as a paid add-on?
  • Does the product still use default passwords?
  • How are security updates installed, and can they be automatic?
  • Does the vendor provide a software bill of materials (SBOM), including open source components?
  • Does the vendor have a public vulnerability disclosure policy?

Also ask who on the vendor’s side will hold access, whether that access is logged, and whether a confidentiality agreement is signed before access is granted. If the vendor processes personal data on the company’s behalf, its role under Indonesia’s Personal Data Protection Law should be clear from the proposal stage.

Questions about ownership and exit

This part decides how easily you can change vendors later:

  1. In whose name are accounts, domains, repositories, and licenses registered? Ideally in your company’s name from the start.
  2. Who owns the source code and documentation? For application development, the clauses are covered in the article Source Code Ownership in Application Development Contracts.
  3. What is handed over when the contract ends? Access, data in a format others can use, and configuration documentation.
  4. How healthy is the vendor? CISA notes that a vendor’s financial health can signal future service disruptions. Years in business, team size, and active clients help you judge it.

Red flags in a proposal

  • The scope is written in general terms, such as “all IT needs”, with no list and no exclusions.
  • Licenses, servers, or equipment are not mentioned even though they are clearly needed.
  • There is no acceptance test or handover criteria.
  • Accounts, domains, or code will be held in the vendor’s name.
  • The vendor is reluctant to answer written questions and only wants to explain through presentations.

How to choose an IT vendor from several proposals

Put every vendor’s answers into one table with the same rows: criteria on the left, one column per vendor. If one vendor answers a question the others did not, put that question to the other vendors in writing as well, so the comparison is fair. Score each criterion with the weights set at the start, and only then look at price. A proposal with a higher total cost can turn out more economical if it covers maintenance and licenses that the other proposals have not counted yet.

How Legia does it

In the IT Consulting service, a second opinion on a vendor proposal generally takes 1 to 2 weeks: Legia reads the proposal you received and assesses whether its scope, timeline, and cost are reasonable. For technology and vendor selection, Legia drafts the evaluation criteria and supports the selection process, including when Legia is not one of the bidders. The resulting document is yours, includes options that do not involve Legia, and can be taken to anyone else. Other situations where an outside view helps are covered in When Does a Company Need an IT Consultant?, and other services in this area are on the IT Support & Consulting page.

Frequently asked questions

Should the lowest-priced proposal be chosen?

Not automatically. Compare the total cost over the system’s life, including licenses, maintenance, and integration, then check whether the scope is the same. The lowest price often means a narrower scope.

Can we ask a vendor to revise its proposal?

Yes, and it is best done before deciding. Ask for a written revision when the scope, exclusions, or ownership are unclear, and give the other vendors the same opportunity.

Who should take part in evaluating proposals?

System users for fit with requirements, IT for the technical and security side, finance for total cost, and legal for the contract, personal data, and ownership.

Sources

Category IT Support & Consulting

Keep reading

Related articles

All Articles