What people buy when they buy a month
Take a simple task: a landing page with a form and CRM integration. In agency estimates it often lands near one month. The client hears "a month of development" and imagines thirty days of code.
In reality, direct implementation is usually three to seven days. The rest is the cost of coordination: five people touching one task, each one waiting for the next handoff.
"A month" is not a work estimate. It is a safety buffer for approvals, vacations, and lost context.
- thesis
What the timeline really consists of
If you break down a standard landing-page month, it looks like this:
- Brief and manager call. 2-3 days to get into calendars.
- Designer handoff. Another 2 days while the designer finishes previous work.
- Design and approval. 5-7 days across "version → comments → version".
- Developer handoff. Queue again. One or two days.
- Actual development. 3-5 days. The part everyone thought they were buying.
- QA and fixes. 3 days while feedback travels through the manager.
- Deploy and access. 1-2 days until someone free can ship it.
Add it up. Out of thirty days, only 4-7 are hands on keyboard. The rest is a conveyor belt of context transfer.
Why one person estimates differently
When one person with AI tools builds the task, the middle of the chain disappears. Not because I type faster, but because I do not need to transfer the task to the next person. The context stays in one head.
What I do instead of handoffs
Design is discussed in chat and assembled directly in code. Screenshots instead of endless Figma ceremonies. Edits happen in an hour, not a day. CRM integration is not a separate stage; it is the same Thursday.
5 people, 7 handoffs, 1 manager on top
Most of the time is not work, but waiting. Every handoff is a place where context or intent can be lost.
1 person, 0 handoffs, direct Telegram channel
Context does not leave the room because there is nowhere else for it to go. An edit takes an hour, not a day.
Honest caveat: I do not take projects that truly need a team. A banking backend with several security layers is not my zone. I work where a useful version can be shipped in a week and where "one month" is mostly coordination.
How to read an estimate next time
A simple test: ask the contractor to split the estimate into direct work hours and coordination hours. Many agencies will avoid that split because the honest version looks strange. That is not a reason to blame them; it is a way to understand what model you are paying for.
Three questions that can save a month
- How many people will touch this task?
- How many times will it move from one person to another?
- Who can answer me directly without a manager?
If the answer to the third question is "nobody", you are buying the chain. If the answer is "the developer", you may have found a modern agency. And if there is one person and that same person answers, well, then you are in my chat.
if you want to add something - telegram @egor_prog, I always answer.