Riajul Islam
← All writing
Career · 10 posts

Career & freelancing

Scoping, pricing conversations and lessons from shipping client work on a deadline.

Career13 min read

The Projects Worth Turning Down

Every bad project was visible in the first conversation. The signals, what they cost when ignored, and how to say no without burning anything.

Career13 min read

Everything I Have Learned About Estimating

You are not bad at estimating the work. You are bad at remembering everything that is not the work — and that is the recoverable part.

Career13 min read

Working Across Time Zones Without Losing Your Evenings

A large time difference is an advantage if the work is structured for it and a slow disaster if it is not. What actually has to change.

Career13 min read

Documentation That Survives You Leaving

Most project documentation describes what the code does, which the code already says. What is missing is why, and who has the passwords.

Career13 min read

The Objections You Get, and What They Actually Mean

"It is too expensive" is rarely about the price. The eight objections that recur, what is underneath each one, and how to answer honestly.

Career13 min read

Choose Your Stack Once, Then Stop

Every project that starts with a technology debate loses a week. Four templates decided in advance, and the narrow cases where you deviate.

Career13 min read

Positioning as AI-Accelerated, Not an AI Consultancy

One says you deliver faster. The other says you sell AI. They attract different clients, and only one of them survives the tooling changing again.

Career13 min read

Pricing Work When AI Makes You Faster

If you bill by the hour and the hours halve, you have given yourself a pay cut for getting better. What to charge for instead.

Career13 min read

A Development Process Without the Ceremony

Six steps from first message to production. What each one is actually for, and why most process overhead solves problems small teams do not have.

Career13 min read

How I Scope a Project Before Quoting It

Most projects that go wrong were mis-scoped, not mis-built. The questions that surface the real work, and what to do with the answers.

Got a project worth
writing about?