Skip to content

Custom development

Salesforce records on an interactive map

An interactive map connects Salesforce records to locations and gives users a direct path back to the underlying record.

Contact us to find out moreAll case studies
Built for
SMT Research, Vancouver
Service line
Custom development
Window
Jun to Sep 2026
The headline numberGeocodingAddress-to-coordinate workflowTechnical capability. Client sales distribution is confidential.

01Key numbers

What we measured

GeocodingAddress-to-coordinate workflowTechnical capability. Client sales distribution is confidential.

02The situation

What was true before

An interactive map connects Salesforce records to locations and gives users a direct path back to the underlying record.

Contact us to find out more

Recognise this in your own org?

Start a diagnosticSee the service lines

03What we built

The mechanism

The public case describes the implementation. Client financial data and findings are withheld under NDA.

Geocoding with review

Convert addresses to coordinates and surface records that need review.

Filters and record actions

Filter by workflow status and open a record directly from its map card.

Sales and Forecasting
Fictional demonstration records
Example workflow status
Scheduled50%
Fictional example
In progress30%
Fictional example
Complete20%
Fictional example

Percentages are of order count, not value. The book carries two currencies as entered and is not converted.

Depiction · Every won order geocoded and plotted, coloured by status. 252 of 252 orders placed, from a starting point of zero with coordinates.The largest circle is one customer. It turned out to be a fifth of the entire book, which nobody knew until the map existed. That finding was worth more than the map.

Surfaces built

Walkthroughs use demonstration data. Client records remain confidential.

  • Interactive record mapImage withheld
  • Status filtersImage withheld
  • Record detail cardsImage withheld
The finding

Client financial information is confidential.

Amounts, ratios, financial findings and underlying client records are not published.

04Outcome

What changed, verified

The implementation is described through its workflows and controls.

  • Interactive record map
  • Status filters
  • Record detail cards
How it was verified

Validation compares source records with system outputs. Client records and financial results remain private.

Sources
  • docs/research/02-revenue-systems.md §1 · Sales Map
  • docs/research/02-revenue-systems.md §1 · The platform-limit story
  • docs/research/03-ai-systems.md §4 · The Apex-to-worker migration

Keep reading

Two more

All case studies
  • Custom development
    28Configuration recordsProvince and tax-class rules stored in custom metadata.

    Tax rules maintained as configuration

    Tax calculation rules need a shared configuration source that works with both formulas and Apex.

  • Custom development
    5 to 6Systems a field technician checked each morningThe recorded before state. No after count was measured, so we do not publish one.

    Five to six systems every morning, and a flow that logged nothing

    Field crews were opening five or six systems before starting work, and a logging flow was telling them it had saved data when it had saved nothing.

Next step

Bring us your hardest Salesforce problem

Tell us which Salesforce workflow needs attention. Start with a free fit conversation; we agree scope and fees before paid work begins.

Start a diagnosticSee the service lines
  • Free fit conversation
  • Live walkthrough of the org itself
  • Vancouver, British Columbia