Lead packs · checklist
How to Identify Businesses With Outdated Websites Responsibly
A responsible research framework for recognizing observable website needs without insulting a business or treating design taste as qualification.
Direct answer
Record observable website conditions that affect users or operations, separate observation from inference, and never treat a dated design alone as proof the business wants to buy.
Define an observable signal
Examples include broken mobile navigation, insecure forms, contradictory contact information, or a site that no longer represents the business. Taste-based judgments (“ugly”) are weak qualification.
- Functional breakage
- Contradictory NAP or offers
- Missing critical paths
- Security or form failures
Separate observation from inference
Record what was seen and why it may matter. Do not assume budget or claim the website caused unverified business problems.
- Observed condition
- Potential user impact
- Research date
Use the data with restraint
Relevant, truthful, low-volume outreach is different from blasting. Follow applicable privacy and channel rules. A visible website gap is still only an opportunity proxy.
- No insulting openers
- No invented revenue claims
- Honor suppression
Next step
Combine this checklist with an industry pack, size quantity to capacity, and keep outreach language aligned to opportunity-proxy rules.
Apply the framework carefully
This article explains a general decision framework. Validate it against your own market, site, customers, systems, data, capacity, contractual commitments, and any applicable legal or professional requirements.