Unit Price Database Manager for Construction

Every construction company builds up its own real unit prices project after project — tiling per square meter, concrete per cubic meter, a standard window per unit — but that knowledge usually sits scattered across closed-out budgets from past jobs instead of living in a database you can actually query. The result is estimating the next job off generic market price books, or trying to recall from memory what it really cost last time.

This skill takes the company's unit price database — code, description, unit, price, last-updated date, and the project it came from — and turns it into a query-ready list: grouped by division, with each price's age calculated, and clear alerts for any line item that has gone too many months without a real-cost refresh. If you provide the previous price, it also calculates how much each line item has moved.

What it doesn't solve — and the skill says so itself — is keeping the database updated for you: you're still the one entering the real cost every time a project closes, and the skill won't invent a price when the data is missing; it flags it as pending and asks you for it. It also isn't a substitute for a market price book if your company doesn't yet have enough of its own project history.

Bloqbase connects the real cost of every finished project to the company's unit price database automatically, so you're not re-keying numbers by hand every time a job closes. Download the skill free with your email, or reach out if you want to see it working with your own project data.

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.