Logistics quote and tracking portal
Crowbar needed a product, not a brochure. I designed and built a quote and tracking portal as a SaaS surface for transportation and storage companies, then handed it to the next engineer after the client had accepted the work.
There was no portal
Quotes and tracking were not sitting in an old app waiting for a redesign. The system did not exist. Sales still had to price work and customers still needed to see where freight was. The brief was a full product for transportation and storage companies — multi-tenant SaaS shape, not a one-off site for a single desk.
I worked directly with sales on what the flows had to do, then built them. Speed was the constraint: the client was in the loop, and the work had to pass their review while the product was still early.
- Greenfield, one primary builder: architecture, UI, API, database, and deploy.
- First implementation in Express, then a move to Next.js when the product needed an App Router surface instead of a bolted-on frontend.
- Hosted on AWS Lightsail with CI so a later engineer could take the repo without inheriting a laptop deploy.
- Early-stage and fast. The success test was client sign-off and a clean offboard, not a traffic chart.
Quote, store, track
quote → db → track
↓
next.js
↓
lightsail
Quotes write into a database sales and operations can trust. Tracking reads that same record, not a parallel spreadsheet. Next.js is the product UI. Lightsail is the boring runtime: one box, backups, and a pipeline. The Express years are not hidden — they are how the domain got real before the UI stack changed.
I was the engineer in the room with sales and the engineer who shipped. When I left for AvenFort, the app was still early, but it was far enough that a new developer could take it and the client had already accepted what was there. Offboarding was part of the work.
Express (initial) · Next.js · AWS Lightsail · CI/CD · shared database for quotes and tracking
A working portal existed where there had been none. The client signed off. The next developer inherited a Next.js app on Lightsail, not a demo on a workstation. I do not publish volume or revenue from this engagement.
- Ship the domain first if you must. A later Next.js migration is cheaper than guessing the UI framework before sales knows the quote.
- SaaS for an industry is a different shape than a custom site for one company. Tenancy and handover show up earlier than polish.
- If you are the only builder, the offboard is the architecture review. CI and a repo the next person can run are the deliverable.
Shipping a portal under a live sales team?
I have taken a logistics product from nothing to a handover the client accepted. Open to remote technical-lead conversations.