FLOW LGX · PART 14 · NOVEMBER 2026

Flow LGX, part 14: after launch — what real users changed

Launch is when the real feedback starts. In November 2026, with companies, carriers and customers using Flow LGX for real work, the job changed from building features to listening and tightening what was there.

About this project

Month by month, how a logistics platform for a Toronto client went from a simple brief to a live, multi-company SaaS product.

In short

After launch the work shifted to listening: small fixes on a steady rhythm, careful re-testing of anything that touches money or access, and a clear plan for what comes next.

What only production teaches you

No amount of testing replaces real users. In the first weeks the useful feedback was rarely about big features. It was about wording on a button, the order of columns in a table, a filter people expected to find in a different place, or a step in carrier onboarding that needed a clearer hint. Each is small; together they decide whether people enjoy using the product.

How we handle changes after launch

A few simple rules keep post-launch work calm:

  • Every report is written down with the role, the screen and what the user expected.
  • Fixes are grouped and released together on a regular rhythm, rather than one risky change at a time.
  • Anything that touches money, permissions or stock is tested again as every affected role before it ships.
  • The client sees a short list of what changed with each release.

What comes next

The platform is now a base to grow on. Natural next steps include deeper reporting for distributors, more help inside carrier onboarding, and continued work on the mobile experience for drivers and shippers. Whatever is built next will follow the same pattern as the rest of this diary: a written scope, a milestone the client can click, and a release with a checklist.

Thank you for following the diary

Fourteen months, one change of direction, and a live SaaS product. If you are planning a logistics, operations or multi-role platform and want to talk about how we would approach it, the contact button on this page reaches us directly.

What we shipped

  • A feedback log by role and screen
  • A regular release rhythm for fixes
  • Re-testing rules for money, permissions and stock
  • A first post-launch roadmap

Lesson learned

After launch, the small things are the product. Users forgive a missing feature far sooner than a confusing button.