Deliverable factories

Build-along · ~12 min at your own keyboard

The graduation move: one trigger fans into the full document set. A closed job becomes the invoice, the client summary, the file-away record, and the review-request draft — one input, four deliverables, one review pass by you.

The long version: One input, many documents ↗

Do this

0/4

Checkpoints

▸You should now see a named trigger event and a list of documents it should produce.
▸You should now see every document saved in one review folder with consistent names.
▸You should now see a time for the run next to your time for doing it by hand.

The three ways this goes wrong

Some documents are missing from the folder. — Check the list against the directive. Each output needs its own step.
File names differ from run to run. — Write the naming pattern into the directive, such as client_doc_date.
You send the files without reading them. — Keep the review folder step. Open each file once before it leaves.

Share what happened

Paste the trigger, the output list, and your time comparison.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.