The Developer Day

One full working day of a senior developer working your list in your own repository, on the technology you name: features, fixes, upgrades and tests, with a written report at the end of the day.

Small development work never justifies a project and never stops arriving. The fixes queue up, the upgrade waits another quarter, and the one person who knows the code is busy on something else.

Each day you book is one full working day with a senior developer in the technology you choose. You send the list and they work it in your order, in your own repository, from features and bug fixes to upgrades taken a step at a time and tests around the code your team is afraid to touch.

Book a series of dates and we keep the same developer wherever we can, so they arrive already knowing your code. Each day closes with a written report: the time each item took, the pull request behind it, and what carries over.

What's included

  • One full working day (8 hours) of one senior developer in the technology you choose, on a date you book
  • Feature work, bug fixes, upgrades, refactoring, tests and code review, worked from your list in your order, in your own repository
  • As many days as you need, booked one at a time or as a series, with the same developer kept across a series wherever we can
  • An end-of-day report showing where all eight hours went, item by item, with the pull requests attached and what carries over

How it works

  1. 01

    Book it

    Pay the fixed price and tell us what you need. No scoping call first.

  2. 02

    We deliver

    An experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in The Orchard.

  3. 03

    Hand-off

    You get everything listed on this page, with notes on what was done, and a walkthrough if you want one.

Before you order

Have these ready so we can start the moment you order. The delivery clock only runs while we have them.

  • A Git repository our developer can push to (GitHub, GitLab, Bitbucket or self-hosted), with an invite for their own named account and your branch rules
  • A project that runs: a devcontainer or docker-compose file, setup steps that work on a clean machine, or access to your staging environment
  • One person who can answer questions during the day, and your list in priority order
  • A weekday at least three working days ahead
  • Named invites to the CI, staging, issue tracker and dashboards your list touches. Send invites, never passwords or keys
  • Seed data, fixtures or an anonymised copy of your database to develop against, since we don't work on production data

Who does it

A salaried Cherry VAs specialist with more than ten years in the field, working from a runbook we have been refining since 2007, supervised by senior management and never a marketplace contractor. You will see who is assigned, and can message them about this task directly in The Orchard.

Who it's for

A team with a steady trickle of development work too small to quote and too frequent to ignore, that wants senior capacity on the days it chooses without a new hire.

FAQ

How does booking work?

Each day is a voucher for one date, and you can buy as many as you need. Pick a weekday at least three working days ahead. Two working days before, we check your repository, your build and our access. If something is still missing at the end of the next working day, we release the date and your voucher stays valid for another one. Moving a day is free with two working days' notice, and a later cancellation uses the day. If we can't get into anything in the first hour, we move your first such day free. Want a weekly rhythm? Book a series of dates and we keep the same developer wherever we can.

What do we need to have ready?

A repository we can push to, a project that runs on a clean machine, access granted to your developer by name rather than a shared login, someone who can answer questions during the day, and a list in priority order. We check all of it two working days before your day, so a missing piece is a message on Monday rather than a wasted Wednesday.

What happens to work that does not finish?

It carries over. The report says where it stands and links the branch, and it starts the next agenda unless you reorder. Nothing is guaranteed to finish inside a day, which is the trade this format makes for flexibility.

Will our developer use AI on our code?

Only if you say yes when you book. Without AI, your developer writes and reviews the code by hand. With AI, they use Claude, our AI coding assistant, and read, test and correct its code before it reaches a pull request. The day costs the same either way. We block Claude from your .env and key files, and we delete our copy of your code within 24 hours of each day.

Related services