How much does scaffolding software cost?

Headline pricing in this market is usually per user per month, sometimes with a band for the number of active jobs. That figure is straightforward to compare between vendors and is generally not the number that determines what the system actually costs you.

What sits outside the licence

• –Implementation and configuration, which varies enormously with how your jobs are structured
• –Migrating existing job, take-off and materials data
• –Training, including the operatives and chargehands who will use it on site
• –Integrations with accounts or payroll, which are rarely included by default
• –The ongoing internal effort to keep job and workforce data current

That last item is the one most often left out of a business case entirely, and it is frequently the largest. Somebody has to keep the system reflecting reality — jobs opened and closed, structures erected and struck, cards renewed, adaptations logged — and if nobody is given that time the system degrades into something nobody trusts, at which point the licence is a pure cost.

Where the value usually comes from

Firms that get a return tend to get it in one of two places: variations that now get captured and paid, and time no longer spent reconstructing what happened on a job. Both are measurable in a way that a general efficiency claim is not, and both are worth estimating for your own business before comparing prices.

Common mistakes

• –Comparing per-user prices without establishing what each excludes
• –No budget for migration, training or integration
• –Ignoring the ongoing internal effort to keep data current
• –Pricing for today's headcount without checking how it scales
• –Comparing against zero rather than against the admin time being replaced
• –Not estimating the value of variations currently going uncaptured

In practice: what the return actually looked like

A firm turning over a few million estimated it was failing to capture perhaps two per cent of its work as variations — adaptations done on site, agreed verbally, never written up, and unrecoverable at final account. That estimate was rough and it dwarfed the licence cost by a wide margin.

Whether a system recovers that depends entirely on whether site actually logs things in it, which is why the training and adoption line in the budget matters more than the per-user price. A cheaper product that chargehands do not use returns nothing.

Ask what it costs to leave

Worth establishing before signing rather than at renewal: what exports, in what format, and whether attachments come with it. Job history, adaptation logs and inspection records are exactly the material a firm may need years later, potentially after the relationship with the vendor has ended.

A vendor with a clear, specific answer is usually describing a product they understand. One who has not thought about it is telling you something too.

Worth knowing: price the failure case too

Business cases for systems tend to model the upside. The more useful figure is often the downside of the current arrangement: what one unrecoverable variation costs, what a missed hire-period overrun costs, what a day reconstructing a job's history costs. Those are concrete and they happen already.

• –Estimate what the current arrangement costs, not just what the system saves
• –Use your own recent examples rather than vendor case studies
• –Include the internal time to keep data current

Where this connects: price the current arrangement too

Business cases model the upside and skip the baseline, which is usually the more persuasive figure. What does the present arrangement cost — one unrecoverable variation, a hire overrun nobody charged, a day spent reconstructing a job's history for a query, an afternoon assembling records before an audit?

Those are concrete, they have already happened, and most firms can name recent examples. A business case built on them is considerably harder to argue with than one built on efficiency claims, and it also tells you honestly whether the spend is justified yet — because for some firms it genuinely is not.

• –Estimate what the current arrangement costs using your own recent examples
• –Include the internal time to keep data current, which is usually the largest item
• –Establish what implementation, migration and training cost separately
• –Check what scales per user, per job or per structure
• –Ask what happens to your data if you leave
• –Be willing to conclude it is not justified yet

One practical test: name three recent losses

Rather than estimating a return, name three specific things from the last twelve months: a variation that was not recovered, a hire overrun nobody charged, and a day spent reconstructing a job's history for a query or a claim.

Most firms can name those quickly, and the total is usually larger than a year's licence. It is also a far more honest basis than an efficiency claim, because it is your own money and your own examples — and if the three are hard to find, that is a legitimate answer telling you the spend is not justified yet.