The bid leak audit:
what we look for in the first 48 hours.

Most ops consultants spend the first month of an engagement learning the business. We spend the first two days finding the leak.

The reason is simple: in a six-week sprint, every day spent learning is a day not spent fixing. The audit below is what makes that compression possible. It is the same checklist we have run inside regulated manufacturing, EPC, agriculture, and an eleven-business private portfolio. The categories travel. The questions travel. The answers reveal the work to come.

If you run this audit on your own business, you will find a leak. Probably more than one. The point of writing it down is not to replace the operator. It is to give you a way to see what an operator would see if they walked your floor on a Monday morning.

The first 48 hours is not for learning the business. It is for finding the leak.

/ SECTION 01The five leak categories

Bid leaks are not a single problem. They are five different problems that look the same from the outside (declining win rate, slipping margin, frustrated estimators) but require different fixes. Confusing them is how most engagements waste money.

The five we look for, in order of how often they actually drive the symptom:

1. Lead-response leak. The clock starts when the lead arrives. If you respond in days instead of hours, the bid is half lost before the estimator opens it.
2. Estimator capacity leak. One person carries every bid. They are the bottleneck and the single point of failure. Backlog turns into half-effort proposals.
3. Knowledge leak. Win/loss data lives in the estimator's head. There is no feedback loop. The same mistakes repeat invisibly across quarters.
4. Pricing-discipline leak. The estimator is also the negotiator, the pricer, and the closer. Margins erode in moments nobody can audit later.
5. Bid-selection leak. The firm bids on everything. The win rate looks reasonable on paper because the unfit bids get filtered late, but the cost of bidding them is invisible.

Of these, two usually matter more than the other three combined. The audit is what tells us which two.

/ SECTION 02The first 48 hours, hour by hour

Hour 0 to 4: the sponsor conversation

Before we look at any data, we sit with the sponsor (the owner, the GM, or whoever signed the engagement) for two hours and ask three questions.

• What does a good month look like in your bid pipeline? Walk me through the one you remember.
• What does a bad month look like? Walk me through the most recent one.
• If we fixed one thing in six weeks, what is the dollar amount you would expect that fix to be worth in twelve months? Show me how you got to the number.

The third question is the one most sponsors cannot answer. That is itself a finding. If the owner cannot put a dollar figure on the fix, the firm has no internal mechanism for prioritizing operational investment. We will likely build one as part of the engagement.

Hour 4 to 16: the data pull

We ask for the last twelve months of bid data in whatever shape it lives. CRM export. Spreadsheets. PDFs. We do not care about the format. We care about completeness.

The five fields we need:

• Lead source and arrival timestamp
• First-response timestamp (the actual reply, not the auto-acknowledgement)
• Bid submission date
• Win/loss outcome and the documented reason
• Bid value

If three or more of these fields are missing or unreliable, we have already found a major finding: the firm is operating bid management without a feedback loop. Almost everything else in the audit is moot until that loop is built.

Hour 16 to 32: the floor walk

We do not run this from a conference room. We sit with the estimator. We sit with whoever fields the lead. We sit with whoever signs off on bids. Half the leaks we find live in handoffs that nobody owns. You cannot see those from a deck.

Specifically, we are watching for three things:

1. The minute-by-minute path of the next live lead. Where does it land? Who sees it first? When is the first action? When is the first reply?
2. The conversations the estimator is having that nobody documents. The off-the-record judgments about which bids will be tight, which clients are price-shopping, which projects will get scoped down at signing. This intelligence is gold and almost no firm captures it.
3. What gets cut when capacity is short. When the estimator is buried, what does not get done? Site visits? Vendor pricing checks? Margin reviews? Whatever gets cut first is where the leak is hiding.

Hour 32 to 48: quantification and naming

At this point we have enough to put a dollar figure on the top one or two leaks. Not a precise figure. A defensible one. Sponsor-signable.

The format we use:

The dollar ranges matter less than the relative ordering. The sponsor signs the table. That signature is what locks the next four weeks of work.

/ SECTION 03What 48 hours buys you

Three things, in order of importance.

A defensible diagnosis. Not an opinion. Not a hypothesis. A signed document that names the top one or two leaks in dollars per year. This is what gets the sponsor and the operator agreeing on what we are actually fixing.

A discard list. The leaks we found that are real but not the priority. We document them anyway. They become the costed roadmap at the end of the engagement, so the sponsor knows what comes next without having to re-engage to find out.

A working week-three plan. By the end of the audit, we know what we are building, who we are building it with, and what "done" looks like. The remaining four weeks are execution, not discovery.

/ SECTION 04How to run a version of this on your own

If you are not ready to engage and want to run a lighter version of the audit yourself, here is the compressed checklist.

1. Pull the last 25 bids your firm submitted. Lay them out in a single spreadsheet.
2. For each, fill in: lead arrival date, first-response date, bid submission date, win/loss, value, and documented reason for the outcome.
3. Calculate average lead-response time. If it is over 24 hours, that is leak 01.
4. Count the percentage of bids with a documented win/loss reason. If it is under 50%, that is leak 03.
5. Ask your estimator: of the last 25, how many did you write at full effort? If the answer is under 20, that is leak 02.

This will not give you the dollar figure. It will tell you which leak is most likely the priority. That is enough to know whether to engage or whether to sit with it for another quarter.

/ SECTION 05When to bring in an operator

If you can run the audit yourself, run it yourself. The frameworks are free for a reason. The work is the offer.

You bring in an operator when one of three things is true:

1. You have run the audit and you know what is leaking, but the fix requires building a system you do not currently have the capacity or the skill to build.
2. You have the capacity and skill, but the fix requires authority across functions that only an outside operator (not staff) can credibly exercise.
3. You need the fix to be measurable, defensible, and handed back working in a fixed window. Internal teams have day jobs. The sprint window forces the work to ship.

If none of those three are true, you do not need us. Run the audit. Fix what you find. We will still send you the next note.

The frameworks are free. The work is the offer.