GenFrontier homeScope a project
Menu
Filed under
Deliver toOperations, warehouse and IT leads deciding what to build or fix first

Logistics software and the work that makes it usable

We build the tracking and inventory layer your ERP, WMS and TMS don't cover, and we do the scoping and handover work that decides whether people use it.

Scope a project
services
An open wooden toolbox seen from above, its trays holding a slide rule, a pencil, a small spirit level and a red stopwatch

GenFrontier builds the shipment-tracking and inventory software your ERP, WMS and TMS don’t cover, scoped in writing before we build and handed over with documentation and a trained team. The services on this page come in two levels, and most projects draw on both.

Two levels of service

Level A: software. This is what gets built. Shipment tracking, inventory management, barcode and RFID labeling, and the ERP, WMS and TMS integration that connects them to the systems you already run. Each one is a bounded layer added around your current systems, not a replacement for them.

Level B: delivery. This is the work that makes the software usable: requirements analysis, project planning, documentation, and onboarding and training. Each is a named deliverable in the statement of work, with a document or a session behind it, rather than a line folded into support.

Three phases

Every engagement moves through the same three phases. They group the six stages described in how we work.

Phase Stages Services What you hold at the end
Scope 1 Walk the process, 2 Write the requirements, 3 Plan the project Requirements analysis, project planning A signed requirements document and a dated plan
Build 4 Build and integrate, 5 Test and cut over Tracking, inventory, labeling and integration software Working software that has passed its acceptance tests
Hand over 6 Document and onboard Documentation, onboarding and training Guides, runbooks and a trained team

Support follows the handover for clients who want it.

How engagements combine them

You do not have to buy all three phases at once. The engagement types cut across the two levels:

  • Scope and plan. The Scope phase on its own, as a fixed-scope first phase. You keep the requirements and the plan, and you can use them with any vendor or developer.
  • Build and integrate. The Build and Hand over phases, starting from signed requirements. The software, its interfaces, the documentation and the training are delivered together.
  • Documentation and onboarding. The Hand over phase for a system you already own, such as a WMS that went live without usable guides or a trained super-user on each shift.
  • Support after go-live. Fixes, small changes and interface monitoring once the system is running.

GenFrontier resells no software and has no vendor partnerships, so a recommendation on these pages is never tied to a license. Source code and configuration are delivered at the end of a build, and ownership and licensing terms are set out in each statement of work.

If you are not sure where to start, follow one fictional shipment through a full engagement in the example project, or bring us the process that hurts most and we will tell you which phase it belongs to.

Scope your project.

Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.