TL;DR
Hire in-house for ongoing, day-to-day GIS work; bring in a consultant for defined projects needing specialist skills or speed. Most organisations end up using both.
Most organisations that work with spatial data hit this question eventually. Do we hire someone, or bring in a consultant?
The answer usually comes down to one thing: whether the work is ongoing or has a defined end point.
When in-house makes sense
If you need someone in your systems every day, across every project, that is a hire. Open-ended consulting at the same volume typically costs more and transfers less; the institutional context an analyst builds over months is difficult to replicate by the day.
There is also the question of context. An in-house analyst learns your data, your workflows, and the quirks of how your organisation actually works. That context accumulates; a consultant starts from scratch on every engagement.
Where spatial data is in the product rather than supporting it, the expertise should live inside the organisation. You wouldn’t outsource your core engineering function indefinitely.
When outsourcing makes sense
Project work is different. A data migration, a platform evaluation, a database build. These all have defined scopes and end points. Hiring someone permanent for a six-month project creates a retention problem when it ends. You can see what a well-scoped engagement looks like in our GIS data review and migration case study.
Speed matters too. Recruiting a good GIS professional takes months, whereas a consultant can start next week. We built a working site selection application in three weeks for a client who couldn’t wait for a hire.
Internal teams also normalise problems. They’ve worked around the same issues for years without quite noticing. An outside perspective tends to surface things the team has stopped seeing.
When external input still makes sense, even with an in-house team
Having capable GIS people in-house doesn’t close the door on external input. There are several situations where bringing someone in is the right call regardless of your internal capability.
The most straightforward is specialism. A good generalist GIS team may not have deep experience in PostGIS schema design at national scale, enterprise Esri deployment, or constraint data processing across a large portfolio. These are narrow enough that you encounter them rarely, and consequential enough that getting them wrong is costly. Bringing in someone who has done it before is faster and lower risk than building that knowledge internally for a single project.
The more interesting case is objectivity. Your team cannot audit what they built with the same eyes an outsider brings. They have been living with the system long enough to have normalised its problems; the datasets nobody has cleaned up, the workflow everyone knows is broken but works around, the data that gets trusted more than it should. They also have a stake in the outcome of any assessment. An external GIS audit produces a picture the team cannot generate for itself, and one that carries weight with leadership in a way internal recommendations often struggle to. A consultant recommending change is not defending their own decisions.
The third situation is a pre-decision sense check. Before a platform migration, a significant procurement, or a change to your core data architecture, an independent review is worth having. Not because your team is not capable of making the assessment, but because the stakes are high enough that a second opinion is reasonable. Our migration scoping engagement is designed specifically for this: a structured external view before you commit to a direction.
Working through the actual cost comparison
The headline day rate for a consultant always looks expensive next to a salary, so it is worth doing the comparison properly rather than on gut feel.
A mid-level GIS analyst salary in the UK typically sits somewhere between £35,000 and £50,000 depending on region and seniority, before employer National Insurance, pension contributions, benefits, equipment, software licences, and management overhead are added. All in, the fully-loaded cost of a permanent hire is usually 25 to 40 percent above the headline salary. That hire also needs onboarding time, which is rarely productive in the first one to three months.
A consultant engagement for the same specialist work, at a typical advisory or technical day rate, looks expensive per day but is bounded. A six-week platform migration scoping engagement at a fixed price is a known, one-off cost with a defined deliverable. There is no notice period, no recruitment cost if the engagement does not work out, and no ongoing salary once the project ends. The comparison only favours the hire once the work is genuinely continuous, because that is when the consultant’s day rate, multiplied across a full year, exceeds the fully-loaded cost of a permanent position.
The break-even point varies by scope, but as a rough guide: if you need the equivalent of more than roughly 100 to 120 consultant days a year, on an ongoing basis, a hire usually works out cheaper over a two- to three-year horizon. Below that, especially for defined, non-recurring work, outsourcing tends to be the more efficient use of budget.
What a good handover actually looks like
The hybrid model only works if the handover from consultant to in-house team is real, not nominal. A good handover includes, at minimum: a written record of every data source used and where it came from, the schema and any naming conventions applied, a plain-English explanation of any non-obvious design decisions (why a view was used instead of a materialised table, why a particular projection was chosen), and a short training session with whoever will maintain the work day to day.
The failure mode is a handover that consists of a folder of files and a single call. Six months later, nobody remembers why a particular table exists, the documentation has not been updated, and the organisation is effectively locked into calling the original consultant back every time something needs to change. A defined, documented handover is what actually transfers the value of the engagement, not just the deliverable itself.
The hybrid
Most organisations use both: an in-house team for the day-to-day and consultants for specific projects that need depth or speed.
The hybrid works when the handover is real: the consultant delivers something defined, documents it, and leaves. The in-house team can maintain it without picking up the phone.
What doesn’t work is letting a consultant drift into an indefinite arrangement without defined scope. No hire commitment, no knowledge transfer, no clear output. Just an accumulating bill.
A retainer is a different thing. Part-time capacity on an agreed monthly scope, with a regular review to keep it calibrated. That works when GIS work is recurring but doesn’t justify a hire. We run this for property and land clients through our embedded GIS support, with scope agreed upfront and reviewed quarterly.
Signs you have made the wrong call
A few patterns tend to show up when an organisation has picked the wrong model, and they are worth watching for.
If you hired in-house for what turned out to be a one-off project, the tell is a GIS role with no clear pipeline of future work once the initial build is done. The person either gets stretched thin across unrelated tasks to justify the position, or the organisation quietly starts looking to move them on within a year. Neither is a good outcome, and both were avoidable with a more honest scoping conversation before the hire went out.
If you outsourced work that turned out to be ongoing, the tell is a consultant relationship that never quite ends. The original defined project is long finished, but every few months there is another small piece of work, another retainer top-up, another “can you just.” At that point the organisation is paying consultant rates for what has become, in practice, a permanent role, without any of the institutional continuity a hire would have built. This is usually the point to either formalise a proper retainer with clear scope, or convert the relationship into a hire if the volume justifies it.
A third pattern is choosing based on internal politics rather than the actual shape of the work. Sometimes an in-house hire is pushed through because a director wants a bigger team, or a consultant is brought in because procurement rules make hiring slow. Both can work out fine, but they are decisions made for reasons other than what the work actually needs, and they tend to need correcting later once the mismatch becomes obvious in the budget or the backlog.
Before you decide
Work through these:
- Is this work ongoing or project-based?
- Do we need this skill set permanently or temporarily?
- Can we define a clear scope and deliverable?
- Do we have someone in-house who can receive the handover?
- What happens when the consultant leaves?
If the answers point to a defined project with specialist requirements, outsourcing is probably right. If they point to steady, recurring work that’s core to operations, hire.
Not sure where your GIS function currently stands? Our GIS Health Check scorecard takes five minutes and tells you where the gaps are.
If you want to talk through what an engagement would look like for your situation, get in touch.