Discover
Map teams, business processes, countries, legal entities and the systems you run today. This is where requirements that would derail a rollout later get found.
Enterprise
Enterprise implementation, in five stages.
Larger rollouts fail on the things nobody mapped: an unlisted legal entity, an approval chain that only one person understood, a permission model that did not survive contact with a real department. Tork implementations are structured to surface those first.
Implementation
Discover, configure, migrate, validate, launch.
Each stage has an exit condition. The next stage does not start because a date arrived — it starts because the previous one is genuinely finished.
Configure
Set up workspace structure, permissions, departments and the workflows your operation actually uses — base roles, permission packs and access scope.
Migrate
Prepare approved customer, employee, project and operational information for import, with the customer deciding what moves and what stays behind.
Validate
Test access, workflows, payroll configuration and integrations before anyone depends on them. Payroll and permissions are validated, not assumed.
Launch
Train owners and administrators, then move the organization into production with a known support path.
Implementation scope and timeline are defined after discovery. We do not publish a standard number of weeks, because the honest answer depends on how many entities, countries, integrations and legacy systems are in play. Discovery produces the scope; the scope produces the timeline.
Where enterprise scope applies
Signals that a rollout needs the full path.
Not every company needs an implementation project. These are the situations where one pays for itself.
Multiple countries or legal entities
Payroll, approval chains and reporting differ per entity. That structure has to be modelled before anyone runs a period.
A real permission model
Departments that must not see each other's data, an audit function that needs read-only oversight, and exceptions that still have to work.
Migration from existing systems
Customer, employee, project and operational records coming out of tools your team has used for years, with decisions about what does not move.
A security or procurement review
An IT reviewer with a questionnaire. Send it early — the security overview states plainly what Tork does and does not claim.
Process work that is genuinely yours
Claims handling, compliance evidence, property operations, inventory or another workflow specific to your industry, built with your team.
More users than a standard plan covers
Seat counts, onboarding and infrastructure arrangements handled as part of the engagement rather than bolted on afterwards.
Start where you are
Different questions need different conversations.
Pick the one that matches where you are in the evaluation.
Start with discovery.
Bring your org structure, countries and the systems you are trying to replace. We will tell you what fits, what needs configuration and what does not exist today.