Consulting packages are blocks of hours that fund technical support: scoping a project, migrating to the cloud, deploying tools or training teams. Three hour volumes and one transformation pack are available.
What these packages are for
A consulting package does not replace a managed-services subscription: it funds expert work with a beginning and an end. Typical uses are preparing a migration, structuring an existing environment, documenting a procedure or training a team on a tool.
The hour volume gives visibility on the available budget. Hours are consumed against the scope agreed at the start, which avoids handling each request separately and losing the thread of the project.
Starter Consulting — 10 hours
This package covers a targeted need: a quick audit, the configuration of a service, a support intervention or unblocking a specific point. It suits small organisations and assignments whose scope fits in a few steps.
Across ten hours, scoping and documentation take a real share of the time. Define two or three concrete objectives rather than an open list. The details of the offer are on the Starter Consulting — 10 h page.
Business Consulting — 40 hours
This volume fits projects split into several batches: migrating a fleet, deploying an ERP, automating internal processes. It lets you chain the phases without reordering after every intervention.
A 40-hour package is usually organised in phases: scoping, implementation, acceptance and skills transfer. Ask for a workload plan at the start, then track consumption at each progress review. See Business Consulting — 40 h.
Enterprise Consulting — 100 hours
This package targets large environments: several sites, several teams, service-continuity constraints. It absorbs a long-running project or several workstreams run in parallel.
At this level a project manager and a milestone calendar become necessary. Hours are also used to support internal teams: documentation, procedures and handover of operations. See Enterprise Consulting — 100 h.
Digital Transformation Pack
The pack combines the three stages of a transformation project: audit of the current setup, migration to the cloud and team training. It addresses organisations that must modernise a set of tools rather than fix a single isolated point.
The three-stage structure avoids the classic mistake of migrating before the usages are clarified. The audit produces a current-state report and a list of priorities, the migration builds on that document, and the training makes the team autonomous on the new environment. See Digital Transformation Pack.
How an assignment runs and quoting
An assignment starts with a scoping discussion: context, objectives, constraints and deadlines. Scoping determines the right package, a written scope and a calendar. This step prevents misunderstandings about what is included and what is not.
During the assignment, each intervention is recorded and consumed time is tracked. If the need exceeds the chosen package, raise it before the hours run out: an additional block can be added. For a need outside the catalogue, such as managed services, cybersecurity or custom development, the request goes through the contact form and leads to a quote.
