ArcGIS development

For organisations on the Esri platform, we extend ArcGIS to fit their operations: custom web apps and widgets, ArcGIS Pro add-ins, field workflows and Utility Network implementations. We also move teams off retired or retiring Esri apps onto their current replacements.

Discuss an ArcGIS project

See it in practice Mello Engine: Automated processing and publishing of CAD, BIM and GIS files to ArcGIS Online.

Review note: Confirm Esri products actually delivered. No partnership or certification claims are made until verified.

ArcGIS ships with a broad set of configurable apps, but the last part of a workflow often needs custom development: a widget, an add-in, an integration or an automated process.

Migrations such as Geometric Network to Utility Network demand careful data preparation and validation to avoid disrupting operations.

We configure first and code only where configuration stops. That keeps solutions upgradeable as Esri releases new versions.

Custom work uses the supported APIs and SDKs, including the ArcGIS Maps SDK for JavaScript, Experience Builder developer edition, ArcGIS Pro SDK and ArcPy. Integrations go through REST services.

Experience Builder applications and custom widgets
ArcGIS Dashboards for operations and management
Field Maps and Survey123 data collection workflows, including Tasks in Field Maps
Migration from retiring apps: Workforce to Tasks in Field Maps, Web AppBuilder to Experience Builder
ArcGIS Pro add-ins and Python toolboxes
Utility Network modelling and migration support
StoryMaps for public communication

Is this the right fit?

Confirm fit guidance matches the projects you accept

A good fit when

You already run ArcGIS Online or ArcGIS Enterprise.
Configuration alone does not cover the workflow you need.
You are moving off a retired or retiring Esri app.

What we will need from you

Access to the ArcGIS organisation or Enterprise environment, arranged by your administrators.
Your change and deployment procedures.
Example data and the people who use the current workflow.

What shapes scope and price

ArcGIS version and deployment model.
Number of apps, widgets or add-ins.
Data migration and validation effort.
Integration with non-Esri systems.

We do not publish fixed prices because these factors vary widely. After a first conversation we send a written proposal with scope, milestones, acceptance criteria and cost, so you can compare like for like before committing.

Where it is used

Network migration: Prepare and validate data for a Geometric Network to Utility Network move.
Field inspections: Replace paper forms with Field Maps and Survey123 workflows that sync to the office.
Workforce retirement: Move dispatch and assignment workflows from Workforce, which Esri retires in late 2026, to Tasks in Field Maps.
Operations dashboards: Live views of outages, crews or asset condition for supervisors.
Analyst productivity: ArcGIS Pro add-ins that automate repeated editing and QA steps.

Apps: Experience Builder, ArcGIS Dashboards, ArcGIS StoryMaps
Field: ArcGIS Field Maps (including Tasks), Survey123, QuickCapture
Legacy and migration: Workforce to Field Maps Tasks, Web AppBuilder to Experience Builder, Geometric Network to Utility Network
Development: ArcGIS Maps SDK for JavaScript, ArcGIS Pro SDK, ArcPy
Data: Utility Network, Enterprise geodatabase on SQL Server