Company details that every document reads

Company name, address, phone, email, website, logo, brand colour and portal tagline are stored once and auto-populate every contract, invoice and customer page.

What it is

The Business Info form writes to the same per-tenant settings row that has always fed the invoice header, the builder tokens in contract templates, and the customer-portal branding. Moving the editing UI here changed where it is edited, not where it is stored.

Also called: company name on invoices · builder info · contract header details

See it
Company details that every document reads
Prepared for
Ronan Petsch
1140 Ridge Line Rd · Fair Play
Shell package$26,623
Concrete & site$7,729
Doors & windows$5,153
Trim & finish$3,435
Total
$42,940
Signature
The Business Info card with company fields and the inline Saved dot, next to a rendered invoice header using the same values. Sample data — no customer information appears here.
How it works
  1. 1Fields save individually on blur; a Save Business Info button commits the whole form.
  2. 2Everything lands on the tenant's invoice_settings row.
  3. 3Contract templates read the same values through their builder tokens; the portal reads them for branding.
Why we built it

The tab's own comment describes the plumbing decision as deliberate: keeping the storage single-source means 'every document keeps reading the same truth' after the UI moved. Splitting storage would have reintroduced the class of bug where the invoice header and the contract header disagree.

The problem
  • Company facts were duplicated per document type and drifted apart.
Sound familiar?
What you get
One edit propagates to contracts, invoices and the customer portal.
No document can carry a different version of the company's own details.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →