Work/Maptive

From one server to 1,100 releases.

Maptive is business mapping and territory-management software used by large enterprises. Since 2020 Shapelab has been the back-end team for its current version, and since 2023 has looked after its cloud infrastructure and release process.

Client
Maptive, mapping and territory-management SaaS
Location
San Francisco, USA
Years
2020 to today
Our role
Back-end team; cloud infrastructure and releases
6years as the back-end team
1100+versions released since late 2023
5CRM systems connected
0customer jobs lost to a release
The problem

A new version of a product with paying customers.

The current version had to reproduce a mature product and then take over existing accounts, maps and billing without loss.

  • 01Every customer brings their own data. Each account uploads spreadsheets with its own columns, sometimes hundreds of thousands of rows, and expects them geocoded and on a map within minutes.
  • 02Heavy work beside interactive work. Address lookups, territory calculations and exports run for minutes or hours while the map has to stay responsive.
  • 03One server, deployed to by hand. Until late 2023 web requests, background work and scheduled jobs shared one machine, and a release was a manual act on a live server.
  • 04Releases must not interrupt customers. Deploying during a customer’s 40-minute import must not kill the import.
What we built

The back end, then the platform under it.

01

Each customer’s data, kept apart

  • Every account’s uploaded spreadsheets are stored separately from everyone else’s
  • Hundreds of thousands of rows per map, ready in minutes
02

Maps that answer business questions

  • Sales territories built from states, counties and ZIP codes
  • Territories balanced automatically
03

Heavy work that stays out of the way

  • Long-running jobs run in the background
  • The map stays responsive while they do
04

Ready for enterprise buyers

  • Single sign-on and two-step sign-in
  • Connections to five CRM systems and a public API for customers’ own systems
05

From one server to a modern platform

  • Web traffic, background work and scheduled jobs each got their own capacity
  • Every change is tested in a staging copy before it goes live
06

Releases customers never notice

  • A long import keeps running while new versions go out
  • A release only counts as done when everything is confirmed healthy
How it flows

A release, from push to production.

01
Change madeBy the team
02
BuiltOne versioned package
03
StagingUpdated automatically
04
Go-liveStarted by a person
05
Health checkUntil everything is confirmed
The outcome

What it changed.

  • 01Releases became routine. More than 1,100 versions shipped in three years.
  • 02No more shared server. A busy import no longer slows the map for everyone else.
  • 03The same team, six years on. Continuous work since June 2020.
  • 04Kept current. Security updates applied as they are released.
Your product

Outgrown a single
server?

We move live products to a modern cloud setup without stopping feature work. Tell us what you run today.

170+ projects · 100+ clients · 17+ years