How to choose the right IT partner for your business

Hiring an IT partner is one of those decisions that quietly shapes the next five years of your business. Get it right and you have a team that prevents problems you never notice. Get it wrong and you spend weekends wondering why your invoice system is down again.

This guide is for the business owner who isn't sure what "good" looks like from the outside. No jargon, no sales language — just the questions I'd ask if I were in your chair.

Look for someone who asks questions before quoting

A good IT partner will not send you a price sheet on the first call. They will ask what your business actually does, who depends on what, what kept you up last month, and what "busy season" looks like. If someone quotes you a monthly retainer before understanding your operation, that retainer exists to cover their uncertainty — not your needs.

Three questions that separate good from generic

Try these on any prospective partner. The answers tell you everything.

1. "Can you walk me through the last time a client of yours had an outage, and what you did?" Real partners tell you a story — often one that includes a mistake they learned from. Generic vendors pivot to a marketing slide about SLAs.

2. "Who on your team would be assigned to us, and can we meet them?" If the answer is vague or the sales contact tries to keep you on their side of the wall, that's a warning. You want to know the engineer, not just the account manager.

3. "What's the one thing we're probably doing wrong that most of your clients also get wrong?" The willingness to give you a free uncomfortable truth on the first call is a remarkably reliable signal.

Red flags worth walking away from

• Long contracts with no exit clause. A partner confident in their work doesn't need to lock you in for two years.
• No written incident history. If they can't tell you how many tickets they handled last month, they're not measuring.
• One-person shops with no backup. Brilliant people get sick, take holidays, and occasionally quit.
• Reluctance to document. Anything built without documentation becomes tribal knowledge, and tribal knowledge walks out the door.

What a good engagement looks like in year one

The first ninety days should feel like an audit, not a sales pitch. Your partner should produce a written snapshot of what you have — servers, subscriptions, backups, people with admin access, licences expiring soon. That document alone is often worth the first year of fees, because most businesses have never had one.

From there, the good ones propose a small list of the highest-impact improvements. Not a two-year transformation roadmap. A small list. The transformation emerges from doing the small list well.

The quiet test

Here's my favourite test. Ask your prospective partner a question that's slightly outside their comfort zone — maybe something about your industry, or a regulation you're unsure about, or a tool they haven't used. Watch what happens.

A bad partner bluffs. A mediocre one deflects. A good one says "I don't know — give me until Friday and I'll come back with an answer." Then on Friday, they come back with an answer.

That's the person you want on your side.