Latest dealsDeals See all deals→
Step 2 of 3 · 11 min

Set rules before you start

Week 2: put boundaries around the work

This week is about making the side income small enough to fit real life. By the end of this step, there will be a clear weekly time limit, a set of working hours, a short list of jobs to refuse, and a simple workflow for enquiries, payment, delivery, and revisions. The aim is not to look impressive. The aim is to make the first paid work possible without letting it spread into every evening.

Last week established one small service, a starter price, and a simple promise. Keep those fixed for now. This week adds the rules that protect time and make the offer easier to deliver consistently.

Actions

  1. Choose the exact hours available each week.

    Decide when side work can happen and write it down in plain terms. Be specific. “Some evenings” is too loose. “Tuesday 7:00 to 8:30 pm, Thursday 7:00 to 8:30 pm, Saturday 10:00 am to 12:00 pm” is usable.

    Start with less time than seems possible. For a first side income, a small reliable block is better than an ambitious plan that fails after one busy week. A good test is this: if work at the main job becomes stressful for a few days, could these side-work hours still happen without resentment? If not, reduce them.

    Count the total weekly hours. That number becomes the capacity limit for now. It is the amount of time available not only for delivery, but also for messages, admin, and revisions.

    If something goes wrong and the week is already overloaded, do not solve it by promising late-night work. Cut the available hours in half for the next two weeks and use that smaller number. A side income that survives a busy month is more useful than one that only works in an ideal week.

  2. Set a maximum number of jobs at one time.

    Look at the service chosen in the first step and estimate how long one job takes from first message to final handover. Include the hidden parts such as clarifying the brief, chasing files, sending payment details, and making one round of revisions.

    Then set a simple rule for how many jobs can be open at once. For most first offers, one or two active jobs is enough. The point is to prevent overlap from turning a small service into a second full-time role.

    Write the rule in a sentence: I can handle one active job at a time or I can accept two small jobs per week, no more. This rule matters later when enquiries begin. Without it, every new message feels like a decision made from scratch.

    If something goes wrong and the estimate was too optimistic, lower the limit immediately. It is easier to say, “I can start next week,” than to recover from missed deadlines.

  3. Decide what you will not take.

    This is the part that keeps the offer clean. Make a short refusal list based on what was chosen last week. Include any work that is too large, too vague, too urgent, or too emotionally draining to fit around the main job.

    Useful categories are:

    • rush jobs that need same-day or next-morning turnaround

    • open-ended work with no clear finish point

    • custom extras outside the original promise

    • calls at times that clash with work or family commitments

    • projects that need specialist software, approvals, or setup not already in place

    • clients who want to negotiate every detail before agreeing to the starter price

    Keep the list short enough to remember. Three to six rules is enough. The purpose is not to reject people harshly. The purpose is to stop taking the kind of work that breaks the system before it starts.

    If something goes wrong and a request is tempting because the money is higher, compare it against the refusal list. If it breaks two or more rules, decline it or reshape it into the standard offer. Early on, consistency is worth more than one oversized job.

  4. Create a simple enquiry process.

    When someone expresses interest, there should be one basic path from first message to confirmed job. Keep it light. A side income at this stage does not need forms, software, or a polished client portal.

    Write a short sequence like this:

    • receive the enquiry

    • check whether it matches the fixed offer and refusal rules

    • ask for the minimum information needed

    • confirm price, timeline, and what is included

    • take payment or deposit

    • do the work

    • send the finished work and handover note

    • handle the agreed revision if needed

    For the “minimum information needed,” write a short list now. For example, if the service is formatting a slide deck, the minimum might be the draft file, deadline, preferred style, and number of slides. If the service is proofreading a CV, it might be the current CV, target role, and whether they want wording edits or formatting only.

    If something goes wrong and enquiries arrive in a messy format, do not start the work from fragments across five messages. Reply with the short list and ask them to send everything in one place.

  5. Decide how payment will work before any work starts.

    Pick one payment method that is easy to use and familiar. Then choose one simple rule. For a small first offer, the cleanest options are either full payment upfront or a clear deposit before work begins and the balance before final files are sent.

    What matters is that the rule is decided now, not improvised later because someone seems trustworthy. Small jobs become awkward when payment is left until the end without any agreement.

    Write a plain sentence you can reuse: The price is £X. Payment is taken upfront before I begin or The price is £X, with 50% to book the job and the remainder before final delivery.

    If something goes wrong and a person resists the payment rule, do not argue for long. Repeat the process once. If they still push back, let the job go. The first few jobs should teach calm administration, not debt collection.

  6. Set a delivery standard.

    Decide how the finished work will be sent and what “done” means. This avoids the common problem where a small task drifts because the client expects one more tweak, then another, then a call.

    Write down:

    • the normal turnaround time

    • the file format or handover format

    • what is included in the first delivery

    • how many revisions are included

    • how long the client has to request that revision

    For example: Delivery within three evenings of receiving files and payment. One completed document returned as a PDF and editable file. One round of minor revisions included if requested within three days.

    Use the language that fits the actual offer from last week. Keep the promise modest and easy to keep.

    If something goes wrong and the work takes longer than expected, do not disappear. Send a short update with a revised delivery time before the deadline passes. Reliability matters more than speed at this stage.

  7. Write three short boundary messages.

    Prepare the messages that are hardest to write under pressure. These can be copied and adjusted later. Draft one for each of these situations:

    • declining a request that does not fit the offer

    • offering the next available start date because capacity is full

    • reminding someone of the payment or revision rule

    Keep them calm and brief. For example: Thanks for sending this. I only take on short CV edits at the moment, so I am not the right fit for a full cover letter rewrite. Or: I can do this, but my next available slot is Saturday, with delivery by Monday evening.

    These messages reduce hesitation. They also make the side income feel like a small professional system rather than a favour done in spare moments.

    If something goes wrong and writing boundaries feels uncomfortable, remember that vague yeses create more friction than clear noes. The message can be warm without becoming flexible.

  8. Put the full workflow on one page.

    Gather everything into one simple note. It can be in a document, notebook, or notes app. The format does not matter. What matters is that the rules exist in one place and can be checked quickly before accepting work.

    The page should include:

    • the offer name and starter price from last week

    • weekly working hours

    • maximum number of active jobs

    • refusal rules

    • minimum information needed for an enquiry

    • payment rule

    • delivery timeline and format

    • revision limit

    • the three boundary messages

    This page becomes the operating manual for the next few weeks. It should be plain enough that it can be followed when tired after work.

    If something goes wrong and the page starts getting complicated, remove anything that is not essential for the first paid job. The system only needs to support a small, repeatable service.

What to watch for this week

The main risk in this step is designing a system for a bigger business than the one that exists. Keep it small. One offer, one price, one payment method, one basic workflow. The second risk is leaving decisions vague because they feel easier to postpone. Vague decisions usually return later as evening stress.

A useful standard: if a new enquiry arrived tonight, there should already be a clear answer to when the work could happen, what it would cost, how payment works, what is included, and when to say no.

Checklist

  • A fixed weekly schedule for side work is written down.

  • A total weekly hour limit has been chosen.

  • A maximum number of active jobs is set.

  • Three to six refusal rules are written.

  • The minimum information needed from an enquiry is listed.

  • One payment method and one payment rule are chosen.

  • A normal delivery timeline, handover format, and revision limit are defined.

  • Three short boundary messages are drafted.

  • All of the above sits on one page that can be reused next week.


Once this is done, the side income stops being an abstract intention and becomes a controlled commitment. That matters because the next step is not about changing the offer. It is about describing the existing offer clearly enough that real people can understand it and respond.

More playbooks

All playbooks →