GIS Development Cost: What Drives the Price
What decides the cost of a GIS application or a dedicated GIS developer: seven cost drivers, licences, hidden costs and how to get an estimate you can trust.
By Ahsan Mukhtar, CEO and Managing Director
Key takeaways
- The cost of GIS development is set mostly by data quality, integrations, the platform and how clear the requirements are, not by the map itself.
- Software licences such as ArcGIS or FME are a separate cost from development and should be listed in any estimate.
- The most reliable estimates come from a short discovery phase on a sample of your real data.
The cost of a GIS project, or of hiring a GIS developer, depends far more on your data, your integrations and how clear the requirements are than on the map itself. Two projects that look alike on screen can differ several times over in effort. This guide sets out what drives the price, so you can compare quotes like for like and avoid surprises.
The seven cost drivers
| Driver | Costs less when | Costs more when |
|---|---|---|
| Data quality | Data is clean, consistent and in one place | Data is spread across shapefiles, CAD drawings and spreadsheets, with gaps and errors |
| Integrations | The app stands alone | It must read or write records in ERP, CRM, asset or billing systems |
| Platform | You already own the right licences, or open source fits | New licences or a platform change is needed |
| Users and permissions | One user group with the same access | Several roles, sign-in through your identity provider, field and office users |
| Scale and performance | Modest data volumes | Millions of features, imagery, point clouds or live data |
| Requirements | The workflow is clear and stable | Requirements are still being discovered |
| Support after launch | Your team will run it | You need ongoing maintenance, monitoring and updates |
Data is the most underestimated of these. Cleaning, converting and validating existing data is often the largest single task in a project, and an estimate made without seeing your data is a guess.
Engagement model changes how you pay, not just how much
- Project-based delivery suits a defined outcome. You agree scope, milestones and acceptance criteria up front, and the price follows the scope.
- Dedicated developers suit ongoing work where priorities change. You pay for agreed capacity each month and direct the work yourself. See hire GIS developers.
- Specialist consulting suits a focused question, such as choosing a stack or planning a migration, and ends in a written recommendation.
Our comparison of dedicated teams, fixed projects and freelancers explains when each fits.
What affects the cost of a GIS developer
- Seniority. A senior engineer who has solved your problem before often costs less overall than a junior one learning on your project.
- Specialism. Narrow skills, such as Utility Network modelling, PostGIS performance tuning or point cloud processing, are scarcer than general web mapping.
- Platform knowledge. ArcGIS and open-source stacks need different experience. Some projects need both.
- Location and overlap. Rates vary by region, and so do working-hour overlap and communication style. Judge the total cost of getting the work done, not the hourly rate alone.
- Continuity. A developer who leaves mid-project takes knowledge with them. Teams that share knowledge reduce that risk.
Licences are a separate line
Development cost and licence cost are different things. ArcGIS, FME and some 3D or imagery tools are licensed separately, often per user or per year. Open-source tools such as PostGIS, GeoServer and QGIS have no licence fee, but still need people to run and maintain them. A good estimate lists every licence the design depends on before you commit. Our guide to open source GIS or ArcGIS compares the two.
Hidden costs to plan for
- Data cleaning and migration that only becomes visible once work starts
- Changes to scope after users see the first version
- Hosting, monitoring and backups
- Updates when the platform changes, for example when Esri retires an app such as Web AppBuilder
- Rework after a poor hire or a vendor that did not understand GIS
How to get an estimate you can trust
- Write a short brief. The problem, who will use the system, what data you have and any deadlines. Our guide to writing a GIS project brief shows what to include.
- Share sample data. Even a small extract lets a provider see the real state of your data.
- Ask for a breakdown. An estimate split by milestone, with its assumptions written down, is easier to compare and to control.
- Consider a discovery phase. A short, paid discovery or a working prototype on real data turns a guess into a plan.
- Compare like for like. Check that each quote covers the same scope, licences, data work, testing and support.
Questions to ask a GIS vendor about price
- Which assumptions is this estimate based on, and what would change it?
- How much of the effort is data preparation?
- Which licences does the design need, and who buys them?
- What happens if requirements change during the project?
- What does support cost after launch?
Summary
GIS development cost is driven by data quality, integrations, platform, users, scale, requirements and support. Licences are a separate cost. The surest way to an accurate figure is a clear brief, a sample of real data and a breakdown by milestone. If you would like an estimate for your project, tell us what you need.
References and further reading
Working on something similar? Jugrafiya builds GIS products, spatial data pipelines and the web and mobile software around them.
Talk to an engineer