Skip to main content
GullySystem
A practical guide

What to ask a vendor before buying software for a design-build firm

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 6 min read

In this guide 6 sections
The short answer

Ask the vendor to run your own files through a live demo: BOQ import, revision history, supplier purchase orders, dated site photos and a full data export on exit. Slides are not proof. Ask for a written answer to each question, because a promise made in a meeting is easy to forget by month three.

Ask for your own BOQ in the demo

Send a BOQ ahead of the call, and choose one with messy rows such as merged cells, a lump-sum carpentry line and a provisional sum for lighting. Type the units three ways. Then watch the screen.

A clean sample proves nothing. Your files carry the habits of several estimators: hidden columns, rates pasted as values, a skirting line priced per running metre beside a flooring line priced per square foot. The import has to survive them all.

Ask about the row it cannot read. It might reject the whole file, skip the row quietly or flag it for a person to fix, and quiet skipping is the worst answer. A missing line becomes a site loss. Ask who fixes it and how long that takes, because some vendors write a custom mapping for each file layout and bill for that work. Get the answer before you sign.

  • Can it read your Excel layout without retyping?
  • Are unit rates and quantities kept as separate fields?
  • Can one BOQ line be split across rooms or floors?
  • Does an unreadable row get flagged or dropped?

Check how revisions are kept

Design-build work changes weekly. The client moves a partition, swaps a veneer or adds a wardrobe with a loft, and each change touches the GFC drawing, the BOQ and the price.

Have the vendor open revision three of a quote beside revision five, and look for which lines moved, who approved the change and on what date. A system that overwrites the old figure leaves you arguing from memory at final billing, with no dated approval to point to. Can the client approve on a phone? A chat reply saying yes is weak.

Then ask the harder question. When a variation is approved, it should flow into the purchase list and the stage invoice, not wait for someone to retype it three times.

Follow one item from quote to supplier

Pick one item, say 18 mm marine ply for a kitchen, and have the vendor trace it from the BOQ line to a purchase order with the plywood supplier.

Look for what your buyer needs: a quotation comparison across suppliers, the delivery date, the target site and a goods receipt when the sheets arrive. A system that stops at the quote leaves your purchase team in Excel, retyping every line by hand for each supplier and each site. That is the whole problem.

Test a short shipment from the supplier as well. You should be able to receive part of an order, keep the balance open and still see which site holds the sheets. Laminates, hardware and tiles bought for one flat often end up in another without a record, so a site-wise stock sheet matters when you compare cost with the quote.

  • Purchase order raised from approved BOQ lines
  • Quotations from two or three suppliers side by side
  • Part deliveries and open balances
  • Cost per site compared with the quoted amount

Test site photo capture on a phone

Your supervisors work on staircases in plaster dust with one hand free, so hand the vendor a phone and ask one of them to upload three photos. Tie each photo to a room and a task, such as the master bathroom waterproofing test, and see how many taps it takes.

Check the date, location and photographer on each photo, then ask whether it uploads later when the stairwell has no signal, so walk into one and test it. A snag list built from photos helps only when each picture points to a room and a trade, such as tiling or electrical.

Photos also settle disputes. When a client says the false ceiling was never inspected, a dated photo with a sign-off is the only reply you need. Ask whether photos can be grouped into a handover album for the client by room and trade, which saves an evening of copying files.

Ask what leaves with you

Vendors sound confident until the exit question. Then listen. Ask for the full export in writing, covering projects, BOQs with every revision, purchase orders, photos at original size and client sign-offs.

Ask which format each record comes in. A PDF of every quote is not a usable export, because you want CSV or Excel for the numbers and the original image files for the photos.

Finish with a pilot. Run one live project for a month, name one person on your side to own it, and decide on that evidence rather than on the demo. Write each vendor’s answers on one sheet. If a demo promise fails in month three, you then hold the date and the speaker’s name instead of a vague memory of who said what.

  • Export format for each record type
  • Who owns the data after the contract ends
  • How long the vendor keeps a copy
  • Cost and time to hand over a full backup

Design-build vendor question sheet

A single sheet holds five blocks: BOQ import, revision history, purchase orders, site photos and data exit, each with three questions to put to the vendor. Columns record the vendor’s answer, what you saw in the demo and a verdict marked pass, partial or fail, so two vendors can be compared line by line. The footer names the pilot.

Open a blank worksheet to print

Questions owners ask

How many vendors should a design-build firm compare?

Two or three is enough. More than three demos blur together, so give each vendor the same BOQ and the same set of site photos to keep the comparison fair.

Should we buy ready software or have one built?

Ready software suits a firm whose process looks like most others, while a built system fits when stage billing or approval steps are unusual. Run the question sheet against both.

Who in the firm should join the demo?

Send the estimator, a site supervisor and the person who raises purchase orders, because each of them catches a different gap in the demo. The owner then judges the answers.

What if the vendor cannot import our BOQ format?

Ask whether the vendor can build a mapping for your template or whether you must change the template to suit the software. A one-time mapping is fair. Retyping every BOQ is a deal breaker.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements