The four moments from the design-studio use case, walked through the actual product — the review inbox, the proposal frame, the record detail, the grid, the briefing. Nothing here is a mock-up of a screen Frontless does not have.
A new inquiry lands in your inbox. Forward it to Frontless and the lead joins your pipeline — with the budget hint, project type, and source captured, and a follow-up scheduled.
Actions your forwarded emails proposed that need your approval before they change anything. Everything else was filed or applied automatically.
dana.keller@strattonrobotics.comBrand identity — introduction via Brick & Mortar
New recordNew Opportunity — "Brand identity — wordmark, system, guidelines" for Stratton Robotics, stage inquiry, budget hint $40–60k, source referral (Brick & Mortar Co)
New recordNew Task — "Discovery call — Stratton Robotics", due Mar 12, assigned to Mara Ellison
Already applied
auto Filed the email and its signature block against Stratton Robotics — source: email.
auto Matched the referrer to Brick & Mortar Co, an existing client, at 94%.
A forwarded email never writes to your records on its own. Anything that would is queued here, under the email 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 email, the contract, the milestone and the question all landed on the same records. That is why the invoice knew its amount, the project knew its schedule, and the hours question had four engagements 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.