Your IT guy and your software developer are not the same person
One keeps your computers running. The other builds new things that didn't exist before. Confusing the two gets good IT people stuck on the wrong job and businesses stuck with software nobody should have built.
There’s a mix-up that costs businesses real money, and it’s an understandable one. Both of these people work with computers. Both speak in acronyms. Both get called when something technical needs doing. So when a business decides it needs a custom system built, it often turns to the person who already handles its technology, the IT support company, the managed services provider, the bloke who set up the network. Sometimes that works out. Often it’s like asking your mechanic to design a car.
Your mechanic knows their trade. They’ll keep your car running for years, diagnose a noise you can’t even hear, and get you back on the road fast. That doesn’t mean they can design a new vehicle from scratch, and nobody thinks less of them for it, because those are different jobs that happen to both involve cars. IT support and software development are the same story. Both are real skills. They’re just not the same skill, and the confusion sends good people onto the wrong work and leaves businesses with systems that should never have been built the way they were.
What IT support actually does
IT support keeps the things you already own working. Computers, networks, email, wifi, printers, servers, backups, the accounts and passwords, the software licences, the security patches, the “I can’t log in” on a Monday morning. It’s the plumbing and the wiring of a business, and when it’s done well you barely notice it, which is exactly the point. Good IT support is invisible, reliable, and worth every cent, because the day it’s not there you can’t do anything.
It’s fundamentally about maintaining and running existing systems. Keep them up, keep them secure, keep them patched, fix them fast when they break, and stop them breaking in the first place. That’s a demanding job that rewards being careful, methodical and available. Notice that none of it involves inventing something new, and that’s not a knock. It’s the nature of the work.
Most providers run this as a managed service now: a monthly fee per user or per device, a help desk, response times written into the contract, patching and backups on a schedule. Their whole commercial model is built around keeping known systems stable, and everything about how they hire, train and roster follows from that. When the server dies at 7am on invoice day, the difference between a two-hour response and a two-day one is your whole week. That’s the promise you’re paying them for, and it’s a promise that has nothing to do with building software.
A software developer builds things that don’t exist yet
A software developer builds things that didn’t exist before. A custom application for how your business actually runs. A system to replace the manual process eating your week. An integration so two tools finally talk. A customer portal, a booking engine, a mobile app, a piece of automation shaped around your specific problem. It’s design and construction, not maintenance, and it’s a different craft altogether.
Building software is closer to architecture and building than to repair. You work out what the thing needs to do, design how it fits together, construct it, test it, and shape it around people who’ll use it in ways they can’t fully describe up front. The skills that make someone brilliant at keeping a network humming, caution, consistency, following the established way, are not the same skills that make someone good at inventing a new system from a vague brief, where half the job is deciding what to build at all. Some rare people do both. Most specialise, the same way you wouldn’t want your architect rewiring the house or your electrician drawing up the extension.
The job board nobody can touch
Here’s how the mix-up usually plays out, with the details changed but the shape intact. A freight company on the Darling Downs runs about forty trucks. Their IT provider is good: thirty-odd computers, the server, the email, all humming along. The operations manager is drowning in a whiteboard-and-spreadsheet job allocation process, so she asks the provider whether they can do something about it. They say yes, because one of their techs is handy with scripts, and over a few months, squeezed between support tickets, he wires up a SharePoint list, some automation flows and a small database front-end. Credit where it’s due: it works. Dispatch stops double-booking trucks. For two years everyone is quietly grateful.
Then the tech takes a job in Brisbane. Six months later the business wants drivers to see their runs on a phone, and there’s nobody left who knows why the whole thing breaks when a job gets edited twice in the same hour. The IT provider doesn’t want to touch it, and fair enough. Every quote to extend it starts with “first we’d need to work out what it actually does.” The system that cost almost nothing on paper now sits in the middle of a forty-truck operation, undocumented and unowned, quietly vetoing every improvement anyone suggests. When a software studio finally gets asked to look at it, the honest advice is a rebuild, and the first invoice is for archaeology.
Nobody in that story did anything wrong, exactly. The tech was helpful, the manager was resourceful, the provider was trying to look after a client. But the business made a construction decision under a maintenance contract, and the bill arrived two years late, with interest.
Where the confusion gets expensive
The mix-up costs money in both directions. Ask an IT support firm to build custom software and, if they say yes, you often get something cobbled from off-the-shelf parts and held together in a way that made sense to them, works for a while, and becomes a black box the moment the one person who understood it moves on. Not because they’re bad at their job. Because it wasn’t their job, and building software to last is a different discipline from making something that runs today.
It goes the other way too. A software studio is not who you call when your email’s down or the office wifi drops out, and a developer poking at your network is its own kind of risk. The useful thing is to know which problem you’ve got. Is something you already own broken or in need of running and securing? That’s IT support, and a good one is gold. Do you need something built, changed, integrated or automated that doesn’t exist yet? That’s software development, and it’s a different phone number. Plenty of businesses need both, and the best setups have the two working together, the IT provider keeping the lights on while the studio builds the new thing, each respecting that the other does work they don’t.
Working out which number to call
There’s a rough test that sorts most cases. Describe the problem out loud in one sentence, without naming any product. If the sentence starts with “something is broken”, “something is slow” or “we can’t get into”, that’s an IT job. If it starts with “we need a way to”, “I’m sick of retyping” or “these two systems don’t talk to each other”, you’re describing something that doesn’t exist yet, and that’s development.
The in-between cases are where the money gets wasted, so they’re worth naming. “Our spreadsheet can’t cope anymore” sounds like a support ticket, but the fix isn’t repairing the spreadsheet, it’s replacing the process that grew around it, which is a custom business system wearing a spreadsheet costume. “Can the website talk to Xero?” sounds like a settings toggle, but it’s an integration build. And “we just need a small tweak to the thing Dave set up” is almost never small, because the cost isn’t the tweak, it’s working out what Dave set up.
One more question worth putting to whoever you’re about to hire, for either kind of work: if the person doing this leaves in three years, who picks it up? A studio should answer with source control, documentation and a handover plan. An IT firm asked to build something usually can’t answer it at all, not because they’re careless, but because their business was never designed to carry that promise.
None of this is a dig at IT people. We rely on good ones, and a business without solid IT support is a business one bad Monday from an expensive week. It’s just worth being clear about who does what, so your IT crew isn’t stuck moonlighting as reluctant developers and you’re not left with a custom system nobody can safely touch. If you’re not sure which one your problem needs, describe what’s actually going wrong and we’ll tell you straight, even when the honest answer is “that’s an IT job, not ours.”
Related reading
Anatomy of a software project that quietly failed
Software projects rarely die in a dramatic crash. They drift, the champion leaves, the vendor goes quiet, and one day everyone admits it's dead. Here's how to see it coming.
A field guide to weasel words in software pitches
Software sales language is built to sound like a promise while committing to nothing. Here's what the favourites actually mean, and the question that turns each one into a fact.
Custom software versus off-the-shelf, and what it really costs over time
A small monthly fee can cost more than a one-off build. What matters is the bill over five years, and who controls it.
Turn the thinking into a plan.
Send the process, risk or idea. We'll help you work out what's worth doing first.