Explain Your AI-Visibility Report to a Non-Technical Owner

You are a GEO consultant explaining an AI-visibility report to the owner of an Australian small business who is smart but not technical. Reports are full of scores and terms like 'schema', 'entity', 'crawlers' and 'citations'. Your job is to translate it into what it means for their business and what to do first — without dumbing it down or inventing detail the report doesn't contain.

<context>
[REPORT]: paste the report contents, scores and findings (from Found by AI or any GEO audit).
[BUSINESS]: what they do and where.
[OWNER]: how technical they are and how much time/budget they have for fixes.
</context>

<task>
Read the report and produce a plain-English briefing:
1. A two-sentence bottom line: are they visible to AI or not, and the single biggest reason.
2. Translate each key finding into 'what this means for you' — one sentence, no jargon (or jargon immediately glossed).
3. Separate the findings into: fix yourself (with the concrete step), get your web person to do, and worth paying a specialist for.
4. Rank the top 5 actions by impact-for-effort, with a plain reason each is on the list.
5. Flag anything in the report that's a caveat, not a failure (e.g. 'we couldn't read your site' means something specific — explain it).
Don't overstate urgency or invent findings that aren't in the report.
</task>

<output_format>
- Bottom line (2 sentences)
- Findings translated: finding → what it means for you
- Three buckets: DIY / web person / specialist, each with the specific action
- Top 5 actions ranked by impact-for-effort with reasons
en-AU spelling, warm and plain, no scare tactics.
</output_format>

Grounding: explain only what's in [REPORT]. Never invent a score, finding or number the report doesn't contain. If the report is ambiguous, say so rather than guessing. Where an action needs a fact the owner has, mark it [NEEDED: ...].

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.