This is still a work in progress, and there is more to shape together. But it is a solid foundation to build from, and the parts that touch the team should carry your input before they go anywhere else.
Everything this role owns comes down to one outcome: the right solution at the right price, faster, winning more because of it.
The obvious way to chase that is process. Rework the queue, tighten the tooling, sharpen the handoffs. That work is coming, and it matters. But it is the second thing, not the first.
A department that feels undervalued, under-resourced, and permanently behind will not adopt new process, will not lean into new tooling, and will not take on greater ownership. It will protect itself, which is a rational response and a completely understandable one. No amount of workflow redesign fixes that.
So this starts with the team. Career structure, culture, integration, and capacity. The process work lands on top of a department that has reason to want it.
Estimating has been treated as the end of the pipeline rather than as one half of what Steelhead sells. The consequences show up in four predictable ways.
None of this is a failure of the people in the room. It is the predictable result of a department treated as a service function while performing a strategic one.
Publishing a defined role structure with four tiers, built to the same standard as the Exhibit Designer roles breakdown. Each tier has documented responsibilities, accountabilities, and compensation bands.
Nobody should have to guess whether growth is possible here. When there is no visible ladder, the reasonable conclusion is that there isn't one, and people stop reaching. This changes the question from "is there anything above me" to "what do I need to demonstrate."
The standard we hold ourselves to. No carrot dangling. Advancement conversations come with written benchmarks and a real assessment cadence. If someone is not ready, they are told exactly what is missing. If they are ready, it happens.
This team works hard, delivers under pressure, and goes home. The work is largely invisible to the rest of the company until something is late. Recognition is not a perk here, it is the correction to a structural visibility problem.
The real obstacle is not willingness, it is rhythm. Departments constantly at capacity postpone whatever isn't a deadline, and team culture is always the first thing to slip. Not because it isn't valued, but because something more urgent is always in front of it. The fix is not more effort from any one person. It is a cadence, so it stops depending on someone finding a window.
Today Design produces a concept and Estimating produces a price, and the two meet late, often in conflict, usually under time pressure. That sequence creates rework and a dynamic where each side experiences the other as the problem. It is also the single biggest source of avoidable delay in the pipeline.
The commitment runs both directions. Estimating takes on strategic contribution and co-ownership of the win. In exchange, Design and Business Development own delivering clean, stable inputs and reducing late-stage churn. One without the other is not a partnership.
Finding the places where this team loses hours to manual, repetitive work, and removing them. Not introducing technology for its own sake, and not asking anyone to change what estimating fundamentally is. The starting point is the friction the team already knows about: the lookups, the re-entry, the reporting, the chasing.
The honest concern, named. The real worry is not that a machine will do the estimating. It is that every efficiency gain will simply be absorbed as more work, and the department will end up doing more with the same or fewer people. That concern is reasonable, and recent history gives it weight.
So here is the commitment. Capacity recovered goes to three places, in this order: reducing overtime and after-hours work, absorbing the volume growth coming as the company scales, and creating room for the strategic contribution the new structure asks for. It does not go to eliminating positions, and it is not a substitute for hiring.
Nobody needs to become an expert. I am not asking this department to become AI practitioners. I need one person inside Estimating who is curious enough to work through it with me, so that what gets built comes from someone who actually does the job. Everyone else receives the benefit without changing how they work.
A proposal, for discussion. Liz is part of the company's AI task force and working through the training, which puts her in a strong position to help identify where the real friction sits. My proposal is that we make room for her to partner with me on this. That is not a decision I would make without you, both because it affects your team's capacity and because Liz should be invited rather than assigned.
The department is currently one Supervisor and three Estimators. That is not the end state.
The target shape is one Estimating Manager, two Senior Estimators, and two Estimators. That structure creates depth, redundancy on complex work, a real bench, and room for people to move up without waiting for someone to leave.
We do intend to add headcount. That should be said plainly, because this department has been carrying the work of a larger team and deserves a straight answer rather than an open question.
The sequence is deliberate. We promote from within before we hire outside. Establishing the Senior tier and advancing internally comes first, followed by a hire at the Estimator level. That way the people already here move up rather than being layered over, and a new person joins a department with depth above them to learn from.
And we fix the system before we add to it. Bringing someone new into a department with unresolved process friction and unclear inputs sets them up to struggle and pulls the existing team away from their own work to compensate. The process work happening in parallel is what makes a new hire an addition of capacity rather than a temporary drain on it.
The honest version: not yet, here is exactly what has to happen first, and here is what the department looks like when it is done.
Melissa owns the room. Team leadership and development, workflow and queue management, quality and accuracy standards across the department, and the day-to-day culture and dynamic of the team.
Alex owns the structure around the room. The role framework and bands, Design and Estimating integration, upstream input quality and the cross-departmental issues that create pressure on this department, tooling and capacity, and advocacy for Estimating with the executive team.
Together we own the outcome. A department that produces faster, more accurate, more strategically valuable work, with people who want to be here and can see where they are going.
This is not a critique of how the department has been run. The constraints described here are structural, and they predate the people currently carrying them.
This is not a plan to do more with less. The tooling work exists to make the volume survivable, not to justify running lean.
And this is not a plan that gets handed down. It gets built together, and the parts that touch the team carry your input before they go anywhere else.
Estimating and Design are two halves of one Client Solutions team. Design shapes the solution. Estimating shapes the price that makes it winnable and buildable.
This defines four tiers so everyone in the department can see exactly what the next level looks like and what it takes to get there. Advancement is not about time served. It is a measurable shift in three things: the complexity you can carry, the accuracy you hold yourself to, and how early in the process your cost insight shapes the solution.
A Supervisor runs the department. A Manager owns the system the department runs on. Put another way, the Supervisor role answers whether the work got done well. The Manager role answers why the work takes what it takes, and how to change that.
| Estimating Supervisor | Estimating Manager | |
|---|---|---|
| Accountable for | The department's output. Accurate, complete, on time. | The department's method. The cost libraries, templates, assumptions, and standards that produce the output. |
| Relationship to data | Produces reporting and reports estimate versus actual results. | Consumes that data and changes formulas and assumptions because of it. Accuracy becomes a system to tune, not a result to report. |
| Entry point into a deal | Work arrives, then gets routed, prioritized, and quality-checked. | Participates in concept development on priority deals, shaping solutions with cost insight before design is finalized. |
| Authority | Escalation point for complex or contested estimates. Advocates for the department. | Formal decision rights. Can require scope adjustments to meet budget, and approves proposal accuracy before client delivery. |
| Team development | Coaches individuals to perform their current roles well. | Builds departmental capability in cost communication, design awareness, and tradeoff articulation. |
| Time horizon | The queue, the deliverables, the week. | The department's capacity a year from now. |
The decisions compound. A Supervisor's mistake costs a deliverable. A Manager's decision about a cost library or a standard affects every estimate that follows it, for a year, in either direction. Wider blast radius in both directions.
It carries margin authority. The ability to require scope changes and to approve accuracy before client exposure is direct exposure to margin. It also means holding the line with Design and Business Development when the numbers do not work, which is harder than it sounds and is compensated accordingly.
Move from reporting accuracy to acting on it, adjusting the formulas and assumptions behind the numbers rather than only observing the results.
Own the cost library, templates, and standards as things to maintain and improve rather than things to use.
Engage in concept development on priority deals, so cost insight shapes design before it is finalized rather than pricing what arrives.
Build the team's tradeoff and cost-communication skill. The measure is simple: are estimators bringing value-engineering options without being asked?
Hold first-pass budget tolerance and require scope adjustments where the numbers demand it. This is as much a political muscle as a technical one.
This tier is not currently filled and is not yet approved. It is defined here because the department needs someone owning the estimating system itself, and naming the seat is what makes that possible. As with every tier in this structure, evidence sets the timeline, not a calendar.
Progression is discussed openly in quarterly conversations and annual reviews. Where someone is working toward the next tier, the benchmarks are written down and assessed against evidence, so advancement is never a matter of guesswork or opinion.
Five come from the existing Senior Estimator role definition. The sixth reflects where the department is going as part of the Client Solutions team.
This is the bar for anyone pursuing the tier, not a bar written for a particular person. Advancement here is a documented path, not a selection.
Maintains estimates within plus or minus 10 percent estimate versus actual across proposals, measured in hours.
Carries the most intricate and highest-value projects, including major annual accounts and competitive opportunities, without oversight.
Uses estimate versus actual results to tighten their own assumptions and inputs over time, rather than only meeting the accuracy standard. Treats accuracy as something to actively improve, not just maintain.
Assists in training Estimators, and serves as a recognized subject matter resource the broader team draws on.
Drafts process and procedure documentation that becomes part of the department's repeatable framework.
Engages during concept development rather than after, bringing value-engineering options with real savings attached. Operates with both a departmental and a company-wide lens.
When someone is working toward this tier, we write down where they stand against each of the six, name what remains, and set a real assessment cadence against it.
The timeline is set by the evidence, not the other way around. These are behaviors and confirmations, not years of experience. When the open items close, the promotion is confirmed. If they close quickly, it happens quickly. The person knows at every checkpoint exactly where they stand and what remains.
That is deliberate. Advancement conversations in this department have previously ended without a concrete outcome. Writing the standard down means the bar is visible, the assessment is evidence-based, and the result is within the person's control.
The same six requirements and the same structured path are available to anyone in the department who wants them. Individual readiness plans are held separately and discussed directly with the person and their manager.