Unpaid, Not Unplanned: Giving the Side Project a Real R&D Budget

There's a particular sort of guilt that comes with closing the laptop on a paid job and opening it again twenty minutes later for something nobody asked for. You know the feeling. The invoice is sent, the client is happy, and yet there you are on a Tuesday night in a cold spare room, mucking about with a podcast edit or a pointless little animation that will probably be seen by eleven people and your mum.

Most UK creatives I know carry that guilt quietly, as though the personal stuff is a hobby they haven't quite grown out of. It isn't. It's the only part of the practice where you get to choose the brief, and choosing the brief is how you find out what you actually think.

The argument here is simple: stop treating side work as a distraction and start treating it as research and development. That doesn't mean monetising it, branding it, or launching anything. It means giving it a small, defensible budget of time and money, and paying attention to what it teaches you.

What actually counts as R&D

Not every unpaid project is research. A lot of it is displacement activity dressed up as ambition — the endless tinkering with a website that will never go live, the 'learning' that is really just watching tutorials at 11pm.

The useful test is whether the work answers a question you couldn't answer on a client job. Are you trying a technique you'd never risk on someone else's money? Testing whether a certain kind of story holds an audience? Working in a medium where you have no reputation to protect?

If the answer is yes, it's R&D. If the answer is 'it keeps me busy and stops me thinking about the pipeline', that's fine too, but call it what it is and don't expect it to feed anything back.

Ring-fence it like a client booking

The single most effective change is also the dullest: put it in the diary. Not 'I'll do some personal work this week' — an actual slot, with a start and an end, treated with the same mild irritation you'd feel about letting a client down.

A few things that make this stick:

• Give it a name. 'Side project' is a shrug. 'The R&D slot' is a commitment, and it survives contact with a busy month.
• Keep it short. Three hours a week is plenty. Two is enough. What kills these projects isn't lack of time, it's the assumption that they need a full day to be worth starting.
• Never let it eat the paid work. This isn't about hustle. If the R&D slot starts cannibalising invoices, you've simply invented an unpaid client with worse boundaries than the paid ones.
• Protect the boring slot, not the exciting one. The Tuesday evening you don't feel like it is the one that matters.

I know a Bristol-based editor who runs hers on Friday afternoons, deliberately when her paid inbox has gone quiet, and has done for years. She's produced almost nothing anyone would call a finished piece. She's also the fastest problem-solver I've worked with, because she's spent a decade trying things she had no business trying.

Set a failure budget you can defend

Here's where it gets practical. Decide, in advance, what this is allowed to cost you. Not vaguely — a number.

Mine is roughly the price of a decent pair of trainers each quarter: a bit of software, a domain, the odd piece of second-hand kit, a train fare to go and look at something. Written down, that's a small line in the accounts. Unwritten, it becomes a slow leak you feel guilty about and can't account for.

The same goes for time. A failure budget means you're allowed to spend the whole slot for six weeks and have nothing to show for it. That's not failure, that's the deal. R&D that always produces an output isn't R&D, it's production with worse pay.

What the budget buys you is permission. Permission to abandon something at week four without it counting as a personal failing. Permission to spend an evening on a test that proves an idea is bad — which is a result, by the way, and a cheap one.

Keep field notes, not a diary

Documentation is where most people stop, because it sounds like homework. So keep it small and unglamorous.

A single note, appended to weekly, with three lines: what I tried, what surprised me, what I'd do differently. No screenshots, no mood boards, no system. If you want a template, use the back of an envelope.

That note does two jobs. First, it stops you repeating the same experiment six months later because you've forgotten the result. Second — and this is the bit people miss — it becomes evidence. Not for a grant application or the 'About' page, necessarily, but for the moment a client asks how you'd handle something difficult, and you can say, with specifics, that you've already done it on your own time.

The handover point

So when does side work feed back into paid work? Usually later than you'd like and more obliquely than you'd expect.

It's rarely a straight line where the personal project becomes the commission. More often it's a technique you now trust, a collaborator you met in the process, a piece of work that did the talking for you when a booker was deciding. The return shows up months after the spending, which is precisely why it needs to be ring-fenced rather than squeezed in around invoices.

What you shouldn't do is rush the handover. The moment a personal project gets a price list attached, it starts obeying different rules. You begin second-guessing the audience, hedging the interesting bits, tidying it up for people who might pay. That's not research any more. Give it room to be uncommercial for longer than feels comfortable.

Know the difference between slow and stuck

The honest caveat: not every side project deserves to survive. Some are just avoidance with a nice title, and the field notes will tell you so if you're reading them properly.

A useful distinction is between slow and stuck. Slow means the questions are still interesting, even if the progress is glacial. Stuck means you're opening the file out of obligation and nothing has surprised you in two months. Slow gets more time. Stuck gets a decent burial and a note in the log about what it taught you.

That's the whole method, really. A slot in the diary, a modest number, a few lines of notes, and the nerve to let the work stay unpaid for a while. It isn't glamorous, and nobody's going to congratulate you for it. But it's the difference between a practice that responds to whatever the market asks for this year, and one that has something of its own to offer when the market changes its mind.