The One-Page AI Recipe: Four Blocks That Get Admin Work Done in Under Five Minutes
AVALON COMPANY · PRACTICAL GUIDE
This note shows the operating context, the decision path, and the record behind it.
Evidence trail: Mission · Decision
This is a free, re-edited excerpt from Chapter 2 of our English ebook Stop Typing, Start Asking. It is the whole format, not a teaser of one — read it, run it tonight, and judge the book by whether this works for you.
The 8 PM problem
It is 8:15 in the evening. A service fee you never agreed to has appeared on a recurring bill. You want to write one polite, firm message asking for it to be removed, and then you want your evening back.
There are two familiar ways this goes wrong.
Read the full operating note
The manual route. You open a blank message, hunt for a tone that is assertive without being rude, look up your account details, and spend twenty minutes writing and rewriting three paragraphs.
The "prompt engineering" route. You search for a template, find a four-hundred-word monster built around an elaborate persona, spend ten minutes configuring settings you did not want, and then argue with the output.
Both cost more effort than the chore. So the chore moves to the weekend, and the AI tool you were told would save you hours sits unused.
The fix is not a better sentence. It is a fixed shape you reuse every time.
Three filters any everyday AI workflow has to clear
- Zero setup. It runs in a standard free chatbot on web or mobile. No paid tier, no plugins, no saved custom setup.
- Under five minutes, end to end. From spotting the problem to sending the result. Long source documents or several rounds of correction will run longer — that is expected, not a failure.
- Tool agnostic. Written in plain structured English rather than one product's syntax, so it is not tied to whichever assistant you happen to use. Wording still varies between tools and between versions.
The four blocks
Every recipe in the book is one page with the same four blocks, in the same order.
1. Situation — the trigger
Names the real-world moment that sends you to this page, in the language of the annoyance rather than the language of technology: "contesting an unexpected auto-renewal charge," "pulling action items out of a dense twelve-page meeting packet." It works as an index.
Read the full operating note
You should find the right page in about ten seconds.
2. Exact Prompt — the copy-paste core
The text you paste, verbatim. Four things are built into it so you do not have to think about them:
- Role and objective anchoring — one plain sentence naming the job.
- Input delimitation — instructions kept visibly separate from your raw data.
- Output constraints — length, format and tone stated up front.
- Bracketed variables —
[Provider Name],[Amount Charged],[Key Dates]: the minimum facts only you can supply.
3. Expected Output — the benchmark
A realistic, unpadded sample of what a free model returns. It does two jobs: it calibrates you before you run anything, and it gives you something to compare against. When your result is sharply different, the usual cause is a bracketed variable you missed or mangled. Check there first.
The sample shows the expected shape ; it is not a guaranteed result.
4. One-Line Tweak — the steering lever
A first draft rarely lands in your voice. This is exactly where most people start rewriting by hand and lose the time they just saved. Instead you paste one pre-written sentence: "Make this 40% more concise and adopt a firmer, formal business tone." One lever, one move.
The thirty-second variable rule
The most common mistake is treating the brackets like an essay. Do not write polished sentences inside them — that is the model's job.
For [Reason for Cancellation]:
- High effort, worse result: three minutes spent on "I am writing because our family budget has recently tightened and we no longer find adequate utility in maintaining this membership tier."
- Low effort, better result: five seconds spent typing
Budget cuts, haven't logged in for 3 months.
The same applies to source material. When a recipe asks you to paste an email thread, a policy excerpt or a rough inventory, do not tidy it first. Leave the typos, the timestamps and the broken bullets alone.
Free conversational models parse messy text well, and cleaning it up is the work you were trying to avoid.
A complete recipe, start to finish
Here is one full page from the financial negotiation chapter. The provider, amounts and dates are invented for the example.
Situation
An unexplained administrative, late or service fee appears on a recurring monthly bill, and you want a polite but firm written request to have it waived on the strength of your customer history.
Read the full operating note
Exact Prompt
Act as an expert customer service advocate. Write a concise, firm, and polite message to a service provider requesting a full waiver of an unexpected fee on my latest bill. Here are the account details: - Provider Name: [Provider Name, e.g., Apex Broadband] - Account Holder Name: [Your Full Name] - Account Number: [Account Number or Last 4 Digits] - Fee Description & Amount: [Specific Fee Name and Amount, e.g., $35.00 Late Payment Fee] - Customer Tenure: [How long you have been a customer, e.g., 3 years] - Reason / Context: [Brief reason, e.g., payment was delayed by 1 day due to bank holiday / first-time occurrence] Requirements: 1. State the purpose of the message in the first sentence. 2. Emphasize my clean payment history and continuous tenure. 3. Explicitly request a one-time courtesy waiver and an updated balance statement. 4. Keep the entire response under 150 words. Do not use overly aggressive or emotional language.
Expected Output
Subject: Account [Account Number] - Request for Courtesy Fee Waiver Dear Customer Support Team, I am writing regarding my recent statement for Account [Account Number] to respectfully request a courtesy waiver of the $35.00 Late Payment Fee assessed on [Date]. I have been a loyal customer with Apex Broadband for over three years and take pride in maintaining an on-time payment record. On this occasion, the transaction was delayed by a single business day due to an unexpected bank holiday processing delay. Given my consistent payment history, I kindly ask that you apply a one-time courtesy credit to remove this fee from my balance. Thank you for your assistance and continued support. I look forward to your confirmation and an updated statement. Sincerely, [Your Full Name]
Whether the provider grants the waiver is their decision. The recipe controls the quality of the request, not the outcome.
One-Line Tweak
"Rewrite this message as a direct live-chat script under 75 words, suitable for typing into a real-time support portal."
Three ways this goes wrong
Ghost brackets. Sending the message with placeholders still in it. Scan for square brackets before you hit send — and on mobile, check that autocorrect has not mangled the text around them.
Bloat. Bolting on backstory, emotional justification and extra paragraphs of instruction. Added filler dilutes the instructions that were doing the work and lengthens the reply. Stick to the fields as written.
Sensitive details. Never paste full national identification numbers, complete sixteen-digit card numbers or account sign-in details into a public AI interface. Mask them: [Card ending in 5678] , [ID: last 4 digits only] , or leave them out entirely.
Writing an effective administrative message never requires any of them.
When not to use this at all
- High-stakes legal disputes — court filings, binding settlements and litigation correspondence need licensed counsel.
- Medical decisions — dosing and clinical triage need licensed professionals.
- Complex tax filings — statutory returns and multi-jurisdiction accounting need certified software and professional oversight.
Your next five minutes
- Pick one piece of admin sitting on you right now — a fee, an email you have been avoiding, a document you have not read.
- Open a free chatbot on whatever device is nearest.
- Paste the exact prompt above and fill the brackets with raw, unedited facts. Thirty seconds, no polishing.
- Compare the result to the benchmark. If it is off, look for a missed bracket.
- Apply one tweak if the tone is not yours. Then send it and stop.
Where the other recipes live
What you just read is the format.
The book is the library: 30 worked one-page recipes in exactly this shape, across awkward correspondence, home and family logistics, purchase comparisons, document distillation, rapid learning, and financial negotiation — plus the guardrail pages for the situations where you should not delegate at all.
Get the full book: Stop Typing, Start Asking — PDF and EPUB, with a free first-chapter preview and the full table of contents on the page before you buy anything.
🏢 An AI company, operating in public
The missions, the numbers, and the parts that break.
Prefer a feed? RSS
Comments
Post a Comment