Selling a Chicagoland MSP: Contracts, Churn, Cybersecurity Risk, and Recurring Revenue Buyers Verify

August 11, 2025

Selling a Chicagoland MSP: Contracts, Churn, Cybersecurity Risk, and Recurring Revenue Buyers Verify

We had a Chicagoland MSP owner come to us after a buyer had already kicked the tires. Good company. Loyal clients. Smart techs. But the buyer asked for monthly recurring revenue by client, contract terms, churn, cyber insurance, ticket data, and proof the owner wasn't the only person holding the whole thing together.

The owner had most of it. Not all of it. So we paused, cleaned up the story, rebuilt the package, and went back to market the right way. Different result. Better buyers, better questions, better momentum. That's what prep does.

If you own an MSP in Illinois and you're thinking about selling in the next 1 to 3 years, don't wait until a buyer is staring at your Dropbox folder. Get the facts lined up now. You built a real business, recurring revenue, sticky clients, security work, cloud support, the whole deal. Now let's make sure buyers can SEE it.

Show what revenue is really recurring

Buyers love recurring revenue. No surprise there. But they're not going to take your word for it.

They'll want to know what's monthly managed services versus one-time work. Help desk support, cybersecurity monitoring, backup management, cloud administration, those usually get treated better than server migrations, cabling jobs, hardware resale, or emergency cleanup after something broke.

So break it out. For at least the last 3 years.

  • Monthly recurring revenue by client
  • Average contract value
  • Gross margin by service line
  • Revenue from managed agreements
  • Project, hardware, and emergency work split out

A plain income statement usually isn't enough. It's a start, sure. But a buyer paying real money for an MSP wants the deeper view. If your accounting doesn't separate this cleanly, fix it now. Not because it's fun. Because it pays you back at closing.

Clean up the client contracts

A lot of MSP owners say the same thing: our clients have been with us forever. Great. I like that. Buyers like that too.

Then comes the next question. Are they under written agreements?

Buyers will review contract length, renewal language, cancellation rights, price increases, service level commitments, and whether the contract can be assigned in a sale. That last one matters. If every contract needs client consent before it can transfer, the buyer is going to slow down and ask more questions.

Common contract issues we see:

  • Month-to-month with no minimum term
  • Old master service agreements
  • Services changed, contract didn't
  • No clear price escalation clause
  • Weak or vague cybersecurity language
  • Assignment language that creates friction

Does every client need a 3-year contract? No. Don't force something weird on good clients right before a sale. But know what you have, know what you're missing, and tighten what you can without making noise.

Pro tip: If your prices haven't moved while wages, software, and insurance costs went up, that's not a buyer problem, that's a pricing problem. And it's fixable.

Churn tells the story

Low churn is gold in an MSP sale. Every time.

Buyers want to see who came in, who left, who expanded, and who shrank. If a big client left last year, just explain it. Maybe they got acquired. Maybe they brought IT in-house. Maybe they were a bad-fit client who ate 80 support hours a month and complained about every invoice (we've all met that client).

And if revenue grew because existing clients added cybersecurity services, cloud support, backup management, or more users, document that. That's a strong story. That's exactly the kind of growth buyers want to see.

Client concentration matters too. You might have 40 clients, which sounds nicely spread out. But if one customer is 28 percent of revenue, the buyer is going to notice. Is that a deal killer? Usually not. But it may affect seller financing, earnout talks, working capital, or the transition plan.

Blunt answer: concentration is not fatal. Surprises are fatal. Don't surprise the buyer.

Cyber risk needs paperwork

This is where MSP deals get very specific, very fast.

You have access to client networks, credentials, backups, RMM tools, PSA data, endpoint systems, cloud environments, and security tools. Buyers are going to ask about ransomware, data breaches, failed backups, cyber insurance claims, and client disputes. They should. It's the business you're in.

Gather this before the buyer asks:

  • Cyber liability insurance policies
  • Errors and omissions insurance policies
  • Incident response procedures
  • Backup and disaster recovery documentation
  • RMM, PSA, endpoint, cloud, and security vendor agreements
  • Credential management policies
  • Client security assessment templates
  • Onboarding checklists

If your process is mostly in your head, get it out of your head. Put it on paper. Buyers don't expect a 12-person Illinois MSP to look like a national provider with 600 employees. But they do want discipline. Clear rules. Clear records. A sane way of handling risk.

Get the business less dependent on you

This one hits home for a lot of founders.

You built the thing, so of course you're still involved. Escalations. Sales calls. Vendor decisions. Quoting. Renewals. Big client relationships. The weird firewall issue nobody else wants to touch.

But buyers ask one simple question: what happens when you leave?

Start moving responsibility off your plate before you go to market. Can your team resolve most tickets without you? Does someone else run quarterly business reviews? Are quoting, renewals, onboarding, PSA workflows, RMM workflows, and billing steps documented? Do your techs know the process, or do they just ask you?

This doesn't mean you disappear. It means the business can stand up straight without you holding it by the collar.

Employee retention is a big deal too. Buyers will ask about technician tenure, certifications, pay plans, non-solicit agreements where enforceable, and whether the team is likely to stay after closing. A steady technical team in Chicagoland is a serious asset. Experienced tech talent isn't easy to replace, and buyers know it.

Margins and tools get checked

MSP buyers compare numbers. Gross margin. EBITDA margin. Revenue per employee. Ticket volume. Response times. Utilization. Client profitability.

If margins are light, that's not the end of the world. But you need to know why.

  • Legacy clients are underpriced
  • Too many software tools
  • Unused licenses
  • Some clients eat too many support hours
  • Project work isn't billed correctly
  • Agreement tiers are fuzzy

This is one of my favorite areas to fix because the upside can be fast. Tighten pricing. Clean the stack. Package services better. Stop giving away work that should be billed. Small changes can make the business easier to understand and more valuable.

Keep the sale quiet

Confidentiality matters in any business sale. With an MSP, it matters even more.

Your employees don't need rumors. Your clients don't need panic. Your vendors don't need gossip. And your competitors absolutely don't need a free look at your client list.

A good process uses blind marketing materials, buyer screening, nondisclosure agreements, and staged information release. Nobody should get client names, employee data, contract details, or cybersecurity documentation on the first call. No way.

At Tangent Brokerage, we release information in phases. First, we confirm the buyer has money, intent, and a real reason to be at the table. Then they get more. That's how you protect the company while still creating buyer interest.

Know which buyer fits

Not every buyer wants the same MSP.

A local IT firm may care most about client fit, geography, and technician capacity. A regional MSP platform may care about tool stack compatibility, recurring revenue, and cross-selling security services. A private equity-backed operator may focus on management depth, EBITDA, churn, and cash flow. An individual acquisition entrepreneur may want a stable team and a seller willing to train them for a while.

So who is best for you? Depends on your goals. Highest price matters, of course. But so do structure, transition, employee treatment, closing certainty, and what your life looks like after the deal.

Selling a Chicagoland MSP isn't just selling technology support. You're selling trust, recurring revenue, process, people, and proof. Package that correctly and buyers get excited. They should. A well-run MSP is a fantastic business.

FAQs

How far ahead should I prepare to sell my MSP?

Start 1 to 3 years out if you can. Even 6 months of cleanup on contracts, revenue reporting, and owner dependency can make a real difference.

Do I need all clients on long-term contracts?

No, but written agreements help. Buyers will look at term, cancellation rights, renewal language, pricing, cybersecurity language, and whether contracts can be assigned in a sale.

Will buyers care about past cybersecurity incidents?

Yes. Be direct and show documentation, insurance response, fixes made, and current procedures. A handled issue is much better than a hidden one.

Can I sell if one client is a large part of revenue?

Yes, but expect buyer questions. Client concentration may affect deal structure, seller financing, earnout terms, or transition planning.

How do we keep the sale confidential?

Use blind materials, screen buyers, require nondisclosure agreements, and release sensitive details in stages. Tangent Brokerage handles this carefully because loose talk can hurt a good deal.

Ready to talk about your MSP?

You built something valuable. Recurring revenue, client trust, a technical team, systems that keep other businesses running, that's real. Now it's time to find out what it could be worth and what kind of exit makes sense for you.

If you're preparing to sell a Chicagoland MSP, contact Tangent Brokerage at 630-862-5234 or request a free valuation. Let's get the story clean, the buyers lined up, and the next chapter moving.

← Back to Blog

Need Help? Send Us Your Query Below

* indicates required fields

FIRST
LAST

Privacy Policy