What managed IT actually covers
Managed IT providers (sometimes called MSPs) handle the operational side of technology. In a typical NZ mid-market business, this means:
Helpdesk support. Someone to call when laptops break, passwords need resetting, or email stops working.
Infrastructure monitoring. Keeping an eye on servers, networks, and cloud services. Patching and updating when vendor releases come through.
Security basics. Antivirus, firewall management, backup schedules, disaster recovery testing.
Procurement. Buying hardware and software licenses on your behalf, often at a margin.
This is necessary work. Every business needs it. The gap is not in what managed IT does. It is in what managed IT is not designed to do. MSPs are built to maintain and support. Their business model rewards stability and volume. They manage what exists. They are typically not resourced or incentivised to step back and ask whether what exists is the right thing for the business.
That is not a criticism. It is a structural reality. You do not ask your car mechanic to redesign your supply chain route, even though they know your vehicle better than anyone.
What a fractional CTO does differently
A fractional CTO operates at the strategy level. Instead of managing technology, they decide what technology the business should be using, in what order, and why.
In practice, for a NZ business doing $10M to $100M in revenue, here is what that looks like week by week.
The first month: understanding what you actually have
The CTO audits your current technology landscape. Not just the systems your IT provider manages, but everything. The ERP. The CRM that sales bought three years ago. The spreadsheet that the production manager built that runs half your scheduling. The three different places customer data lives. The integration that breaks every time someone updates the accounting software.
This audit produces a current state map that most businesses have never seen. It shows every system, every data flow, every manual workaround, every cost, and every risk. It also shows the gaps: where data is being re-entered manually, where systems do not talk to each other, where you are paying for functionality you do not use, and where you are missing functionality you need.
Month two: building the roadmap
The CTO takes the current state, aligns it against your business plan for the next 12 to 36 months, and builds a technology roadmap. This answers: what needs to change, in what order, at what cost, and what the business impact will be.
A concrete example. A NZ food manufacturer doing $30M revenue is planning to open a second production facility in 18 months. Their current ERP handles one site. Their warehouse management is a combination of the ERP and spreadsheets. Their quality system is paper-based. The roadmap might look like:
Months 1 to 3: Implement proper warehouse management within the current ERP to replace spreadsheets. Cost: $40K. This needs to happen first because the second site will need the same system from day one.
Months 4 to 6: Move the quality management system from paper to digital, integrated with the ERP. Cost: $25K. This eliminates duplicate data entry and makes compliance audits faster.
Months 7 to 12: Configure multi-site operations in the ERP. Set up the second site with the same processes and systems. Cost: $60K.
Month 12 onwards: Implement business intelligence reporting across both sites. Cost: $20K.
Total: $145K over 12 months, sequenced to deliver value at each stage and ensure the second facility opens on a solid technology foundation.
Without a CTO, the same business might spend $200K over the same period on disconnected projects that each made sense individually but do not add up to a coherent system. Or worse, they open the second facility and spend the first six months manually reconciling data between two locations because nobody planned for multi-site operations.
Ongoing: the decisions nobody else makes
Once the roadmap exists, the CTO's role shifts to execution oversight and decision-making. This is typically 2 to 4 days per month and covers:
Vendor management. When a software vendor pitches you a new product, the CTO evaluates it against the roadmap. Does it fit? Does it replace something already planned? Is it a distraction? Your managed IT provider will tell you whether they can support it. Your CTO will tell you whether you should buy it.
Architecture decisions. Should your new system integrate via API or middleware? Should you build a custom integration or use a standard connector? Should data flow in real-time or batch overnight? These decisions have cost implications that compound over years. Making them well saves tens of thousands of dollars. Making them poorly creates technical debt that gets more expensive to fix the longer you leave it.
Team development. Do you need to hire a developer? Should your IT coordinator become a systems administrator? Is your managed IT provider still the right fit, or has the business outgrown what they offer? A CTO makes these calls based on where the technology landscape is heading, not where it is today.
Board and leadership communication. Translating technology investments into business language. When the board asks why you are spending $60K on warehouse management software, the CTO explains it in terms of picking accuracy, labour savings, waste reduction, and readiness for the second facility. Not in terms of modules and licenses.
Security posture. Not the firewall rules and antivirus updates (that is managed IT), but the bigger picture. Risk assessment across all systems. Compliance with customer and regulatory requirements. Incident response planning. Whether your cyber insurance coverage actually matches your exposure.
The gap that shows up in growing NZ businesses
Most NZ businesses start with managed IT because it solves the immediate pain: things break, someone needs to fix them. That works until the business reaches a stage where technology becomes a strategic factor, not just a utility.
The signs are consistent across industries:
You are evaluating a major system change and the advice feels biased. You are looking at a new ERP, CRM, or e-commerce platform. Your managed IT provider recommends the one they partner with. The ERP vendor recommends themselves. You have no independent voice in the room who understands your business well enough to challenge both of them.
Your systems do not talk to each other and nobody owns that problem. Sales data lives in the CRM. Financial data lives in the ERP. Inventory data lives in a spreadsheet. Customer complaints live in email. Your managed IT provider keeps each system running individually, but nobody is responsible for making them work as a whole. You have islands of data and a team of people manually bridging the gaps every day.
Technology spending is increasing but you cannot explain the return. You are paying for more tools, more licenses, more support hours, more integrations. But the business is not measurably more efficient, more accurate, or more competitive. The spending feels like it is maintaining the status quo rather than moving the business forward.
You are making technology decisions by committee. The CEO, CFO, operations manager, and sales director all have opinions about technology. None of them are technologists. Decisions get delayed because nobody feels qualified to make the call. Or decisions get made based on who argues most convincingly in the meeting rather than what the data and the business plan support.
Your competitors are pulling ahead. They are automating processes you still do manually. They have real-time visibility into their operations while you are waiting for someone to update a spreadsheet. They are responding to customers faster because their systems are connected. You know you need to do something, but you do not know what to do first or how much it should cost.
Why not just hire a full-time CTO?
Cost. A full-time CTO in New Zealand commands $200,000 to $350,000 in salary, plus benefits, plus the expectation of a senior leadership role with equity or long-term incentives. For a business doing $10M to $50M in revenue, that is hard to justify when you need strategic technology leadership 2 to 4 days a month, not 5 days a week.
There is also a practical issue. A full-time CTO in a $20M business often ends up doing operational IT work because there is not enough strategic work to fill 40 hours a week. You hire a strategist and they end up resetting passwords and managing the Wi-Fi. That is expensive IT support, not technology leadership.
A fractional CTO gives you senior technology leadership at a fraction of the cost, typically $8,000 to $15,000 per month for 2 to 4 days of engagement. You get the same strategic thinking, the same vendor independence, the same board-level communication. But scoped to what your business actually needs right now, with the flexibility to scale up during major initiatives and scale back during steady-state periods.
How they work together
The best arrangement is having both. A fractional CTO sets the direction. Managed IT executes and maintains it. These are complementary, not competing.
The CTO decides you need to move from on-premise servers to Azure. The managed IT provider plans and executes the migration, then manages the cloud environment day to day. The CTO evaluates and selects a new ERP. The implementation partner delivers it. The managed IT provider handles the ongoing support. The CTO reviews the monthly IT spend, identifies waste, and ensures every dollar aligns with the roadmap.
This separation works because strategy and operations are different skills. Your managed IT provider is excellent at keeping things running. Your CTO is excellent at deciding what should be running. Asking one person or team to do both usually means one side suffers.
When managed IT is still the right answer
Not every business needs a fractional CTO. If your revenue is under $5M, your technology stack is simple (email, accounting, maybe a basic CRM), and your competitive advantage does not depend on technology, managed IT is probably all you need.
The honest test is this: are your technology decisions still simple? If the answer is yes, if you are choosing between two email providers or deciding whether to upgrade your laptops, managed IT handles that. If your technology decisions have become complex, expensive, or strategic, if you are choosing between ERP platforms, deciding whether to build or buy, or trying to connect systems that were never designed to work together, you need someone whose job is to make those decisions well. That is what a fractional CTO does.
Equerra provides virtual CTO services for NZ mid-market businesses from $8,000 per month. Technology roadmaps, vendor management, architecture decisions, and board-level reporting. Book a discovery call to talk through whether a fractional CTO makes sense for your business.
