DrivLynk

DrivLynk connects carriers, drivers, and dispatchers on one platform: post a load, get matched, get it moved. We inherited the build from a previous overseas agency that had run well past budget with little usable code to show for it, so the engagement began with an audit of what actually existed before any new work started. From there we rebuilt and shipped the production API, the Flutter apps for iOS and Android, the onboarding and payment web app, and the admin dashboard, then took the mobile apps through the App Store review process that had stalled under the previous team. It is now our largest engagement, and it is still active.

• The previous agency had gone well past budget and left little of the platform we could safely build on without a full audit first
• The mobile apps were stuck behind App Store review blockers the previous team had never resolved
• Performance and caching problems only showed up at real scale, once actual drivers and carriers were using the platform
• Payments, load matching, and document handoffs between carriers and drivers all had to work with no room for silent failures

• Audited the codebase we inherited from the previous agency before writing new code, so the rebuild targeted what was actually broken
• Built the Node.js and TypeScript API on DigitalOcean Kubernetes, backed by MySQL, Redis, and object storage
• Built the Flutter apps for iOS and Android covering driver and carrier flows, onboarding, and in-app payment
• Built the React Router v7 onboarding, payment, and auth web app, plus a React and TanStack Router admin dashboard
• Took the mobile apps through App Store submission and review, resolving the blockers that had stalled the previous launch attempt
• Ran a scale audit and fixed the performance and cache-invalidation issues it found, with QA tracked through Jira
• Now run paging and on-call for the production system, so incidents get caught before drivers and carriers notice