True Point

Pool design & quoting

True Point is a quoting tool for concrete and fibreglass pool builders. It reads the CAD the firm already draws in, runs the exact geometry in the browser, and prices it against what is actually on the shelf, so a quote that took months comes back in hours. What leaves the office is a fabrication order the factory can build from, with a delivery and installation date that holds.

Geometry

Exact B-rep

OpenCascade, not a mesh

Runs

In the browser

Local-first document

Quantities

Off the solid

Areas, volumes, counts

Configurator

Live

Drag it yourself, below

The whole run, CAD to payment

The interface

No left-hand navigation. A top rail carries the document and the four things a designer moves between; underneath it the workspace is the shape every CAD user already knows: feature history on one side, the model in the middle, the selected feature's parameters on the other. The price updates as a consequence of the geometry, in the same panel.

What the design actually cost to arrive at

A pool quote is not one number, it is a number that moves. This is one project from first site visit to order: the quoted value over time, the revisions it took, and the client feedback events that moved it. The spa coming out is the whole story; everything after it is the client buying value back.

Why a real kernel matters

Most quoting tools draw a picture and price a list. If the two disagree, the list wins and the client finds out on site. True Point takes the other approach: one document, one exact kernel, and every quantity read from the evaluated solid. Deck area is the face area. The bearer count is the pattern count. Water volume is the volume.

The architecture follows the local-first CAD model: the document lives in the browser, the geometry is evaluated by OpenCascade compiled to WebAssembly, and the shaded view is a result rather than the source of truth. Typed agents operate against the same schema and the same kernel as the person, under an authority the account owner grants, so an automated change is a reviewable commit against the open document rather than opaque parallel state.

Options, priced as you move them

The client does not want a quote, they want to know what they get for the money. So the drawing and the price are the same object: drag the length, swap the surround, change the coping, and the plan redraws while every affected line re-prices. The lines that do not depend on size sit still.

This is the real thing, not a recording. Move the steppers. Porcelain tile, travertine, clay paver and honed concrete each carry their own rate and their own drawn surface; the bullnose and the square edge are different profiles at different money; and the glass barrier is drawn to AS 1926.1 because in Australia it is not optional.

A reader who does not touch the screen should still see the mechanism, so here are four moves off that baseline with the figures they actually produce. The change is the part that matters, and the count beneath it: not just that the total moved, but how few lines moved with it. Change the surround material and one line re-prices. Change the length and six do, because six of them are measured off the shell. Nothing here is asserted; each row is the same price() the embed above runs.

The screen the client is in

The office screens above are half the job. The client never opens the configurator and never reads the schedule; they get a link, and this is what is behind it. Same document, same solid, same numbers, said in the words of someone who is buying a pool rather than building one. Depth is not a parameter, it is 1.2 metres at one end and 1.9 at the other. The barrier is not a line item at $415/lm, it is frameless glass that keeps the view open where a fence would close it off, and it is there because AS 1926.1 requires it.

The price is one number, fixed, with the single condition that could move it stated plainly: the soil report. There is an Accept button and a way to ask a question, and a timeline showing the quote issued and the deposit next. Nothing here was re-typed from the office view; it is the same quote rendered for the person paying it.

The same model is the source of both documents that leave the office. Nothing is re-entered between them: the client sheet and the fabrication order are two renderings of one solid, which is why the barrier run on the quote and the barrier setout on the fabrication order can never disagree.

The hard part is the barrier, not the pool

A paved courtyard is a parts list. A pool is a regulated assembly, and most of the difficulty sits outside the water: the barrier, the gates, the level change, the plant run. So the configurator carries the fence material and height, the number of gates and what they are made of, whether the surround is in-ground or raised, the step down between levels, an adjoining or separate spa, the cover, the heating, the water treatment, and how far the filter housing sits from the pool.

Those options are not decoration. Choose a fully above-ground surround and the ground on the outside of the barrier falls away, so a 1500 mm fence reads 550 mm from the outside face and the configuration stops being compliant. The panel says so, in the same words a certifier would use. AS 1926.1 sets 1200 mm as the minimum from finished ground, with a 900 mm non-climbable zone, gaps under 100 mm, and gates that are self-closing and self-latching. A quoting tool that cannot see that is quoting a pool that cannot be signed off.

A pool with no chlorine in it

Choose freshwater and the chlorinator line disappears from the quote. In its place the model adds a regeneration zone, sized as a proportion of the swim area, and a sand and gravel bed. This is a swimming pond: the water is cleaned biologically by the root zone of the planting and by the bed it passes through, and it circulates slowly rather than being pushed through a filter under pressure.

It is also the case that proves the point about geometry. The planting is generated from the shape of the regeneration zone, so every stem carries its own height, lean and seed head, and changing the zone ratio replants the bed at the same density rather than stretching a picture of one.

Modelled, not drawn

This pool was built in a real CAD kernel, not illustrated. A rectangle was sketched and extruded, the four vertical corners filleted to make the oval plan, the solid shelled to a 150 mm wall, then the supports patterned along a datum axis and cut to the falling ground. Fifty-one solids, three hundred and twenty-seven faces, all valid, and the wall material comes out at 7.795 m³ because that is what the kernel measured.

The whole thing exports as STEP. That is the difference between a picture of a pool and a model of one: a fabricator can open the file, and every quantity on the quote traces back to it.

An exact hidden-line drawing generated from the solid: plan, elevations and isometric at 1:50, third angle. Produced by the kernel, not traced.

What is drawn