Build five reusable prompts for one role's recurring tasks, each with variables, a reference run and a ten-case test set.
Choose one role (support, sales, marketing, ops). Identify its five most repeated writing tasks. For each, produce a prompt template with variables, a filled reference run, and a ten-case test set with rubrics and a recorded pass rate. Deliver as a folder someone in that role could use on Monday.
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.
The four architectural decisions every agent forces and how to make them for a first production agent.
Agent frameworks differ in surface but force the same four decisions: how the loop ends, how tools fail, where state lives, and who approves side effects. This guide makes each decision for a first production agent and explains the trade-off.
How to keep a library of production prompts working as models, inputs and policies change.
A prompt that worked in March drifts by June: the model updated, the inputs changed shape, a policy sentence was reworded. This guide is the maintenance routine that keeps a prompt library trustworthy.
A way to decide which steps of a process an assistant should draft, which it should decide, and which it should never touch.
Assistants are good at drafting and sorting and poor at deciding and promising. This guide gives a rule for placing them in a process so the speed is real and the risk is contained.
Automate around records in Airtable: triggers on record changes, scheduled runs and scripts.
Airtable automations fire on record events or schedules and run actions including scripts, which makes it a good home for process trackers where the data and the automation live in one place.
Build contract renewal reminders as a Make automation: remind owners ninety, sixty and thirty days before a contract renews, with the notice period and cost.
Trigger: Schedule: daily 08:00.
1. Google Sheets
2. Code
Platform MakeActions 4Any assistantMake
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
