IT Outsourcing: Key Questions to Ask Before Hiring

IT Outsourcing: Key Questions to Ask Before Hiring

IT Outsourcing: Key Questions to Ask Before Hiring

IT Outsourcing: Key Questions to Ask Before Hiring

Quick Answer: What questions should I ask an IT outsourcing company before hiring?

Ask an IT outsourcing company to prove its security and data-handling claims with documents, not adjectives. That means requesting current ISO/IEC 27001 certification details, a SOC 2 Type II report with its date, a signed GDPR Article 28 data processing agreement, and clear answers about where your data will actually be stored and processed.

Certifications differ in weight: ISO/IEC 27001 is an international standard for an information security management system, while SOC 2 is an attestation prepared by an independent CPA firm. One is not a substitute for the other, and “aligned with” is not the same as “certified.”

Before signing, compare certificate numbers and expiry dates, report periods, subcontractor lists, data location, exit and data-return terms, named staff versus promised staff, escalation paths, and pricing for change requests. Ask for all of it in writing.

Why the Questions Matter More Than the Sales Pitch

Why the Questions Matter More Than the Sales Pitch

A polished proposal deck can make any vendor look enterprise-ready. The problem is that outsourcing puts someone else’s hands on your systems, your customer records, and your intellectual property. Once that happens, your risk is their operational habits.

The good news is that due diligence is mostly a paperwork exercise, and paperwork is hard to fake for long. Certificates have numbers and expiry dates. Audit reports have periods and auditor names. Contracts either contain a data processing agreement or they don’t. Asking precise questions separates vendors who invested in governance from vendors who invested in a website.

There is also a practical reason to ask early. Vendors who genuinely hold certifications answer in hours. Vendors who don’t tend to reply with “our internal processes follow those principles,” which is a polite way of saying no. That single exchange tells you a great deal about how the relationship will run.

Start With Security Certifications and Audit Reports

Is your ISO/IEC 27001 certificate current, and who issued it?

The current edition of the standard is ISO/IEC 27001:2022, published in October 2022 to replace the 2013 version. Ask for the certificate number, the certifying body, the scope statement, and the expiry date. Then check the certifying body’s public register yourself. A certificate that covers “software development in Warsaw” does not cover a support desk in another country.

Watch the language carefully. Certified means an accredited third party audited the management system. Compliant and aligned mean the vendor read the standard and believes it matches. Those are very different claims, and marketing teams blur them constantly.

Can you share a SOC 2 Type II report, and how recent is it?

SOC 2 reports are attestations issued by independent CPA firms under trust services criteria covering security, availability, processing integrity, confidentiality, and privacy. A Type II report covers a period of observed controls, typically six to twelve months, while a Type I report covers a single point in time. Ask which type you are receiving and when the observation window closed. A Type II report older than a year deserves a follow-up question about what changed since.

If your vendor also runs AI-driven support tools, the security questions multiply. A useful companion read is this breakdown of AI chatbot security questions to ask before buying, which covers model training data and prompt handling.

How do you manage risk day to day?

The NIST Cybersecurity Framework 2.0, published in February 2024, added a Govern function to the earlier five. It is voluntary, but it gives you shared vocabulary. Ask the vendor to describe how they identify, protect, detect, respond to, and recover from incidents, and who owns each step. Vague answers here usually mean nobody owns it.

Data Protection, Privacy, and Contract Terms

Will you sign our GDPR Article 28 data processing agreement?

The GDPR has applied since 25 May 2018, and Article 28 requires a controller to use only processors that provide sufficient guarantees, backed by a written contract with mandatory terms. The practical question is simple: will the vendor sign your DPA, or insist on theirs? Then ask where data will be processed, including support access from other countries, and which subcontractors touch it.

Which privacy and quality standards apply to you?

ISO/IEC 27701 extends the information security family into privacy information management, and ISO 9001:2015 covers quality management systems. For both, request the certificate number and expiry and verify with the issuing body. If card payments are in scope, ask whether the vendor is PCI DSS compliant and at what level; version 4.0 arrived in March 2022 with future-dated requirements taking effect on 31 March 2025.

What happens when we part ways?

This is the question almost nobody asks, and it causes the most pain. Ask for the termination assistance clause, the format your data comes back in, how long deletion takes, and whether you get a deletion certificate. If the answer is “we’ll figure it out,” you have found your biggest contract risk.

People, Process, and Delivery Capability

Who actually does the work?

Ask for the named team, their roles, and how much time each will spend on your account. Then ask what percentage of the team is on-site, nearshore, or offshore, and how turnover is handled. A common mistake is accepting a senior architect in the pitch and a rotating bench in month three. Put the named roles in the contract with a replacement-approval clause.

How mature is your process, and can you prove it?

CMMI is a process-improvement appraisal framework historically used to assess software and services organisations; version 2.0 was released in 2018, and the CMMI Institute was acquired by ISACA in 2016. If a vendor claims a maturity level, ask when the appraisal happened and who performed it. An appraisal from five years ago describes a company that may no longer exist in its current form.

For security operations specifically, this managed detection and response checklist walks through coverage hours, tooling, and escalation expectations.

How do you handle incidents and communication?

Ask for the severity definitions, the response-time commitments for each level, and the name of the person who declares an incident. Then ask for a redacted post-incident report from the last two years. Vendors who have never had an incident are either very lucky or not measuring.

Commercial Terms, References, and the Questions Vendors Hope You Skip

What is included, and what costs extra?

Get the pricing model in writing: fixed fee, time and materials, or retainer. Then ask what triggers a change request, how much notice you get, and what the rate card looks like for out-of-scope work. Ask about annual escalation caps and currency. The cheapest quote often becomes the most expensive contract once change requests start flowing.

Can I speak to a client who left you?

References from happy customers are table stakes. The revealing question is whether you can speak to a client who terminated the relationship, or at least to one in your industry with a similar system. Ask referees what surprised them, what they wish they had negotiated, and how quickly issues were resolved.

What does onboarding look like in the first ninety days?

Ask for a written onboarding plan with milestones, the documentation you will receive, and how knowledge transfer is verified. If the vendor cannot describe week one, week four, and week twelve, they are improvising.

A few more questions worth asking, in plain terms:

  • Which certifications appear on your website but are held by a parent company or partner?

  • Who is our escalation contact when the account manager is unavailable?

  • How do you handle staff departures on our account, and what notice do we get?

  • Do you use subcontractors, and can we veto specific ones?

  • What insurance covers a data breach caused by your team?

If you are also evaluating consumer-grade tools alongside enterprise vendors, the same instinct applies: check what is verified rather than what is claimed. A Rillabox review for buyers shows how product claims and actual terms can drift apart, and the same discipline of reading the fine print applies to outsourcing contracts.

How to Compare Vendors Side by Side

Once you have answers, put them in one table so the comparison is honest. A simple scoring approach works better than gut feel.

Question area What good looks like Red flag
Security certification Current ISO/IEC 27001:2022 certificate, verifiable “Aligned with ISO principles”
Audit report SOC 2 Type II, less than 12 months old Type I only, or refuses to share
Data protection Signs your Article 28 DPA, lists subcontractors “Our standard terms are non-negotiable”
Data location Named countries, named support access points “Cloud-based, location varies”
Team Named staff, replacement approval clause Senior pitch, junior delivery
Process maturity Current CMMI appraisal or documented SDLC Undated maturity claim
Exit terms Data return format, deletion certificate Silent on termination
Pricing Written rate card, change request triggers “We’ll scope it as we go”

Score each vendor from one to five per row, weight the security rows highest, and keep the evidence in a shared folder. When procurement asks why you chose a vendor, the table answers for you.

Conclusion

Hiring an IT outsourcing company is a trust decision dressed up as a procurement exercise. The questions above convert that trust into evidence you can check: certificate numbers, audit periods, signed agreements, named people, and written exit terms. Vendors who welcome those questions tend to be the ones worth hiring, because they have already done the work of proving it.

Ask early, ask in writing, and keep the answers. The conversation itself is the interview.

Frequently Asked Questions

Is ISO/IEC 27001 certification legally required to hire an IT vendor?

No. ISO/IEC 27001 is not generally a legal requirement, though sector rules in finance and healthcare may impose equivalents. It is a due-diligence signal that the vendor runs a managed information security system, not a legal gate.

What is the difference between SOC 2 Type I and Type II?

Type I covers controls at a single point in time. Type II covers a period of observed operation, typically six to twelve months, which makes it far more useful for judging whether controls actually work day to day.

Do we need a data processing agreement if the vendor never sees personal data?

If any personal data is processed on your behalf, GDPR Article 28 requires a written contract with mandatory terms. Even limited access, such as support staff viewing customer records, counts. Ask for the DPA and confirm where processing happens.

How many references should we ask for?

Three is a reasonable minimum: one current client, one in your industry, and one who has been through a renewal or a difficult incident. Ask each what they wish they had negotiated, and listen for patterns across all three.

Should we require a specific CMMI maturity level?

Not automatically. CMMI appraisals describe process maturity, not security or fit. If a vendor claims a level, verify when the appraisal happened and who performed it, then weigh it alongside certifications and references.

What is the biggest mistake buyers make in these conversations?

Skipping exit terms. Teams negotiate hard on price and onboarding, then discover there is no clause covering data return, deletion, or transition assistance. Ask about the ending before you sign the beginning.

on this page