Representative projects across logistics, benefits administration, and equipment operations.
Building real-time visibility and exception management for a regional delivery network.
[Representative Client]
A 50-truck regional delivery company with 3 distribution centers and 40 drivers across a 5-state area.
Dispatch was handled via phone and spreadsheet. Delayed deliveries weren't caught until drivers called in. Route optimization happened manually, and exception handling required multiple back-and-forth calls. This created delays and made it hard to recover from disruptions.
Dispatchers caught delays in real-time and coordinated exceptions without calls. Route efficiency improved, and the team gained visibility into operations. Delivered on time and under budget.
We spent a week riding along with dispatchers and drivers, observing workflows and pain points. We learned that most delays were known too late—drivers would call in after missing a window. The team was also managing complex exception workflows that changed by the minute.
We designed a dispatch console that showed every active delivery on a map, color-coded by status. Delays triggered alerts. Dispatchers could see upcoming exceptions and coordinate with drivers without phone calls. We also built a simplified driver app for route changes and problem reporting.
We built the system using React for the front end, Node.js for the API, and PostgreSQL for data. Integration with their existing GPS hardware took extra care but was essential for real-time tracking. We ran security audits because the system handles location data.
We rolled out first to one dispatch center, ran two weeks of parallel operations with the old system, then full cutover. Training took 2 days. Within a week, dispatchers were using the new system for all decisions.
Real-time dispatch map
All active deliveries on one screen, status at a glance.
Automated delay alerts
When a delivery falls outside the window, dispatch gets notified immediately.
Exception coordination
Dispatchers can reassign deliveries, adjust routes, and notify drivers through the platform.
Driver mobile app
Simple app for receiving route changes, confirming deliveries, and reporting problems.
Reporting dashboard
Weekly and daily summaries for management: on-time percentages, route efficiency, exception frequency.
React, Node.js, PostgreSQL, PostGIS for geospatial queries, AWS for hosting, Twilio for SMS notifications.
The team had one dedicated product lead who spent half time with us. We did weekly demos, and they gave feedback immediately. When the GPS integration got complicated, their technical team helped us understand the hardware constraints. By launch, everyone understood the system because they'd helped build it.
Making enrollment and claims submission easier for benefits members, reducing support volume.
[Representative Client]
A specialty benefits administrator serving small and mid-market employers with flexible health and wellness plans.
Members could only view benefits info through a PDF guide. Claims submission required a paper form mailed in. The support team fielded 50+ calls per week explaining coverage details. Enrollment for new members was manually entered.
Members could self-serve for common tasks. Claims submitted online were processed faster. Support calls dropped 60% in the first quarter. Enrollment took days instead of weeks.
We observed support team calls to understand what members asked about most. We interviewed members about their pain points. Most confusion came from not understanding what was covered and when. Claims submission felt bureaucratic.
We designed a portal that showed each member's specific plan details in plain language. We created a step-by-step claims submission flow that guided members through the process, explaining what each field meant. We highlighted common questions and answers for quick self-serve.
We built with security and privacy in mind—HIPAA compliance was non-negotiable. We integrated with their existing claims system so submissions flowed directly to processing. We added role-based access so employers could see aggregate data without seeing member details.
We phased in by employer group, starting with the largest. We created onboarding guides and held webinars for employers to explain to their teams. The support team monitored usage and we iterated on confusing areas.
Personal plan summary
Each member sees their coverage, deductible, and out-of-pocket max in plain language.
Guided claims submission
Step-by-step form with help text, showing what's required and why.
Claims history and status
Members can see all past claims and current status—never wondering if it went through.
FAQ and search
Common questions answered directly—reducing support calls for simple questions.
Employer dashboard
Employers see enrollment status and plan participation without seeing member details.
React, Node.js, PostgreSQL, HIPAA-compliant AWS setup, encryption at rest and in transit, role-based access controls.
We worked closely with both the product team and the support team. Support staff helped us understand what members actually asked about—not what we assumed. This was invaluable for designing the FAQ section. The compliance team reviewed security early and often, catching requirements before they became expensive late changes.
Unifying fragmented sales and service workflows for a multi-location equipment supplier.
[Representative Client]
An equipment rental company with 8 locations, 150+ staff, and 2000+ active customer relationships.
Sales team used one system, service team used another. Customer data was duplicated across systems. There was no clear visibility into what equipment a customer had rented or their service history. Cross-team communication happened via email.
One system for sales and service. Customer data unified. Service reps could see rental history instantly. Sales could see service interactions to understand customer relationships better. Cross-location visibility improved coordination.
We mapped the full customer journey from initial sales call through long-term service. We found sales reps didn't know what service calls customers had made. Service reps often re-explained known issues because they couldn't see the sales notes. Data duplication and spreadsheet workarounds were rampant.
We designed a single platform where every customer had one profile. Sales reps saw service history. Service reps saw rental agreements and past interactions. Every location could see cross-location rentals and service. Workflows for quotes, contracts, and service requests were all built into one system.
This was a complex migration—we had to pull data from two legacy systems, de-duplicate customer records, and build integrations. We created a data warehouse layer that handled the messy merging safely. We built APIs so the old systems could keep running during the transition.
We did a gradual cutover by location, starting with the smallest. Sales team migrated first, then service. We ran parallel systems for 3 weeks to catch data issues. Training was intensive—this was a major change to their workflow.
Unified customer profile
One customer record visible to all teams, all locations, with complete history.
Equipment tracking
See what each customer has rented, when it's due back, and any pending service requests.
Service request workflow
Service reps log calls, create tickets, track status—all visible to other locations and teams.
Cross-location dashboard
Management sees all active rentals, due dates, service backlog, and utilization by location.
Quote and contract generation
Sales reps create professional quotes and contracts directly in the system, with automatic terms and pricing rules.
React, Node.js, PostgreSQL, legacy system integrations via APIs, data warehouse for de-duplication and reporting.
This project required buy-in from both sales and service leadership. We did workshops with each team separately first to understand their specific needs, then brought them together to find common ground. The data migration was complex—their IT team worked closely with us to understand the legacy system quirks and ensure nothing was lost. Post-launch, we had a few weeks of intensive support as the teams adjusted to the new workflows.
Start with a conversation about your specific challenges and opportunities.
Plan your product