SKLA is licensed by your operation's complexity tier — not per driver, vehicle, or admin user. Choose the plan that covers your contracted operational capacity (COC).
COC reflects the volume and complexity your organization runs on the platform: scheduled people and assets, active operating units, and advanced modules you enable. The plan sets the contractual ceiling; the system tracks actual use for predictable growth.
Drivers, nurses, technicians, facility teams, and other operational roles on active schedules.
Vehicles, aircraft, vessels, and other resources tied to trips, shifts, or operations.
Hospitals, depots, contracts, sites, and operating centers with active scheduling.
Solver, advanced compliance, API, BI, and ERP/HR connectors increase supported complexity.
The tier is set in your contract. Plan adjustments are handled commercially only when growth is consistent — always with prior notice.
Complex operations do not grow only in logins or drivers. They grow in rules, assets, units, integrations, and operational requirements.
Investment tracks your operation's real evolution — not every one-off hire on payroll.
References to guide tier fit — not a public formula or calculator. The exact tier is set in a commercial assessment.
About 80 scheduled collaborators, a lean fleet, and one or two operating units.
Typical tier: Essential
About 250 collaborators across three depots or units, with tower and compliance in daily use.
Typical tier: Professional
More than 500 complexity points combining teams, assets, multiple units, and corporate integrations.
Typical tier: Enterprise
Units, integrations, and advanced modules can change tier fit even with a similar headcount.
Tier numbers (for example, up to 100) are a contracted operational complexity index — not headcount alone. People, assets, units, and modules all contribute.
Essential
Up to 100
Contracted COC
Lean operations with few units and straightforward scheduling rules.
Professional
101 to 500
Contracted COC
Multi-site operations with transport, compliance, and tower in daily use.
Enterprise
501 or more
Contracted COC
National groups, holdings, and 24×7 operations with integrations and central governance.
Beyond the plan tier, you add modules by segment and maturity. Pricing on commercial proposal.
Gap-fill suggestions and schedule optimization.
Rule packs by collective agreement, legal profile, and mode.
Fleet, duty, timeline, and tower — per enabled mode (passenger, freight, rail, etc.).
Advanced KPIs and exports for governance.
Integration with ERP, HR, and legacy systems.
Accumulated risk score for tower and solver prioritization.
Composition considers scheduled collaborators, operating assets, active units, integrations, and advanced modules — not a single isolated count.
In a brief commercial assessment we indicate the right tier for your operation and prepare an initial proposal.
Occasional peaks above the limit do not block day-to-day use. We assess recurring growth and, if needed, handle tier adjustments commercially in advance — always with prior notice.
Yes. Optional modules (solver, advanced compliance, transport, API, BI, and others) can be enabled as your operation evolves, through a commercial proposal.
Not directly. Tier fit is based on contracted operational capacity — we do not charge per manager seat or per driver in isolation.
Yes. Each plan has a minimum term from go-live (Essential 12 months, Professional 24 months, Enterprise 36 months), as detailed in the proposal and contract.
No. Implementation is a separate project — configuration, training, and integrations — with scope and fees defined in the commercial proposal, distinct from the monthly license.
Each proposal is tailored to your operation size, contracted modules, integrations, and implementation scope. We do not publish a fixed public price list.
Request an operation assessment