Fleet portal
The fleet tracking portal that ran on Tookan, rebuilt as a custom Next.js portal. It cut costs by about 80% and gave AiudApp direct control over the workflows, interface, releases and continued development of its core operation.
named production case · takeover → fractional CTO
Andres came to me for a fleet tracking portal that ran on Tookan. I rebuilt it as a custom Next.js portal at about 80% lower cost, then built the customer tracking app, updated the drivers' Flutter app, put routing on our own Valhalla server and built the API gateway enterprise clients connect through. Andres runs the business. I run the technology behind it.
the original condition
Andres Bocanegra asked me for a fleet tracking portal. At the time it ran on Tookan, some client dashboards lived in Bubble, the drivers used an outdated Flutter app and Xano held the data. Patching the Tookan setup would have added one more piece to a system nobody owned. I proposed rebuilding the portal and taking over the whole thing, and Andres said yes.
three connected product surfaces
The operations team, field workers and customers each saw a different interface, but their workflows shared data, task state and business consequences. Treating any surface as a standalone development job would have left the ownership gap in place.
The fleet tracking portal that ran on Tookan, rebuilt as a custom Next.js portal. It cut costs by about 80% and gave AiudApp direct control over the workflows, interface, releases and continued development of its core operation.
The Flutter app the fleet drivers use was updated and its flows optimized. Observed backend requests fell from 192.3 to 81.8 per active user-hour, a 57.5% reduction.
After the portal, a separate Next.js tracking app for Andres's customers, and an API gateway so enterprise clients connect to the platform with their own API keys. Client dashboards were also moved from Bubble into their own Next.js application.
measured production results
what was done
A custom Next.js portal instead of a third-party dispatch product, at about 80% lower cost. Six months, because the business kept running on it and an enterprise client kept changing the requirements along the way.
A separate Next.js application for Andres's customers to follow their own tasks, designed as part of the platform. Client dashboards were also moved from Bubble into their own Next.js application, with Xano kept as the shared backend.
Bring the Flutter app the fleet drivers use into the new brand, improve its flows and cut backend requests per active user-hour from 192.3 to 81.8.
Replace paid Google routing with our own self-hosted Valhalla server, with infrastructure and deployment under direct technical ownership.
An API gateway in front of the platform so enterprise clients connect with their own API keys, every call logged and replayable, and new partners onboarded without a deploy.
the outcome
Rebuilding the Tookan portal in Next.js took six months, because the business kept running on it and an enterprise client kept changing the requirements. Work across the rest of the platform continued for the following year and is still ongoing. AiudApp got a platform it could grow on at about 80% lower cost, Andres got his time back, and the work did not end with an invoice: I became a partner in the business.
“I really hope my competitors don’t find out about you lol.”
what this case does not claim
Tell me what your company runs on and who is holding it together today. In 15 minutes I'll tell you what it takes for me to own it, and what it costs.