Fixes
- Defects and regressions on a running app or site, with a reproduce step in the brief.
Ad-hoc development support
Ad-hoc development supportHourly development on a codebase that already exists.
Use a developer by the hour for fixes, small features, reviews, and the work a live product produces. This is capacity on code you already have, not a new product from a blank repo. Each job is quoted, then started when you accept. You keep the client.
We can build with
- WordPress
- Wix
- Squarespace
- Webflow
- Shopify
- React.js
- HTML
What hourly development is for
You stay the agency of record. We never email or call your client. The work lands in their repo, under your name.
- 01
Fixes on a live codebase
Bugs, regressions, and the small change that is blocking a release.
- 02
A feature that does not need a full project
A scoped ticket: an endpoint, a form, a report, a payment hook, written against the stack they already run.
- 03
A review before you ship
A pass on a pull request or a release candidate, with notes your team can act on.
- 04
Quoted hours, not an open retainer
You describe the job. We send hours and a date. Work starts after you accept.
- 05
Their repo, your process
We work in the git remote and the board you name. We do not open a parallel stack unless the quote says so.
Jobs that fit hourly capacity
If the work needs a new architecture, a mobile app, or a blank product, use those pages instead.
Small features
- Tickets that sit on the current stack.
- A new product is Custom Web Applications or Mobile App Development.
Reviews
- A timed pass on code or a release, with written notes back to you.
How a job runs
From the ticket to a pull request you can merge
You are involved before anyone checks out the repo. The quote is for that case.
What the hours cover, and what sits outside
The tickets named in the quote, on the branch and stack you named, with the review pass written there.
A new product, a rewrite, a mobile app, or work on a stack we did not quote is a different order. Extra hours after the quoted set are a new quote.
What we do, and what we need from you
The job waits on access and a way to reproduce. This is the split.
| Task | Your agency |  |
|---|---|---|
| We quote the hours once we can see the codebase and the ticket. | ||
| We work on the named branch, in the stack you described. | ||
| We leave a pull request or a patch your team can review. | ||
| We never contact your client. | ||
| Read access at minimum, write access when we must open the PR. | ||
| The stack, the environment, and steps to see the issue. | ||
| Acceptance of the quote before we commit. | ||
| Someone who can merge and who speaks to the client. |
Existing codebases only
A greenfield web app is Custom Web Applications. A native app is Mobile App Development. Hourly support assumes the repo is already there.
Dedicated people are a different page
If you need the same developer every week, book Dedicated Resources. This page is jobs, not a named seat.
How to sell the hours
Offer it as overflow on accounts you already run. The client never hears a second engineering brand.
Agencies often add these extra services
Frequently asked questions
Agencies that need hourly development on a codebase that already exists, under their own name.
Need hours on a live codebase?
Send the ticket and the access. We quote the hours, and we start when you accept.