From the book · Unleash Your Business With AI
The Prompt Library
The 45 prompts from the back of the book, in one place, ready to copy.
1. Sort your week into three buckets
When to use it: you want to see which tasks AI should touch at all (Chapter 3).
Team: [roles]. What we do in a normal week: [rough list, no customer names or numbers] Put each task in one bucket: - Automate: same steps every time, low risk, no person needed on each case. - Assist: AI drafts, a person checks and decides. - Keep human: pricing, credit, tax, legal, hiring, key relationships. Never put a pricing, tax, legal or hiring decision in Automate. Give a table: Task | Bucket | Why. Then name three Assist tasks to start with. Ask me up to five questions first.
Check: move any task it has placed wrongly. Start with Assist.
2. Find the work that never gets done
When to use it: valuable jobs are skipped because nobody owns them.
What my team does in a normal week: [rough list, no customer names or numbers] 1. List tasks a business like mine should do regularly that are missing here, such as reviewing lost orders, reading customer reviews or checking slow-moving stock. 2. For each, say in two lines why it matters and whether AI could assist. 3. Rank them by likely value. Do not assume facts I have not given.
Check: give one missing task an owner.
3. Turn one chat into a one-page system
When to use it: an occasional AI task should run the same way every time (Chapter 1).
Task: [for example "replying to new retailer enquiries"] How it is done today: [the steps, in your own words] Who does it: [role]. Who checks it: [role]. Write a one-page system: when it starts, the numbered steps, where AI drafts and where a person decides, what is checked before sending, who owns it, and how we will know each week that it ran. Use only the steps I have described. Where a step is missing or unclear, write "QUESTION:" and ask me. Do not invent steps, prices or policies.
Check: the person who does the job corrects the page.
That's the first one
Open the rest, free
Enter your email once and every prompt page and guide on this site opens.
- 4. Your business note
- 5. The five-part brief
- 6. A first draft
- 7. Summarise and reply
- 8. Reply in the customer's language
- 9. Check my draft
- 10. Let AI interview you first
- 11. Turn a repeated task into a saved prompt
- 12. Structure a messy enquiry
- 13. First reply to a new enquiry
- 14. Questions to ask before you quote
- 15. Quotation from the price list
- 16. Five follow-ups, each with something useful
- 17. Hold the price
- 18. Prepare for an important call
- 19. Lost-deal review
- 20. Complaint reply: AI drafts, you decide
- 21. FAQ answer sheet
- 22. Marketplace listing from the facts sheet
- 23. What the reviews are telling you
- 24. Ask for an honest review
- 25. One product, ten captions
- 26. A month of content in one sitting
- 27. Four-line script for an owner reel
- 28. One video into ten posts
- 29. WhatsApp broadcast
- 30. Voice note to SOP
- 31. Meeting notes to action list
- 32. Daily report from an export
- 33. Ask your sales data a question
- 34. Slow-moving stock
- 35. Argue against me
- 36. Job post, screening questions and scorecard
- 37. Payment reminders
- 38. Personal data double-check
- 39. Where could this answer be wrong
- 40. Draft your team's AI rules
- 41. Correct a mistake that reached a customer
- 42. Weekly AI checkpoint
- 43. The 30-day decision
- 44. The AI map of your business
- 45. Review the year honestly
4. Your business note
When to use it: once, carefully. Then paste it into every chat (Chapter 5).
About my business. Use this in every answer in this chat. - Business name: [name] - What we sell: [products, price range, materials] - Who buys: [for example "retailers in tier-2 cities"] - Channels: [WhatsApp, marketplaces, retailers, distributors, showroom, website] - Our strengths: [only what is true] - Tone of voice: [for example "respectful, warm, direct"] - Languages our customers use: [list] - Things we never say or promise: [for example "no delivery date without checking stock, no discount beyond the price list"] - Person using this chat: [role] Rules for you: - If you do not know a fact about our products, ask me. Never invent specifications, prices, certifications or delivery times. - Write in plain English unless I ask for another language. - Keep drafts short enough to read on a phone.
Check: two senior people correct it. No customer data or confidential terms go in.
5. The five-part brief
When to use it: you are writing your own prompt (Chapter 6).
You are [role, for example "sales executive at a hardware wholesaler"]. Context: [the situation in two or three lines] Task: [exactly what you want written or done] Format: [for example "WhatsApp message, under 60 words, no emojis"] Example of my usual tone: "[paste a past message you liked]" Use only the facts I have given. If something you need is missing, ask me before you write.
Check: a generic answer means thin context. Add facts, not adjectives.
6. A first draft
When to use it: you face a blank screen.
Write a first draft of [document or message] for [audience]. Points to include: [list] Tone: [simple / formal / warm]. Length: [short / one page]. Use only the facts I have given. Mark anything you are unsure about with the word CHECK. Do not add prices, dates or promises I have not listed.
Check: resolve every CHECK before it goes anywhere.
7. Summarise and reply
When to use it: a long email, circular or thread needs an answer.
A message I received, with names and numbers removed: "[paste]" 1. Summarise it in three bullet points. 2. List anything I need to decide or do, with any date mentioned. 3. Draft a short reply that [accepts / declines / asks for more time / asks these questions: ...]. Do not add any commitment I have not stated. If something is unclear, say so instead of guessing.
Check: read the original yourself if money, a deadline or a legal point is involved.
8. Reply in the customer's language
When to use it: a customer writes in another language (Chapter 9).
A customer sent this message, with name and number removed: "[paste]" 1. Translate it into English. 2. My reply in English, already checked, is: "[your reply]" 3. Translate my reply into [language] in the polite, everyday form a respected shopkeeper in [region] would use. Keep product names, sizes, prices and dates exactly as written. 4. Translate your version back into English, literally. 5. List any phrase you were unsure about.
Check: the back-translation matches your meaning. A native speaker reads any template.
9. Check my draft
When to use it: you want a second pair of eyes on your own writing.
Check this [message / quotation / notice] before I send it: "[paste draft]" List spelling and grammar mistakes, unclear sentences, wrong tone, and anything that could confuse a customer or read as a promise I may not intend. Then give a corrected version that changes as little as possible. Do not change any number, date or name. If one looks wrong, flag it and leave it.
Check: compare its numbers with your original.
10. Let AI interview you first
When to use it: you cannot write the brief, but can answer questions (Chapter 20).
I need to [write a brief / plan a project / describe a small app I want built] about [topic]. Interview me before you write anything. Ask one question at a time. Cover who it is for, what it must achieve, what it must not do, what I already have, and what "done" looks like. If I say "I don't know", note it as an open point and move on. After at most ten questions, write a one-page brief using only my answers, with open points listed at the end. Do not fill gaps with assumptions.
Check: show the brief to the people who will use the result.
11. Turn a repeated task into a saved prompt
When to use it: a team member repeats one writing task daily (Chapter 25).
I work as a [role] at a [type of business]. Every day I have to [describe the repetitive writing task]. Help me write one reusable prompt for this task. - Put the details that change each time in [square brackets]. - Include a line telling the AI to use only the facts I give it and to write "CHECK" beside anything it is unsure of. - Include a reminder not to paste customer phone numbers, addresses or bank details. Then show me the prompt filled in with a made-up example, marked as an example.
Check: try it on a real case today, then add it to the shared library.
12. Structure a messy enquiry
When to use it: an enquiry arrives as voice notes and half-sentences (Chapter 7).
A new enquiry, with personal details removed: [paste the messages or your notes] 1. Extract: customer type, products, quantity, timeline, location, budget if mentioned, special requirements. Mark anything missing as "Unknown". 2. Rate it Hot, Warm or Cold with one line of reasoning. Hot means clear product, quantity and timeline. Cold means vague or price-shopping only. 3. Suggest the next action. Do not add anything that is not in the messages.
Check: log it in the enquiry sheet the same day.
13. First reply to a new enquiry
When to use it: a new enquiry needs a fast, useful first reply.
A new enquiry, with name and number removed: "[paste]" Our basics: [minimum order, delivery areas, usual dispatch time] Write a WhatsApp reply under 80 words that thanks them, answers what we can, asks no more than three short questions we need before quoting, and ends with one clear next step. No emojis. Do not mention any price, discount, stock position or delivery date I have not given you.
Check: a person reads and sends it. No promise you cannot keep.
14. Questions to ask before you quote
When to use it: a wrong quotation on a big order would cost margin.
A customer wants: [short description of the requirement] List the questions I should ask before I give a price, so I do not misquote or miss a hidden cost. Group them under product, quantity and packing, delivery, payment and credit, timeline. Mark the three most important. Then write one polite WhatsApp message under 70 words that asks only those. Do not suggest any price or terms.
Check: send one message with the questions, not five.
15. Quotation from the price list
When to use it: you have the requirement and today's price list.
Price list dated [date]: [paste only the relevant rows: item, unit, price, minimum order, GST rate] Standard terms: payment [terms]; delivery [terms]; freight [terms]; validity [days]. Customer requirement: [items, quantities, delivery city] 1. Prepare a quotation table: Item | Qty | Unit price | Total with GST. Show the calculation for each line below the table. 2. Use only prices from the list. If an item is not on it, write "PRICE TO CONFIRM" and do not guess. 3. Apply no discount. If the order may qualify for one, tell me in a separate note. 4. Add a short covering WhatsApp message. End with a list of what I must check before sending.
Check: every price against the list, every total in Excel, the delivery promise against stock.
16. Five follow-ups, each with something useful
When to use it: a quotation has gone out and the customer is quiet (Chapter 8).
We sent a quotation to [customer type] for [products] on [date]. No reply yet. True things that might help them decide: [for example "new stock has arrived"] Write five follow-ups: 1. Next day: confirm receipt and offer to answer questions. 2. A few days later: one useful piece of information from my list. 3. A week on: one direct, polite question about where they stand. 4. Two weeks on: close the loop and make it easy to say "not now". 5. Next month or season: something new. Each under 50 words, WhatsApp style. No false urgency, no guilt, no offer or deadline I have not given you.
Check: personalise each one and note the next follow-up date.
17. Hold the price
When to use it: a customer says you are too expensive (Chapter 10).
The customer said: "[paste the objection]" What we know: [for example "ours carries a warranty"] What I am allowed to offer: [for example "nothing on price; free freight above (order value)"] Write three replies, each under 60 words: 1. Value: why our price is what it is, using only my facts. 2. Question: ask what they are really comparing. 3. Option: an alternative within what I am allowed. No pressure tactics. No discount. Do not invent facts about competitors.
Check: you choose the reply and decide the terms.
18. Prepare for an important call
When to use it: you have ten minutes before a call with a large buyer.
I have a call with [customer type]. What I know about them: [past orders, what they asked, any concerns, no personal data] My goal for the call: [for example "a trial order of two items"] Give me: 1. Six questions to ask to understand their needs. 2. The three objections they are most likely to raise, with a calm, honest response to each. 3. What to offer and what not to offer on this call. 4. A one-line opening and a one-line close. Use only the facts I have given.
Check: strike out any offer you would not honour.
19. Lost-deal review
When to use it: once a month, on the enquiries marked lost.
Our lost enquiries for [month], with the stated reason and notes. Customer names are replaced with codes. [paste table] 1. Group the losses by real reason. Look past the stated one: "no reply" after a quotation may mean a slow quotation or a weak follow-up. 2. Count the enquiries in each group, from this data only. 3. Name the three changes to our sales process most likely to reduce losses. 4. List anything in the data that is unclear. Do not invent numbers.
Check: recount one group yourself. Try one change for a month.
20. Complaint reply: AI drafts, you decide
When to use it: a customer is upset about a delay, defect or service (Chapter 9).
Complaint, with personal details removed: "[paste]" What we know so far: [the facts, honestly] What I am authorised to offer: [for example "replacement after we receive photos"] Write a calm reply under 100 words in four parts: acknowledge the problem, state the facts, say what we will do, say when they will hear from us next. Do not promise a refund, replacement, compensation or deadline beyond what I have authorised. Do not admit legal liability or blame a third party. Then tell me anything risky in the message that I should handle personally.
Check: the owner or a named manager approves every complaint reply.
21. FAQ answer sheet
When to use it: your team answers the same questions in different ways.
Questions customers ask us often, with the rough answers my team gives today: [paste 10 to 20] For each, write a clear, friendly answer under 50 words that staff can copy and paste. Keep every fact exactly as given. If an answer is unclear or contradicts another, do not choose between them. Flag it. Give a table: Question | Approved answer | Notes.
Check: you settle every contradiction. Date the sheet.
22. Marketplace listing from the facts sheet
When to use it: you are writing or repairing a listing (Chapter 12).
Marketplace and category: [for example "Amazon, kitchen storage"] Category rules from the current style guide: [title format, character limits, bullet rules, restricted words] Product facts, the only source of truth: [paste the product's row from your facts sheet] Words customers search with: [list] Write a title in the category format and within its limit; five bullet points, each a short benefit followed by the fact that proves it; and a short description. Use only my facts. If a common specification is missing, write "MISSING:" and name it. No "best" or "No. 1", no certifications I have not listed, no competitor names. Finish with a checklist of every fact you used.
Check: verify each listed fact against the physical product and the current category rules.
23. What the reviews are telling you
When to use it: once a month, for your best-selling products.
Product: [name] Reviews from [marketplace], [period], reviewer names removed: [paste reviews with star ratings] 1. Group the complaints into themes. For each, count the reviews that mention it, from this data only, and quote two short phrases. 2. Do the same for praise. 3. Separate problems we can fix in the product, the packaging, the listing and delivery. 4. Suggest the five fixes most likely to matter. Do not invent reviews or counts. If a theme is unclear, say so.
Check: read the original reviews behind two or three themes before acting.
24. Ask for an honest review
When to use it: an order has reached a customer who bought directly (Chapter 23).
Write three short messages asking a customer who recently received [product] from [business name] to leave an honest review on [Google / our website]: one very short, one warmer, one formal. The same request goes to every customer, not only those we expect to be happy. Ask for an honest review, never a five-star one. Offer no reward of any kind. No emojis. Under 50 words each.
Check: on marketplaces, use only their own review-request tools. Never write a review yourself.
25. One product, ten captions
When to use it: one product photo must fill several channels (Chapter 14).
Product facts: [paste the product's row from your facts sheet] Write ten captions, each from a different angle: the problem it solves; who it is for; how it is made; gifting; a care tip; a comparison with what people use now; a question to the audience; [upcoming festival]; behind the scenes; one short line. Each under 60 words, with one clear call to action. No emojis. No claim, offer or statistic that is not in my facts.
Check: every claim traces back to the facts sheet.
26. A month of content in one sitting
When to use it: at the start of each month.
Month: [month and year]. Channels and frequency: [for example "Instagram four times a week"] Products to focus on: [list]. Real offers: [list, or "none"]. Moments this month: [festival season, sale period, launch] Customer questions we heard recently: [paste five to ten] Create a calendar table: Date | Channel and format | Topic and product | Call to action. Base every post on a fact, a customer question or an offer I have given. Do not invent offers, testimonials, statistics or festival dates. Then list what I need to shoot or collect.
Check: the owner confirms every offer and date before scheduling.
27. Four-line script for an owner reel
When to use it: you want to speak to camera without rambling (Chapter 15).
I am the owner and want to film a short talking reel about [topic]. The one thing viewers should learn: [message]. Facts I can use: [list] Write a four-line script: a hook that makes the right customer stop; the problem or surprising fact; the useful answer or proof; one clear call to action. Short, spoken sentences. Then give three alternative hooks. Use only my facts.
Check: read it aloud and change any line that does not sound like you.
28. One video into ten posts
When to use it: you have recorded a longer video, talk or podcast.
Transcript of a video I recorded about [topic]: [paste transcript] Create: 1. Three short reel ideas, each with the exact lines to cut and a hook. 2. Two carousel outlines of five to seven slides. 3. Two LinkedIn posts under 200 words each. 4. Three quote cards using lines I actually said. Use only what is in the transcript. Do not add facts, numbers or quotations I did not say.
Check: confirm each quote against the recording.
29. WhatsApp broadcast
When to use it: you have real news for people who agreed to hear from you (Chapter 13).
Audience: [for example "retailers who agreed to receive updates"] Purpose: [for example "announce the festive range"] Facts: [product and offer facts, and dates I have confirmed] Write one broadcast message under 80 words and a version under 40 words for WhatsApp status, each with one clear action. State the offer and terms exactly as given. No false urgency, no emojis, no claims I have not given you.
Check: send only to people who agreed, and not too often.
30. Voice note to SOP
When to use it: a process lives in one person's head (Chapter 16).
A transcript of [role] explaining how to [task]. It may be in mixed language and unstructured. Names are removed. [paste transcript] Turn it into a Standard Operating Procedure: title; purpose; who does it and how often; what is needed before starting; numbered steps with one action each; quality checks; common mistakes; who to ask if something goes wrong; a short checklist to print. Keep every detail the speaker mentioned. Where something is unclear or missing, write "QUESTION FOR [role]:" at that step. Do not fill gaps yourself. Use English a new joiner can follow.
Check: the person who does the job corrects it. A second person tests it.
31. Meeting notes to action list
When to use it: a meeting has just ended (Chapter 17).
Meeting: [topic], [date]. Attendees, roles only: [list] Notes, with personal and customer details removed: [paste] Give me a three-line summary; the decisions made; an action table with columns Action | Owner (role) | Deadline | Status; the open questions; and a version under 120 words for the team WhatsApp group. If an action has no owner or deadline in the notes, write "OWNER?" or "DATE?". Do not assign them yourself.
Check: fill every "OWNER?" and "DATE?" before posting.
32. Daily report from an export
When to use it: you want your morning numbers without opening the spreadsheet.
This is [report name], exported from [Tally / our system] on [date]. Customer details are removed. Columns: [list each column and what it means] [paste the data or attach the file] 1. Calculate with code or exact formulas, not estimation: [for example "total pending, pending over 30 days"]. 2. Show the method for each number. 3. Summarise in under 120 words: what changed, what needs action today, one question for the team. 4. List rows that look like errors. Do not round unless I ask. Do not guess any missing value.
Check: match one or two totals against the source every day.
33. Ask your sales data a question
When to use it: you have a sales export and questions (Chapter 18).
A cleaned sales export for [period], with no customer personal data. Columns: [list and explain] [paste the data or attach the file] First report the number of rows and the grand total of [amount column], so I can match them with my books. Then answer: 1. [for example "Which ten products had the highest net sales?"] 2. [your second question] 3. [your own question] Calculate with code or exact formulas. Show the method and the Excel formula I could use to check each answer. If the data looks wrong or incomplete, tell me.
Check: row count and grand total must match Tally. If not, stop.
34. Slow-moving stock
When to use it: before a season or at month-end.
Our stock report exported on [date]. Columns: [for example "item, category, quantity, value at cost, last sale date, quantity sold in the last 90 days"] [paste the data or attach the file] 1. Using exact calculations, list items with no sales in the last [number] days, and items where stock is more than [number] times the last 90 days' sales. 2. Total their value at cost, by category. 3. Suggest ways to clear them, such as bundles, retailer schemes or stopping reorders, with the risk of each. 4. Show your method. Do not suggest prices. What to clear, and at what price, is my decision.
Check: confirm the top five in Excel before acting.
35. Argue against me
When to use it: before a new product line, hire, city or large purchase.
Decision I am considering: [describe it] My reasons: [list] What I know about the costs and risks: [list] 1. Give the five best reasons not to do it. 2. Imagine it is a year later and the decision failed. Give the five most likely reasons. 3. For each, suggest one low-cost way to test or reduce the risk first. 4. List the three questions I should answer with real data before deciding. Be direct. Do not invent market facts, and do not tell me what to decide.
Check: answer the data questions from your own books. You decide.
36. Job post, screening questions and scorecard
When to use it: you are hiring (Chapter 19).
I am hiring a [role] in [city]. Day-to-day work: [list]. Must-have skills: [list]. Salary range: [range, or "do not mention"]. Days and hours: [details]. Write: 1. A job post under 200 words. 2. Six screening questions that test real job skills, two of them practical, with what a strong answer looks like. 3. A scorecard for the must-have skills, describing a 1, a 3 and a 5. Keep everything job-related. Nothing about age, gender, religion, caste, marital status or family plans.
Check: same scorecard for everyone, no CVs pasted. AI never shortlists or rejects.
37. Payment reminders
When to use it: an invoice is due or overdue and the relationship matters.
An invoice for [amount] dated [date] was due on [date]. Relationship: [for example "good retailer, usually pays a week late"] Write three reminders, each under 50 words: a friendly one on the due date; a firm but polite one after [number] days; a request for a call to agree a payment date. Do not mention legal action, interest or penalties. I will add those myself.
Check: confirm the amount and due date against your books.
38. Personal data double-check
When to use it: you have already cleaned a chat export or notes (Chapter 21).
I have removed personal data from the text below. Check it again. List anything left that could identify a person: names, phone numbers, addresses, email IDs, GST or PAN numbers, bank or UPI details, order IDs linked to a person. Do not repeat any sensitive item in full. Show only its first two characters followed by asterisks, and the line where it appears. Text: [paste the cleaned text]
Check: this is the second check. Remove obvious details yourself first.
39. Where could this answer be wrong
When to use it: you are about to act on something AI told you (Chapter 22).
Look again at the answer you just gave me. 1. For each fact, number, date, name or rule in it, say where it came from: my data, a document I gave you, or your own general knowledge. 2. Mark every item from your own general knowledge as UNVERIFIED. 3. List the weak points or possible errors, starting with the one that would cost me most if wrong. 4. Name the three items I should check first, and where. Do not defend the answer. If you are not sure, say so plainly.
Check: recalculate key numbers. Confirm rules and rates with the official source or your CA.
40. Draft your team's AI rules
When to use it: staff use AI and nobody has said what is allowed (Chapter 24).
Draft a one-page AI use policy for my team, in plain English. Approved tools: [list]. AI owner: [role]. Our never-paste list: [paste] Cover, in order: approved tools; what is never pasted; cleaning data first; a person checks everything before it goes to a customer, supplier or portal; AI never decides prices, discounts, delivery dates, refunds, credit, legal or tax matters, or hiring; AI images show the product as it ships; real people appear only with written consent; no fake reviews; what to do when AI gets something wrong; who to ask. End with a line for name, role, signature and date. Mark anything I must decide with "OWNER TO DECIDE".
Check: a working draft, not legal advice. Read it to the team and have everyone sign.
41. Correct a mistake that reached a customer
When to use it: a wrong price, date or fact has gone out.
A message we sent to a customer contained an error. Personal details are removed. What we sent: "[paste]" What was wrong: [the fact]. The correct position: [the fact]. What I am authorised to offer, if anything: [for example "nothing beyond the correction"] Write a calm correction under 80 words: say what was wrong, give the correct information, apologise once and state the next step. No excuses. Do not offer anything I have not authorised or admit legal liability. Then write two lines for our mistakes register: what went wrong, and which check would have caught it.
Check: the owner approves the correction. Fix the process, not the person.
42. Weekly AI checkpoint
When to use it: every week, with the AI owner (Chapter 25).
This week's notes on how we used AI in the business, with no customer data: - Uses that ran: [list] - Problems: [list] - This week's numbers: [paste] - Last week's numbers: [paste] 1. Summarise the week in five lines. 2. List the top three problems. For each, say whether the fix is a prompt change, a process change or training. 3. State the change in each number from last week, and show the working. 4. Suggest one focus for next week. Use only what I have written. If something is missing, ask me. Do not guess.
Check: recalculate the changes yourself. The decision is yours.
43. The 30-day decision
When to use it: on day 30, with your scorecard filled in.
My scorecard after 30 days of using AI in my business: [paste your scores, your answers and your notes, with no customer data] Act as a practical business adviser. 1. Name the three uses I should keep and make standard, and why. 2. Name the uses to fix or drop, and why. 3. Suggest one area to go deeper on next month, with four weekly steps. Base every point on what I have written. Do not assume results I have not reported.
Check: write down what you decide and share it.
44. The AI map of your business
When to use it: your first system runs and you are choosing the next (Chapter 26).
Team: [roles]. Main pain points now: [for example "quotations are slow, nobody reads reviews"] 1. List the recurring tasks in each department: sales, customer service, marketing, marketplaces, operations, team, accounts. 2. Put each in one bucket: Automate, Assist or Human. Never put pricing, legal, tax, hiring or key relationship conversations in Automate. 3. Give each a priority from 1 to 3, where 1 means it touches money, happens weekly, is done badly today and is easy to check. Give a table: Department and task | Bucket | Priority | Why. Then name my top five priority-1 tasks and which to start with. Ask me up to five questions first.
Check: correct the map with your managers. Pick one system.
45. Review the year honestly
When to use it: at year-end, after answering the ten questions in Chapter 27.
My written answers to the ten year-end review questions, with no customer personal data: [paste the questions and your answers] Act as an experienced adviser who wants this business to do well and does not flatter. 1. Ask me up to seven follow-up questions, one at a time, where my answers are vague, contradict each other or avoid the hard part. 2. Then summarise what I have said into three priorities for 2027. 3. List anything I claimed without evidence. Use only what I tell you. Do not invent figures, market facts or trends. Do not tell me what to decide.
Check: verify the listed claims in Tally or Excel before planning around them.
Prompts for each chapter
Every chapter has its own page.
