Service lanes we runHours
Suggested engagements for this lane. Contact opens with this service selected; a confirmation is emailed to the address you enter.
Capacity
Some months the work is a queue, not a project. Capacity is billed monthly: the hourly rate times 30. A monthly block does not roll over.
How an engagement runs
-
01
Choose
Pick the country, then the number of hours. The amount updates immediately.
-
02
Request
Send the block. We confirm the queue before any hour is spent.
-
03
Spend
Hours go to agreed tasks. You can see what each block was used for.
-
04
Renew
Add hours, or let a monthly block renew at the same size.
What you leave with
- A block of time you can point at the next real task
- A monthly allocation when the queue does not end
- A monthly bill equal to the hourly rate times 30
Hour packs tied to this lane
Monthly care
A team with steady, varied tasks and no single project brief.
Monthly plus
Product or operations teams with a weekly backlog.
Engineering month
Companies that want reserved capacity without a fixed-scope contract.
Included in the build
Capacity
A month for a queue, not a substitute for a scope.
Some months the work is a queue, not a project. Capacity is billed monthly: the hourly rate times 30. Monthly care is the smaller block. Monthly plus is for a stream that needs regular attention. An engineering month is a reserved block for a dedicated stream, still not a fixed-scope product build.
A monthly block does not roll over. That is deliberate. Unused time is not a balance you can spend in a later panic. If the work has a shape and an end, it should be a fixed engagement. Capacity is for the backlog that is real and varied: small product tasks, site work that is not a relaunch, engineering that does not fit a single brief.
You still confirm what the month is for before hours are spent. A capacity block without a note becomes a feeling that someone was busy. The note can be short. It cannot be blank.
Capacity against the blocks it is often confused with.
Not support
Support is for breaks in work we already know.
- A form, a login, a page, a workflow that stopped.
- A named contact and a smaller month.
- A large change is sent back as its own request.
Not a fixed build
A product surface needs a scope.
- Discovery, a business application, or a SaaS MVP.
- An edge, a release, a handover.
- Capacity does not absorb a silent rewrite.
The month itself
A fresh allocation, times thirty.
- Care, plus, or an engineering month.
- The large figure on the page is the hour times 30.
- Unused hours do not roll.
Need a different shape of work?