Big Enough to Deliver, Small Enough to Care: Why SMEs Are Winning in Geospatial

The Pace Paradox

Does it ever feel as though the world operates at two contradictory speeds, simultaneously too quick and too slow? It’s a cliché to speak about instant gratification, the world at our fingertips, Artificial Intelligence… And yet nothing ever seems to get done. Projects hang in purgatory for months, years. We ask AI a question and get an answer in seconds—but then spend just as long verifying it. We get an email response in less than a day, meanwhile critical GIS deployments can take four months of discovery before a single engineer sees working software. The illusion of progress hinders the real thing. This is the pace paradox. And this paradox exists right at the heart of geospatial delivery.

In this blog, we’ll investigate how this pace paradox reveals how SMEs may just sit within the best middle ground between the slow-delivery value offered by Large System Integrators and instant, AI-style solutions that offer no real value at all. So, if your current provider is changing (perhaps through acquisition, or even just strategic shifts), this may be food for thought when selecting a replacement!

The Large Systems Integrator Challenge

Let’s say you get into bed with a Large Systems Integrator (How dare you!). It’s true that LSIs bring proven processes, governance frameworks, and multi-tower expertise. But that infrastructure often creates extended timelines before organisations see tangible value. We have it on pretty good authority that it goes something like this…

A typical LSI engagement timeline:

• Week 1: Kick-off with sales team. Delivery team ‘to be confirmed’
• Weeks 2-4: Environment access, security questionnaires, workshop scheduling
• Week 5: 26-page governance framework arrives
• Weeks 6-14: Multi-workstream discovery phase with architect → config → data → test handoffs
• Month 4: Detailed proposal on how work will be done. Still no working software

Seriously. We heard about one utilities client who spent sixteen weeks in LSI discovery for a Field Maps deployment. They had governance frameworks, architecture documents, and test strategies. Know what they didn’t have? A single working form for their field engineers to test (legend goes that they’re still waiting…).

How SMEs Work at the Right Speed

SMEs don’t skip the careful parts, we skip the parts that don’t add value. Our approach focuses on delivering working solutions progressively, with continuous client feedback. So, who likes examples!?

Recent MGISS projects demonstrate this approach:

Public Sector Asset Management: Deployed ArcGIS Enterprise for multiple local authorities covering highways, utilities, and property assets. Progressive rollout with pilot phase validated before wider deployment. Field teams were testing working systems within weeks, not months.

Utilities Field Operations: Delivered a six-week pilot integrating existing as-laid data into a GIS-ready field workflow for a utilities provider. Early access for field operatives reduced rework and supported a full operational rollout within four months.

Highway Network Management: Implemented Field Maps solution for highways inspection teams. Week 1-2: Requirements gathering and initial configuration. Week 3-4: Pilot deployment with one team. Week 5-6: Refinement based on field feedback. Result: working solution with 85% user adoption within first month.

The pattern is consistent: early value delivery, continuous iteration, and solutions shaped by actual use rather than theoretical frameworks. In essence, we get things done!

Scale, Risk, and Governance

Can SMEs Handle Scale?

We know you’re thinking it—Can SMEs handle scale? It’s important to know that scale in this context is usually a design question meeting an automation question, rather than a ‘how many employees do you have’ question.. LSIs might have fourteen people working in HR and a chef on payroll, but that doesn’t automatically add value to your specific deployment, does it?

Genuine scale means:

• Cloud-native architectures that expand elastically
• Automated data pipelines processing millions of features
• Partner ecosystems for specialist capabilities
• Templated solutions proven across multiple deployments

To use our own example again, MGISS has deployed solutions covering multiple local authorities and utility networks. These scaled not through consultant numbers, but through properly designed architecture and automated processes.

What About Governance?

Small supplier doesn’t mean small governance. Professional SMEs deliver:

• Response SLAs with named escalation paths
• Cloud and offline options for data security
• 30/60/90-day plans with measurable outcomes
• Full documentation and knowledge transfer
• Quality certifications: ISO 9001, Cyber Essentials & Cyber Essentials Plus
• Compliance with government standards; Cots solutions for NETZero, BNG, NUAR, National Highway/GDMS
• Faster Procurement through GOV.UK Dynamic Purchasing Systems pre-approval (We’re an LVPS appointed supplier!)

The UK public sector actively encourages SME engagement through specific frameworks and targets (evidence that size doesn’t determine risk or capability!).

Partner Ecosystems

An SME’s strength lies partly in its partnerships, and not to boast, but we’ve got some good ones! MGISS works with Esri, Eos Positioning Systems, and Leica Geosystems, allowing us to bring specialist capabilities when needed without that huge enterprise overhead that LSIs deal with.

For example, Esri has engaged MGISS to add sector-specific expertise on projects where our utilities and highways experience complements their enterprise platform capabilities. We also work with partners like Eos Positioning Systems (we’re their chosen distributor in the UK and Ireland!), trusted to carry out hardware services and repair, with a partnership that ensures seamless integration between GNSS positioning systems and GIS platforms. That’s what you call a healthy partner ecosystem!

When Large Systems Integrators Make Sense

As much as it hurts to admit, SMEs aren’t the solution for every scenario. LSIs are genuinely appropriate when:

1. Multi-year, multi-tower enterprise transformation

If you’re replacing SAP, Oracle, and GIS as part of a £50M+ programme, you need a prime contractor managing complex vendor relationships across all workstreams. The geospatial component might be 8% of the programme.

(Though even here, consider an SME as specialist subcontractor for the geospatial workstream. LSI manages the programme; we deliver the working GIS.)

2. Highly regulated sectors with specialist accreditation requirements

Some sectors require security clearances or accreditations that represent significant barriers to entry for smaller firms.

3. Global rollouts requiring in-country presence

If you need 24/7 follow-the-sun support across 30+ countries with local technical teams, LSIs have that infrastructure established.

For everything else: the operational deployments, the system integrations, the ‘get our field teams digital’ projects: SMEs typically deliver better outcomes, faster, at lower cost.

The Bottom Line: What Do You Actually Need?

The pace paradox presents two unsatisfactory options: LSI processes that deliver value too slowly (sometimes so slowly that the value itself has gone stale), or non-expert, AI-style instant solutions that lack depth and verification.
SMEs occupy the middle ground. Not too quick that we skip careful design, not too slow that you’re waiting months for tangible value. You get years of expertise, crafted, focused teams, a strong partner ecosystem…

Consider whether you genuinely need:

• Working software with visible value
• Experienced people who’ve solved this specific problem
• Direct access to the team doing the work
• Rapid iteration based on field feedback
• Transparent pricing without hidden overheads
• Solutions shaped to your actual needs, not generic frameworks

If this resonates with your requirements, or if you’re evaluating replacements for your current provider and are wondering whether a focused SME partner might be just the right fit, then let’s have a conversation about your specific project.

---