How I Estimate a React Project Without Lying

Published 2025-10-14 by Faraz Rahimi

I estimate jobs, not screenshots. Auth, one core workflow, integrations, and the ugly last 20% each get a number.

How I Estimate a React Project Without Lying

Tags: Freelance, Estimating, React, Process, unlisted

I split: setup, the main job, a second job if real, integrations, QA on real devices, buffer for the unknown. I show the buffer. Hidden buffers feel like padding. Visible buffers feel like adulthood.

If they cut the buffer, they buy the risk. I write that down.

Integrations are not a line named "API"

Each system is a mini-project: auth, mapping, failure, retries. A WMS is not "one endpoint."

I estimate my calendar, not a fantasy twin

If I have other work, the elapsed time is longer than the hours. Clients live in elapsed time. I say both.

Original post: https://farazrahimi.com/posts/how-i-estimate-a-react-project-without-lying