WRITTEN BYJamal Akbar Alam
· 3 min read

What I say no to, and why it makes the work better

READING NOTES04 / 23

People judge a freelancer by what they say yes to. I think you learn more from what they turn down. Here is my list, and the reasoning, because a clear no early is cheaper than a vague yes that goes wrong in month two.

Work outside what I'm good at

If a project needs something I can't do well, I say so and, where I can, point you to someone better. That's not modesty. If I take a job I can only half do, you pay for the learning, and the result is worse than it would have been with the right person.

My range is wide, but it has edges: websites, web apps, Shopify stores, React Native apps, and the design that goes with them. Past that, I'd rather refer than improvise.

Builds that need a team on a deadline

I'm one person. A big store, a platform with many moving parts, or a launch date that assumes five people working in parallel is beyond what one person should promise. I would sooner turn it down than sign a schedule I can only meet by cutting corners you can't see.

An open-ended stream of design

If what you really need is a steady flow of campaigns, brand pieces and illustrations every week, a dedicated designer or a small studio will serve you better. I design as part of building things. That's different from being your standing design department.

Starting without a written scope and a price

I write the scope and the price down before any work begins, and I price by project, not by the hour. That's not about distrust. It's that "we'll figure it out as we go" is how both sides end up disappointed: you're surprised by the invoice, and I'm surprised by the scope.

A short, specific scope also forces a useful conversation early about what the thing is for.

Starting without the first half

Payment is 50% upfront and 50% before launch. The upfront half isn't a test of your good faith. It's what lets me set time aside for your project and say no to other work. A project that starts without it tends to start slowly and end badly.

Locking things in my name

Your domain and hosting should be registered to you, not to me. If I hold the keys, you can't leave without asking permission, and that isn't a position I want to put a client in. I'd rather you can walk away tomorrow and still own everything. It keeps me honest.

What this does for you

None of this is a wall. Each one comes with a different answer: a referral, a smaller first step, a clearer scope. What it protects is the part that's actually valuable, which is that when we do work together, I'm focused, you know what you're getting, and neither of us is guessing.

If that sounds like the way you'd want a project to run, tell me what you need. If you're deciding whether you need one person or two, web designer vs. web developer lays out the trade-offs.

Have something in mind?

Let’s talk