One letter, one overrun, one invoice that bills the extra.
The four moments from the consulting 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.
You email an engagement letter to a prospect. BCC Frontless and the engagement lands in your pipeline — fee, phases, budgeted hours and follow-up all extracted.
Actions your forwarded emails proposed that need your approval before they change anything. Everything else was filed or applied automatically.
elena@northbridgeadvisory.ieEngagement letter — network redesign, 12 weeks
New recordNew Engagement letter — "Halcyon Network Redesign — 12 weeks" for Halcyon Logistics, stage proposal sent, fee €96,000.00 fixed, 400 budgeted hours across 4 phases
New recordNew Task — "Chase the Halcyon letter", due Jan 15, assigned to Elena Vasquez
Already applied
auto Filed the engagement letter PDF against Halcyon Logistics — source: email.
auto Read the fee schedule as four phases — €32,000, €24,000, €24,000 and €16,000 — and attached them to the proposed letter.
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 letter, the timesheets, the phase sign-off and the rate-card question all landed on the same records. That is why the burn finding knew each phase’s budget, the invoice knew which hours were billable, and the earned-per-hour answer had a year of fees and hours to divide — nothing was re-keyed between them.
Nothing was written without you approving it first.
The overrun you absorb and the extra you bill are told apart, in writing.
Frontless proposed. You disposed. Both are in the audit log.