Has GIS or no GIS: the only question that decides how you should buy GIS support
TL;DR
If you already have a GIS function, you need senior capacity added to it: embedded support. If you don't, you need a defined project delivered and handed over: project delivery. Buying the wrong one is the most common reason external GIS support disappoints.
There are two reasons an organisation brings in outside GIS help, and they’re not the same conversation.
Do you already have a GIS function? If yes, you need senior capacity added to it. If no, you need a defined project delivered and handed over.
That one question decides everything else: how the work should be scoped, how it should be priced, and what a good outcome looks like. Most disappointing GIS engagements happen because the wrong one got bought.
If you already have a GIS function
Organisations with an existing GIS team rarely have a headcount problem. They have a seniority problem. There’s usually someone doing the day-to-day mapping and data work well enough. What’s missing is someone senior enough to sanity-check a platform decision before it gets expensive to unwind, or to answer for the whole team when things go sideways.
That gap shows up in a specific way: every project needs one person’s sign-off, every new hire has to have the data explained to them from scratch because the conventions live in someone’s head, and the work quietly stalls whenever that person is out.
None of that means the team is failing. It means the work has outgrown the headcount, and a full-time senior hire is a slow, expensive way to fix it: a six-figure role, a recruitment process that runs months, and a person who, once in post, may only be needed for the senior-judgement part three or four days a month.
What actually closes this gap is capacity added to the team that already exists, working in your conventions, without another permanent headcount line. We call this embedded GIS support: a GIL, Fractional GIS Lead, scoped to the days a month the work needs rather than a full contract.
If you don’t have a GIS function at all
A team with no internal GIS capability has a different problem, and embedded support is the wrong answer to it. There’s nobody for a fractional lead to extend, and a retainer with no team behind it just accumulates a bill against work nobody in-house can pick up.
What this situation actually needs is a defined piece of work: a clear scope, one deliverable, one price, and a handover that leaves you able to run the output yourself. We built a national building polygon dataset, 44 million records across 317 local authorities, for a client with a live product to ship and no in-house GIS function. Nobody there needed to become a GIS team. They needed clean, queryable spatial data underpinning a platform on a deadline. You can see the shape of that engagement in our national building intelligence platform case study.
That’s what project delivery looks like: someone owns the outcome, documents what they built, and gets out of the way. No ongoing retainer, no team to plug into, no dependency that outlives the project.
Why the mismatch is the expensive part
Buying the wrong shape of engagement doesn’t just waste money, it actively obscures the real problem.
An open-ended retainer bought by a team with no GIS function papers over the fact that nobody internal owns the output. The consultant relationship never quite ends, because there’s no handover destination for it to end into. A few months in, there’s still another small piece of work, another top-up, another “can you just,” and the organisation is paying for what has become, in practice, a permanent role without any of the institutional continuity a hire or a proper embedded arrangement would have built.
A one-off project bought by a team that actually needs ongoing senior capacity fixes nothing structural. The deliverable lands, the consultant leaves, and the same gap that caused the problem in the first place is still there for the next platform decision. The organisation ends up re-buying the same fix every year instead of putting in place the thing that would have made subsequent buying cheaper.
The five-minute version
Before scoping anything, work through this:
- Do we already have people doing GIS work day to day?
- If yes, is the gap hands, or judgement at a senior level?
- If no, is there a specific deliverable with a defined start and end?
- Who in the organisation will own the output once outside help is gone?
If you have a team and the gap is seniority, that’s embedded support. If you don’t have a team and the work has a clear end point, that’s project delivery. If you’re not sure which describes your situation, the GIS scorecard takes five minutes and gives you a maturity read you can act on.
Not sure which one fits? Get in touch and we’ll work through it with you before anything gets scoped.