# Contractor Storm Landing Page Brief

Use this before writing a storm landing page. Pick one storm service landing page, emergency storm landing page, city storm landing page, insurance-process landing page, before-and-after landing page, review/testimonial proof landing page, or Webzaz-fit conversion route.

## Page decision

- Page type:
- Service:
- City/service area:
- Buyer hesitation:
- Proof asset:
- CTA:
- Response expectation:

## Proof rules

- Photo proof:
- Review/testimonial proof:
- Insurance-process clarity:
- City proof:
- Before-and-after set:
- Permission status:

## Do not publish if

- The city proof is fake or thin.
- The insurance language implies claim approval or payout.
- The emergency page promises arrival times operations cannot support.
- The page is a product pitch without proof.

## Product fit

- Webzaz fits when the landing page needs service pages, city pages, galleries, FAQs, quote forms, and website trust.
- LocalKit, QR/profile routes, emergency routing, estimate follow-up, AI answering, scheduling, dispatch, and no-show controls stay separate.


## 2026-05-09 20:00 ET growth-route QA

- Added `storm-landing-page-brief-growth-route` so the public artifact names the owner growth route, source-preserved measurement fields, human keyword target, and Webzaz/LocalKit boundaries.
- Webzaz is relevant only for website proof, forms, service/city pages, galleries, quote CTA trust, and storm landing-page conversion. LocalKit/profile, reviews/referrals, CRM, dispatch, scheduling, AI answering, no-show, follow-up, and claim workflows stay separate.