The short answer
Most growing organisations start with one capable person who "does IT", until the role becomes help desk, security officer, network engineer, vendor manager and strategist at once. If several signs below sound familiar, the problem is not the person: one role carries more risk than one human can hold. The answer is usually backup, not replacement: co-managed IT behind them, or a provider for daily operations.
The seven signs
| Sign | What it looks like |
|---|---|
| 1. Knowledge lives in one head | Passwords, firewall settings, vendors: "ask them". Illness, resignation or a two-week holiday becomes an operational risk |
| 2. Urgent beats important | Resets, printers and laptops all day; patching slips, backups go untested, projects stall. UPS batteries, inverter and failover link go unchecked until the grid fails |
| 3. Nobody on duty after hours | A 2 a.m. alert, or a Saturday power or link failure, goes to one phone, or nobody: you are relying on luck |
| 4. Security outgrows a generalist | Insurer questionnaires, client and bank security reviews, EDR alerts and MFA rollouts need specialist time; answers are "I think so" |
| 5. Growth creates a queue | New hires wait for laptops; a new office, remote staff or a new system goes unplanned; growth runs on one person's evenings |
| 6. No evidence when asked | Clients, funders or regulators ask about protecting personal data; no asset list, access review or backup test record |
| 7. Spending without a plan | Surprise renewals, overlapping subscriptions, run-to-failure hardware, no budget, dollar pricing and exchange-rate swings: strategy squeezed out by support |
Quick self-check: tick each statement that is true today
- Only one person knows how key systems are configured
- Patching and backup testing are behind schedule
- There is no defined after-hours cover
- Security questionnaires take weeks and involve guesswork
- New staff wait for equipment or access
- We cannot show written evidence of our security controls
- IT spending is reactive, with no roadmap or budget forecast
Three or more ticks usually means it is time to add support.
What your options really are
Hire a second person
Suits steady work for two and IT staff you can manage. Adds capacity, not 24/7 cover, depth or tooling.
Co-managed IT
Your IT person leads users; a provider adds monitoring, patching, routine work, after-hours cover, escalation.
Fully managed IT
A provider runs daily IT under a service agreement; your IT person often becomes coordinator or business-systems lead.
Compare the two provider models: fully managed vs co-managed IT.
Example: co-managed IT in practice
A 60-person professional services firm has one long-serving IT coordinator. She is excellent with users but has not taken a full week off in two years. The firm chooses co-managed IT: the provider takes monitoring, patching, after-hours alerts and new-laptop builds, and writes up the network and Microsoft 365 configuration. She keeps user support during the day and leads the move to a new practice management system, the project she never had time for.
Common objections, answered honestly
| Objection | Honest answer |
|---|---|
| "We are too small." | Size matters less than risk: a small organisation with client financial or health information faces the same attackers. Providers scope to what you have |
| "It will cost more than our IT person." | Maybe; it depends on scope. Compare it with what one person cannot provide: holiday cover, overnight monitoring, specialist security skills, management and patching tools (costs in Nigeria) |
| "Can't we just ask an AI chatbot?" | Good for explaining or drafting a policy; it cannot see your firewall, reset a compromised account at night or be accountable. You need access, context and a written obligation to act |
| "Our IT person will feel replaced." | Involve them from the start; in most co-managed arrangements their role becomes more interesting, not smaller |
Rather talk it through? Tell us how IT runs today and we will suggest whether co-managed or fully managed support closes your gaps. Talk to a Promatics specialist
When to bring in help
Keep things as they are if your IT person has a manageable workload, documented systems, a tested backup and holiday cover. Bring in help when any is missing, before growth or a new location, or when a client, insurer or regulator asks for evidence you cannot produce.
What working with Promatics looks like
- Onboarding assessmentDevices, users, applications, vendors and risks documented, out of one head.
- Responsibility matrixWritten: what your IT person owns, what we own, what is shared.
- Everyday supportManaged-service clients: 24/7 monitoring and support, a ticket per request.
- vCIO reviewsA named vCIO for roadmap and budget reviews.
Response targets are set in the service agreement. Staff access uses named accounts with least privilege, good practice whenever you use a managed provider. Our managed IT services page explains the scope, and co-managed IT covers the model that keeps your IT person at the centre.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Cybersecurity Framework, National Institute of Standards and Technology
- Nigeria Data Protection Act 2023 and guidance for data controllers and processors, Nigeria Data Protection Commission
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.