From the quoting desk.

A quote can look professional and still be commercially wrong. The common failure is to total materials and labour, add a percentage that sounds reasonable, then discover that overhead, waste or changed supplier rates were never represented in the cost base.

Siteglass treats the company catalogue, labour burden, quantities, waste, tax treatment and minimum gross margin as structured inputs. The language model can ask for missing scope and explain the result. It does not get to improvise the arithmetic.

The important output is not only the final number. It is the trace: which rate was used, when it was approved, which comparable jobs informed the scope and which exclusions remain for the owner to review.

A folder of PDFs is not automatically knowledge. A previous quote may contain a useful scope pattern and an obsolete material rate at the same time. Treating the whole file as current truth makes automated quoting less reliable, not more.

A practical memory layer records document type, date, company, job, location and the exact extracted passage. When the agent finds a comparable quote, it should say why the job is comparable and which parts are not being reused.

Current approved rates remain a separate structured source. Past quotes provide precedent; the catalogue provides the present price; the owner provides the commercial authority.

A chatbot produces an answer. An agent can search company data, calculate, create a document, prepare an invoice hand-off or monitor a tender source. That extra capability is useful only when each tool has a narrow input contract and an audit event.

Before Siteglass calls Xero or Microsoft 365, it should revise the live connector state, identify the target tenant and show the proposed action. The configured authority then approves the change in the app or through a verified phone flow.

The same rule applies to current web research. External facts can inform a recommendation, with source and observation date attached. They cannot silently rewrite an approved company price.

Forwarding every construction notice creates another inbox to ignore. A monitoring agent should first normalize the location, closing date, buyer, scope, value band and mandatory requirements, then compare those fields with the company profile built during setup.

A match needs reasons. The owner should see which capabilities aligned, which requirements remain unverified and how much time is left to respond. A low-confidence match belongs in a quiet review queue; a strong match nearing close can justify a phone notification.

The agent can prepare a checklist and prefill known company details, but licensing declarations, experience claims and final submission remain controlled actions. That separation keeps speed without inventing eligibility.

Material prices move at different speeds. A supplier PDF, emailed price list and completed purchase can each describe a different point in time. Siteglass keeps those observations separate from the approved catalogue rate until the owner accepts the update.

When a change is approved, the system records the old value, new value, effective date and source. New estimates use the current approved rate, while old quotes retain the rate that was actually used when they were prepared.

The same history applies to labour. Changing the hourly sell rate should update future work and margin calculations without rewriting issued quotes or hiding the cost assumptions behind a completed job.

The quoting workspace should remain the source of the scope and protected totals. Once the owner releases the quote or the customer accepts it, a reviewed connector action can create the matching record in Xero with the tenant’s configured sales accounts and GST treatment.

Deposits, variations and paid status need explicit events. Each hand-off should keep the Siteglass quote identifier so an auditor can move from the accounting entry back to the estimate, approvals and document that produced it.

Automation removes double entry; it does not remove reconciliation. Exceptions such as a duplicate contact, unmapped account code or changed tax treatment should stop in a queue with enough context for a person to resolve them.