The First Seven Days When You're Starting Broke

A week is enough to learn whether a zero-cost start has anything in it, on one condition: every day has to end with something you can point at.

Days that end with reading, comparing or deciding do not count, and they are the ones that quietly consume the week. Seven deliverables, one per day, is the whole structure.

Day one and two: choose one thing and write down what you are offering

Day one produces a decision, and nothing else. Take your shortlist and cut it with two questions: which of these can start without buying anything, and which can I describe in one sentence a neighbor would repeat? Whatever survives both, pick it. If two survive, pick the one where you can already name a person to approach.

Day two produces the offer in writing. Not a business plan — five lines. What you do. What is included and what is not. Roughly what it costs, as a range rather than a fixed figure. When you are available. The one sentence you will actually say out loud.

Build nothing on these two days. No name, no page, no logo, no shopping. If you have one whole free day rather than two evenings, the hours run differently and an hour-by-hour plan for a single free day sequences it properly.

Day three and four: tell actual people, in person and by message

Day three is face to face, and it is deliberately the people you would see anyway: the shop, the neighbors, the school gate, the people on your shift. It costs nothing and it is the fastest route to a yes.

Day four is messages, sent one at a time, each one written to the person receiving it. Group broadcasts feel efficient and get ignored by everyone equally.

Both days end with a number written down: how many people were told, and who. That number is the only honest measure of whether the week has started. Twelve people told and no work is a real week; two people told and no work is a week that has not begun. The wording of the ask is where the discomfort lives — how to make the first awkward ask is about exactly that sentence.

Day five: do the first job even if the terms are awkward

Awkward will mean one of a few things. The price came out lower than you wanted. The scope grew while you were standing there. The customer is your aunt. You had to borrow a tool to do it.

Do it anyway. The first job's purpose is to turn an idea into something you have done, and it pays you in things you cannot get any other way: how long the work actually takes, which part you underestimated, what the customer worried about.

Two hard limits. Do not do it free for somebody who could pay, because that price becomes the price among everyone they know. And do not take work needing equipment you cannot source or a certificate you do not hold. Write down the real duration when you finish, because that is the number you were guessing at when you priced it.

Day six: get paid, and write down what happened

Ask for the money at the end of the job, in the same breath as handing it back. "That's all done — so that's the price we said, cash or transfer?" Asking in the moment is straightforward; asking three days later by text is a different conversation.

Then record it the same day, in one line. Seven columns, and every job after this goes on the same page:

That last column is the one that changes next week, because it tells you which of days three and four actually worked. What to do with the money once it exists is its own decision — what to do with the first money a zero-cost start produces.

Day seven: repeat, adjust or drop

Three outcomes, and the rules for choosing between them are simpler than they feel.

Repeat if the work was doable, the money was worth the hours, and anybody asked what else you do. That question is the strongest signal available in week one.

Adjust if the work was fine but something specific hurt — the price, the travel, the type of customer, the scope you agreed to. Change one variable for next week and only one. Change three and you will never know which mattered.

Drop it if you dreaded the day and the money did not make up for it, or if nobody in your area wants the thing at a price that works. Dropping after one honest week is a decision, not a failure, provided you finished the job you had committed to.

What a week with nothing in it proves, and what it does not

A week that produced no work tells you a few real things. Which channel got no response. Whether people understood the sentence, or asked you to repeat it. Whether you genuinely asked, or only announced that you were available and waited.

What it does not tell you is whether the idea works. A handful of conversations in one week is a small sample, and a single wet weekend can account for it. Treat week one as a test of your process rather than a verdict on the work. How long a zero-cost start takes to show a signal is dealt with in how long a zero-cost start takes.

The one exception: if nobody understood what you were offering, the sentence is wrong. Fix the sentence before you repeat the week.

Who cannot give seven days to this, and what changes

Shift workers, carers, people holding two jobs, people in a housing or health crisis — a clean seven-day run is not on offer, and pretending it is just makes the plan something to feel bad about.

Stretch the week to a two weeks and keep the same seven deliverables. One change matters more than the rest: days three and four have to stay next to each other. Telling people on the third and following up on the twentieth means starting twice, because the conversation has gone cold and you open it again from scratch. Protect the adjacency of the telling days and let everything else move.

If the constraint is a full-time job rather than an unpredictable one, the scheduling problem has its own answers — see starting a side hustle around a full-time job.

Write the seven deliverables in a note tonight, one line each, and cross them off as they happen. If day four ends with nobody told, the week has not started yet, whatever else got done.