When hiring does not fit the work
Plenty of teams have three months of backlog and nothing after that. A full-time hire is expensive to find, expensive to keep and awkward to unwind. Booking hours means you pay for the work that exists, scale the block up when a deadline gets close and scale it back down when it passes.
Inside your process, not beside it
We work in your repository, your branch strategy and your ticket tracker. Pull requests go through your review. Standups happen at your time, which is the part that usually falls apart with developers twelve hours away. Bolivia sits at UTC-4, so a 9am meeting in New York is 9am here too.
How the hours are tracked
We agree a block of hours per month. Every week you get what was done and what it cost, tied to tickets you can open. Unused hours roll into the next month rather than evaporating, and the block can be changed with a week of notice.
What it includes
- Work inside your repo, tickets and review process
- Weekly report of hours against delivered tickets
- Web, mobile, database and infrastructure work
- Code review for your existing team
- No recruitment fee, no benefits, no notice period
- Monthly block that goes up or down as you need
Questions
What is the hourly rate?
It depends on the stack and how many hours are reserved each month, so we quote it in writing before starting rather than posting a number that would be wrong for half the cases. It sits well below US and Western European rates, which is the reason you are reading this page.
Is there a minimum?
Around twenty hours a month is the sensible floor. Below that too much of the time goes into reloading context instead of shipping, and your effective cost per useful hour goes up.
Tell us what you need
Send a couple of lines about the problem and we will come back with scope, price and a date. No cost for asking.