ArcGIS config vs. a real geospatial platform — what teams get wrong

There’s a conversation we have often. A company says, “we already have GIS, we just need it on the website,” and what they actually need is a piece of software. Or the reverse: they ask for a “custom platform” when a configured off-the-shelf map would do the job for a tenth of the cost.

The two get conflated constantly, and picking the wrong one wastes real money. Here’s the line.

Configuration

Tools like ArcGIS Online let you take existing layers and publish a hosted, interactive map without writing code. Point, click, style, share. For a lot of needs — a straightforward web map, a field data-collection form, an internal viewer — this is the right answer, and paying a developer to rebuild it from scratch is a waste. If a contractor can configure it in a day, don’t commission a platform.

A real platform

You’ve crossed into software when you need things configuration can’t give you:

• Search and query over your own data model — filter targets by commodity, grade, status; join drill results to holes to projects; ask questions the vendor’s UI doesn’t support.
• One source of truth feeding multiple surfaces — the same PostGIS database driving an internal view, a data room, and a public investor map, so they can’t drift apart.
• Custom interactions and performance — large datasets, specific workflows, a UX built around your users instead of a generic tool’s menus.
• Integration — pulling from and pushing to your other systems, or exposing an API.

That’s not a map you configure. It’s an application you build.

Why the mix-up is expensive

• Companies buy a platform when config would do — and overpay for something a hosted map handled.
• Or they try to force software-shaped problems into configuration — bolting workarounds onto a tool that was never going to search their data model or keep three surfaces in sync, and end up with a fragile mess that’s more expensive than doing it properly would have been.

The honest test: can an off-the-shelf tool, configured, do this — or am I fighting the tool? If you’re fighting it, you need software. If you’re not, don’t build software.

Where we sit

We do both, and we’ll tell you which one you actually need — including “you don’t need us for this, configure it.” When it genuinely is software — search, custom layers, a real data model, a fast interactive experience — that’s custom web GIS, built on a PostGIS foundation. A short sprint is usually the cheapest way to find out which side of the line you’re on.