Estimating engineering work you then have to deliver
Work breakdown to per-role hours, requirement compliance matrices, and banded thresholds that stop a bid and re-estimate instead of silently overrunning.
- client
- No single engagement
- period
- 2023 to present
- track
- #advisory#leadership
Context
Part of my remit is engineering sales. I scope, price and bid for engineering work, and then I lead the team that delivers it. That second clause is the whole point. The estimate is written by the person who has to live with it.
This study describes the method. It does not describe any deal. Rates, contract values, budgets and client-attributable hour counts are not mine to publish, and nothing below depends on them.
The problem
A fixed price on a regulated engagement is a promise about the future made with incomplete information. There are two easy ways to break it. Quote low and overrun quietly, which costs the delivery team. Pad the number until the bid is safe, which costs the bid. A proposal the client can hold you to, and that you can hold yourself to, needs structure underneath the number.
What I did
- Work breakdown structures down to per-role hours. Every line carries a role and an hour count in a ledger, so the price is a sum of things someone can argue with individually.
- Requirement compliance matrices. Every requirement identifier gets one of three classifications: comply, comply with clarification, or do not comply. One engagement ran to 237 identifiers. The third column matters because it exists. Saying no to a line before signing is cheaper than discovering it after.
- Scoping bands with stop-and-re-estimate thresholds. Each package carries a band. If effort crosses it, delivery pauses and the estimate is redone with the client in the room. The bid degrades honestly instead of silently.
- An engineering delivery plan, a statement of work and a kickoff briefing produced alongside the commercial proposal, so the team that starts on day one starts from the same document the client signed.
- Milestone-gated payment structures on the commercial side, and reviewer-attestation separation of duties on the delivery side, so the person who signs off on a piece of work is a different person from the one who built it.
What it cost
- Time before revenue. A 237-line compliance matrix is days of work with no guarantee of a win.
- The stop-and-re-estimate threshold is uncomfortable to trigger, and it only works if it is written into the contract. A threshold that lives in a spreadsheet is a wish.
- Bid-to-delivery continuity means I cannot blame the estimate. That is the discipline and it is also the exposure.
Outcome
The practice is the outcome: bids that turn into deliverable plans, teams that start from the document the client signed, and estimates that are answerable because the person who wrote them is the person delivering. There is no figure in this study, by design.