From sent to accepted

The record

One row, already written

Ledgerline Capital Inc. is a row your rep filled in weeks ago: the company, Dana Whitcombe as signatory, the Meridian Verify package, the reference and the dates the quote holds for. Nobody retypes the name on page three and nobody re-dates the cover by hand.

The rate card is not a field on the row. It is set once in the design, so a change to the $0.006 per call is one edit that reaches every quote, while the fields that differ per buyer arrive with the row.

The row is the agreement between your data and the page. The recipient, the package, the reference and both dates are derived rather than authored, so a proposal cannot quietly name a different company than the record it came from.

Arrives from your CRM, from a spreadsheet, or over the API. The shape of your table does not have to change first.

The page

The same values, in the document's voice

One design, bound once to the deal record. Ledgerline Capital Inc. gets a proposal at an address of its own, and its name, its reference and the date it holds until are the row's, filled in rather than retyped.

Every other open opportunity is treated the same way by the same design. What changes between them is the data, which is why a correction to the rate card is one edit rather than forty.

The reading

Dana reads it, and two things follow

She opens the link on a phone during the meeting and again on a laptop that evening. Four minutes and eighteen seconds of that reading sits on the rate card, which is the sort of thing a sent attachment can never tell you.

She leaves one question against the 7-day payment terms. You answer it where she asked it, or you publish a second version from the same design, and the link she already has carries the newer one.

The version she read first is not overwritten. It stays retrievable at the revision she saw, so a later disagreement about what was offered has a document behind it rather than two people's memories. A month on, both sides open the same address and find the same two versions in the same order.

The outcome

Accepted, on 19 August

The page Dana agreed to is the record of what was agreed, still at the address she read it at, carrying the rates that were on screen at the moment she said yes. It also lays out what follows: an invoice against the $1,200 commitment, sandbox keys with the $250 credit applied, then live keys.

Nothing has to be exported for the file. The history holds what moved between the first send and the acceptance, and who was reading when it moved, so a renewal conversation twelve months out starts from evidence rather than recollection.

The address keeps working after the deal closes. Finance opens it, the customer opens it, and nobody circulates a fifth copy of a file that was already the wrong version by the time it was attached. The link is the artifact, and it needs no custodian to keep it current or to settle which copy was the real one.

A proposal closes on one word. The workflow below closes on a different one and reaches it a different way.