Saying no to a project protects the others

The temptation is strong, especially as a freelancer, to say yes to everything. But a saturated schedule is always paid for somewhere: in care, in deadlines, or in sleep.

I select projects on three simple criteria: do I have the skills to do it well, do I have genuine availability, and is the client's approach compatible with how I work.

The first criterion avoids selling expertise you don't have. Better to point toward someone more qualified than to learn at the expense of a client paying full price.

The second is the hardest to honour. It's tempting to squeeze in one more project 'on the side', but the side always ends up spilling onto the work in progress. Availability has to be counted honestly.

Declining isn't rejection. It's often a favour: pointing toward someone better suited, or proposing a more realistic scope. An honest no beats a yes that will disappoint.

And in the long run, a reasoned no inspires more trust than a systematic yes. The client understands you'll never sell them something they don't need.

Every declined project is time given back to the ones I accepted. It's as simple as that.