Seventy Nine Minutes

The communication problem

A fixed price offer promises a quote within two hours of the call. That promise is easy to make and hard to keep, because the slow part is never the arithmetic. It is writing the thing up, checking it, building somewhere for it to live, and making a way to pay that actually works. Most studios answer with a follow up email saying a proposal is coming, which is how a decision made in the room cools off by the time anything arrives.

The design approach

Make the quote a built artifact rather than a letter, and generate it. The engine takes the call notes and produces one page on the site, a PDF with the signature, and pay links, from a single specification file. Inside those minutes the draft also went through a four lens review, of which thirty four of thirty six findings were applied, and a policy check caught a set of links that would have let someone pay for everything at once in a way the refund terms could not support. Those links came out before the quote went anywhere.

The work

One private page, a nine page PDF and working pay links, sent seventy nine minutes after the call ended, inside a promise of two hours.

• Call ended 11:30 AM. Quote in the inbox at 12:49 PM. Seventy nine minutes against a two hour promise.
• Three separate Launches presented on one page, each with its own pay link rather than a single total.
• A four lens review ran on the draft before it was sent, and thirty four of its thirty six findings were applied.
• A refund policy check removed the pay for everything at once links, because the terms could not support them.
• The page was opened on a phone before the link was sent.
• The whole thing comes out of one specification file, so the next quote is a file rather than an evening.
• The quote page is private and carries a no index rule. It is not reachable from the site.