One proposal, four channels, five invoices in one pass.
The four moments from the marketing-agency use case, walked through the actual product — the review inbox, the record detail, the briefing, a chat answer, the proposal frame. Nothing here is a mock-up of a screen Frontless does not have.
Actions your forwarded emails proposed that need your approval before they change anything. Everything else was filed or applied automatically.
priya@halyardagency.comProposal — demand generation, six months
New recordNew Engagement — "Demand generation — 6-month outcome-based" for Stratton Robotics, stage proposal sent, value $90,000.00, outcome target "200 qualified MQLs/month by month 6"
New recordNew Task — "Chase the Stratton proposal", due Mar 12, assigned to Priya Raman
Already applied
auto Filed the proposal PDF against Stratton Robotics — source: email.
auto Read the fee schedule as $15,000.00 × 6 months and stored it on the engagement.
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 proposal, the channel numbers, the month’s billing and the hit-rate question all landed on the same records. That is why the invoice knew its fee, the briefing knew what was promised, and the hit-rate answer had four engagements to read from — nothing was re-keyed between them.
Nothing was written without you approving it first.
Measurement and judgment are marked differently, on purpose.
Frontless proposed. You disposed. Both are in the audit log.