TREY MOTSENBOCKER
← All work

SalesDay Pulse

STATUS
CLIENT WORK: LIVE
TIMELINE
FEB 2026 – PRESENT
SCALE
30+ retail store locations
ROLE
Problem definition · Workflow design · Application development · Deployment
ARCHITECTURE
Mobile-first client over a managed backend, with map rendering as the primary account view rather than a list.
STACK
React · Supabase · Leaflet.js

BUSINESS PROBLEM

A field sales rep was managing daily routes, visit notes, and dozens of retail accounts, meaning individual stores, across a phone, a notebook, and memory.

WHAT I BUILT

A mobile-first field sales tool for managing the daily route, logging visits as they happen, and seeing active accounts on a map instead of a list.

RESULT

In daily use by one field sales rep covering 30+ retail store locations.

MY ROLE

  • Problem definition
  • Workflow design
  • Application development
  • Deployment

HOW IT WORKS

  1. 01Accounts and the day's route are shown mobile-first, because the tool is used standing in a parking lot.
  2. 02Visits are logged at the moment they happen rather than reconstructed at the end of the day.
  3. 03A map view shows active accounts geographically so the route can be adjusted in the field.

TECHNICAL IMPLEMENTATION

React front end with Supabase for data, and Leaflet.js for account mapping.

LIMITATIONS

  • Built for one rep's workflow. It is not a multi-user CRM and has no manager reporting view.
  • No offline mode, so a dead zone means the visit gets logged late.