Q01
Question — Could you walk me through the most recent live or completed project from tender to handover and name every paid tool, service, device, and data source the team relied on?
Uncovers — Tool inventory, spend surface area, workflow coverage, project versus central ownership.
Why it stays clean — It asks for a real project walkthrough rather than opinions about categories.
Follow-up probes —
- Which of those were required by the client, main contractor, subcontractor, or your own firm?
- Which ones had a direct invoice or renewal attached?
- Which ones were used on site rather than only in head office?
Polite-answer trap — Useless/evasive: “We use the usual construction software stack.” Redirect: “Could we take one recent project and list the actual named systems and services that showed up on it?”
Q02
Question — For each paid tool or service you just named, who pays for it, roughly what is the annual or project cost, and is it per-seat, per-project, enterprise, or month-to-month?
Uncovers — Price anchors, budget line, commercial model, procurement pattern.
Why it stays clean — It asks for existing spend and contract structure, not willingness to pay.
Follow-up probes —
- Which cost is visible to the project team versus hidden in overhead?
- Which invoice or renewal owner has access to the number if you do not?
- What is the closest band: under £1k, £1–10k, £10–50k, £50–250k, or above £250k?
Polite-answer trap — Useless/evasive: “It varies too much to say.” Redirect: “Could we pick the last renewal or the most recent project invoice and use that as the example?”
Q03
Question — Which paid tools are bought centrally, which are charged to individual projects, and which are bought informally by a team or department?
Uncovers — Budget fragmentation, buyer location, rogue spend, adoption path.
Why it stays clean — It separates actual purchase routes from abstract org-chart ownership.
Follow-up probes —
- Who sees the invoice in each case?
- Which category bypasses IT or procurement most often?
- Which project manager or department head has bought something directly in the last year?
Polite-answer trap — Useless/evasive: “Everything goes through the proper channels.” Redirect: “What was the last small purchase that did not need a formal procurement process?”
Q04
Question — Which hardware or site devices does the firm pay for today, including tablets, cameras, scanners, access-control devices, sensors, radios, or recording equipment?
Uncovers — Non-software spend, site constraints, evidence capture habits, operational maturity.
Why it stays clean — It asks for existing paid assets rather than suggesting new device categories.
Follow-up probes —
- Who requested the last batch?
- How often are they lost, replaced, repaired, or left unused?
- Which devices have recurring subscriptions or data charges attached?
Polite-answer trap — Useless/evasive: “We have some tablets and phones around.” Redirect: “Could you describe the last site setup and what devices were actually issued to named roles?”
Q05
Question — Which current tool entered the company most recently, and what was happening in the business when it was first introduced?
Uncovers — Trigger events, adoption entry point, urgency, champion behavior.
Why it stays clean — It uses a recent past purchase as the anchor instead of asking about appetite.
Follow-up probes —
- Who first brought it up?
- What problem or incident made it worth considering then?
- What was the first project or team that used it?
Polite-answer trap — Useless/evasive: “We are always looking at new tools.” Redirect: “Which one actually became a paid tool most recently, and what month did that happen?”
Q06
Question — Which tools or paid services around documents, drawings, cost control, programme, quality, safety, snagging, photos, reporting, or handover are compulsory on some projects but optional on others?
Uncovers — Client-driven adoption, project-type variance, compliance-driven spend.
Why it stays clean — It asks where adoption has already occurred under real project conditions.
Follow-up probes —
- Which client or project type makes it compulsory?
- Who pays when it is client-mandated?
- What changes on projects where it is optional?
Polite-answer trap — Useless/evasive: “It depends on the project.” Redirect: “Could we compare the last project where it was compulsory with the last project where it was optional?”
Q07
Question — Which paid tools are used by commercial, site management, design coordination, document control, HSE, quality, and finance teams in a normal week?
Uncovers — Role-level usage map, daily embeddedness, cross-functional coverage.
Why it stays clean — It asks about normal-week behavior rather than feature availability.
Follow-up probes —
- Which role opens each tool every day?
- Which role only sees exports or reports?
- Which role refuses or avoids the tool?
Polite-answer trap — Useless/evasive: “Everyone uses the system.” Redirect: “Who opened it on site last week, and who relied on someone else to enter the data?”
Q08
Question — When a new seat, site licence, module, or add-on is needed, what exact approval route does it follow?
Uncovers — Expansion friction, land-and-expand mechanics, thresholds, blockers.
Why it stays clean — It focuses on a recurring operational action that has happened before.
Follow-up probes —
- Who requested the last extra seat or licence?
- How long did approval take?
- Was the answer yes, no, or delayed until renewal?
Polite-answer trap — Useless/evasive: “We just add seats when needed.” Redirect: “What happened the last time someone asked for an extra licence mid-project?”
Q09
Question — Which paid tools have integrations, exports, or manual rekeying into other systems, and who maintains those links?
Uncovers — Integration burden, hidden admin spend, switching cost, data ownership.
Why it stays clean — It asks for current workflow mechanics instead of proposing integration improvements.
Follow-up probes —
- Which export is used most often?
- Who fixes it when it breaks?
- Which field is manually copied from one place to another?
Polite-answer trap — Useless/evasive: “They are mostly integrated.” Redirect: “What was the last time someone had to manually move data between two systems?”
Q10
Question — Which subscriptions, licences, or services are due for renewal in the next two quarters, and who will review them?
Uncovers — Renewal cadence, buyer authority, near-term budget visibility.
Why it stays clean — It asks about scheduled real decisions rather than future interest.
Follow-up probes —
- Which renewal is most likely to be challenged?
- What usage or value evidence will be reviewed?
- Who prepares the renewal case?
Polite-answer trap — Useless/evasive: “Renewals are routine.” Redirect: “Which renewal email or invoice crossed someone’s desk most recently?”