What to Do When a Client Needs IT Services Outside Your Expertise

Last year a long-time managed services client of mine (a 30-person architecture firm I had been supporting for about four years) called me with a problem I could not solve. They had just won a government contract that required them to pass a cybersecurity compliance audit within 90 days. They needed a vulnerability assessment, a written security policy, and someone who could walk them through the audit process.

I handle their network, their workstations, their backups, and their day-to-day help desk tickets. I am good at keeping small office infrastructure running. But compliance auditing and security policy development? That is a different discipline entirely. I had two choices: try to figure it out on the fly and risk doing a mediocre job on something with real consequences, or connect them with someone who actually does this work every day.

I made the introduction to a cybersecurity consultant I had worked alongside on a previous project. She handled the engagement, the client passed their audit on time, and I earned a referral fee for the introduction. The client never left my ecosystem. I still manage their infrastructure, and they now see me as the person who solves their tech problems even when the solution is outside my own skill set.

That experience taught me something I wish I had figured out years earlier: referring specialized work is not losing a client. It is strengthening the relationship. Here is how I approach it now, from building a partner list to structuring the fee arrangement.

Why Freelance IT Support Specialists Hit Specialty Gaps

If you run a general IT support practice for small businesses, you are a generalist by design. Your clients hire you because you can handle the broad range of tech issues a 10 to 50 person office encounters: network configuration, workstation deployment, printer troubleshooting, email setup, backup management, basic security hardening. You are the person they call when something stops working and they do not know who else to ask.

But the IT landscape has gotten more specialized. Here are the kinds of requests I regularly encounter that fall outside what a generalist should handle:

• Cybersecurity assessments and compliance. Penetration testing, vulnerability assessments, SOC 2 preparation, CMMC compliance for government contractors. These require specific certifications, tooling, and experience that take years to build.
• Cloud migration and architecture. Moving a company from on-premise servers to Azure or AWS, setting up hybrid environments, configuring identity management across cloud platforms. This is a full specialty with its own certification tracks.
• Advanced networking. Multi-site VPN configurations, SD-WAN deployments, enterprise-grade wireless design for warehouses or multi-floor offices. A generalist can configure a small office network, but enterprise networking is a different scale.
• VoIP and unified communications. Deploying and managing phone systems, integrating video conferencing infrastructure, configuring SIP trunking. This is its own world with its own troubleshooting headaches.
• Custom software development and database work. A client wants a custom inventory system or needs their database restructured. Development is not IT support, even though clients assume their IT person handles everything with a screen.
• Data recovery and digital forensics. A crashed drive with irreplaceable data, or a suspected breach that needs investigation. Both require specialized tools and clean-room procedures that a general support tech should not improvise.

The temptation is to say yes to everything because you do not want to lose the client. I made that mistake early in my career: took on a cloud migration I was not qualified for, spent three weekends reading documentation, and delivered a setup that worked but was fragile and hard to maintain. The client ended up hiring someone else to redo it six months later. I would have been better off connecting them with the right person from the start.

Building a Partner List of Specialists You Trust

The foundation of good specialty referrals is having people to refer to. You need a short list of specialists, not a long list of names you found on Google, but a curated group of people whose work you have seen or whose reputation you have verified through shared professional connections.

What specialties to cover

Based on the requests I get from my small business clients, here are the specialties I keep covered in my partner list:

1. Cybersecurity consultant: vulnerability assessments, compliance work, incident response, security policy development
2. Cloud architect or migration specialist: Azure, AWS, Google Cloud platform design and migration
3. Network engineer: multi-site networking, SD-WAN, enterprise wireless, firewall management at scale
4. VoIP and communications specialist: phone system deployment, unified communications platforms
5. Developer or database administrator: custom applications, database design, integrations between business systems
6. Data recovery specialist: physical drive recovery, ransomware recovery, forensic investigation

You do not need five contacts in each category. One reliable person per specialty is enough to start. Two is better, because people get busy and you need a backup.

How to find and vet specialists

I built my partner list over about two years, mostly through three channels:

• Past projects where a specialist was already involved. The cybersecurity consultant I mentioned earlier. I met her because we were both working with the same client. She handled the security assessment while I managed the infrastructure remediation. I saw her work firsthand, knew she was thorough and communicated well, and added her to my list.
• Local IT professional communities. Most metro areas have IT meetups, MSP peer groups, or vendor-sponsored events where independent professionals connect. I attend a couple of these a year. The goal is not to collect business cards. It is to meet people, learn what they specialize in, and have a real conversation about how they work.
• Referrals from other IT generalists. I know three other freelance IT support people in my area. We do not compete because we each serve different neighborhoods and client types. When one of them finds a good specialist, they share the contact. This informal network has been my best source of vetted partners.

What to look for before adding someone to your list

• They communicate clearly with non-technical people. Your clients are small business owners, not CTOs. A specialist who talks over their heads or makes them feel stupid will reflect badly on you, even if the technical work is flawless.
• They respect your existing relationship with the client. This is critical. A good referral partner does not try to take over the client relationship or upsell services that overlap with your support contract. They do their specialized work and hand the client back to you for ongoing support.
• They deliver on time and follow through. When you put your name behind a referral, their reliability becomes your reliability. One missed deadline or ghosted follow-up from a specialist, and your client starts questioning your judgment.
• They are responsive. When your client has a cybersecurity scare or a server migration deadline, the specialist needs to respond within a day, not a week. Responsiveness is the single most common complaint I hear about specialists who do good work but are hard to reach.

Presenting the Referral to Your Client So They Stay in Your Ecosystem

This is the part where most IT support professionals lose the client without realizing it. They say something like: “That is outside my area, you should call this person,” hand over a name and number, and step out of the picture. The client calls the specialist directly, builds a relationship with them, and the next time they have any IT question (even one you could answer) they call the specialist first.

How you present the referral determines whether the client sees you as someone who could not help, or as the person who solved their problem by bringing in the right expert.

Frame yourself as the coordinator, not the bystander

When a client asks me for something outside my expertise, I never say “I cannot do that.” Instead, I say something like: “This is specialized work that needs someone with deep experience in cloud migrations. I work with a specialist who handles exactly this for companies your size. Let me make the introduction and I will stay involved to make sure the project connects properly with your existing infrastructure.”

That framing does three things:

• It positions the specialist as part of your extended team, not a replacement for you.
• It tells the client you are still their primary point of contact for technology decisions.
• It signals that you have a network of professionals you can draw on, which actually increases your value in the client’s eyes.

Make the introduction yourself

Do not give the client a phone number and walk away. Send a warm introduction email that connects the client with the specialist. Something like:

“Hi [specialist name], I would like to introduce you to [client name] at [company]. They are a managed services client of mine and they need help with [specific project]. I have attached a brief summary of their current setup so you have context. [Client name], [specialist name] has handled exactly this type of work for several of my other clients and I am confident she will take great care of you. I will stay in the loop as the project moves forward to make sure everything ties back into your existing systems.”

You are still in the middle of the conversation. The client did not have to go find someone on their own. The specialist has context before the first call. And both parties know you are involved.

Stay visible during the engagement

After the introduction, do not disappear. Check in with both the client and the specialist periodically. Not to micromanage, but to make sure the project is on track and that any infrastructure dependencies are handled on your end.

When the cloud migration specialist needs information about the client’s current server configuration, you provide it. When the cybersecurity consultant delivers findings that require changes to the firewall, you implement them. You are still the person managing the client’s technology environment. The specialist is handling one piece of it.

This involvement also protects you from the scenario where the specialist delivers something that does not integrate well with the client’s existing systems. You catch those issues early instead of cleaning up after the fact.

Follow up after the project completes

When the specialist’s engagement wraps up, schedule a brief call or visit with the client. Review what was delivered, make sure everything is working, and handle any loose ends. This reinforces that you are the ongoing technology partner and the specialist was brought in for a specific project.

I also ask the client: “How was the experience working with [specialist name]? Did they communicate well? Was everything delivered on time?” This feedback helps me decide whether to keep that specialist in my rotation, and it signals to the client that I am responsible for the quality of people I bring into their world.

Structuring the Fee Arrangement So You Get Paid When the Project Completes

Referring specialized work should not be free labor. You earned the client relationship over months or years of reliable service. Your introduction carries weight because the client trusts you. That trust has financial value, and a referral fee arrangement is the standard way to acknowledge it.

What IT specialty referral fees typically look like

The fee structures I have used and seen among other IT support professionals generally fall into two categories:

1. Percentage of the project value. The most common structure for larger engagements. A typical range is 10% to 15% of the total project fee. On a $12,000 cloud migration, that is $1,200 to $1,800. On a $6,000 security assessment, that is $600 to $900. The percentage scales naturally with the size and complexity of the work, which keeps the arrangement fair for both sides.
2. Flat fee per referral. Better for standardized services with predictable pricing. If a VoIP specialist always charges around $3,000 for a small office phone system deployment, a flat $300 to $400 referral fee is clean and simple. Neither party needs to verify the exact invoice amount.

When payment should happen

This is where most informal referral arrangements fall apart. You make the introduction, the specialist does the work, the client pays the specialist, and then weeks go by without the referral fee showing up. The specialist is not trying to cheat you. They just moved on to their next project and your fee slipped off their radar.

The solution is agreeing on payment timing before the first referral. The two models I have seen work best:

• Payment within 14 days of the specialist receiving client payment. This ties your fee to the specialist actually getting paid, so they are not fronting money before the client’s check clears. It gives them a two-week window to process the payment, which is reasonable for any professional running a real business.
• Payment at project milestones for longer engagements. For a six-month compliance project billed monthly, waiting until the very end to get your fee means waiting half a year. A better approach is tying your fee to each milestone invoice: when the specialist collects payment for phase one, your fee on that portion is due within two weeks.

Put the terms in writing

This does not need to be a formal document. A simple email exchange that confirms the fee percentage or flat amount, payment timing, and what counts as a qualifying referral is enough. Something like:

“To confirm: for clients I refer to you, I receive [X%] of the project value, payable within 14 days of you receiving payment from the client. This applies to the initial engagement. If the client engages you for additional work later, we can discuss whether that is covered separately.”

Having this in writing prevents the two most common problems with referral arrangements: ambiguity about how much is owed, and disagreements about when it should be paid. It also makes the arrangement feel professional rather than like an informal favor that either party can forget about.

What about repeat business from referred clients

This comes up when a referred client goes back to the specialist for additional work months or years later. My approach is simple: the referral fee covers the initial engagement. If the client contacts the specialist directly for future work without going through me, that is between them. If I make a new introduction for a new project with the same client, the referral terms apply to that new project.

Trying to claim a fee on every future engagement between the specialist and the client creates resentment and makes people reluctant to accept your referrals. Keep it clean: one referral, one fee, one project.

The Real Math: Why Specialty Referrals Are Worth Your Time

Here is what my specialty referral activity looked like over the past twelve months. These are my numbers from my practice. Yours will vary based on your client base, your area, and the specialists you partner with:

• Total referrals made: 9 client introductions to specialists across cybersecurity, cloud migration, VoIP, and custom development.
• Referrals that converted to paid engagements: 7 out of 9.
• Average specialist engagement value: approximately $9,500.
• Average referral fee earned: roughly $1,100 per converted referral (averaging about 12%).
• Total referral fee income: approximately $7,700 for the year.
• Time invested per referral: about 30 minutes for the introduction email, plus periodic check-ins during the engagement. Call it 2 hours total per referral, including the follow-up after the project finishes.

That works out to roughly $550 per hour for the time I spent on referral coordination. And those numbers do not account for the indirect value: every one of those 7 clients is still on my managed services contract. None of them left because I could not handle a specialized request. They stayed because I got them what they needed.

Compare that to what would have happened if I had tried to handle the work myself: I would have spent significantly more time learning and delivering a service I am not qualified for, the quality would have been lower, and I would have risked the entire client relationship if the result was not up to standard.

Mistakes That Undermine Specialty Referrals

I have made or seen each of these. Sharing them so you can avoid the learning curve:

• Handing over a name without an introduction. Telling the client “call this person” and stepping away. You lose control of the relationship and the client may not follow through, or they may find someone else on their own. Always make the introduction yourself.
• Referring to someone you have not vetted. A referral partner who does mediocre work or treats your client poorly damages your reputation, not theirs. The client will associate the bad experience with you because you made the connection.
• Waiting until the client asks for a specialist. The client may not even know they need one. When you notice a cybersecurity gap, a server infrastructure that has outgrown its capacity, or a compliance requirement they do not know about, bring it up proactively. This positions you as someone who looks ahead, not just someone who fixes what breaks.
• Being vague about the fee arrangement. “We will figure it out later” means one of you will be disappointed later. Set terms before the first referral.
• Trying to handle work outside your competence. The worst outcome is a botched project. The second worst is a mediocre result that the client has to pay someone else to fix. Both cost you more than the fee you would have earned by doing the work yourself.

Getting Started: Your First 30 Days

If you are a freelance IT support specialist who has been saying yes to everything or turning down specialized requests with a shrug, here is what I would do this month:

1. Identify the gaps. Look at the last 12 months of client requests. Which ones were outside your expertise? Which ones did you take on anyway and struggled with? Those are the specialties you need to cover in your partner list.
2. Find one specialist in your highest-priority gap. Start with the specialty that comes up most often. For most small business IT generalists, that is cybersecurity or cloud migration. Find one person you trust (through a past project, a peer recommendation, or a local IT community) and have a conversation about working together.
3. Agree on referral terms before the first introduction. A brief email confirming the fee structure and payment timing. Keep it simple.
4. Make your first referral using the coordinator approach. The next time a client needs specialized work, use the introduction method described above. Position yourself as the coordinator, make the warm introduction, and stay visible during the engagement.
5. Follow up and collect. After the engagement finishes, check in with the client, get feedback on the specialist, and make sure your referral fee is paid on time.

Building a specialty referral network does not happen overnight. But it compounds. Each successful referral strengthens your relationship with the client, validates the specialist as a partner you can rely on, and generates income from work you were never going to do yourself. Over time, your partner list becomes one of your most valuable business assets, because the IT support professional who can solve every problem, even when the solution is outside their own hands, is the one clients never leave.

If you want a simple way to formalize referral agreements with your specialist partners and track payments as projects close, take a look at what PureIntro offers for tech and digital professionals.

This post reflects one professional’s experience and is for informational purposes only. It is not business, legal, financial, or professional advice. Results described are individual and not guaranteed. Referral fee arrangements may be subject to state and local regulations. Consult a qualified professional for guidance specific to your situation. PureIntro facilitates referral tracking and payment processing but does not guarantee payments between users or any particular business outcome.