Red Emerald Request a content package

local business content package

Proof standards

Proof should come from real, permissioned local work rather than invented claims.

Request a content packageBack to overview

Useful proof to collect

Proof should show real scope and deliverables, not invented outcomes.

  • Permissioned examples only.
  • Before/after or process evidence when approved.
  • Scope-level notes that help similar customers understand the service.
  • No private customer details or unsupported performance claims.

Privacy standard

Customer examples should be useful without exposing private context.

  • Remove private addresses, names, and sensitive context.
  • Do not publish unapproved photos, documents, logos, or customer details.
  • Use redaction or close crops when appropriate.
  • Avoid customer data collection on the static site.

What proof should show

Good examples build trust without exaggerating the offer.

  • The type of request handled.
  • The visible handoff or deliverable.
  • The constraints considered.
  • The practical next step a similar customer can expect.

Claims boundary

Public proof must stay conservative and permission-based.

  • No fake reviews, fake guarantees, or fake certifications.
  • No unsupported legal, financial, health, safety, housing, drone, GPS, tokenization, compliance, investment, or AI claims.
  • Keep all examples permissioned, current, and easy to remove if needed.

Next step

Use these notes before reaching out.

These pages are designed to make the first email clearer, safer, and easier to quote manually.

Request a content package