← Back to Blog

Sales Gallery Technology Cost Drivers

Sales Gallery Technology Cost Drivers

Sales gallery budgets are usually built from the visible parts: screens, software, installation. Those are the predictable costs and they are not where the number moves.

What moves it is the asset inventory, which is invisible at specification time, grows with the shape of the building, and is the one line a platform demonstration never shows you.

The driver that dominates: how many assets

A gallery displays produced content, and on a pre-construction development every piece of it is made rather than photographed.

The count is the budget. Not the resolution, not the style, not the software. How many distinct things have to exist before opening day.

For a small development with four plan types and one finish scheme, that count is modest and the gallery is inexpensive. For a tower with eight unit types, three finish schemes and a view that changes every ten floors, the same brief produces an order of magnitude more work.

Any quote that does not contain a count has not been scoped, and any comparison between quotes with different counts is not a comparison.

Why height multiplies cost and width does not

This surprises developers and it follows directly from what buyers ask.

A wide low rise development has many units and most of them see roughly the same thing. One view per orientation covers the question adequately, because the difference between the second floor and the third is not what anybody is paying for.

A tower sells height. The view is the product, it changes continuously, and the price difference between floors is justified by it. Which means views cannot be shared across floors, and the count scales with the thing the building is selling.

That is why two developments with the same unit count can differ substantially in gallery cost, and it is entirely rational.

Finish variations multiply across everything they touch

The second multiplier, and the one most often underestimated because it sounds like a small addition.

A finish scheme is not one asset. It is a variation applied to every interior view of every unit type it applies to. Three schemes across eight unit types with two interiors each is not three extra images, it is a multiplication.

There are cheaper ways to handle it, including showing finishes as material boards and applying them live in a real time build rather than pre rendering every combination.

Choosing that approach early is a large saving. Discovering the multiplication after the content is specified as pre rendered is a large overrun.

Pre rendered or live: the structural choice

This is the decision that determines whether the asset count is a problem at all.

Pre rendered content is produced image by image. Quality is the highest available, hardware requirements are modest, and every additional floor, orientation or finish is another production item.

Live content is a model rendered on demand. Any floor, any direction, any finish, without producing that specific case in advance. Image quality is lower than offline rendering and the model has to be built to a real time standard.

For a low rise, pre rendered is simpler and cheaper. For a tower, live is frequently the only route that does not produce hundreds of images, and the higher model cost is recovered many times over.

Hardware, and why it is the small number

Screens, touch displays and the machines behind them are the most visible line and rarely the largest one.

They are also the most predictable, because they are catalogue items with known prices, which is precisely why budgets get built around them and then have to be revised.

The exception is direct view LED, which is a construction item rather than a purchase. It carries structure, power, heat and installation costs that a mounted display does not, and it should be priced with the fit out rather than with the technology.

Installation belongs to the fit out programme

Mounting, cable routes, power positions, sightlines and acoustics are all decided by whoever builds the room.

Technology designed in at drawing stage disappears into the space. Technology added afterwards produces a screen on a bracket with a visible cable in a room whose entire purpose is to look considered.

The cost difference between those two outcomes is small if the coordination happens early and substantial if it happens late, because late means remedial work in a finished room.

Data integration, priced or deferred

The moment a gallery shows availability or pricing it becomes a system rather than a delivery.

Connected to a system of record, it stays correct automatically and there is an integration cost. Maintained by hand it is free and it is correct for about three months.

The third option, which is legitimate and rarely chosen, is not to show availability at all. That removes an entire failure mode and costs nothing.

Support, the line most often left blank

A gallery runs for the length of a sales programme, which is measured in years, and hardware fails on the days with the most visitors.

Support has a real cost: response time, spare hardware, somebody who can attend, and periodic attention as operating systems and platforms update.

Budgeting nothing for it does not remove the cost, it converts it into an emergency purchase at a worse price, or into a gallery that is quietly dark.

The revision budget nobody sets

On a development the design changes during construction, and the gallery is where those changes are most visible.

A gallery built from an owned, structured model absorbs a change as a re render of the affected assets. One delivered as a fixed compiled experience requires going back to the vendor.

Setting a revision allowance at the start, and structuring the content so revisions are localised, is worth more than any negotiation on the initial price.

What repeats and what does not

The cost profile is very different for a single building and for a multi phase programme, and treating them the same is expensive.

Phase one carries everything: the model, the material library, the standards, the platform setup and the training. Phase two reuses all of it and costs a fraction.

That saving only exists if the same model is retained and the project owns it. Commissioning phase two from a different vendor discards the entire accumulated investment and starts again.

The specification work that never appears as a line

Before anything can be priced, somebody has to decide what the gallery holds, in what order, at what level of detail, and for which unit types.

That work is real effort and it usually happens for free during a sales process, which means it gets done by whichever vendor is most persuasive and shaped around what that vendor sells.

A development that pays for the specification separately, before selecting a build vendor, gets a document that produces genuinely comparable quotes and does not accidentally specify somebody product.

It is unusual in this category and it is the highest return decision available in it, because the specification determines every other number on this page.

Timing, and the cost of compressing production

Content is the long pole and it is the task compressed when everything else slips, which is exactly backwards.

Hardware has a lead time that cannot be argued with. Fit out has a programme. Platform setup is measured in days. Content is measured in weeks and it is the only line that can absorb pressure, so it does.

Compressed production costs more in two ways: overtime rates on the studio side, and a gallery that opens with placeholders on the developer side, which is the more expensive of the two because it happens in front of buyers.

Starting content before the platform is chosen is counterintuitive and correct, because the assets are needed regardless of which platform displays them.

Multiple galleries, and what changes

Developers operating several galleries, whether across phases or across communities, face a different arithmetic and frequently price it as if each were the first.

The content, standards and material library are shared. The platform licence, hardware and installation are per location. Support scales with locations rather than with content.

That means the second gallery is substantially cheaper than the first on the content line and roughly the same on everything else, and a proposal that prices the second identically to the first has not accounted for the reuse.

It also means consistency has real value: three galleries running the same content and the same tool is a training and support problem solved once, while three different setups is the same problem three times.

What developers regret paying for

Patterns emerge across projects and they are worth stating because they are consistent rather than anecdotal.

Bespoke applications built for one development, which cost more than a platform licence, need maintenance nobody budgeted, and cannot be reused on the next project.

Large format installations in temporary spaces, where the install and removal costs were not in the original number and the format could not move to the next gallery.

Vision films, which absorb a meaningful share of a content budget, are watched once, and answer none of the questions a buyer came with.

Live availability with no owner, which works until it does not and then actively damages the sales conversation it was meant to support.

The comparison that makes the number legible

Judged against marketing spend, a gallery looks expensive. Judged against a fitted show unit, it usually does not, and the second comparison is the honest one.

A show unit is expensive, immovable, shows exactly one configuration, cannot be updated when the specification changes, and is unmatched for the buyer standing inside it.

A gallery covers everything the show unit cannot: other unit types, other floors, other finishes, unbuilt phases, and buyers who never visit.

Most developments are best served by both, and the useful internal conversation is about the split rather than about whether the gallery is affordable.

Where the money produces the most return

Coverage first. Gaps in the inventory appear precisely where buyers ask questions, and a gallery that cannot answer a question in the room hands the answer to a competitor.

Retrieval speed second. A path an agent walks hundreds of times, with a few seconds of friction each time, becomes avoidance.

Reliability third, because a dark gallery on a Saturday costs more than any feature adds.

Spectacle last, and with less of it than a demonstration suggests, because the impressive parts are the ones buyers compliment and the plain parts are the ones they use.

Measuring whether the gallery paid for itself

Gallery spend is argued from opinion at every project because almost nobody measures the last one, and the measures available are simple.

Whether the sales team chooses to use it when nothing obliges them to is the strongest single signal, because agents abandon tools that do not help and keep the ones that do.

How often it was working when a visitor arrived, which requires only a log and is the number most likely to be embarrassing.

And which content was actually opened, since platforms can record that and it usually reveals that a third of the produced assets were never shown, which is the most actionable finding available for the next phase.

The cheapest configuration that still works

For a modest development, a defensible gallery is a good exterior set, a complete explorable plan set, one solid interior per unit type, honest finish boards, a site or level plan showing position, and a browser version of the same content.

No immersive room, no bespoke application, no live availability, no custom hardware.

It covers every question a buyer actually asks, it opens complete rather than with placeholders, it travels home with the visitor, and it costs a fraction of what a specified gallery usually does.

Starting there and adding only what a named requirement demands is the sequence that wastes the least money in this category.

To get a gallery priced from an asset count rather than from a screen quote, request a quote.

Frequently asked questions

What is the largest cost in a sales gallery?

The asset inventory. On a pre-construction development every view, interior, finish variation and plan is produced from drawings, and the count of those assets moves the budget far more than screens or software. A quote without a count has not been scoped.

Why do towers cost more than low rise for the same unit count?

Because a tower sells height. The view changes continuously and justifies the price difference between floors, so views cannot be shared across floors. In a low rise most units see roughly the same thing and one view per orientation covers it.

How can finish variations be handled cheaply?

By applying them live in a real time build rather than pre rendering every combination. A finish scheme is not one asset, it is a variation across every interior it touches, so pre rendering multiplies quickly. Choosing this approach early is a large saving.

What should be budgeted for support?

Response time, spare hardware, somebody who can attend, and periodic attention as platforms update. A gallery runs for years and fails on the busiest days. Budgeting nothing converts the cost into an emergency purchase or a dark gallery.

What is the cheapest configuration that still works?

A good exterior set, a complete explorable plan set, one solid interior per unit type, honest finish boards, a plan showing position, and a browser version of the same content. It answers every question buyers actually ask and opens complete rather than with placeholders.