Transparent hour banks
Buy a block and spend it on whatever you ask for, with a breakdown of where every hour went. No minimum per incident and no creative rounding.
A dashboard that won't refresh, a flow that broke, an integration that changed on the other side. Hour banks without aggressive expiry and with consumption in plain sight.
Buy a block and spend it on whatever you ask for, with a breakdown of where every hour went. No minimum per incident and no creative rounding.
When something breaks: priority by real impact, a committed response time and an explanation of the cause. Not just «it works now».
Refreshes that fail, flows that stop running, services that degrade. Ideally we find out first and tell you.
A new indicator, one more field, another data source. Most hours go on growing what works, not on putting out fires.
Every change is documented, so the hour bank doesn't become the only memory of how your system works.
Everything below is in real projects. If something isn't on the list, we tell you before we start and not after.
After twelve months, not three. And we tell you when they're running low instead of letting them quietly disappear.
It depends on the agreed criticality. For a system down during working hours, same day. For an improvement, planned into the next window. What we don't do is promise a number we won't meet.
Yes, after a review. We need to understand what's there before answering for it, and that initial review consumes hours from the bank. We tell you beforehand.
No. You buy the bank when you need it and renew if it makes sense. If you don't need us one month, you pay nothing.
Someone who knows your system, not a first line that opens a ticket and escalates. It's the advantage of a small consultancy and it's deliberate.
Twenty minutes is enough to know whether there's a project. If there isn't, we'll say so.