FLOW LGX · PART 13 · OCTOBER 2026
October 2026 was the month Flow LGX went from “working on our machines” to “working for real users at flowlgx.com”. Deployment is not a button press at the end; it is a milestone with its own checklist.
Month by month, how a logistics platform for a Toronto client went from a simple brief to a live, multi-company SaaS product.
In October 2026 Flow LGX went live: fast-loading pages, a public website for shippers and carriers, and a go-live checklist covering email, payments and settings.
The front end is built with Vite into small, cache-friendly files. Each build gives JavaScript and CSS files unique names based on their content, which lets the server tell browsers to keep them for a full year. When we release an update, the file names change and browsers fetch only what is new. Repeat visits load almost instantly.
Before each release the build had to pass type checks and linting with zero errors — a rule we kept for the whole project.
Alongside the signed-in platform, flowlgx.com has a public site for shippers: how the mobile experience keeps them informed away from their desk, advanced search and filtering, shipment documents such as invoices and packing lists, a complete timeline view for each shipment, photo documentation, a step-by-step process and a frequently asked questions section. The “Become a carrier” onboarding is linked from the top of every page.
The super admin home page puts problems first. An “alerts require attention” panel lists risks — for example admin accounts that have not switched on two-factor login. Below it sit the numbers an owner checks every morning: active distributors, vendors and customers, and revenue this month, followed by a payments chart (collected, pending and failed over four weeks) and marketplace activity (requests, bids and awards over fourteen days).
We do not call a product live until this list is done:
Treat go-live as a milestone with a checklist, not as the last day of development. Most launch problems are configuration, not code.