See My Business Through a Customer's Eyes

1. 1

   Language and tone

   Shared

   Keeps the answer clear, positive and understandable. It prevents the AI from hiding simple ideas behind jargon or presenting useful criticism as a fault-finding exercise.

   language-and-tone.partial

   1

   Write in clear, unambiguous, plain English.

   2

   Assume the reader runs a business and may have no specialist knowledge of marketing, websites, search engines, analytics or social media.

   3

   Do not use jargon when an ordinary word or short phrase will do.

   4

   If a technical or specialist term is genuinely necessary, use the term, explain it immediately in plain English, explain why it matters here, and provide a reliable reference confirming the meaning.

   5

   Keep the framing positive, balanced and constructive.

   6

   Where something is working, say so before describing the issue or risk that remains.

   7

   Do not soften a serious issue so much that it becomes unclear.

   8

   The aim is to eliminate ambiguity and create clarity.

2. 2

   Evidence and certainty

   Shared

   Stops the AI from presenting guesses as facts. It makes the report show what was actually found, what is a reasonable interpretation, and what could not be confirmed.

   evidence-and-certainty.partial

   1

   Use publicly available information you can actually find.

   2

   For important factual claims, provide the source used to confirm them.

   3

   Clearly distinguish between Observed, Inferred and Not verified.

   4

   Never present an inference as a confirmed fact.

   5

   Do not invent missing information.

   6

   Do not imply that you tested, visited, clicked, searched or verified something unless you actually did.

   7

   Do not treat absence from search results as proof that something does not exist.

3. 3

   Source hierarchy

   Shared

   Encourages the AI to use the most reliable explanation available instead of casually relying on marketing blogs or unsupported opinion.

   source-hierarchy.partial

   1

   Prefer references in this order:

   2

   1. Official provider or platform documentation where the subject relates to a specific service or product.

   3

   2. A recognised neutral reference such as Wikipedia for general concepts.

   4

   3. Another authoritative source only when the first two are not suitable.

4. 4

   Define the customer and their goal

   Gives the review a concrete task instead of asking vaguely whether the business has a good customer experience.

   customer-scenario.partial

   1

   Create a realistic customer scenario in which the customer is trying to: [CUSTOMER GOAL].

   2

   The customer begins here: [STARTING POINT].

   3

   Base the scenario on the public information available.

   4

   Do not invent sensitive personal characteristics or an unnecessarily detailed persona.

5. 5

   I need something — what do I do first?

   Starts with the customer's problem rather than with the business's website.

   need-and-search.partial

   1

   Begin from the customer's need and follow the most plausible route to discovering [BUSINESS NAME].

   2

   Note what search terms, listings, recommendations or channels may reasonably be involved.

6. 6

   First encounter with the business

   Captures what a new customer understands and feels they still need to know.

   first-contact.partial

   1

   Describe what is immediately clear, what creates confidence, what is unclear and what questions remain.

7. 7

   Can I get the information I need?

   Checks whether the customer can answer the practical questions that affect their decision.

   research-phase.partial

   1

   Look for likely questions about services, prices where relevant, availability, location, opening hours, process, suitability, policies, examples of work and contact methods.

   2

   Only judge information as missing where it is reasonably relevant to a [TYPE OF BUSINESS].

8. 8

   Do I feel confident enough to proceed?

   Looks at the evidence a customer may use to decide whether the business feels credible.

   trust-phase.partial

   1

   Identify the specific public signals that increase or reduce confidence.

   2

   Avoid vague statements about trust where there is no observable basis.

9. 9

   Can I take the next step easily?

   Tests the practical route to calling, messaging, booking, visiting or buying.

   action-phase.partial

   1

   Follow the intended action without submitting forms, making bookings or contacting the business.

   2

   Note unnecessary steps, unclear choices or missing expectations.

10. 10

    What happens next?

    Checks whether the customer knows what to expect after making contact or booking.

    after-action-expectation.partial

    1

    Look for public information explaining response times, confirmations, preparation, arrival, collection, delivery or other relevant next steps.

    2

    Do not penalise the business for information that would only reasonably appear after a transaction.

11. 11

    Where did I have to work too hard?

    Collects the points where the customer had to search, guess, repeat or switch channels unnecessarily.

    friction-log.partial

    1

    List meaningful points of friction in journey order.

    2

    Distinguish inconvenience from actual blockers.

12. 12

    What was unexpectedly good?

    Captures useful positive moments worth protecting or building on.

    delight.partial

    1

    Identify anything unusually clear, reassuring, convenient, personal or useful in the journey.

13. 13

    Finding format

    Shared

    Gives every finding the same useful structure. The reader sees what is already working, what may need attention, the evidence, why it matters and exactly what can be done next.

    positive-finding-format.partial

    1

    Report each finding using these headings, in this order:

    2

    - Finding: A short plain-English description of the issue or opportunity.

    3

    - Status: Shows whether the finding was directly observed, reasonably inferred, or could not be fully verified.

    4

    - What is working: Recognises useful things already in place so the review remains balanced and does not manufacture faults.

    5

    - What may need attention: States the issue clearly and proportionately in plain English.

    6

    - Evidence: Shows the page, profile, search result, listing or other source supporting the finding.

    7

    - Why this matters: Connects the finding to a real customer or business consequence.

    8

    - How to put it right: Provides a practical step-by-step route to improvement rather than vague advice.

    9

    - References for the fix: Provides reliable guidance supporting the recommended process.

    10

    - Effort: Uses Small, Moderate or Larger to give a rough sense of the work involved without inventing precise cost or time estimates.

14. 14

    Recommendation discipline

    Shared

    Prevents the AI from defaulting to rebuilds, subscriptions or fashionable tools when a smaller change would solve the problem.

    recommendation-discipline.partial

    1

    Prefer simple, realistic improvements over large projects.

    2

    Fix or improve what already exists before recommending replacement.

    3

    Do not recommend a paid product, subscription, redesign, rebuild or new platform simply because one exists.

    4

    Keep recommendations proportionate to the business and the evidence found.

    5

    Do not create an exhaustive improvement list when a smaller set of meaningful actions will do.

15. 15

    Three changes that would improve this journey

    Ends with the smallest meaningful changes rather than a complete redesign of the business.

    three-changes.partial

    1

    Recommend three proportionate improvements tied directly to observed customer friction.

    2

    Preserve the things that already work.

16. 16

    Action prioritisation

    Shared

    Turns a long analysis into a small number of useful next steps. You should finish knowing what to do first, not merely knowing what is wrong.

    action-prioritisation.partial

    1

    Finish with the three actions most worth considering first.

    2

    For each action include what to do, why it comes before the other findings, the first practical step, and the best supporting reference.

    3

    Prefer small, realistic improvements where they can produce a meaningful result.

17. 17

    Something useful I learned

    Shared

    Adds the quiet educational layer. Instead of delivering a lecture, the prompt explains one useful marketing, customer-experience or technology concept that arose naturally from the work.

    teaching-note.partial

    1

    Briefly explain one marketing, customer-experience or technology concept that arose naturally from this review.

    2

    Explain what it means, why it matters to this particular business, and provide one reliable place to learn more.

    3

    Keep this short and practical.

    4

    Do not turn the report into a lesson.

18. 18

    Research boundaries

    Shared

    Defines what the AI must not do. It keeps a broad review from quietly becoming security testing, legal advice, invasive research or an unrelated technical audit.

    research-boundaries.partial

    1

    Stay within the stated purpose of this prompt.

    2

    If something deserves deeper investigation, identify it, explain why it may matter, and recommend the appropriate deeper review instead of attempting that entire review here.

    3

    Do not perform vulnerability scanning, penetration testing, endpoint probing, login attempts or other security testing.

    4

    Do not submit forms, make bookings, place orders, contact the business or change anything.

    5

    Do not claim legal or regulatory compliance or non-compliance from a broad review.

    6

    Do not guess private information such as revenue, profitability, customer numbers, budgets, internal systems, staffing or business plans.

    7

    Do not infer motives, competence or intentions of owners, staff, agencies or competitors.

19. 19

    Limits of this particular prompt

    The boundaries that apply to this prompt specifically, on top of the general research limits.

    scope-notes.partial

    1

    Do not pretend to complete transactions, bookings or contact forms.

    2

    Do not invent emotional reactions unsupported by the public experience.

    3

    Do not build a fictional demographic persona unless explicitly asked for one.

SharedSections marked shared are the same in every prompt in the library. The rules on tone, evidence, recommendations and limits are deliberately identical wherever you meet them, so you only have to learn them once — and so no prompt can quietly hold itself to a lower standard than the others.