The first year of working for yourself: the quiet lessons

Write down the boundary

My most useful project document described what was included, what was not and who would approve the work. It was short enough to read during a call. Clear scope did not eliminate changes, but it made them discussable before extra work became a source of resentment on either side.

Separate revenue from available money

An invoice is not the same as a payment. I kept a simple calendar of expected receipts and recurring expenses, and asked a qualified local adviser about taxes and obligations. The figures were modest. Knowing which money was available made decisions less dependent on the mood of the latest client call.

A weekly review beats constant checking

On Friday I checked unpaid invoices, next week’s commitments and the state of ongoing projects. That appointment reduced the temptation to open the same spreadsheet throughout the day. A review needs a few useful questions, not a collection of charts designed mainly to make the business appear sophisticated.

Keep a small circle

A few trusted peers helped with practical questions: how to phrase a proposal, whether a deadline was realistic and when to ask for specialist advice. Sharing experience was useful without pretending every business had the same constraints. Comparisons become less helpful when nobody discusses costs, failed pitches or unpaid time.

Define a good enough year

I wanted reliable work, timely payment and evenings that mostly belonged to me. Those goals made some decisions easier, including declining projects that would consume every weekend. Growth can be worthwhile, but it should solve a problem you actually have rather than satisfy a borrowed idea of success.