Hourly & retainer
For work that cannot be scoped up front — exploratory automation, integration spelunking, continuing change to systems already running — engineering capacity is contracted by the hour or reserved by the month.
Consulting engagement
Invoiced against an itemised timesheet
Quoted per engagement once the work is understood. Complex or regulated work — financial data, market systems, personal data — carries the additional controls it requires, and those are priced into the quotation rather than added later.
Managed retainer
Agreed in advance, renewed monthly
You work with the engineer who writes the code. There is no account manager between you and the work, no handoff to a junior, and no ramp-up time billed to you while somebody learns the domain.
Working from IST (UTC+5:30), with held overlap of 6:30pm – 11:30pm IST (9am – 2pm ET) for North America and 2:30pm – 7:30pm IST (10am – 3pm GMT) for the UK. Real hours, reserved — not "flexible availability" that turns out to mean email only.
Every invoice is accompanied by a timesheet breaking down what the hours bought. You can see where time went before you pay for it, and raise anything that looks wrong. Cancellation terms are on the terms page.
Work lands in your repository and runs on your infrastructure. Credentials stay scoped and are returned at the end of the engagement. Full IP assignment on payment; NDA on request.
This is a deliberately senior, focused practice, which is what makes the arrangement worth buying — and it also means availability is genuinely limited. Where we are booked, you will be told when capacity opens rather than being added to a queue and billed for a slow start.
If a fixed-scope project or a one-off assessment would serve you better than an open-ended hourly arrangement, that is what we will recommend. See engagement models for the alternatives.
Including, where it applies, that hourly is the wrong instrument for it — a fixed-scope project or a single assessment is often the better answer.