Reserved monthly hours
A fixed block of senior-consultant time, blocked on our calendar for you. Used or not, the capacity is yours every month.
Reserved senior capacity for a PowerBuilder application you cannot afford to be without. Named consultant, documented secondary, guaranteed response time — insurance against key-person and vendor risk, billed monthly.
A retainer is not an open-ended commitment — it is a fixed monthly package with explicit deliverables. Every item below is part of the contract, not a vague promise.
A fixed block of senior-consultant time, blocked on our calendar for you. Used or not, the capacity is yours every month.
First substantive response within one business day, every time. For production incidents, much faster — agreed in the run book before anything breaks.
One senior consultant owns the relationship from the first call. Not a rotating queue, not a shared inbox. You know who picks up the phone.
A documented secondary senior who can pick up the system if the primary is unavailable. Stays current via the run book — no warm-up time when you need them.
Plain-language document describing the application, its dependencies, recent changes, known risks and operational notes. Maintained continuously — handover-ready at all times.
Every 90 days: written summary of what we did, what is stable, what is drifting, what to plan for the next quarter. Executive-readable.
Once a year: half-day workshop with your team to align on the next 12 months — system risks, planned changes, infrastructure shifts, modernization triggers.
Slack, Teams, email, ticket system — your choice. Single agreed channel so requests don't get lost between tools. Response SLAs apply.
Continuity retainers are less about today's problem and more about tomorrow's. They suit organizations that cannot afford the system to be uncovered — but cannot justify a full-time senior PowerBuilder hire.
The application is critical, but workload doesn't justify a full-time senior. Hiring a junior creates a different risk. A retainer fits the actual demand curve.
Months go by without incidents, then suddenly something breaks. A retainer is the difference between an inconvenience and an outage.
A previous consultancy or solo developer left abruptly. The retainer with a documented secondary makes that scenario survivable by design.
One internal expert holds critical knowledge of the system. The retainer is a parallel safety net while you address the underlying dependency.
Retainers fail when nobody uses them or when expectations drift. We invest in onboarding upfront and in quarterly check-ins so the retainer stays aligned with what the business actually needs.
Read the system, write the baseline run book, meet your team, agree communication channel and response SLAs. One-off, fixed-fee, usually two weeks.
2 weeks · fixed feeMonthly capacity is blocked on our calendar. Billing starts. You can use it for incidents, small changes, advisory calls — anything within scope.
monthlySingle channel for requests. Tracked in a shared backlog. Priority and timeline agreed per item. Run book updated as we go.
ongoingEvery 90 days: utilization, what worked, what didn't, what the next quarter looks like. Scope and hours adjustable each cycle.
every 3 monthsThe reserved capacity is the point of the retainer — you are paying for availability, not just consumption. We don't refund unused hours. In a typical engagement, usage is uneven (busy months and quiet ones) and averages out over a quarter.
By default no, because rolling balances erode the meaning of 'reserved'. In practice, if utilization is unusually low for two consecutive quarters, we re-scope the retainer downward rather than carrying a balance. You only ever pay for what you actually need going forward.
Three months minimum so the onboarding investment makes sense for both sides. After three months it rolls month-to-month — 30 days notice to cancel or to change scope. Most retainers run for years; the short notice is a quality control on us, not a planned exit for you.
Often yes, but not always. If you genuinely need only occasional help, ad-hoc consulting is cheaper. If you need a large block of structured project work, fixed-scope is cleaner. We will tell you honestly in the intake call which shape fits — including 'not us'.
The secondary is a named senior consultant kept current on your system via the run book and quarterly handovers. If the primary is unavailable (illness, holiday, longer absence), the secondary picks up with no warm-up time. You are never relying on one person.
Send a short description of the system and the risk you're trying to cover — key-person, vendor, post-vendor, post-incident. We'll reply within one business day with a practical retainer scope sized to your needs.
Retainers commonly start after a fixed-scope rescue, modernization assessment or technical-leadership review — once the immediate work lands, the retainer keeps the system safe afterwards.
Production support, troubleshooting, small fixes, stabilization and continuity for systems that are running but no longer easy to maintain in-house.
Upgrade planning, PowerBuilder 2022 / 2025 readiness, UI improvements, deployment modernization, PowerServer / PowerClient strategy.
SAP, REST APIs, reporting systems, PDF/document workflows, external platforms — bridging PowerBuilder cleanly into the wider enterprise stack.
Oracle PL/SQL, SQL Server T-SQL, stored procedures, packages, triggers, views and performance tuning of data-heavy enterprise applications.
Architecture review, code review, mentoring, project coordination and rescue consulting — senior eyes on the difficult decisions that protect the system.