Choosing a GIS for a small project is less about brand loyalty and more about what you need to hand over at the end. A two-person consultancy producing a landscape appraisal for a parish council has different needs from a housing association mapping its assets, or a volunteer group recording footpath erosion on a phone. Open-source and commercial tools can both do the job. They differ in where the money goes, who answers when something breaks, and how much time disappears into learning the interface before the real work starts.

Start with the job, not the brand

Before you compare software, write down what the project actually produces. A PDF map for a planning submission is a different problem from an interactive web map, a spatial database that three people will query, or a field survey that has to work offline in a valley with no signal.

Pay attention to the awkward requirements. Does the client insist on a specific file format? Does the data need to sit alongside existing council or company systems? Will someone else maintain this after you leave? Ten minutes spent answering those questions usually narrows the field faster than any feature comparison.

Cost: the licence is only part of the bill

Open-source GIS is free to download and free to use. That matters when the budget is small and most of it needs to go on data, travel or staff time. But the licence is rarely the biggest line in the calculation. What you save on seats you may spend elsewhere:

• Training and the slow weeks while people find their way around the interface
• Someone to install, configure and back up a spatial database if you go down the PostGIS route
• Cloud hosting if maps need to be online and available to others
• A consultant when you hit a problem the forums cannot solve quickly
• Documentation, so the next person can pick the project up without archaeology

Commercial licences flip that around. You pay up front, usually annually and often per named user, and advanced extensions are commonly priced separately. The advantage is predictability: the cost is visible and easy to put in a funding bid. Ask for a written quote rather than trusting a blog post — including this one — for figures, because pricing shifts with seat count, organisation type and whether you buy direct or through a reseller. Many vendors offer discounts for charities, students and small teams, so it is always worth asking.

Support: what happens when something breaks

With a commercial product, support is part of the deal. You get a ticket system, a service-level agreement, sometimes a named account manager, and a structured training path. For a small team with no GIS specialist, that can be worth more than the licence fee.

Open source works differently. Help arrives through documentation, mailing lists, Stack Exchange, GitHub issue trackers and local user groups. It is often generous and fast, but it is not a contract. If you need a guaranteed response, you can buy support from a consultancy or a hosting provider that specialises in open-source GIS — a middle path plenty of UK organisations take.

A useful test: imagine something breaks at four o'clock on a Friday before a Monday deadline. Write down who you would contact and how quickly you would expect a reply. If you cannot answer that, you have found the gap you need to fill, whichever software you choose.

Plugins, extensions and the formats you will actually meet

QGIS has a large plugin repository, and the range is genuinely impressive. Quality varies, though. Before installing anything, check when it was last updated, whether it still works with your version, and whether its issue tracker shows signs of life. A plugin that has not been touched in four years might still be fine, but do not build a critical workflow on it without testing.

Commercial platforms take the opposite approach: fewer add-ons, more curation, and usually a price tag. You get tools that have been tested together and someone to call when they misbehave. You also get a tighter ecosystem, which can make moving data out later more awkward than you expected.

Formats and coordinate systems

Data, not software, causes most small-project pain. Shapefiles are still everywhere, but they carry baggage: a size limit, ten-character field names, no proper date fields, and a cluster of sidecar files that get separated the moment someone emails them. GeoPackage is a better default for vector data and works in both worlds. GeoTIFF remains the sensible choice for raster.

In the UK, most project data arrives from a handful of sources: Ordnance Survey open products, licensed OS datasets such as AddressBase, Environment Agency flood data, Natural England and MAGIC layers, and HM Land Registry INSPIRE polygons. Some of it is open under the Open Government Licence; some is licensed and comes with usage terms you should read before publishing anything. Coordinate systems catch people out too. British National Grid is EPSG:27700, and mixing OSGB36 data with ETRS89 data without setting the right transformation will shift features by a noticeable margin. Check rather than guess.

Learning curves and skills that transfer

QGIS is approachable if your goal is making a decent map, but the interface is dense and there is no single correct workflow. ArcGIS Pro offers more guided tools and a consistent design language, which some newcomers find easier, though the terminology and licensing model take getting used to.

If your project involves repeated analysis, large tables or joining datasets, a little SQL or familiarity with the GDAL command line pays back quickly. Both major packages wrap these tools, but understanding what sits underneath makes problems far easier to diagnose. The good news is that skills transfer. Someone who learns projections, joins and symbology in one package can move to the other without starting again.

Be realistic about time. A person comfortable with spreadsheets can usually produce a respectable locator map in an afternoon. Cleaning messy address data, matching postcodes and building a workflow that runs again next month takes much longer — often the bulk of the project. Budget for that, not just for software.

A practical way to choose

1. Write down the deliverables: file types, print sizes, whether anything goes online.
2. List your data sources and check what formats and licences they come with.
3. Count the users and note whether any of them are occasional or non-technical.
4. Run a one-day test with your own messy data, not a tutorial dataset.
5. Cost three years, including training, support and hosting — not just year one.
6. Decide who supports it and how, and write that down.
7. Document the workflow and set up backups before the project gets busy.

Hybrid setups are common and sensible. Plenty of small teams use QGIS for analysis and cartography, a commercial cloud service for sharing maps with non-specialists, and a paid support arrangement for the bits they cannot fix themselves. One caution if you plan to redistribute software or embed it in a product you sell: open-source licences such as the GPL carry obligations, and commercial agreements have their own restrictions. Take proper legal advice before building something commercial on top of either.

For most small UK projects, the deciding factor is not which package has more features. It is which one your team will actually open on a Monday morning and use well.

Photo: https://kaboompics.com/ / Pexels