IT support keeps what you have running: devices, email, accounts, backups and the person who answers when someone cannot log in. A technical lead owns the bigger picture: how your systems connect, what you buy or build next, which suppliers you rely on, and the plan for the year. In our experience, owner-led firms with 15 to 150 staff have the first and often have nobody in the second job.
That is not a criticism of your IT provider. They were hired to do one of those jobs, and they probably do it well. The gap only shows up when a decision lands that is not a ticket.
What IT support does well
A good IT support provider, often called an MSP (managed service provider), handles the daily machinery:
- Setting up and replacing laptops and phones.
- Looking after Microsoft 365 or Google Workspace: users, licences, mailboxes, multi-factor authentication.
- The helpdesk: password resets, printers, “my email has stopped”.
- Backups, antivirus, patching and the security basics.
Security basics have a recognised baseline in the UK. Cyber Essentials is a government-recommended certification developed by the National Cyber Security Centre (NCSC). It is built on five controls: firewalls, secure configuration, security update management, user access control and malware protection. If your provider has not mentioned it, ask. The NCSC also publishes a free guide to cyber security for small organisations.
This work is a service with a queue. You ask, they fix. That is the right shape for it, and you should keep it.
What a technical lead does
A technical lead does not fix the printer. They are the person accountable for the answers to questions like these:
- What systems do we run, and how do they connect? Who owns each one, what data moves between them, and where does someone retype it by hand?
- Buy, build or leave alone? When the team asks for a new tool, someone has to weigh it against what you already pay for. Leaving a CRM is one of those calls, and our checklist for moving off GoHighLevel shows what it involves.
- Where does automation or AI fit? Quoting, invoicing, lead handling, reporting: which are worth doing first, and which are a distraction.
- Who are our suppliers, and are they any good? The web agency, the software vendor, the person who built the spreadsheet. Someone has to read their quotes and contracts and ask what happens if you leave.
- What is the website for, and is it doing that? A rebuild is the riskiest version of that question, and we cover it in how to rebuild a website without losing rankings.
- What is the plan for the next twelve months? In order, with rough costs, in plain English.
The test is what happens when a decision arrives that is not a request. A supplier sends a quote for a new system. A salesperson pitches an AI tool. Your finance director wants invoices to stop being retyped. IT support will tell you if the tool will run on your laptops. A technical lead tells you whether you should buy it at all.
Signs your business needs a technical lead
None of these means something is broken. Together they mean a job is not being done by anyone.
- The same information is typed into two or three places: quotes into the accounts package, website enquiries into a spreadsheet.
- A quote for software or a website arrives and nobody in the firm can say whether it is fair.
- When you ask your IT provider about software, the website or automation, the answer is that they only do support.
- One person understands how something works (a spreadsheet, a login, an integration) and nobody else does.
- You are being sold AI tools and have no way to tell which are worth a trial.
- Nobody can list the software you pay for, who uses it, or where your customer data sits in each.
- Decisions about systems are made by whoever pushed hardest or most recently.
If two or three of these are familiar, the signs your business has outgrown spreadsheets goes through the same ground from the operations side.
Three ways to get one
You do not need a full-time executive to fill this job. There are three routes, and each has a real downside.
1. Hire someone full-time. You get their whole attention and their knowledge stays in the firm. It is also the biggest commitment: salary, recruitment time, and a senior person who needs enough to build and a team to lead. In a firm with no engineers, there may be less than a full week of senior technical work, and a good person without enough to do can get bored and leave. It is also hard to hire for a job you cannot assess yourself.
2. Use a fractional technical lead. A senior person works with you for a fixed number of days each month, owns the plan and the decisions, and is accountable for outcomes. You pay for the days you need. The trade-off is that they are not there every day, so hands-on work has to be done by your IT provider, a supplier or someone in-house. Quality varies, so ask for references and ask what they have built, not only what they have advised. Our guide to when you need a fractional CTO covers what to expect, and the fractional CTO service page covers how we work.
3. Buy project by project. You pay a supplier for a defined piece of work, such as a quoting tool, a website or an integration, with a fixed scope and a written agreement. There is no ongoing commitment and a clear end. The downside is that each project is judged on its own. Nobody owns how it fits with the rest, and the supplier who builds it is also the one advising you whether you need it. We sell both of the last two, so weigh our view accordingly. How we price is on our pricing page.
A rough guide, not a rule:
- Under about 15 people, with one or two core systems: good IT support plus the occasional fixed-scope project is usually enough.
- Around 15 to 150 people, several systems, no one in the role: fractional is usually the best starting point.
- Constant technical work and a team to lead: that is when a full-time hire starts to make sense.
Keep your IT provider
A technical lead does not replace your IT support. They work alongside it, and they usually make the provider’s job easier, because someone is now deciding what they should look after.
Here is a simple split to show how the work divides:
| Job | IT support | Technical lead |
|---|---|---|
| New starter laptop and accounts | Yes | |
| Microsoft 365 licences and multi-factor authentication | Yes | Checks it is done |
| Backups running and tested | Yes | Checks it is done |
| Cyber Essentials | Usually | Decides if you need it |
| Quote for a new website or system | Yes | |
| Where website enquiries go and who answers them | Yes | |
| Invoice and quote data typed in twice | Yes | |
| Which AI tools staff may use, and with what data | Yes, with you | |
| Supplier contracts and renewals | Yes |
Print it, tick the rows that are covered in your firm today, and look at the blank ones. That is the job description. For the AI row, our one-page AI policy template is a starting point.
What it looks like in practice
I was CTO at Vanarama and helped scale it. The part of that job that carries over to a firm of any size is deciding what to build, what to buy and in which order. You can read more on my background and on the Vanarama work.
The same shape works at a much smaller scale. A construction firm in Hertfordshire came to us for a website. We then built an online quoting tool, and an invoice dashboard linked to Xero, where supplier bills are filed from the mailbox, matched to purchase orders and coded instead of being keyed in by hand. We now stay on a monthly retainer for ongoing technical support and for rolling out Claude with training for the team.
If you are not sure which of the two you need, book a 30 minute call. We will tell you plainly if the right answer is to keep your IT provider and change nothing else.