A plan that matches where your organisation is today

Yes. The plan can be changed during the engagement, both up and down. The change applies to the organisation, not to an individual user.

The available scope changes with the plan, and the difference in the subscription is settled within the billing cycle. Data, work orders and vehicle history stay in place - changing a plan is not a move to a new account.

Yes. Specialist data, advanced automation, extra communication channels and supplier integrations are add-ons bought on top of a plan - you don’t have to move to a higher subscription just to switch on one specific thing.

No. Specialist technical data is a separate add-on, and its availability also depends on the data provider’s licensing terms. No plan includes it automatically in its price.

Yes. Additional locations can work inside one organisation on a shared service standard, with roles, permissions and data separation preserved. That scope is addressed by FLEETPRO and by individual rollouts for service networks.

Yes - fleet coordination is one of the processes the platform is being built from. Vehicle status, inspection dates, cost decisions and documents are visible to both the fleet coordinator and the workshop. For larger fleets and CFM we run a rollout conversation.

Yes - we grant Partner API in a controlled, auditable scope, agreed individually with the partner after verification and consent. It is not open, self-service access.

Yes, as an individual integration. The data scope, permissions and the stage of the process the service is wired into are agreed before switching it on - access is granted case by case, never by default.

Yes. All prices in the price list are net, per organisation, billed monthly. VAT is added on top.

Yes, and that is usually how we start. BASIC puts basic customer and vehicle handling in order, and a higher plan or an add-on is switched on only once the process actually calls for it.

We start with a demo and a conversation about your processes, and the starting terms - including time to get to know the system - are agreed before signing. We don’t switch an organisation on blind, without going through configuration.

Yes - the rollout can include cleaning up and importing data, but the scope depends on the quality of the sources, the type of data and how the organisation is configured. Before migrating we decide which data is operationally needed: customers, vehicles, work-order history, services, price lists, locations and partners.

Not always. The safest approach is to start with the key process and move the rest across gradually: bookings, work orders, vehicle history, reports, integrations and communication.

It depends on the number of locations, the quality of the data, the integration scope and the chosen plan. For a straightforward workshop a rollout can be shorter; for a network, a fleet or partner integrations it needs a plan of its own.

A failed payment does not cut off access overnight. We retry the charge and flag the problem, and the organisation has time to settle it before access is restricted.