Filing a generated document to the record automatically

A document the system generates had to be handed over for a person to upload by hand, because sending the file through the tooling cost too much. That turned out to be a fact about typefaces rather than about documents. The skill builds a one page executive summary from what the customer said on the […]

In this series · Part 19 of 22

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

A document the system generates had to be handed over for a person to upload by hand, because sending the file through the tooling cost too much. That turned out to be a fact about typefaces rather than about documents.

  • The skill builds a one page executive summary from what the customer said on the discovery call, quoting them rather than summarising, and files the PDF onto their record itself.
  • The earlier measurement put a single page at roughly 178,000 tokens, which is what ruled this out. Re-measuring showed the cost is driven by how many typefaces are embedded, not by length. One page using a single family came in at 232 kilobytes against 521 for one using eleven.
  • The size check now runs at the moment of upload rather than sitting in the documentation as a claim. Over the limit, the file is handed over and the number reported.
  • The generator can refuse. The field holding the customer's own cost figure accepts anything, and on one record it held a number identical to that company's revenue. Reading that field and printing it produces a confident wrong document, so an implausible value stops the run.