One bottleneck stops you winning work. The other stops you keeping the margin on work you already won. Two numbers will tell you which is costing more.
When a contractor asks whether to add an estimator or a project coordinator first, the real question is usually simpler than it sounds: which of my two bottlenecks is costing me more right now.
One of them stops you winning work. The other stops you keeping the margin on the work you already won. Both feel urgent from inside the business, and they feel urgent in the same way - a senior person is drowning and something is slipping. But they are different failures with different price tags, and the cheaper fix is rarely the one that gets chosen first.
This is a decision you can usually make with two numbers and an afternoon.
An estimator changes how much work you can price, which changes how much work you can win.
The mechanism is straightforward. Most contractors have a fixed weekly ceiling on bids, set by whoever prices the work. When invitations exceed that ceiling, the excess is declined - usually quietly, usually by the person already at capacity, usually without anyone recording that a decision was made. Adding estimating capacity lifts the ceiling.
What that looks like in practice: quantity takeoffs, plan reading, bid solicitation and subcontractor follow-up, comparison of received quotes, proposal assembly, and the administrative work of keeping a bid calendar honest.
What it does not change: your win rate on the bids you were already submitting, your pricing judgment, or your relationships. Capacity is not skill. If you are pricing forty jobs and winning two, an estimator gives you eighty losses instead of forty. The constraint there is something else.
A project coordinator changes how much of your project managers' time goes to managing projects rather than administering them.
Most project managers spend somewhere between a third and half their week on work that does not require their judgment: chasing submittals, logging RFIs, updating schedules, assembling documentation, following up with subcontractors on paperwork, and preparing the reports that tell everyone else what is happening. None of that needs a project manager. All of it needs somebody.
What that looks like in practice: submittal registers and transmittals, RFI logs, document control, schedule updates, subcontractor communication, meeting minutes, closeout package assembly, and progress reporting.
What it does not change: decisions about sequence, cost, risk or client relationships. A coordinator moves information; a project manager makes calls. Confusing the two produces a coordinator who is blocked constantly and a project manager who is still doing the work.
The diagnosis is usually visible in how the pain gets described.
"We are turning down bid invitations." Estimator. And the cost is measurable: count the invitations declined last quarter, apply your average win rate and average contract value, and you have the number.
"Our project managers are working nights and things are still slipping." Coordinator. The cost is harder to see but usually larger, because it shows up as change orders unclaimed, submittals late, closeout dragging, and retention held longer than it should be.
"We won a big job and it exposed everything." Coordinator, urgently. Growth in project size raises documentation load faster than it raises field complexity.
"Bids go out late and half-finished." Estimator, but check first whether the estimator is late because they are also coordinating live jobs. That is common in companies under about thirty people, and the fix is the coordinator.
The default instinct is to hire the estimator first, because winning work feels like the growth move and administration feels like overhead.
That instinct is right roughly half the time. The other half, it makes things worse in a specific way: you win more work, that work lands on project managers who were already at capacity, and the margin you gained on volume is given back in poor execution, missed change orders and slow closeout. The company gets busier and no more profitable.
The question worth asking before hiring an estimator is: if we won thirty percent more work next quarter, could we deliver it with the office we have? If the honest answer is no, the coordinator is the first hire, and the estimator is the second.
Your bid pipeline is constrained and your delivery side has headroom. You are declining invitations. Your win rate on submitted bids is healthy, so more submissions convert predictably. Preconstruction is one person deep and that person is a single point of failure.
Your project managers are the constraint. Documentation is late. Change orders are being identified after the window to claim them. Closeout takes months. You are about to start a project materially larger than your usual size. Or your estimator is being pulled into live job administration, in which case the coordinator fixes both problems at once.
Past roughly twenty to thirty office and field staff, most contractors need both, and the two roles reinforce each other: the estimator fills the pipeline, the coordinator makes the delivery of that pipeline survivable. Adding one without the other simply moves the bottleneck rather than removing it.
This is the part that determines whether either hire works.
A support role only creates capacity if work actually moves to it. The common failure is that a coordinator is added and project managers keep doing the same tasks, because delegating requires deciding what to delegate and then living with it being done differently. Six weeks later the coordinator is underused and the conclusion is that the role does not work.
Before either hire, write down the specific recurring tasks that will move, and who currently does them - the list in before you hire another project manager is a good place to start. If you cannot fill a page, the problem may not be capacity.
Two numbers. First: bid invitations declined in the last ninety days, multiplied by your win rate and average contract value. Second: hours your project managers spent last week on documentation, chasing and reporting, multiplied by their loaded cost, then annualised.
Whichever is larger is your first hire. If they are close, hire the coordinator, because it protects the value of everything you win afterwards.
Many small contractors run it that way, and it works until bid volume and live job volume peak at the same time - which they tend to do. The person then chooses, usually in favour of whatever is loudest, and the other side slips. If you are seeing bids go out late during busy delivery periods, that is the structure failing rather than the person.
Either works remotely, because both are systems and documentation roles. If you can only place one remotely, most contractors get more out of placing the one that carries the higher volume of routine production work - usually the coordinator early on, and the estimator once bid volume is the binding constraint.
Yes. The role involves submittals, RFIs, schedules and closeout documentation, and someone without construction context will not recognise when a submittal register is wrong or when an RFI response does not actually answer the question. General administrative experience is not a substitute.
An assistant project manager carries delegated decision-making - cost tracking, procurement follow-through, and judgment within limits set by the project manager. A coordinator carries information flow and documentation. The coordinator is the earlier hire for most companies; the assistant project manager makes sense once there is enough delegated authority to justify it.
That is common, and it is the usual reason contractors look at remote support rather than a local hire. The comparison between remote and in-house estimating is a separate decision with its own arithmetic, as is the choice between a per-bid estimating service and a dedicated estimator. Both are worth running properly before assuming a full-time local position is the only option.
Within a maximum of approximately two weeks we can normally present two to three pre-screened candidates who meet the requirements of the position and are ready to be interviewed. The final hiring time depends mainly on how quickly your own evaluation and decision process moves.
One consultation is enough to define the role, agree the requirements and start the search. Most companies have a shortlist to interview inside two weeks.
