Power Liens / provider search

We replaced their entire mapping stack. Without leaving a black box behind.

In four weekends, a live provider-search experience moved off MapQuest and into an owned operating surface.

Discuss a Product BuildSee the delivery record
Delivery
4 weekends
Commercial model
Fixed bid
Migration
Controlled, then complete

Delivery receipt

The brief was not a redesign. It was a clean exit.

Replaced a MapQuest dependency with owned map infrastructure, provider routing, and a maintainable search surface.

Delivery
Shipped across four weekends
Commercial model
Fixed bid
Outcome
Vendor risk was removed and provider search became an owned, maintainable production surface.

Architecture

A live migration, with a maintained path at the end.

Provider discovery depended on MapQuest licensing, rate limits, and an external data layer.

Migrated the mapping experience to React Leaflet with owned provider routing, geocoding, and a maintainable push architecture.

The rollout used a controlled two-to-one split: PL Maps carried 67% of traffic while the legacy map remained available for the remaining 33%, then the fallback disappeared once the owned path was proven.

  1. Before

    • MapQuest API carried all traffic
    • No control of the data layer
    • No push capability

  2. During rollout

    • 67% PL Maps via React Leaflet
    • 33% legacy fallback
    • Vercel Blob provider feed live

  3. After

    • PL Maps handled all traffic
    • Owned geocoding and search
    • Push architecture in place

Delivery

Four weekends. Four irreversible decisions.

  1. Week 1

    Foundation

    • React Leaflet 5 migration
    • CartoDB tile integration
    • Provider search and clustering

  2. Week 2

    Push architecture

    • Vercel Blob provider feed
    • Controlled traffic split
    • 67% PL Maps and 33% legacy

  3. Week 3

    Quality pass

    • Map behavior and pins
    • Mobile QA at 375px
    • Performance optimization

  4. Week 4

    Compliance and handoff

    • CCPA consent system
    • Final QA
    • Client handoff

ThynkQ roles

Founder-led accountability, with specialist support close by.

The engagement remained founder-led. The wider ThynkQ team supports focused work across these disciplines.

  • ThynkQAccountable delivery owner
  • Marvin HellmanChief Investment Officer
  • Alfred BostorousEngineer
  • Ivan MihailovTechnical Project Manager
  • Ryan G.Product strategy & operations

Next project

A fragile dependency is a product decision.

Start with a focused Product Build conversation. The first step is a clear scope, not a generic sales call.

Discuss a Product BuildSee selected work