Monday Me, Friday Me and the Sunday Night Phone Call: A Freelancer's Week in Full

Freelancing gets sold as freedom: pick your clients, pick your hours, work from a nice café in Hebden Bridge if the mood takes you. The reality, at least the week I've just had, looks a bit more like a slow-motion negotiation between the version of you that writes a to-do list on Monday morning and the version of you that answers a WhatsApp at 9pm on Sunday.

Here's how it actually went down. Names changed, invoices very much not.

Monday: The Optimist Writes a List

8:45am, and Monday me is insufferable. Fresh planner, decent coffee, a list of six tasks for the week — a Stripe integration for a Leeds fintech, some accessibility fixes for a charity site, a quote to write for a potential retainer. Very doable. I even schedule time for the admin I always claim I'll do and never do.

By 11am, the fintech client has pinged me on Slack: "Quick one — any chance we could also add the export feature while you're in there?" It's phrased as a favour, it's phrased as small, and it is neither. But it's Monday, I'm feeling generous, and I say yes to a "quick look".

That quick look eats two hours. The Stripe integration itself goes fine. The export feature is a different beast entirely — the data model wasn't designed for it, and I spend the afternoon essentially designing a small reporting layer for free.

Lesson one, logged for the nth time: "while you're in there" is the most expensive phrase in freelance software.

Tuesday: The Quote Nobody Reads Properly

I spend the morning writing a proposal for the retainer — two days a month, maintenance, monitoring, a defined response window. I put real effort into the scope section, because that's the bit that saves you later.

The client replies within an hour: "Great stuff, but can you just confirm it covers any ad hoc requests we have?"

It doesn't. It never does. But this is the moment where freelancers either hold the line or start the slow erosion that turns a defined engagement into an unlimited one. I write back and explain that ad hoc work is billed separately at my standard rate, and point them to the change-request section. They come back fine with it — most clients do, honestly. The fear is always worse than the conversation.

Tuesday afternoon, I finally touch the accessibility work. Two hours in, the charity's volunteer coordinator — lovely person, no idea about dev process — asks if I could "just make the newsletter popup nicer while I've got the site open".

I make the popup nicer. It takes forty minutes. I don't bill for it. This is the freelancing equivalent of leaving a tap running.

Wednesday: Day Rates and the Maths Nobody Does

Midweek is when I usually do the honest accounting, and it's grim reading this week.

My day rate sounds healthy on paper. But work it back: of the roughly 40 hours in a working week, how many are billable? Chasing invoices, writing proposals, CPD, the tax return I've been ignoring since October — none of it earns. Realistically I'm billing 25 of those hours, maybe 28 in a good week. Which means the rate you quote has to be roughly 1.5x the salary-equivalent number you have in your head, plus holiday, plus the gaps between contracts, plus the fact that nobody pays your pension.

And every free forty-minute popup fix quietly wrecks that maths. Scope creep isn't just annoying; it's a pay cut you authorised yourself.

Thursday: The Change Request Email That Works

By Thursday I've had enough of my own bad habits, so I actually use the process I recommend to other people. The fintech's export feature — the one I half-built for free — gets formalised:

• What's in scope, in plain English
• What's explicitly out of scope
• An estimate for the extra work, billed as a separate change request

The client approves it within the day. Nobody is cross. The feature gets built properly instead of bodge-extended onto work it was never designed for. Everyone wins, mostly because I stopped being a pushover for 48 hours.

Friday: Tidying Up and Telling the Truth

Friday is wrap-up day: invoice the fintech including the approved change request, send the accessibility summary, flag the popup fix as a goodwill extra so the client knows it was a gift, not a norm. That last bit matters — if you don't name the freebies, they quietly become the baseline.

I finish at 4pm feeling almost smug. The week mostly worked. Boundaries mostly held. One more client message to answer and then the weekend.

Sunday, 9:14pm: The Test

The fintech's integration has fallen over. Payments failing in production. The message: "Sorry to bother you, I know it's Sunday — any chance you could take a quick look?"

Now. Is this in scope? No. Is there an emergency clause in the contract? There is — a callout fee, minimum half-day, weekend rate. I wrote it. I'd forgotten I wrote it, which is the point: the clause you skim past when everything's friendly is the one standing between you and a two-hour unpaid Sunday night panic.

I reply: happy to help, here's the emergency callout as per the contract, I can be on it within the hour. A beat of silence. Then: "Yes, fine, please just fix it."

It took ninety minutes. A third-party webhook had changed its payload. I invoiced the callout on Monday and it was paid without a murmur. The client even thanked me for being responsive.

The Template: Protecting Your Evenings and Weekends

If you take one thing from my week, take this. Put it in every contract, and reference it in every kick-off call so it's never a surprise:

1. Working hours. "Support and communication are provided Monday–Friday, 9am–6pm UK time." Simple, and it sets the default expectation.
2. **Emergency definition." Define what actually counts: production down, data loss, security incident. Not "the client is worried."
3. Callout terms. Weekend/out-of-hours response at a premium rate, minimum half-day charge, response within X hours — not immediately.
4. Change requests. Anything beyond agreed scope gets a written estimate and approval before work starts. Even for small things. Especially for small things.
5. A goodwill budget. Give yourself a deliberate allowance — say, one free favour a month, capped. It keeps relationships warm without becoming a leaky tap.

None of this makes you difficult. Clients respect clarity; it's the freelancers who bill vaguely and answer at all hours who end up resenting the work. Monday me writes the list. Friday me invoices properly. Sunday me — thanks to a clause written months ago — got paid for the privilege of the panic.