Choosing a managed IT provider comes down to one thing most buyers never test: the model behind the pitch. The websites all promise the same things. The questions below expose how a provider actually makes money, who owns your documentation, who does the advising, and who owns the outcome when something fails. Ask all ten. The answers separate an advisor from a vendor in under an hour.
A note on reading the answers: you’re not listening for polish. Every firm on your shortlist has answered these before. You’re listening for specifics, for names, and for the occasional honest “no.” Vague is the tell.
1. Who owns the documentation of my environment?
Your environment — passwords, configurations, licenses, vendor accounts, how it all connects — has to be written down somewhere. The only question is who holds the pen. If the provider treats that knowledge as theirs, you can’t leave without pain, and both of you know it.
What a good answer sounds like: “You do — unconditionally.” The environment gets documented as part of onboarding, the documentation is kept current, and if you ever leave, it goes with you. Any hesitation here — “it’s proprietary,” “we’d have to prepare something” — tells you the exit is designed to be painful. Good providers keep clients with service, not with switching costs.
2. Who will actually be advising me — and will it be the same person in two years?
Most firms are sold by a senior person and serviced by whoever is next in the queue. Advice only compounds when the same person keeps your context. Every change of contact resets that clock to zero.
What a good answer sounds like: A name, not a role. You should hear who your advisor is, how long they’ve been with the firm, and why they’ll still be there. At owner-run firms, the answer is often the owner. If the answer is “you’ll have a dedicated team,” ask how long the last three clients kept the same contact.
3. How do you make money besides the monthly fee?
Hardware margin, license resale, project work — most providers have revenue riding on what they recommend. That doesn’t make them dishonest. It makes their advice worth auditing.
What a good answer sounds like: Straight disclosure, without flinching. Which products they resell, what carries margin, and whether anyone is paid on what you buy. Then the important part: a recommendation stands on its own reasoning, and they’re comfortable when you purchase elsewhere. If the strategy always ends in a purchase order, you’ve found the business model.
4. What do the first weeks look like if we switch to you?
Transitions are where vendors and advisors part ways fastest. A vendor wants your signature, and the cutover becomes your problem. An advisor has a sequence and can walk you through it before you ask.
What a good answer sounds like: A specific order of operations: map and document your environment before anything moves, build the new setup in parallel while the old one keeps running, then a quiet cutover — and they manage the handoff with your old provider so you don’t referee it. Vague answers here become loud problems later.
5. When something you manage fails, who owns the outcome?
Something will eventually fail. That’s not pessimism — it’s operations. What you’re actually buying is what happens next: one name behind the answer, or a circle of vendors pointing at each other.
What a good answer sounds like: “That’s on us” — said plainly, with an example. You want to hear how they handled a miss: what they fixed, what they changed afterward, and what it cost the client. The best version of that last part is “nothing” — you shouldn’t be billed for the incident a provider was hired to prevent.
6. Tell me about a time you told a client not to spend money.
This is the fastest advisor-versus-vendor test there is. Anyone can recommend more. Judgment shows up in the “no.”
What a good answer sounds like: A real story, recent and specific — a project they talked a client out of, a renewal they trimmed, a tool they removed instead of adding. Listen for subtraction. If every story the firm can offer ends with something being purchased, the advice is a sales channel with better manners.
7. How will you tie technology decisions to revenue, risk, and operations?
Technology spend that never touches the P&L is a hobby. Somebody at the table has to translate — what a decision earns, what it protects, what it makes possible on a Monday morning.
What a good answer sounds like: They start by asking about your business, not your firewall — how you make money, what an hour of downtime costs you, what your clients and insurers require. The roadmap that follows reads in business terms with reasoning attached, not a product catalog with dates on it. We’ve written about what that advisory role actually involves.
8. What does your security approach assume about a firm my size?
Attackers scan for targets of opportunity — the unlocked door, the forgotten account — not for famous names. A provider’s assumptions tell you whether they’ve thought about firms like yours or are reselling an enterprise playbook at a discount.
What a good answer sounds like: Plain language you could repeat to your own leadership team. The firm assumes you’re a target of opportunity, protects the user and their identity — not just the hardware — and can explain what’s allowed to talk to what, and why. Owning tools isn’t the same as managing posture; they should volunteer the difference.
9. Who answers when my people call?
The day-to-day experience of IT is a person with a problem and whoever picks up. If that person has to re-explain your environment every time, your team eventually stops calling — and small problems get big quietly.
What a good answer sounds like: People who already know your environment — not a stranger reading a script for the first time. Ask how on-site visits work and what they cost; the honest model doesn’t penalize you for needing a human in the room. Then put the same question to their references and compare notes.
10. Who owns your firm?
The IT industry changes hands constantly. Ownership decides whether the promises made in the sales meeting survive the next acquisition — the pricing, the staffing, and the person you signed up to work with.
What a good answer sounds like: A straight answer with names in it. If the founders still own and run the firm, the person accountable for the promise is the person who made it. A recent acquisition isn’t disqualifying by itself — but ask what changed for clients after the deal, and then call one and ask them.
One honest disclosure before you use this list
These ten questions favor a particular model: owner-run, advisory-led, documentation in the client’s hands, nobody paid by the product. We built Performance Connectivity around that model — three partners, same owners since 1997 — which is exactly why we’re comfortable publishing the list.
So take the disclosure at face value, and then use the questions on us as hard as you use them on anyone else. Good answers exist at more than one firm in Westchester. The point of the list is to make everyone give you theirs.
Choosing an IT provider isn’t a feature comparison — every proposal claims the same features. Ask who owns your documentation, who does the advising and for how long, how the firm makes money, and who owns the outcome when something fails. The answers expose the model behind the pitch, and the model — not the price — is what you’ll be living with for the next five years.
A few more fair questions
How many providers should we seriously evaluate?
Two or three. Enough to see real contrast in the answers, few enough that you actually check references instead of collecting proposals. The volume of quotes matters far less than the quality of the questions you ask each one.
Do we need a formal RFP?
For a 10–100-person firm, usually not. An RFP compares what vendors write; these questions compare how they think. An hour of conversation with each finalist, notes in hand, tells you more than a spreadsheet of checked boxes. If cost is the sticking point, start with what managed IT actually costs in this market so you’re comparing against a real baseline.
What if we’re mid-contract with our current provider?
Read the exit terms before you do anything else — notice period, equipment, data return. Make sure you can get out, and know what it costs. And before you leave, it may be worth raising your complaints directly: we’ve written about which problems are fixable and which are structural.
If you’re comparing providers in Westchester or Fairfield right now, bring your shortlist. Book a conversation and put the ten questions to us first — you’ll get straight answers, including where we’re not the right fit.
