How we run your hour pack.
No fine print: how work is requested, how it's executed, how it consumes the pack and how it's billed.
Every request gets an estimate and the right profile.
Send requirements
For each pack use, you send us the detailed requirements of the service or task (via email, JSM or the agreed channel).
We estimate effort and complexity
The Quabu team estimates the time and classifies the work as easy, normal or hard. That classification drives the profile that executes it and the consumption factor (see next section).
The estimation consumes the pack
Time spent estimating a request is deducted from the pack, regardless of whether it is finally executed. This way analysis is always compensated.
You decide to move on
With the estimate in hand (hours × profile factor) you decide whether to go ahead, adjust scope or postpone. No surprises.
Every hour is deducted based on the profile that runs it.
A simple change a junior consultant can handle isn't the same as a critical integration that requires an architect. That's why, at estimation time, we classify the task and apply a consumption factor to the pack.
Junior Consultant
1 h worked consumes 0.8 h from the pack
Standard configurations, simple scheme changes, day-to-day admin tasks.
Atlassian Consultant
1 h worked consumes 1 h from the pack
Standard workflows and automations, advanced permissions, functional improvements in Jira, JSM or Confluence.
Atlassian Architect
1 h worked consumes 1.5 h from the pack
Critical integrations, multi-instance architectures, complex migrations, end-to-end solution design.
The classification is shared with you in the estimate. If scope changes, we re-estimate before continuing.
We plan with your team and execute remotely.
Joint planning
We schedule execution with your team, aligning availability and priorities. We aim to fit your moment as much as possible.
Capacity reserved
Quabu reserves capacity of the assigned profile (junior, consultant or architect) so tasks can be run in a proper time frame.
All remote
Implementation is remote. We coordinate detailed planning with you so times and resources match expectations.
CET business hours and ×1.5 outside of them.
Standard hours
Consulting hours run in Quabu's office hours, Monday to Friday, 9:00 to 18:00 (CET). Within this window the profile factor applies (0.8 / 1.0 / 1.5).
Off-hours work
Night or weekend interventions carry an additional ×1.5 factor that multiplies on top of the profile factor already applied.
4 h of architect work at night → 4 × 1.5 (profile) × 1.5 (off-hours) = 9 h from the pack.
We detect and communicate any deviation immediately.
Not your fault
If the deviation is caused by scope changes or missing initial info, Quabu completes the task without billing additional hours.
Client-dependent factors
If the deviation depends on the client (changed requirements, delayed info…), the extra time is deducted from the pack or billed separately.
Paid upfront in blocks of 100 hours.
- Initial block
We invoice the first 100-hour block upfront to kick off the service. From then on you consume at your own pace.
- Following blocks
When the pack balance approaches zero, we invoice the next 100-hour block upfront so service isn't interrupted, until the contracted pack (100, 300, 500 or 500+ h) is complete.
- Cancellation
You can cancel with 30 calendar days' notice. Hours in the already-paid block remain available until the end of the notice period; no new blocks are issued.
A first 100 h block is invoiced upfront. Once used up, the second 100 h block is invoiced, and so on until the pack's 300 h are complete. Each task consumes hours based on its profile (0.8 / 1.0 / 1.5).
How many hours do you need?
Use the pack suggester to see a recommendation, or write to us directly.