Websites first · Benchmark intelligence · Selective partner access
We build fast websites. Our benchmark system supports that. Sometimes, we share a slice.
Primary: performance-focused websites and landing pages for service businesses.
Secondary: a Florida website-performance benchmark layer we use internally and publish in the Florida Web Performance Index — so decisions stay grounded in observed speed, structure, and public signals.
Tertiary: for select B2B partners, we offer filtered, case-by-case access to parts of that dataset: documented exports built from public business information, public website observations, and benchmark signals — scoped to what you need, not a public marketplace and not a consumer profile product.
This is a side offering, not our core business. We do not position exports as permission to email, call, or text anyone — channel rules are yours to satisfy. We scope columns, filters, and row counts in writing before moving forward.
Who this is for
B2B teams that need benchmark-informed context — we take engagements selectively and define delivery together.
Vertical and regional context aligned with the same benchmark definitions we publish — for strategy, pitches, and client planning.
Competitive density, performance bands, and public-site signals in the metros you care about — scoped by industry and geography, not bulk lists.
Market framing from aggregated or bucketed benchmark signals derived from public websites — not harvested consumer data.
Coverage and methodology consistent with our public index and research pages, so your citations stay aligned with ours.
How agencies use partner benchmark data
Practical B2B patterns we see — not guaranteed playbooks. All use cases assume you treat the export as company intelligence from public and observed signals, then apply your own legal and channel standards.
Some agencies use filtered company intelligence to spot businesses where public signals suggest active or recent paid advertising alongside weak mobile performance, slow load behavior, or thin landing-page structure — a starting point for positioning better sites or landing experiences.
This is not a promise of conversion lift or ad outcomes, and it does not grant outreach rights. How you contact businesses — and whether you may — remains your compliance responsibility.
When a business shows public review / reputation signals but no site we treat as meaningfully benchmarkable, a review-rich no-website stack can support conversations about web presence, listings, or partnerships — framed as company-level context, not consumer data.
We do not position this as permission to blast outreach or as a substitute for lawful marketing rules in your channel.
For teams that need a broader map of accounts that clear a quality floor — websites present and not scoring poorly in our banding — the market coverage stacksupports territory views and account planning rather than “broken site” urgency lists.
Density and composition vary by market; we quote available rows against your slice before you commit.
What's included
Exact columns depend on scope. Below is the category menu we can draw from — not a guarantee of every field for every row.
- Filter dimensions agreed in advance: state, metro / city, industry (including mapped clusters), score bands, confidence cuts, and other benchmark flags.
- Formats: CSV / Parquet for analysis teams; optional aggregate-only views where that fits the use case.
- Written data dictionary: definitions, known limitations, and refresh cadence.
- Metrics aligned with the public index where you need comparability.
- On request: scheduled refresh windows, retained historical snapshots when available, and NDA-governed custom fields.
Internal opaque ID, city, state, industry labels, lat/lng at metro precision (no street addresses in standard exports).
Public website URL or domain, match confidence label, benchmarkable flag, exclusion flags where applicable.
Mobile PageSpeed-style score, load time / LCP proxies, snapshot timestamps (when enriched).
Public review counts and ratings where published, plus ads-running signals from our benchmark pipeline — framed for market and competitive context, not as an outreach mandate.
Boolean / categorical signals from public pages: analytics tags, pixels, schema, CMS hints — tied to the matched business website, not consumer profiles or health data.
Partner benchmark data — published pricing bands
These are limited-release slices of filtered company intelligence: businesses scoped by market, website quality, benchmark signals, and recent observations from our pipeline — not a generic outreach database. Industry sets the base price; metro-targeted slices add 15% to the amounts below. Town-level, exclusive, or highly filtered scopes are custom quote. Field categories are summarized under What's included.
For businesses with websites, using strong benchmark and website-observation filters — for example ad-running or not, performance score, load time, contact fields, review signals, on-site observations, and social presence where available.
| Industry | 100 records | 100 · metro (+15%) | 500 records | 500 · metro (+15%) |
|---|---|---|---|---|
| Service | $1,000 | $1,150 | $2,000 | $2,300 |
| Medical | $1,500 | $1,750 | $3,000 | $3,500 |
| Lawyers | $1,750–$2,500 | $2,000–$2,900 | $3,500–$5,000 | $4,000–$5,750 |
500-record full-intelligence pricing is structured as 2× the 100-record base for Service and Medical; Lawyers use the stated bands.
For review-rich businesses with no meaningful web presence — Google reviews / reputation signals without a site we treat as benchmarkable.
| Industry | 500 records | 500 · metro (+15%) |
|---|---|---|
| Service | $1,000 | $1,150 |
| Medical | $1,500 | $1,750 |
| Lawyers | $2,000 | $2,300 |
Market coverage stack: businesses that have websites and do not score poorly — a broader account-mapping / coverage view, not a weak-site urgency slice.
| Industry | 500 records | 500 · metro (+15%) |
|---|---|---|
| Service | $750 | $850 |
| Medical | $1,000 | $1,150 |
| Lawyers | $1,500 | $1,750 |
Town, exclusive, and highly filtered slices are scoped case by case. Premium legal and specialty medical niches may price above the standard bands. Custom delivery and tighter territorial limits are quoted separately. Use custom quote for: town-level slices, exclusive territory, highly filtered universes, premium legal sub-niches, premium private-pay medical niches, ad-runners-only ultra-tight slices, high-confidence-only or special delivery requirements.
Freshness standard: relevant fields are rechecked within 21 days of sale so you receive recent observations, not a stale pull.
Distribution: we do not sell the same defined slice to more than one agency. We also limit partner agencies per area so slices stay defensible — filtered company intelligence, not commodity lists.
Evaluation records (before a full slice): Service 3, Medical 2, Lawyers 1.
Delivery & fulfillment
Partner exports are prepared manually against an agreed written slice — not an instant self-serve download.
What you receive
- A defined slice: filters, column set, match-confidence rules, and how we counted rows — in writing before delivery.
- The file itself: default UTF-8 CSV (opens cleanly in Excel or Sheets); Parquet available when your team prefers it.
- A data dictionary for the columns in your export, aligned with the same concepts we use in public methodology where applicable.
Masked sample vs paid delivery
The public masked sample is synthetic structure only — safe to share internally. Paid delivery is built to your agreed filters from our live benchmark index, not copied from the demo file.
Recheck before handoff
For standard partner sales we re-run qualifying checks against recent observations so row counts and key flags still match the slice spec — typically within 21 days of sale. Ongoing or near-real-time feeds are only when explicitly contracted.
What we do and do not guarantee
- We guarantee delivery to the written spec and honest reporting of universe size for those rules at quote time.
- We do not guarantee that every row carries every optional field (enrichment can fail per site), that third-party sites stay unchanged after delivery, or any business outcome from your analysis or outreach.
Limited-release slices & custom scopes
Published bands describe common slices; we still release selectively and respect distribution rules for defined slices. Town-level, exclusive, highly filtered, or premium-niche scopes are quoted and documented case by case — including any non-standard geography or column package.
Invoicing and file transfer details are confirmed after scope approval. We keep this lightweight — no partner dashboard required.
What we need from you to quote fast
No long form — send the same details through our normal contact page. The more of the list below you cover in one message, the faster we can return universe size and price alignment.
- Industry / vertical: Service trades, Medical, Lawyers, or another mapped cluster — we price and filter against our published industry sets.
- Geography: State plus metro, city, or region you need. Standard vs metro-targeted bands reference this.
- Slice type: Full website intelligence, review-rich no-website, or market coverage — match the band you’re considering.
- Standard vs metro vs custom band: Published pricing assumes standard or metro (+15%). Town, exclusivity, or tight filters → custom quote.
- Approximate record target: e.g. 100 vs 500 where bands apply, or “evaluation sample then full pull.”
- Urgency: Rough timeline so we can sequence prep and recheck windows honestly.
- Exclusivity or custom requirements: Territory lock, column limits, aggregate-only delivery, NDA — say it up front to avoid rework.
Optional: use the quick chips in the next section to prefill slice, tier, industry, record target, exclusivity, and timeline — then add any nuance in the message body.
Request or quote — signal what you need
Pick a preset to prefill slice type, geography band, and (where relevant) row target. Layer industry, metros, exclusivity, and urgency using the quick chips — or write it all in the message body. For a full structured partner request (company type, slice options, acknowledgments), use the dedicated request form — it hands off to the same contact step with your answers pre-filled.
Quick chips (merge with presets)
Timeline (optional)
Each chip sets a partial prefill. For the fullest automated prefix, start from a preset row above (slice + tier + rows), then add anything missing in the message — or write the full spec manually.
We confirm fit and check distribution rules (we do not sell the same defined slice to more than one agency; partner density per area is limited).
We reply with available universe size for your filters, column options, and next steps. Custom slices — town-level, exclusive, highly filtered, premium legal or medical niches, or special delivery — are quoted case by case.
Fastest scoping: industry vertical, metro/region, slice type (from the published bands), standard vs metro tier, 100 vs 500 where relevant, and whether you need evaluation records before a full pull.
Open contact formHow records are built
Plain-language version of the pipeline we use to inform website and performance work. Partner exports use the same concepts; we agree which stages and confidence cuts apply so counts stay honest.
- 1
Tracked
Businesses retained in the index with stable internal identity, geography, and industry assignment. Counts align with public “tracked” totals where we publish them.
- 2
Observed on the public site
Public website URL and page-level observations where the site was successfully read — for example tech tags, schema hints, CMS patterns. No paywalled or login-gated content.
- 3
Enriched
Lab performance runs (e.g. mobile score, load-time proxies) when the pipeline successfully benchmarks the matched URL. Not every tracked row is enriched on every run.
- 4
Confidence-qualified
Website match confidence (e.g. high / medium / low / manual review). Public headline figures often use medium-or-better matches so denominators stay defensible. Partners can request tighter cuts when it makes sense.
Coverage & freshness
Snapshot from the same public stats we use on marketing pages — server cache refresh (typically on the order of hours). Last refresh: Mar 21, 2026.
Tracked businesses
3,586,173
Industries (rows)
277
Cities represented
23,134
Records touched (30d)
0
With website URL
0
Public site observations
0
Performance-enriched (reported)
2,487,085
Enriched + medium+ match
2,487,085
Avg mobile (medium+)
57.1
% below 70 (qualified mobile)
0%
Target scale (roadmap)
50,000
“Target scale” is a public roadmap cap — not current coverage. Partner scopes are quoted against available rows when we agree to proceed.
Masked sample — what a delivery can resemble
Download a synthetic, masked CSV (three rows) to see column headers and the shape of partner benchmark exports — fictional domains and ids only, safe for sharing internally. Paid slices are always filter-specific to your scope and rechecked against recent observations before delivery (standard: within 21 days of sale), so counts and cells match the agreement — not this static demo file.
Same data as the table below. UTF-8 CSV; open in Excel, Sheets, or your stack.
Preview (synthetic rows)
| record id | city | state | industry | website | match confidence | mobile score | load sec | ads running | review bucket |
|---|---|---|---|---|---|---|---|---|---|
| fl_••••9a2f | Jacksonville | FL | HVAC | cool***air.example | high | 44 | 4.8 | true | 120–199 |
| fl_••••3c81 | Tampa | FL | Roofing | roof***pro.example | medium | 58 | 3.1 | false | 20–49 |
| fl_••••e710 | Miami | FL | Legal | law***grp.example | high | 72 | 2.4 | true | 200+ |
How to read these columns
- record_idInternal-style opaque id (masked here). Live slices use stable ids tied to our index.
- city / statePublic geography at city + state. Standard exports avoid street-level precision.
- industryMapped industry or cluster label used for filtering and reporting.
- websitePublic domain or URL pattern (masked in this file). Match quality matters for benchmark rows.
- match_confidenceHow confidently the URL maps to the business (e.g. high / medium). Partners often choose a minimum cut.
- mobile_score / load_secLab-style performance snapshot when enrichment succeeded — same family of signals as our public index.
- ads_runningObserved signal from our pipeline (not a guarantee of current ad spend).
- review_bucketBanded public review volume for context — not a consumer profile.
Methodology & trust
We document how the flagship index is built — discovery, benchmarking, and limitations. Partner deliveries include a written slice spec that uses the same definitions so figures stay comparable to our research and the public index.
Terms of engagement
How this works
- Every partner export is scoped case by case — we confirm fit, filters, and delivery format before you commit.
- Slices are limited-release; we do not treat benchmark exports as an open catalog. Some territories or premium niches may require custom pricing.
- Paid files are prepared to your written scope, then rechecked before handoff so what you receive matches what we quoted.
- You remain responsible for lawful use and for channel rules (email, phone, SMS, privacy, sector-specific duties). We do not sell patient records or consumer profile products; exports are company and public-signal intelligence from our benchmark pipeline.
Responsible use
Data is provided for business intelligence and benchmarking. It reflects public business and company context, public website observations, and performance and benchmark signals from our pipeline — not patient data or consumer profile products.
You are responsible for lawful use, including how you choose to use contact or identity fields if present, and for compliance with rules that apply to your channels and sector — for example email, telephone, text messaging, privacy, and any industry-specific obligations. We do not represent that a purchase grants consent for outreach or that any channel is “safe by default.”
Start with what we actually sell
Our core work is websites and performance. If a scoped benchmark export would help your team, tell us your organization, geography, industries, and whether you need row-level or aggregate delivery. We'll reply with universe size, column options, and next steps — typically within two business days.