TL;DR
Most GIS teams are missing seniority, not headcount. A GIL (Fractional GIS Lead) fills that specific gap: someone senior enough to sanity-check a platform decision, cover a capacity gap, or bring an outside view, scoped to the days a month the work actually needs rather than a full-time contract. Three tiers, from £2,400/month for 3 days to £8,000/month for 10+, no fixed-term lock-in.
Most GIS teams aren’t short on headcount. They’re short on seniority.
There’s usually someone doing the day-to-day mapping and data work. What’s missing is someone senior enough to sanity-check a platform decision before it gets expensive to unwind, cover a capacity gap while a role sits open, or bring an outside view when a project goes sideways. That gap is real, it’s expensive to leave unfilled, and it’s also expensive to fill the obvious way.
We’ve started calling the alternative a GIL: Fractional GIS Lead.
The problem with the obvious fix
The instinct when a team feels this gap is to open a req. Head of GIS, six figures, a recruitment process that runs months. Eventually it fills, and the person in the role turns out to be needed for the senior thinking part three or four days a month. The rest of an expensive hire’s time gets absorbed into whatever’s in front of them, because that’s what happens to expensive people sitting idle.
That’s not a failure of the hire. It’s the wrong shape for the problem. Most teams don’t need a full-time senior GIS person. They need senior GIS thinking on a schedule that matches how often the problem actually shows up.
What a GIL actually does
A GIL is senior GIS support, built into your team on a fixed number of days a month, covering what a junior or mid-level hire structurally can’t:
- Sanity-checks platform and architecture decisions before they get expensive to unwind. A schema choice or a platform migration that looks fine in a proof of concept can be a six-month problem at production scale. Catching that before commitment is cheaper than catching it after.
- Covers a senior capacity gap during parental leave, a hire search, or a busy quarter, without a permanent headcount decision to fill a temporary hole.
- Brings outside perspective from sectors and platforms the team doesn’t see day to day. A GIS lead who’s only ever worked inside one organisation has a narrower reference set than one who’s seen the same problem solved five different ways elsewhere.
- Sits inside the team, not outside it: in the meetings, the Slack, the sprint planning. The difference between a GIL and a traditional consultant is embedding, not just availability.
It’s the same idea as a fractional CFO or fractional CMO, applied to a role nobody had properly named in GIS yet.
How it’s structured and priced
| GIL Starter | GIL Growth | GIL Embedded | |
|---|---|---|---|
| Days per month | 3 | 6 | 10+ |
| From | £2,400/month | £4,800/month | £8,000/month |
| Fit | Occasional senior sign-off | Regular embedded support | Near-full senior cover |
All three tiers sit at the same flat day rate. Scope is agreed upfront and reviewed quarterly, and there’s no fixed-term lock-in: a GIL scales with what the team actually needs, not a contract written six months before anyone knew what that would be.
Pricing is published rather than “contact us for a quote.” Most GIS consultancies in the UK don’t do that. We think that’s a mistake on their part, not a norm worth following.
Why fractional, not full-time
A full-time senior GIS hire costs the salary, the recruitment time, and the risk of hiring for a role that doesn’t need five days a week yet. A GIL costs what the work actually takes, starts within weeks rather than months, and comes with a track record already built rather than a probation period.
It also solves a different problem than a contractor does. A contractor executes a defined piece of work and leaves. A GIL is ongoing: the same person, embedded, building context on your data and your team over time, so the senior judgement gets better the longer the arrangement runs rather than resetting with every new engagement.
Who this is and isn’t for
A GIL extends a GIS team that already exists. If your team has the junior and mid-level GIS capacity covered but nobody senior enough to lean on, that’s exactly the gap this is built for.
If there’s no internal GIS function at all, a GIL isn’t the right entry point. The equivalent fit is project delivery: a defined piece of work, scoped to a brief, with one deliverable and one price agreed before anything starts.
Different starting points need different kinds of help. If you’re not sure which one describes your team, the GIS scorecard takes about five minutes and gives you a maturity read you can act on. If you already know, see how embedded support works or get in touch to talk through scope.