CWICR Overhead & Markup Calculator

A direct cost estimate coded by CWICR division is only the base of the bid — overhead still has to get allocated across it and profit still has to get marked up on top, and doing that by hand, division by division, is exactly where a small-dollar line item quietly ends up with a percentage markup that looks fine on paper but leaves almost no real profit dollars once it's actually built.

The skill takes the CWICR-coded direct cost estimate plus the contractor's own overhead rate — either a percentage or a fixed indirect cost pool to allocate pro-rata by each division's share of direct cost — and the desired profit markup percentage, then computes the fully-loaded bid price division by division, showing direct cost, allocated overhead, and profit broken out separately. It flags any division where a uniform markup produces a profit dollar amount that looks unrealistically small for the scope, a common estimating mistake that a flat percentage applied everywhere doesn't catch on its own.

It does not tell you what overhead rate or markup you should charge — that's a business and market decision based on your own cost history, risk, and competitive position, and the skill says so directly rather than suggesting a number. It only computes the allocation and markup math correctly once you supply the rates, and flags allocation red flags for you to review, not to resolve on its own.

Bloqbase itself is built for the Spanish market, but if you manage projects across markets and CWICR is part of how your US jobs get bid, this skill slots into that workflow directly. Download it free with your email, or write to us if you want to see it working with your actual project's estimate.

How to use it with judgment: start with one real, well-defined case, enter only data you can verify, and keep the reviewed version. The goal is not to fill in another document for its own sake, but to turn a project decision into a record that someone else can understand and review later.

Before making it part of your process, check three things: the inputs come from an identifiable source, the calculations or wording match the actual project, and it is clear who must approve the result. If one is missing, treat it as working material rather than final project documentation.

How to prepare the input: start with a real case and define which question the skill must answer, which period the data covers, and which fields cannot be missing. Mark estimates or incomplete sources before requesting the analysis.

How to review the output: check that conclusions can be traced back to your data, inspect the rows or documents behind each alert, and discuss priority cases with the person responsible for the project. A skill helps organize judgment; it does not replace technical, contractual, or financial approval.

How to make it part of the workflow: keep the prompt, the source data, and the reviewed result with the project. This lets you repeat the analysis when progress changes, compare periods, and explain why a recommendation was accepted, rejected, or sent for review.

How to put it to work on a real project

The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.