Ten hours is fewer jobs than it sounds

Ten hours a week at forty minutes per job does not produce fifteen jobs. It produces something closer to nine or ten, because a substantial and irreducible share of every session goes on things that are not the work: reading briefs, answering enquiries that never convert, delivery, and the administration afterwards.

The gap between those two numbers is where most part-time income projections go wrong, and it is entirely predictable once you count it properly.

Where the time actually goes

Time your own week once, honestly, with a clock rather than an impression. The categories are consistent even though the proportions differ by format.

Enquiries. Including the ones that go nowhere. This is the single most underestimated line, because each individual reply is short and there are many of them.

Reading and clarifying a brief. Short for good briefs and long for thin ones, and thin ones are common.

The work itself. The only part anyone counts.

Delivery and the handover message. Small per job, non-zero, and it recurs every time.

Admin. Recording the job, checking the payout, chasing anything outstanding, updating your own numbers.

A reasonable planning assumption for someone past the first month is that the work itself is around two-thirds of the total, and it is worse than that early on because enquiry volume is high relative to bookings while you are converting poorly.

The arithmetic, worked

Take a ten-hour week and a forty-minute written assessment as an illustration rather than a promise.

Three hundred and eighty minutes at forty minutes a job is nine jobs, not fifteen. Multiply by your price, subtract fees, and you have a figure that will be roughly a third below whatever you got by multiplying hours by an assumed rate.

This is illustrative arithmetic with its assumptions on the page, not a forecast. Your enquiry-to-booking ratio is the variable that moves it most, and it improves considerably with tenure - which is also why an effective hourly rate keeps changing even when the price on your listing does not.

Reducing the overhead rather than the hours

The unbilled third is compressible, and compressing it is worth more than a price rise for most part-time earners, because it converts directly into billable minutes at your existing rate.

Templates for the recurring messages: the holding reply, the clarifying question, the handover. Written once, reused forever, and they cut the enquiry line by a large fraction. A scope sentence in the listing, which prevents the clarification exchange from happening at all in many cases. Batching admin into one block a week rather than doing it per job, because the switching cost is most of it. The cost is measurable: Rubinstein, Meyer and Evans (2001) found that alternating between tasks carries switching-time costs, and that they grow as the tasks get more complex. Keeping the admin under ten minutes a day is the detailed version, and for a ten-hour week it is the highest-return hour you will spend.

What does not work is trying to speed up the work itself. The specificity in the deliverable is the product, and the minutes spent on it are the ones a buyer is actually paying for.

Designing a week that survives a busy month elsewhere

The reason part-time arrangements fail is not the arithmetic; it is that the arithmetic assumes a constant, and your other commitments are not constant.

Three structural choices make a week durable.

Fix the sessions rather than the total. Two named blocks a week that happen regardless is more robust than ten hours to be found somewhere, because a floating commitment is the first thing a busy fortnight deletes.

Keep a stated turnaround you can hit on your worst week, not your best. Turnaround is the promise that a bad month at work will break first, and breaking it costs a review. A 48-hour promise you always meet is worth more than a 12-hour one you meet most of the time.

Have an explicit way to be unavailable. Pausing a listing for a week is cheap; going quiet on live enquiries is expensive. The mechanism differs by platform and is worth knowing before the week you need it.

The volume question sits underneath all of this: whether to take more jobs at a lower price or fewer at a higher one is a real decision at part-time scale, and it resolves differently than it does full-time because your ceiling is hours rather than demand. When volume beats price works through the conditions, and the short version for a ten-hour week is that volume rarely wins, because you run out of week before you run out of buyers.

What the numbers are for

Not motivation. The point of doing this arithmetic is to have a realistic figure before you commit, so that a month that lands where the maths said it would reads as success rather than disappointment.

Two adjacent things belong to other properties. Where buyers are coming from and how they choose is covered from their side, and it matters here because your enquiry-to-booking ratio is mostly their behaviour rather than yours. If part of your offer is objective measurement, the time cost of doing it consistently is not trivial and the conventions worth following are documented externally rather than invented per job. Buyers arriving after trying the free automated options tend to have sharper briefs, which quietly reduces your clarification line - one of the few overheads that has fallen rather than risen.

For the platform-side detail of how availability, pausing and turnaround are actually surfaced to buyers, Rate Cock's judges page is the current source, and it is worth checking before you design a week around assumptions about it.