# Contractor Storm Offer Stack Scorecard

Score each area from 0–5 before launching a storm page or website offer.

| Area | Score | Pass condition |
| --- | --- | --- |
| Storm offer framing | ___ / 5 | Names the exact storm service, city/service-area context, buyer hesitation, proof asset, and next step. |
| Quote CTA promise | ___ / 5 | Explains what happens after submit, what details are needed, and when to call instead. |
| Response expectation | ___ / 5 | Uses response windows, urgency, and handoff language the team can actually support. |
| Inspection request | ___ / 5 | Focuses on documentation, photos, scope, safety, and next steps without implying insurance approval. |
| Proof package | ___ / 5 | Combines photos, captions, reviews/testimonials, city proof, permission status, and repair outcomes. |
| Insurance clarity | ___ / 5 | Separates what the contractor documents, what the owner controls, and what claims the page must not make. |
| Website conversion routing | ___ / 5 | Uses Webzaz only when the offer belongs across service pages, city pages, landing pages, galleries, FAQs, quote forms, and website trust. |

## Product-fit guardrail

Webzaz fits website structure. LocalKit, QR/profile routes, review/referral routes, emergency call routing, estimate follow-up, AI answering, scheduling, dispatch, and no-show controls stay separate.

## Owner growth route

- Use this scorecard to turn storm offer clarity into qualified quote intent, not broad storm traffic.
- If offer clarity is weak, route the owner into the landing page brief, page proof checklist, local SEO proof, or website proof map before launch.
- Preserve `primary_source=storm_offer_stack_scorecard` through scorecard download, proof route, landing-page brief, and Webzaz-fit website conversion requests.
- Webzaz belongs only when the scorecard reveals a website structure, service/city page, quote-form trust, gallery proof, or landing-page hierarchy gap. Keep LocalKit/profile, dispatch, scheduling, CRM, AI answering, review/referral, and claim workflows separate.