One quote, one absence, one invoice — on the same records.
The four moments from the construction use case, walked through the actual product — the review inbox, the briefing and the drafts it proposes, the proposal frame, the record detail, the grid. Nothing here is a mock-up of a screen Frontless does not have.
New recordNew Bid — "Kitchen + dining remodel" for Foster Construction, stage quote sent, value $48,000.00, scope read from the quote body
New recordNew Task — "Chase the Marlow Road quote", due Mar 12, assigned to Dana Whitfield
Already applied
auto Filed the quote PDF against Foster Construction — source: email.
auto Matched Foster Construction to an existing client at 99% — one live job already open.
A BCC’d email never writes to your records on its own. Anything that would is queued here, under the message it came from.
Fixed data, real surfaces. The proposal, answer and confirmation frames are the
product’s own components; the briefing, grid and record detail are read-only twins of
theirs, built from the same markup. space plays and pauses, ←→ step.
Four moments, one spine.
The quote, the absence, the milestone and the question all landed on the same records. That is why the invoice knew its amount, the schedule knew which jobs cared, and the materials question had twelve months of your own history to answer from — nothing was re-keyed between them.
Nothing was written without you approving it first.
Every value carries where it came from — an email, a document, a rule, or your own hand.
Frontless proposed. You disposed. Both are in the audit log.