From the first workshop to the fifth year.
AF-X Flow, AF-X Deploy, AF-X Run. One method, whether you are buying one product or five platforms.
One method, three phases, no handover to a stranger.
AF-X starts with a workshop that proves the fit before anyone signs, deploys against the plan it produced, then keeps running the platform with you for as long as you own it. The same three phases apply to one product in one workshop or five platforms across a national network. Only the duration and number of sites change, never the sequence.
AF-X Flow
“Prove the fit before anyone signs a project.”
Before there is a project there is a workshop. Flow establishes what you actually run, what AF-X would replace and what it would leave alone. It ends in a written fitment and gap output, not in a proposal.
The phase most vendors skip, or bill as a discovery project after the contract is signed.
- Discovery workshopRun against pre-defined AF-X reference workflows, built from real automotive lifecycle journeys, not from a blank sheet.
- Current-state mappingWhat you run today, what stays, what AF-X replaces.
- Data and integration assessmentAssessed against the four AF-X integration areas, system by system.
- Fitment and gap outputWhat fits out of the box, what needs configuration, what is out of scope. In writing.
- Scoped deployment planSequence, and the indicative business case that goes with it.
AF-X Deploy
“Roll out site by site, without stopping the business.”
Deploy runs the plan Flow produced, in a fixed sequence, site by site. Nothing is ripped out and no part of the business stops while it happens.
Seven steps in a fixed order, run site by site.
- ConfigureYour workflows, your sites, your users.
- ConnectBolt onto the DMS, GMS or ERP you already run. Nothing is ripped out.
- MigrateThe data that has to come across, and only that.
- TrainRole-based, in your process, not generic product training.
- TestUAT against the workflows agreed in Flow.
- Go-liveSite by site, never big bang.
- HypercareBridge to RunAn agreed bridge at elevated cover between go-live and business as usual, before handover to AF-X Run.
AF-X Run
“The phase that decides whether it was worth it.”
Run is not a support desk with a phone number. It is three tracks that carry on for as long as you own the platform: keeping it working, changing it as you change, and expanding it when the business is ready.
Three tracks, running in parallel, for as long as you own the platform.
- Support
- Monitoring
- Releases
- Incident management
- Service reviews
- New sites
- New users
- Configuration changes
- Minor enhancements
- New products
- New platforms
- AI adoption
- Expansion reviews
The people behind a successful AF-X implementation.
AF-X
- Owns solution
- Owns deployment
- Owns integration
Your team
- Owns decisions
- Owns adoption
- Owns business process
Partners
- Extends delivery
- Owns local execution
How long each phase takes.
The timings below are a guide, not a fixed schedule. After AF-X Flow, we’ll agree a rollout plan around your products, integrations and sites, setting out the sequence of work and where activities can happen in parallel. Hypercare begins after go-live.
- Phase 01
AF-X Flow
Confirm the right starting point before anyone signs.
- Phase 02
AF-X Deploy
Go live site by site, without stopping the business.
- Phase 03
Hypercare
Elevated support from launch into everyday operation.
- Phase 04
AF-X Run
Keep improving the platform as the business evolves.
Every AF-X implementation follows the same method. The scope changes based on business complexity.
A focused start on one workflow or improvement area.
Broader adoption across workflows, teams or sites.
Wider rollout and coordination for complex operations.
Compare timelines by phase →
| Starter | Growth | Enterprise | |
|---|---|---|---|
| AF-X Flow | 1–3 weeks | 1–3 weeks | 1–3 weeks |
| AF-X Deploy | 4–8 weeks | 8–16 weeks | 3–8 months |
| Hypercare | 1 week | 2 weeks | 4 weeks |
| AF-X Run | Ongoing | Ongoing | Ongoing |
Support that scales with your operation.
Support follows the tier you buy, so coverage and initial-response targets match the complexity of your operation. Resolution timing depends on diagnosis and any third-party systems involved.
Foundation support.
- Channel
- Support portal
- Coverage
- Business hours, in your market
- Service review
- Not included
- Release access
- Standard release train
- Standard request initial response
- Within 2 business days
Operational support.
- Channel
- Support portal and phone
- Coverage
- Priority queue, business hours across the markets you run
- Service review
- Quarterly service review
- Release access
- Standard release train, with advance notice
- Standard request initial response
- Within 1 business day
Dedicated support model.
- Channel
- Support portal, phone and a named customer success manager
- Coverage
- Extended coverage, agreed in the service description
- Service review
- Monthly service review with your CSM
- Release access
- Standard release train, with input into release planning
- Standard request initial response
- Within the same business day
Compare support levels →
| Starter | Growth | Enterprise | |
|---|---|---|---|
| Channel | Support portal | Support portal and phone | Support portal, phone and a named customer success manager |
| Coverage | Business hours, in your market | Priority queue, business hours across the markets you run | Extended coverage, agreed in the service description |
| Service review | Not included | Quarterly | Monthly with your CSM |
| Release access | Standard release train | Standard release train, with advance notice | Standard release train, with input into release planning |
Run is where the next product gets added.
TRANSFORM and Land & Expand are the same motion from two ends. Your first product earned its place by fixing something measurable; the next is a configuration change and a line on the same agreement, not a new procurement.
Land
One product. One measurable problem. Live in weeks.
Connect
Bolt it onto the DMS, GMS or ERP you already run.
Expand
Add the products next to it once the first one pays.
Platform
The platform arrives as a consequence, not as a purchase.
Scale
Roll the same standard across every site and every market.
Questions buyers ask before they start.
Do we have to replace our DMS?
No. AF-X bolts onto the DMS, GMS or ERP you already run through four integration areas, and the Connect step in Deploy exists precisely so that nothing is ripped out. The replacement decision stays yours: later, or never.
Can we start with one product and still get this method?
Yes. Flow, Deploy and Run are one method whether you are buying one product or five platforms. What changes is how long each phase takes and how many sites Deploy runs through, not the sequence, and not the outputs.
Who runs the training?
An AF-X trainer, in the Train step of Deploy, role by role and inside your own process. Where an implementation partner or country partner delivers Deploy, they train against the same material and the same method.
What happens between go-live and business as usual?
Hypercare provides extra support between go-live and AF-X Run. It typically lasts 1–4 weeks, depending on rollout scope and early live performance. The tier table shows indicative examples; we’ll confirm the duration in your rollout plan.
What is included in the subscription and what is a project cost?
Run—support, monitoring, releases, incident management and service reviews—sits inside the subscription at your tier. Flow and Deploy are scoped work, with the commercial terms confirmed in your proposal.
Can our own implementation partner deliver Deploy?
Yes. An implementation partner or a country partner can deliver Deploy against the same method, the same plan and the same fitment and gap output produced in Flow. Flow and Run stay with AF-X so the method, and the accountability for it, do not fragment.
Start with a Flow workshop.
A working session to understand your workflows, systems and opportunities before any larger commitment.
No project.No commitment.No procurement process.
Just a Flow workshop against AF-X reference workflows, and a written fitment and gap output at the end of it.
Or take one of the two standing routes. Both of them still start with Flow.
Buying one product and buying five platforms use the same method. The workshop is the same conversation either way.