Kraan Bouwcomputing

What Stevin gets out of Kraan Bouwcomputing

Kraan Bouwcomputing specializes in the calculation work: estimating, cost price and project costs for contractors and construction firms. On that specialism it is strong, stronger than the calculation module of a broad ERP. The flip side of a dedicated estimating tool is that it mainly looks ahead, to the quote, and watches less of what happens to those numbers during execution. We see firms stall on this: an estimate still running on last season's prices, a project where the actual costs climb while the estimate stays put. Kraan calculates it correctly, but it does not lay the estimate next to the execution on its own. Stevin puts a layer on top, through the API or an export, and flags what creates margin risk with an action underneath. The estimator decides, Stevin keeps an eye on the distance between budgeted and actual.

What you pair it with

Choosing Kraan gives you strong calculation work, but the estimate sits apart from what actually happens on site. That bridge between budget and execution is something you have to organize yourself. The connection runs through the API or an export, so the estimate data comes out. The question is whether something flags the out-of-date price or the climbing costs in time. Without that monitoring, you only discover margin risk at the after-the-fact costing, when the profit is already gone and correcting is no longer an option.

Common mistakes

• →Estimating with last season's prices because nothing marks the out-of-date lines.
• →Only seeing climbing costs on a project once the estimate is already out of date.
• →Leaving the estimate apart from the execution, so budgeted and actual drift apart.
• →Only discovering margin risk at the after-the-fact costing, when the profit is already gone.