Custom vs Generic Price Database [2026]

If your main question is which tool helps you manage that database day to day, start with the construction budget software page and the pricing page, then come back to the strategy in this guide.

What are generic price databases and what are they for

Generic price databases are catalogues of construction line items with reference prices, maintained by public institutions or professional bodies. Examples include national construction price indices, regional cost databases, and industry-standard references published by organisations such as the RICS, BCIS, or Spon's price books.

These databases are useful because they offer a starting point: thousands of line items catalogued with detailed technical descriptions, standardised units of measurement and reference prices. For someone starting out in the sector or needing to price something outside their speciality, they're a valuable resource.

The problem with quoting using prices that aren't yours

A generic database gives you the average price of a line item across a broad geographical area. But your business doesn't operate in "a broad geographical area". It operates in your town, with your suppliers, with your specific labour costs and your company structure.

These are the real differences between a generic price and what you actually end up paying:

Labour: varies by up to 40% by area

The hourly cost of a skilled tradesperson in London is not the same as in Newcastle. Regional pay rates, demand for tradespeople and cost of living create significant differences. A generic database uses an average price that reflects neither reality.

Materials: depends on your suppliers

If you've been buying from the same merchants for 10 years, you have negotiated prices that may be 10-20% below list price. Or above, if you buy small quantities or premium materials. Your real price is what you pay, not what a database says that averages across hundreds of suppliers.

Productivity: not everyone works at the same rate

Generic databases assume standard productivity rates (X hours per m² of partition wall, Y hours per electrical point). But you know your plumbing team is 20% faster than average, and that painting jobs always take longer than estimated. Only your own records have that data.

What is a custom price database and why it works better

A custom price database is your own catalogue of line items with the real prices you work with in your business. It doesn't replace generic databases: it complements them with your reality.

What a good custom database includes:

• •Your usual line items with the exact description you use (not from a generic catalogue)
• •Updated prices based on what you actually pay your suppliers
• •Your real margin built in, not a theoretical percentage
• •Organised by sections matching how you structure your projects
• •Quality variants: you can have the same item at standard, mid-range and premium prices

The main advantage isn't just accuracy. It's speed. With your own database, creating a new quote means selecting line items you already have, adjusting quantities and you're done. No hunting for prices, no guessing, no "let me check what it cost last time".

If your next bottleneck is not just the database itself but turning it into sections, line items and quantities inside each quote, review arcley's construction budget software page.

When to use a generic database and when to use your own

It's not an either/or choice. The answer depends on the context:

The optimal pattern: use generic databases as a reference when you step outside your comfort zone. But for the 80% of your work (the jobs you do every week), your own database is infinitely more effective, faster and more reliable.

How to build your price database from scratch (step by step)

You don't need 500 line items to get started. Most small practices and renovation companies work with 50-100 regular items that cover 90% of their jobs. Here's how to build it:

Step 1: Review your last 5 quotes

Open your last 5 quotes (spreadsheet, Word, whatever format you use) and extract all the line items. You'll notice many repeat: "Strip existing floor finish", "Tile bathroom walls", "Complete plumbing installation"... Those recurring items are the core of your database.

Step 2: Standardise names and units

In one quote you wrote "Wall tiling", in another "Ceramic wall finish" and in another "Fix wall tiles". They're the same item. Standardise the name and unit of measurement (m², nr, lm, item) so your database is consistent and searchable.

Step 3: Use real prices, not theoretical ones

For each item, review what you actually charged the client and what you paid suppliers and labour. The price in your database should reflect your usual selling price, not a reference book figure. If you work on a 25% margin over cost, include it. It's your price, not an academic one.

Step 4: Organise by sections

Group items as you use them in your quotes. The most common structure:

• •Demolition and preliminary works
• •Brickwork and blockwork
• •Plumbing and drainage
• •Electrical
• •Finishes (floors, walls, ceilings)
• •Joinery
• •Decoration
• •Waste management

If you always work on domestic renovations, this structure covers practically everything. If you do new-build, you'll add sections like Foundations, Structure, Roofing, etc.

Step 5: Start using it and improve as you go

Don't wait for the perfect database before getting started. With 30-50 items you can already create quotes much faster than starting from scratch. Each new quote is an opportunity to add new items and adjust prices. In 3-6 months you'll have a database that reflects your real business with an accuracy no generic database can match.

The compound effect: why your database improves over time

The most important difference between your own database and a generic one is that the former becomes more valuable the more you use it. And we're not talking about marginal improvement:

• •Month 1: you have 40 items. You create a new quote in 2 hours (used to take 6).
• •Month 3: you have 80 items. You duplicate a previous quote and adjust only what changes. 45 minutes.
• •Month 6: you have 120 items and updated prices. You can quote on the first site visit because you know your numbers and your database confirms them.
• •Month 12: your database is your competitive advantage. You quote faster, more accurately and with more confidence than anyone starting each quote from scratch.

Every quote you create feeds your database with new data: items you didn't have, updated prices, variants for different client needs. It's a virtuous cycle that rewards consistent use.

A generic database doesn't offer this effect. You'll always have the same outdated average prices, the same descriptions that don't match how you describe things, and zero memory of how your business works.

Common mistakes when building your price database

We've seen many professionals attempt to create their price database and give up after a few weeks. Almost always for the same reasons:

Trying to be too exhaustive at the start

If you try to catalogue 300 items before you start using it, you'll never finish. Start with the 30 you use most. Add the rest when you need them. Your database doesn't have to be "complete" to be useful, in fact, it will never be complete and that's fine.

Not updating prices

A database with 2-year-old prices is worse than an updated generic one. Each time you finish a project, spend 15 minutes updating the prices of the items you used. You don't need to update everything at once: just what you've recently completed.

Not distinguishing between cost and selling price

Some professionals store cost prices (what they pay suppliers) and then mentally add a margin when quoting. This works until they make a mistake and send the quote with cost prices. Your database should have the final selling price you deliver to the client. The margin is already included.

Storing the database somewhere inaccessible

If your database is in a spreadsheet on your office computer and you need to quote on a site visit, it's useless. Your database needs to be accessible from anywhere, always updated and searchable. If you can't find an item in 10 seconds, there's an organisation problem.

Conclusion: your price database is your most valuable asset

Generic price databases have their place: as a reference, as a starting point for unfamiliar projects, as backup when a developer wants to see "official" prices. But they shouldn't be the basis for your day-to-day quoting.

Your custom price database is where the real knowledge of your business lives: what things cost, how you describe them, how you organise them. It's an asset that grows with every project and that, unlike any other tool, is exclusively yours. Nobody else has your same suppliers, your same productivity rates or your same margins.

Start small, use it from day one and improve it with every quote. In 6 months you'll wonder how you ever worked without it.

Sources and reference material

If you want to review the standards and reference datasets behind price databases and budget exchange, start here: