hibranwar

Project Cost Estimation

Operator's Handbook · No. 18 of 50

Calculate the Cost Before Signing, Not After the Work Has Started

Project losses are rarely caused by more work than expected. They are caused by estimation that leaves out costs that were always predictable: mobilization nobody calculated, overhead allocated at half the actual rate, contingency that never made it into the bid, or labor hours underestimated confidently because the last project had a similar name. The problem is not arithmetic. The problem is a missing checklist and a feedback loop that never gets built. This book is for contractors, project-based service businesses, and engineering firms who want to fix both, at any scale from the solo operator doing every estimate by hand to the business preparing for a private placement audit.

This book was originally written in Bahasa Indonesia for Indonesian operators. Examples, regulations, currency (Rupiah), and institutional references reflect Indonesian context. The frameworks, diagnostics, ratios, and operator habits described apply broadly to small and mid-sized businesses in other emerging markets and to many developed-market SME settings as well.

The book covers what belongs in every estimate before a price is sent to a client, how to calculate contingency from risk categories rather than rounding up by feel, and how to build a historical cost database from completed projects so that the next estimate is better than the last. The framing that runs through all ten chapters: LPJK 2023 data shows 34 percent of Indonesian SME contractors recorded a financial loss on at least one project per year, with underestimation at the bidding stage as the primary cause, not unforeseen field conditions. Field conditions are real. The question is whether the estimate included contingency for exactly that kind of field condition. Usually it did not.

What you'll find

  • A complete project cost component checklist including the two categories most commonly omitted: mobilization and demobilization costs, and site safety and housekeeping costs, both invisible in technical drawings and both material to actual project margin
  • The AACE International five-class estimation system in operational terms: what accuracy range to expect from each class and why submitting a Class 5 estimate as a fixed-price bid is structuring a contract for potential loss
  • Bottom-up estimating based on Work Breakdown Structure, the method that provides systematic coverage and leaves the least room for missing a line item
  • Three-point estimating and risk-based contingency: how to calculate a reserve from identifiable risk categories (scope definition quality, subcontractor count, field condition verification status) rather than adding a round percentage
  • Building a historical unit cost database from closed projects, the single most defensible estimating asset a contractor can own
  • Variation order procedures: why real-time documentation of scope changes determines whether a legitimate claim gets paid
  • PSAK 72 compliance for revenue recognition on project contracts: percentage-of-completion methodology and the documentation auditors need to verify the figures (PSAK 72 is Indonesia's equivalent of IFRS 15)

Who this is for

  • Contractors and project-based service businesses at early scale, working without a formal estimating function and building methodology from scratch
  • Mid-size project firms ready to formalize their two-tier estimation review process, variation order protocol, and project-type risk matrix
  • Pre-IPO businesses that need auditable backlog estimation documentation, residual margin evaluation across an active project portfolio, and PSAK 72 implementation

Topics

project cost estimation contractor bid SME contractor cost overrun AACE classification work breakdown structure WBS contingency reserve variation order revenue recognition overhead allocation historical cost database planning fallacy project margin construction cost

Categories

BUS049000
BUSINESS & ECONOMICS / Project Management
direct subject match; the book is a project cost estimation manual grounded in project management methodology (AACE, PMI, WBS) and written for project-based businesses at three scales.
BUS082000
BUSINESS & ECONOMICS / Small Business
written for contractor-operators at three revenue scales, with each level getting calibrated methodology and documentation requirements.
BUS027010
BUSINESS & ECONOMICS / Finance / Financial Risk Management
contingency calculation from risk categories, residual margin analysis, and revenue recognition compliance place this in financial risk territory for project-based businesses.

About the author

Ibrahim Anwar, known as Hibranwar, is an entrepreneur and writer at the intersection of engineering, business, and content. Dutch Literature from Universitas Indonesia. He runs operating businesses across industrial pump distribution, engineering services, and handmade leather craft, and writes from the seat of the operator. Hundreds of digital publications. Writing as system, not expression. Direct and functional. ORCID 0009-0006-0425-4923. He wrote this book from over a decade of preparing, submitting, and reconciling project bids with actual field costs, including the specific projects where the reconciliation did not go well and where the gap between estimate and reality was traceable back to what the checklist missed.