Case Study

We replaced their entire mapping stack. From scratch.

Power Liens · Los Angeles, CA

PL Maps — a real-time provider search platform for healthcare professionals.

Power Liens needed to get off MapQuest. We built the full replacement — map engine, geocoding, routing, push architecture, and compliance — on a fixed bid with a four-weekend timeline.

Architecture

From MapQuest dependency to owned infrastructure.

PL Maps is a staff tool for searching and routing healthcare providers across a network. The original version was fully dependent on the MapQuest API — licensing risk, rate limits, and no control over the data layer.

We migrated to React Leaflet 5 with CartoDB Voyager tiles, replaced geocoding with Nominatim, and built a Vercel Blob push architecture that decouples the provider feed from the UI entirely.

The rollout used a 2:1 split — 67% of traffic to PL Maps, 33% to legacy — as a controlled migration. By Week 4 the split was dropped completely.

Before

· MapQuest API (all traffic)
· Vendor routing
· No push capability

During Rollout

· 67% PL Maps (React Leaflet)
· 33% MapQuest (fallback)
· Vercel Blob push live

After

· PL Maps only (100%)
· Owned geocoding + routing
· Push architecture

Delivery

Shipped in four weekends.

Week 1

Foundation

Delivered

·React Leaflet 5 migration
·CartoDB tile integration
·Core routing engine

Week 2

Push Architecture

Delivered

·Vercel Blob provider feed
·Real-time routing split
·67% PL Maps / 33% legacy

Week 3

Polish + QA

Delivered

·Map animations + pins
·Mobile QA at 375px
·Performance optimization

Week 4

Compliance + Handoff

Delivered

·CCPA consent system
·Final QA
·Client handoff

Team

Two people. One timeline.

Rodolf Boctor

ThynkQ

Full-stack engineering, architecture, delivery

Ryan

Power Liens

Product direction, domain expertise

Have a project like this?

Fixed bids. Tight timelines. No surprises.

Work with us →See more work

Development by thynk