How to build a credible, research-based estimate without pretending every requirement needs a giant cost model.
The lack of an IGE is usually a symptom. The real problem is the lack of documented market research. An estimate is just market research with a number on it. If the customer can't put a number on the requirement, that's the contracting team's first signal the package isn't ready.
You won't find an IGCE calculator on this site, on purpose. Some estimates are a three-quote price check. Some are serious cost models with labor, materials, indirect rates, profit, risk, coefficients, escalation, travel, and all the other math that makes normal people stare into the wall. No single tool covers both ends, and pretending one does makes the customer dumber, not smarter.
That said — if there's real demand for some IGE building tools, even focused ones for specific use cases (services labor estimators, product line-item builders, that kind of thing), let me know. I'll build them if there's a need. Drop a line.
This lesson keeps it simple. The goal is to help customers give contracting a credible, research-based estimate before solicitation so the acquisition team can plan funding, understand the market, and handle whatever competition actually shows up after the request goes out.
IGCE usually means Independent Government Cost Estimate. You'll also hear IGE, Independent Government Estimate. People use the terms interchangeably in normal acquisition life. The point is the same: the Government has its own estimate of what the requirement is likely to cost.
An IGCE is a planning and analysis tool, full stop. It doesn't decide award. It doesn't replace competition. It doesn't prove a proposal is fair and reasonable on its own. It's a number with a story behind it that helps the acquisition team plan funding, understand the market, and check whatever prices come in.
This is where the conversation goes against the grain. The FAR isn't full of universal IGCE requirements for every supply and service buy. Most CO training treats the IGCE like it's mandatory everywhere; in writing, it isn't.
RFO FAR Part 36 explicitly requires an independent Government estimate for construction actions expected to exceed the simplified acquisition threshold, and for architect-engineer services above that threshold before negotiations. Outside that Part 36 lane, the FAR doesn't require an IGCE for routine supply and service buys. Agency policy, local package rules, funding processes, and contracting office procedures may still require one — but it's local practice, not a FAR mandate.
So why do contracting offices still ask for one? Because the acquisition still needs an estimated value. Funding still has to be planned. Market research still has to be documented. And when proposals come back thin, the CO needs something to compare them against.
RFO FAR Part 10 does require market research appropriate to the circumstances. The estimate is how that market research becomes useful to the acquisition team — a number with a documented basis. That's the lane this training lives in.
"Independent" means the contractor doesn't build the Government's estimate. The Government still uses the market — quotes, catalogs, prior buys, public pricing — and absolutely should.
Practitioner reality: if a CO has three quotes from market research that meet the requirement, those three quotes are the IGE for that buy in practice. The estimate becomes "based on three quotes received during market research from Vendor A ($X), Vendor B ($Y), and Vendor C ($Z), with adjustments for quantity and shipping." That's a defensible, research-based estimate. Calling it something else doesn't make it more or less valid.
The Government still owns the estimate. That means documenting the sources, adjusting for scope and quantity, and explaining assumptions. The line gets crossed when one favored vendor writes the estimate and the Government just changes the letterhead. That's not independent. Multiple market data points with the Government's own analysis around them — that's independent.
One contractor's preferred solution copied into Government format isn't doing the job. Multiple market data points with the Government explaining how those data points relate to the requirement is.
The IGCE matters because we don't know how much competition we'll get until the solicitation closes. The fewer competitive prices we receive, the more the pre-solicitation estimate matters.
| Competition result | How much the IGCE matters | Why |
|---|---|---|
| Three or more good quotes | Helpful, but not the star | Competition gives the CO strong price data. The IGCE still helps explain funding and spot obvious outliers. |
| Two good quotes | More important | The CO has some competition, but the estimate helps sanity-check whether both prices are in the expected range. |
| One quote | Very important | Now the file needs other support. A pre-existing estimate helps show whether the only price received makes sense. |
| Sole source or restricted source | Critical | There may be no competition to protect the Government. The estimate, market research, technical analysis, and negotiation support matter much more. |
More competition usually gives better pricing evidence. Less competition means the Government needs more independent support. That's why the estimate has to be ready before we know which world we're in.
Here's the trap. The Government solicits without an IGE. One contractor responds. Now the file needs an estimate to support price reasonableness. Somebody scrambles to build one — and all of a sudden the IGE looks pretty much exactly like what the sole contractor proposed. Because what else were they going to use?
Even when nobody did anything wrong, that's the worst-looking version of the file. The estimate appears to have been copied from the only price received and called independent. Reviewers, auditors, and protesters all see the same thing.
The estimate belongs in the planning record before solicitation, not as a rescue document written after the solicitation result makes everyone nervous. By the time you "need" the IGE, it's already too late to look independent.
If the requirement is to buy a computer, the customer shouldn't be expected to estimate the RAM, display, screws, hard drive, plastic, electricity, packaging, and factory labor. That's not useful for most commercial product buys, and frankly, that's not how the industry prices anyway. Just go ask industry what it costs.
For products, start with market prices for products that actually meet the requirement.
Estimated cost is $50,000. Source: customer guess.
Estimate is $48,000 to $55,000 based on three commercial products meeting the minimum specification, quantity of 35, published prices pulled on 5 May 2026, plus estimated shipping and three-year warranty.
Services can get more complicated because people, hours, labor mix, location, shift coverage, supervision, and risk all matter. You still don't have to become an indirect-rate expert to help.
Start with the parts the requiring activity knows.
If you don't know how to add G&A, overhead, profit, fee, escalation, or risk, say so and reach out to contracting. They may have data on what those rates typically run for the contract type and dollar range. Customers aren't expected to know that a firm-fixed-price contractor carries more risk (and is therefore generally allowed more profit), or what reasonable G&A and overhead rates look like. Your job is to provide the technical assumptions and market data you can defend; contracting can help layer on the rest if they've got the data to support it.
For each labor category: number of people, hours per year, expected hourly rate or salary source, location, required qualifications, and known workload assumptions. Then add known non-labor costs. That's not a perfect cost model, but it gives contracting something real to work with.
A credible estimate usually comes from more than one source. The goal is to understand the market well enough to explain your estimate — not to find the cheapest internet number and call it a day.
| Source | Useful for | Watch out for |
|---|---|---|
| Market research quotes | Products or services where vendors can provide rough pricing before solicitation. | Do not let one vendor shape the requirement or the whole estimate. |
| Catalogs / published prices | Commercial products, software, standard services, parts, supplies. | Catalog price may not include shipping, discount, installation, warranty, or quantity effects. |
| Prior contracts | Recurring buys, recompetes, similar installations, historical usage. | Adjust for time, scope changes, inflation, quantity, and different terms. |
| USAspending research | Finding what other agencies paid for similar work or vendors. | Award descriptions can be vague. Confirm whether the scope is actually similar. |
| Wage determinations | Service labor floors and labor category clues for covered work. | Wage rates aren't fully burdened contractor prices. |
| BLS / labor market data | Labor-rate sanity checks by occupation and location. | Salary data still needs assumptions for fringe, overhead, G&A, profit, and contract risk. |
The best estimate package lets the CO understand the basis of the estimate without interrogating everyone two weeks later. Pretty spreadsheets are fine. Documented sources, assumptions, and ranges are what actually matter.
Before submitting the package, write one paragraph that explains the estimate in plain English: what data you used, why it matches the requirement, what assumptions drive the price, and what you aren't sure about. That paragraph will save contracting time.