Hire a fractional IT director when technology choices are already costing real money and nobody qualified owns them. In practice that is often somewhere between about five and thirty people, with no internal IT lead, rising subscriptions, and decisions about cloud, security or suppliers made on a hunch. Below that it is usually too early. If what you want is a phone number when Wi-Fi dies, you want support, not a director. Page Forge is not an MSP and does not sell a helpdesk. The role is defined in what is a fractional IT director. This post is the timing. If you already know it is time, here is how our fractional IT director service works.
What is the job, in one paragraph, so the timing makes sense?
A fractional IT director is senior judgement on a part-time clock. They write down what you have, what you should spend, what to ignore, and whether a supplier’s contract is fair. They do not reset passwords at 6pm. If they start doing that, you no longer have a director. You have a technician with a grander title.
That distinction is the whole hiring test. Strategy on a calendar. Tickets on a different invoice, if you need them at all.
What are the signs it is time?
You do not need all of these. Two or three that have lasted more than a quarter is enough to have the conversation.
Decisions are guesswork, and the sums are no longer small. Choosing a suite, signing a three-year line, or turning AI loose on customer data, with nobody who can explain the trade-off, is how you buy the wrong thing twice.
Spend is creeping and nobody can list it on one page. Seats here, a backup tool there, a leftover number from a person who left. When the total would annoy you if it were a van lease, someone should own it.
You suspect the supplier is expensive, and you cannot check. The MSP, the telco or the software vendor will not independently mark their own homework. A director sits on your side of that table. Sometimes the answer is “the contract is fine”. That is still value.
Headcount has moved and the old arrangement is creaking. What worked at six people with one shared inbox starts to fray at eighteen: leavers, devices, files in private drives, no MFA, no one who can disable an account. Growth is a timing signal because the cost of a sloppy foundation rises with each hire.
IT only appears when something is already broken. Then it disappears again. That is luck, not a plan. A fractional block puts a date in the diary for the unsexy work: backup test, licence count, the domain that renews in November.
A large change is on the calendar. An office move, a new system, an acquisition, an insurer asking questions, or a scare that woke the owners up. Those moments are expensive to improvise.
If you recognise the list and you are still under five people with a working mailbox, read the next section before you book anyone.
When should you wait?
Waiting is a valid outcome. I will say it on a call.
You are a sole trader or a tiny team with simple, stable tools. A one-off tidy of mail and MFA is usually enough. A director’s calendar is overhead.
Nothing is being decided, and nothing is breaking in a costly way. No new contract, no growth strain, no pile of unused seats. Save the money.
The pain is a printer, a flaky laptop or a forgotten Wi-Fi password. That is break-fix or an MSP. Buying strategy to soothe a broken keyboard is how you stay annoyed and still have a broken keyboard.
You want someone “on tap” forever. That is a support contract. A director who becomes an unofficial helpdesk has failed the brief.
There is a cost to hiring late: the bad contract already signed. There is a cost to hiring early: paying for a roadmap you will not follow. The honest window is when decisions exist and ownership does not.
How is this different from buying more IT support?
Support is reactive. A ticket, a fix, a monthly fee per user. Useful if you have enough kit to justify it. The incentive is to keep you on their stack and to renew.
A director is the person who asks whether you need that stack. They may tell you to hire an MSP. They should not be the MSP on the same invoice if you want an independent reading of that invoice.
You can have both. Many firms should. The support firm images the laptop. The director asks why you have forty unused licences and no restore test.
Page Forge sells projects and scheduled advisory time, then hands over. No helpdesk. No ongoing support contract. If the first conversation ends with “you need tickets, not me”, that is a successful conversation. Details are on IT and AI consulting.
Do not hire a director because an antivirus popup frightened you. Do the basics. If you want a calm view of Defender versus a paid suite, start with do I need antivirus in 2026, not with a retainer.
What should the first conversation produce?
Not a 40-page proposal. Not a tool you must buy from the speaker.
You should leave with a plain answer to four questions:
- Is it too early, and if so, what one-off job would be enough?
- If it is time, what block of time is proportionate: a half-day a month, a half-day a quarter, or a single project?
- What will not be included (tickets, night monitoring, sitting in the office)?
- What would “stop” look like, so you do not slide into an unspoken helpdesk?
A useful first meeting also produces a rough inventory prompt: users, domains, who bills you, where files live, whether MFA is on, whether a backup has ever been restored. You can start that list before you speak to anyone. If you cannot start it, that itself is a signal.
I will not put a pound figure on advisory time here. It is quoted to match the block. Website prices do not belong on this invoice. If the person cannot describe the finish line, they are selling access. Access is support.
How do you keep it from becoming a helpdesk?
Write the boundary on day one. The director owns the roadmap, spend and supplier conversation. Implementation might be you, an MSP, or a separate project. After handover, tickets are still not the product.
Review on a date you set. Continue, reduce to a quarterly check, or stop. Stopping should be possible without the business forgetting the Wi-Fi password. If only one human understands the estate, the role has failed.
The explainer post describes a document pack someone else could pick up. Use that test. If you are more dependent, not less, you hired the wrong shape of help.
Frequently asked questions
How many employees should I have before hiring a fractional IT director?
There is no hard rule. The role commonly makes sense from roughly five to thirty people with no internal IT lead. Below that, a single project is usually enough. Well above that, you may be shopping for a permanent hire.
Is a fractional IT director the same as IT support?
No. Support handles tickets. A director handles decisions, budget and supplier oversight. Do not hire a director because the printer queue is stuck. Hire support for that, or fix the printer.
How is this different from asking my current IT provider?
Your provider has an interest in their own renewal. A director who sits with you can say the contract is fair, or that it is not. That independence is the product. It vanishes if the same company is also the helpdesk.
What if I only need help with one decision?
Then buy a project, not a rhythm. Choosing a suite, planning a migration, or writing a short security baseline can be one job with a finish. A fractional calendar is for when those decisions keep arriving.
How do I know it is too early?
If tools are simple, spend is small, and nobody is asking you to sign something large, it is too early. A call that ends with “not yet” is a good call. Do the MFA and backup basics first.
Will Page Forge become our IT department?
No. We quote advisory time or a project, then you own the outcome. We will not take your tickets. If you need an IT department, you are hiring a different kind of firm, or a person.
If decisions currently run on gut feel, a bounded conversation is the right first step. See IT and AI consulting, or get in touch. We will tell you if you need a director, a one-off tidy, or an MSP. We will not sell you a helpdesk dressed as strategy.