The one-page brief format that lets a designer or writer produce assets without a meeting, and what each section is for.
A brief exists so that someone else can make the assets correctly the first time. Most briefs are either a paragraph of hope or a deck nobody reads. This guide sets out a one-page format where every section answers a question the maker would otherwise have to ask.
How to produce listing images that show the real product clearly, consistently, and in the formats marketplaces want.
Listing images decide whether a buyer reads the rest. This guide covers the two cases a store meets — screenshots of digital products and photographs of physical ones — with the rules that keep every image honest, consistent and usable across platforms.
Build help article suggestion on ticket close as a n8n automation: when a ticket closes, suggest the help article that would have answered it, and log the gap if none exists.
Trigger: Help desk ticket status changes to closed.
Use feed validation tools to catch listing data errors before a marketplace or ad platform rejects the feed.
Marketplaces and shopping ads ingest a product feed — a file of titles, prices, availability, images and identifiers — and reject items with missing or malformed fields; a validator checks the feed against the platform's rules before submission so rejections are fixed in bulk rather than one email at a time.
Use feed validation tools to catch listing data errors before a marketplace or ad platform rejects the feed.
Marketplaces and shopping ads ingest a product feed — a file of titles, prices, availability, images and identifiers — and reject items with missing or malformed fields; a validator checks the feed against the platform's rules before submission so rejections are fixed in bulk rather than one email at a time.
Read a CRM export and list deals with no activity for a set number of days, sorted by value, with a suggested action column.
Stalled deals hide in a long pipeline list; a script over the weekly export surfaces them in seconds with the last note attached so the next action is obvious.
A small function that turns a model's classification into a routing decision with an explicit threshold and escalation list.
Routing on a model's category without a confidence threshold sends uncertain tickets to the wrong queue; the rule belongs in code where it can be tested.
Build back-in-stock notification as a Zapier automation: when a product's stock goes from zero to positive, email the customers who asked to be notified, once.
Trigger: Inventory sheet row updated where stock changed from 0 to above 0.
Take one manual process from map to live automation with error handling, a manual fallback and a measured saving.
Choose a recurring process. Map it from three real examples, build the automation one block at a time, add error routing and idempotency, test three samples and one deliberate failure, and run it live for two weeks with a log of runs, failures and time saved.
Write a two-page guide for your team on what your chosen assistant does well, where it fails, and the rules for using it, with every claim tested by you.
Produce a two-page internal guide for a real team: what the assistant is, three tasks it does well with evidence from your own tests, three ways it fails with examples you produced, and five rules for use. The guide must not contain a claim you did not test yourself.
What an evaluation run must show before an agent is released or updated.
An agent update without an evaluation is a guess deployed to users.
☐ A fixed test set of thirty or more inputs including refuse cases
☐ Expected outputs or a rubric per case
Items 10ClaudeChatGPT
Instant delivery after paymentLicence stated on every productRe-download anytime from My LibrarySecure checkout — Polar or FungiesNew products every week
Instant delivery after paymentLicence stated on every productRe-download anytime from My LibrarySecure checkout — Polar or FungiesNew products every week