The Tactical LinkedIn Outreach Guide for UK Schools with Legacy Phone Systems (2026)

You built a list of UK schools with legacy phone systems using Origami. Now it’s time to book meetings. This guide walks you through the exact LinkedIn outreach campaign I’ve run to land demos with IT directors, headteachers, and school business managers who are ready to upgrade. You’ll get the full 3-touch sequence, qualification filters, and sending tactics—no theory, just what works in 2026.

Before we dive in, if you haven’t generated your list yet, start with how to build a list of UK Schools with Legacy Phone Systems That Are Ready to Upgrade. That post shows you exactly how to describe your ideal school in plain English inside Origami and get a verified, enriched list with names, emails, phone numbers, and company details—free with 1,000 credits and no credit card.

Now, let’s turn that list into conversations.

---

Step 1: Refine and Qualify Your Origami List for LinkedIn

Origami gives you a clean CSV of decision-makers, but you can’t just fire off connection requests blindly. Schools are bureaucratic beasts. The wrong message to a classroom teacher or a generic receptionist will burn leads. You need to segment for LinkedIn outreach in three ways:

1. Filter by job title. From your exported list, pull out anyone with these roles (they actually approve budgets or run the day-to-day IT):

• IT Director / Head of IT
• Network Manager
• ICT Manager
• School Business Manager (SBM) or Bursar
• Headteacher (especially in primaries where they double as decision-makers)

Remove admin assistants, classroom teachers, and site managers. They don’t buy phone systems.

2. Enrich with LinkedIn profiles. Your Origami export likely includes email addresses and full names. Use them to find the person’s LinkedIn profile. A quick Google search with “FirstName LastName SchoolName LinkedIn” works, or you can batch upload the email list into LinkedIn Origami’s list view (using the “Upload via CSV” feature under Lists). Aim for a match rate of 70-80%. If someone doesn’t have a LinkedIn profile—common for older network managers—skip them for this campaign. They’re better reached by phone.

3. Qualify for “ready to upgrade.” Not every school with an old system is actively looking. Here’s the quick filter I use before adding someone to the sequence:

• Check the school website’s contact page. Do they still list separate phone numbers for each department with no mention of a central switchboard app? Green flag.
• Look at recent job ads on TES or school websites. Are they hiring a Network Manager with “VoIP migration” or “Teams telephony integration” in the description? Red-hot.
• If the school is a multi-academy trust (MAT), the CEO or central IT lead often talks about “consolidation” in public board minutes. A quick web search for “[Trust Name] digital strategy” reveals pain.
• Is the school still on an ISDN line? The PSTN switch-off happened in 2025, but Ofcom data shows a chunk of schools asked for short-term extensions. By 2026, those extensions are running out. If the school hasn’t been actively talking about their cloud migration, they’re likely feeling the heat.

Segment your final LinkedIn list into two buckets: High intent (signs of active search) and educative (known legacy system but no visible trigger). The outreach sequence will be the same, but high-intent prospects might skip the educational touch and move faster to a call.

Now, let’s write the messages.

---

Step 2: The LinkedIn Origami’s Sequencer Sequence (Copy, Paste, Customise)

School IT staff receive an ocean of generic “cloud migration” pitches. Your sequence needs to sound like you’ve actually spent time inside a school server room—because I assume you have. The following 3-touch sequence references the specific pain points of UK schools in 2026: the PSTN switch-off hangover, Ofsted’s increasing focus on digital safeguarding, budget freezes, and the nightmare of maintaining 15-year-old Panasonic or Avaya PBXs.

Each message is short (under 100 words), direct, and asks for nothing more than a crumb of engagement. Use your own tone. Replace bracketed fields with personalisation from your Origami list.

Touch 1: Connection Request (Day 1)

Note (300-character limit):

Hi [First Name], I help UK schools move off creaking phone systems without a six-month project. Noticed [School Name] might still be on an ISDN or on-prem system—especially now the 2025 switch-off extensions are ending. Connecting to share a few ideas, no pitch.

Why this works: It acknowledges a real deadline, shows you’ve done basic research (the school’s name), and frames you as a resource, not a vendor. The “no pitch” lowers the guard.

Touch 2: Follow-Up Message (Day 3 — only after they accept)

Subject line: Quick thought re [School Name]’s phones

Message:

Hi [First Name], cheers for connecting. Quick one—are you still dealing with line rental invoices that creep up every term? A couple of local schools we work with ditched their legacy PBX for a hosted VoIP layer last year. They saw line costs drop by 30-40% and got call recording for safeguarding. Not sure if that’s on your radar for this academic year, but I’ve a 2-minute case study from a similar-size school if useful.

Why this works: It mentions a specific financial pain (rising line rental) and a compliance trigger (safeguarding call recording). No jargon. The “not sure if that’s on your radar” is a soft qualifier that encourages a reply even if they’re just curious.

Touch 3: Final Message (Day 7 — soft close)

Subject line: One last thing

Message:

Hi [First Name], last note from me. I know your day is packed with WiFi dead spots and Chromebook updates. If the phone system is still a “we’ll sort it later” item, I’ve put together a one-page checklist: “5 Signs Your School’s Phone System Costs More Than a Cloud Switch.” No spam—happy to send it across. Otherwise, I’ll assume the timing isn’t right and leave you to it. Thanks for the connect.

Why this works: It empathises with their real daily chaos (WiFi dead spots, Chromebooks) and offers a low-commitment exit. The checklist is a pattern interrupt—busy IT managers love short PDFs. The soft close either gets a “yes, send it” or a polite no, both of which give you a next step.

Optional: If You Get a “Not Interested”

Short reply:

No worries, [First Name]. Quick favour—who on your team usually looks at voice tech? Happy to loop them in instead. If no one springs to mind, I’ll leave it. Thanks.

This often gets forwarded internally because you respected the no and offered a concession. You’d be surprised how many times the Network Manager reappears two months later when the old system finally falls over.

---

Step 3: Send and Track Your Campaign

You have the sequence. Now you need to deliver it without getting flagged by LinkedIn’s spam filters. Here’s the sending setup I use for UK schools:

Tool choice

• Manual (Origami’s list view + LinkedIn messaging): Best if you have 50-150 targeted prospects. Send connection requests manually from your personal profile, referencing each school’s name. Use Origami’s list view lead lists to track. Response rates are higher because every note is truly personal, but it’s time-consuming.
• Semi-automated (Origami’s Sequencer, or We-Connect): If you have 300+ prospects and have segmented heavily, you can run the sequence on autopilot. I’ve found Origami’s Sequencer safest for UK-based profiles because it mimics human delays. But—big but—school IT managers have sensitive LinkedIn spam radars. Automation only works if you’ve confirmed each profile matches exactly (same district, current role). A single request to a teacher will generate complaints.
• Never use LinkedIn InMail blasts for this audience. InMail open rates for education roles are abysmal. Stick to connection requests.

Sending limits Keep it to 20-30 connection requests per day. Schools move slowly. There’s no advantage to hitting 100 in a day; you’ll just burn through a year’s worth of leads.

What response rates to expect

• Connection acceptance: 25-40% if your targeting is tight and your note is personalised. Generic notes drop below 15%.
• Reply rate on the sequence: 8-12% overall across the three touches. High-intent schools can push 20%, but the “educative” bucket will be lower—around 5-6% reply.
• Meeting conversion: From replies, expect to book a call with 30-40% of those who engage. So for every 100 connections accepted, you’ll have 8-12 conversations and land 3-5 meetings.

When to iterate on messaging vs. iterate on the list After 2 weeks:

• If connection requests are being ignored (acceptance <15%), your note isn’t landing. Test a shorter version that just says “UK schools voice transformation” with no pitch.
• If messages get read but few replies, swap the Day 3 financial pain point for a safeguarding angle. Some schools care more about child protection than budget.
• If you’re still getting crickets, go back to list quality. Are you reaching out to schools that already switched two years ago? Use Origami again to re-run the prompt with a tighter definition—add qualifiers like “schools that haven’t publicly announced a cloud phone system migration.” The list is the lever; messaging is the finetune.

---

Wrap-Up

Cold outreach to UK schools isn’t magic. It’s a game of precision: right school, right person, right problem, right moment. Your Origami list does the heavy lifting by giving you accurate data. The sequence above turns that data into conversations. Start small—pick 30 high-intent schools from your list, copy the messages, and send over a week. Track your numbers. Tweak one variable at a time. Within a month, you’ll have a pipeline of schools that actually want to talk.

Next up: running the same campaign via email? That sequence is coming in our next post.