GenFrontier homeScope a project
Menu
Filed under
Deliver toBuyers deciding how to start a tracking or inventory software project

Four ways to work with GenFrontier

You can start with a written scope and plan, a build, documentation and training for a system you already run, or support after go-live. Each engagement is set out in its own statement of work.

Scope a project
engagements
Two halves of a torn blank shipping label lying close together, their jagged edges lined up and small red crosshair marks matching on both halves

Not every project should start with a build. Some teams need a written scope before they can ask for budget. Some already own a WMS that nobody was trained on. Some need help keeping a new system running. We offer four engagement types so you can buy the part you need, and each one maps to the six stages of our method.

The four types compared

At a glance Scope and plan Build and integrate Documentation and onboarding Support after go-live
Stages covered 1 to 3 4 to 6 6, for a system you already run After stage 6
Suits Teams that need a firm scope, a plan and an estimate before committing Teams with signed requirements and a plan, from us or from their own work Teams running software with thin or missing documentation and training Teams that want help running what was built
You provide A process owner, time on the floor, sample documents, an IT contact Test environment, system access, partner specifications, testers Access to the system, subject-matter experts, current procedures A named contact, access as agreed, priorities
You receive Process map, integration inventory, requirements with acceptance tests, project plan and estimate Working software and interfaces, source code and configuration, UAT results, cutover plan Guides, SOPs, runbook, training sessions and materials Fixes, small changes, interface checks and an updated runbook
Ends when You sign the plan The handover checklist is signed Training is delivered and documents are accepted The agreed term ends or either side gives notice

What goes in a statement of work

Every engagement is written up in a statement of work (SOW) before work starts. You read it, change it if needed, and sign it. It sets out:

  • Scope: what is included and, just as important, what is not.
  • Deliverables: each document, piece of software, session or report, by name.
  • Acceptance: how each deliverable is checked and who signs it off.
  • What you provide: people, access, environments and data, with the dates they are needed.
  • Schedule, fees and payment terms for that engagement.
  • Change process: how change requests are raised, estimated and approved.
  • Ownership and licensing terms for the source code, configuration and documents delivered.
  • Data handling, confidentiality and incident notification, as described on our security page.

We do not publish prices, because the cost depends on the number of sites, interfaces, trading partners and users. A Scope and plan engagement is how most clients get a reliable estimate for the build.

Scope and plan

Who it suits. Operations and IT leads who know something is missing between their systems but need a written scope, a plan and an estimate before they can ask for budget or compare vendors. It has a fixed scope, so you know what you get before it starts.

What you provide. A process owner who can settle disagreements, about half a day on the floor per area, people for two review sessions, sample documents and exports with sensitive fields removed, and an IT contact who knows the interfaces.

What you receive. A current-state process map, an integration inventory, a requirements specification with an acceptance test for each requirement, and a phased project plan with an estimate for the build.

How it ends. Your sponsor signs the plan. The documents are yours to use with any vendor. You can build with us, brief another developer, or score packaged software against your own process.

Build and integrate

Who it suits. Teams with signed requirements and a plan who are ready to build the missing layer: shipment tracking, inventory management, barcode and labeling workflows, or the interfaces between your ERP, WMS, TMS and partners. If your requirements were written elsewhere, we review them first and note any gaps.

What you provide. A test environment and access to the systems involved, under your accounts and policies. Trading partner EDI specifications and carrier API accounts. People for demos, testers for user acceptance testing, and a sponsor for the go or no-go decision.

What you receive. Working software and interfaces built in increments and demonstrated on your test data. The source code and configuration. A UAT plan and results, a cutover plan, and the documentation and training described in stage 6.

How it ends. The handover checklist is signed: deliverables accepted, source code and configuration delivered, open issues listed with owners, and support arrangements agreed.

Documentation and onboarding

Who it suits. Teams that already run a WMS, TMS or in-house tool that was never properly documented, or whose trained staff have moved on. It is also a low-risk first engagement for teams who want to see how we work before a larger project.

What you provide. Access to the system, preferably a test copy. Time with the people who know it best. Any existing procedures, however out of date.

What you receive. An admin guide, user guides and SOPs for each role, an integration runbook where interfaces exist, and role-based training sessions with the materials. The documentation and onboarding and training pages list each deliverable.

How it ends. Training is delivered, documents are accepted, and the files are handed over in formats your team can edit.

Support after go-live

Who it suits. Clients who want help keeping a system running after go-live, usually software we built. If we did not build the system, we normally start with Documentation and onboarding so the support work begins from written knowledge.

What you provide. A named contact who sets priorities, and access as defined in the SOW.

What you receive. Defect fixes, small changes within the agreed scope, checks on interfaces, and an updated runbook. Requests go to support@genfrontier.com and are logged so you can see their status. The SOW states what is covered, how requests are raised and the hours of cover.

How it ends. At the end of the agreed term, or on notice as the SOW allows. Access is removed and open items are handed back with notes.

Where to start

If you are not sure, start with Scope and plan. It is the smallest commitment that produces something you can act on. To see what each stage produces, read the fictional example project, or answer a few questions in the FAQ.

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.