From an address to a signature.
A proposal is not a PDF someone formatted. It is the readable face of one calculation — and the same calculation stands behind the price, the documents and the invoice that follows it.
How it gets built.
The customer and the address
Pulled from the lead if there is one, so nobody retypes a name or a postcode. The postcode is the input that decides the certificate zone, the state scheme and which activities are even available.
The roof, from above
An aerial scan of that address sizes the array against the real roof planes and returns a yield figure with shading already accounted for.
The system, from the catalogue
Hardware is chosen from the controlled library — never typed in free text — so every line carries a real model number, a datasheet and a written warranty.
Incentives applied
Certificates, program tiers and state schemes resolve against the address and the install date, and are itemised rather than quietly folded into one discounted number.
The price, checked against the floor
The owner can type the figure the customer should pay and the engine works the discount backwards to it. If that would cross the floor, it is refused — not warned about.
Issued as a link
One URL, readable on a phone. Opening it is recorded, so the follow-up call is informed rather than hopeful.
Signed, invoiced, handed over
Signature in the browser re-prices against the locked terms, raises the deposit invoice and moves the job to operations with its paperwork attached.
What the customer actually reads.
The selling half first, the obligations in full behind it, and the same numbers in both.
Nothing in that document is typed twice. If a figure is wrong, it is wrong in the engine — which means it is wrong once, findable, and fixable for every quote at the same time.