# Report template

Fill this in. Keep sentences short. Lead every point with what it means for the
reader. Delete any section that would be empty rather than padding it.

---

# {App name}, in plain English — and where it could get better
*A second opinion on {scope: the whole app / the competitor-tracking system / …}*

**How to read this:** no technical background needed. Part 1 is the summary — if
you read nothing else, read that. Parts 2–3 go area by area for anyone who wants
detail.

## Part 1 — The short version

**What you have.** {2–3 sentences: what the product does, who uses it.}

**The headline.** {3–5 bullets, one plain line each — the biggest risks and
opportunities. No jargon.}

**If it were me, this is the order I'd tackle things:**

| Fix | Why it matters to you | Effort | Payoff |
|---|---|---|---|
| {…} | {business impact} | Small/Medium/Large | High/Medium/Low |

---

## Part 2 — Area by area

### {Area name, in business terms — e.g. "Competitor tracking"}

**What this does.** {the capability, as the business experiences it}

**How it works today.** {a plain walkthrough — a small story beats a diagram}

**What's working.** {genuine credit — the parts that are solid and worth keeping}

**What's holding you back.**
- **{Problem in plain terms}.** What it means for you: {business impact}.
  Severity: {Minor / Worth fixing / Serious / Urgent}. Effort to fix: {Small /
  Medium / Large}.

**How I'd do it differently — and why it's worth it.** {the better design in
outcomes: more reliable / faster to change / cheaper / safer / easier to hand
off. Say whether it's a cheap rewire or an expensive rebuild.}

{repeat per area}

### The technology bets

{One entry per significant choice — framework, sign-in, hosting, database, key
libraries — AND anything a rebuild would move them ONTO. Each gets both sides.}

**{Technology}.**
- *Buys you:* {in business terms}
- *Costs you:* {in business terms — bills, hiring, shipping speed, upgrade work,
  the risk of betting on something young. Don't soften it. If it hasn't shipped a
  stable 1.0, say so and say what that means: pin the version, budget upgrades.}
- *Usually:* {recommendation tied to their stage — normally "keep it, watch this"}

{The same bar applies to anything you're recommending they move to. A stack you
propose with no cons listed is a pitch, not a second opinion.}

---

## Part 3 — The fine print (optional)

**How confident am I.** {where you're certain vs guessing; what you'd verify
against real data before committing}

**A few words explained.** {glossary — only terms that couldn't be avoided}