Module · Estimates
Construction estimating software for UK consultancies.
Benchmark estimates at PCSA stage. Detailed estimates at Stage 4. Both built on the same rate library, both flowing into procurement and the PCSR. The estimating layer your QS team would build if they had a year.
Detailed Estimate
Imperial House — Stage 4 · NRM2 elemental
Floor area
1,240 m²
£/m²
£811
vs Benchmark
+4.2%
Where estimating breaks at scale
Every project starts with an estimate. Every consultancy maintains them in fundamentally fragile ways.
The benchmark estimate at Stage 0 sets the budget. The detailed estimate at Stage 4 sets the tender. Both should compound into a rate library. Few consultancies have one.
No firm-wide rate library
Each QS keeps their own rates in their head and their workbooks. The benchmark estimate built by a junior QS is a different beast from the one built by a senior. Variance kills tender accuracy.
Stage 4 detailed estimate disconnected from Stage 2 benchmark
The £/m² benchmark at Stage 2 says £750. The detailed estimate at Stage 4 lands at £820 — 9% over. Nobody reconciles; the client gets a surprise.
Estimating data lost at closeout
Out-turn cost vs original estimate is the consultancy's most valuable estimating dataset. Most firms don't archive it systematically. The next bid is a guess.
How it looks
NRM2 elemental. Package-linked. Live £/m² benchmarking.
The detailed estimate every QS team needs — with line-by-line rates, automatic £/m² benchmarking against your historical projects, and direct linkage into procurement packages.
Detailed Estimate
Imperial House — Stage 4 · NRM2 elemental
Floor area
1,240 m²
£/m²
£811
vs Benchmark
+4.2%
Capabilities
Two estimating modes. One rate library.
Benchmark estimates
High-level cost-per-m² estimates for early-stage feasibility. Driven by your firm's historical project data, not generic BCIS averages.
Detailed estimates
NRM2-elemental detailed estimates with line items, rates, and package allocation. Ready to convert into BoQ or tender pack.
Firm-wide rate library
One central rate library, used across every project, every QS. Updated as award data lands. New estimates start at the right rates.
Package linkage
Each line item flows into a procurement package. The estimate is the cost plan; the cost plan is the procurement matrix; the matrix is the PCSR. One model.
Stage-by-stage refinement
Stage 0 → Stage 1 → Stage 2 → Stage 3 → Stage 4. Each stage refines the previous. Variance against earlier stages tracked automatically.
Out-turn feedback loop
Final out-turn cost feeds back into the rate library. The library gets sharper with every project closed out — your estimating gets more accurate, not less.
Who uses it
Built for the people producing every estimate the firm sends.
Quantity Surveyors
Build the detailed estimate using the firm's real rates, not yours. Convert into tender pack in one click. Reconciliation between Stage 2 benchmark and Stage 4 detailed is automatic.
Cost Coordinators
Maintain the firm-wide rate library. See every estimate against every benchmark. Spot the QS whose estimates consistently come in low.
Directors / Partners
Bid stage feasibility in 24 hours, not a week. The Director conversation with the client at Stage 0 has real numbers, not gut-feel guesses.
See estimates that compound across the firm.
A 30-minute demo on a real project of yours — bring an existing estimate and we\'ll show you the rate library it would build.
Frequently asked questions
Do you do BoQ generation?
Yes — a detailed estimate can be converted into a Bill of Quantities ready for tender, with NRM2 codes, descriptions, quantities, and units. Rates are stripped before issue.
Where do the benchmark rates come from?
Your firm's own historical project data, not generic BCIS averages. New consultancies can seed with BCIS or Spons data; once you've closed projects in Projavio, your own data takes over.
How does this work with takeoff tools?
Detailed estimates can import quantities from any takeoff tool (Cubit, Bluebeam, etc.) via CSV. Native integrations on the roadmap.
Does it support sectional or stage estimates?
Yes. Estimates can be split by RIBA stage, by project section, or by sub-project (useful on multi-block developments). Roll-ups across sections happen automatically.
How does it differ from doing it in Excel?
Same numbers, but the rate library is firm-wide rather than QS-specific, and the estimate flows into the procurement matrix and PCSR without re-keying. Less reconciliation, sharper forecasting.
Can we keep our existing estimating templates?
Most firms' Excel templates map cleanly to Projavio's schema. We help you migrate during onboarding. The structure carries; the formulas don't need to.
Does it support MEP-specific estimating?
MEP estimates can be built as detailed line-items or as package allowances. Specialist MEP estimating tools (e.g. CYMAP, Trimble) export to CSV; Projavio imports.
Estimating that compounds.
One rate library across the firm. Every project sharpens it. Every estimate is closer to out-turn than the last.