44 lines
3.7 KiB
Markdown
44 lines
3.7 KiB
Markdown
# Case Study: Emergency Plumbing (Tampa)
|
|
URL: https://bizl.com/case-studies/emergency-plumbing
|
|
Extracted: 2026-08-09
|
|
|
|
## Core Messaging / Positioning
|
|
- Hero: "**From zero AI presence to owning emergency plumber Tampa in 67 days**."
|
|
- Vertical hook: "Here are some top-rated emergency plumbers in Tampa" (implied local AI listing).
|
|
- Situation: "A 24/7 emergency plumber that AI engines did not even know existed" — "This Tampa plumbing company had been in business for **18 years** with a strong reputation in the area. When emergencies hit at 2 a.m., locals called them. But the next generation of customers were asking ChatGPT for an emergency plumber, and the company was nowhere to be found."
|
|
- Execution: "A step-by-step plan our team executed while the owner ran the business" — "From the day the business signed up for **Stay Found**, our team handled everything."
|
|
- Result headline: "**Score went from 21 to 70. Calls tripled. In 90 days.**" (Note: hero says "67 days," headline says "90 days" — timeline inconsistency on page.)
|
|
|
|
## Key Claims & Stats
|
|
- This Tampa company: **18 years in business**, strong local reputation, yet "nowhere to be found" for AI emergency-plumbing searches.
|
|
- **Score: 21 → 70** (dashboard, 90 days after starting Stay Found).
|
|
- "**Calls tripled. In 90 days.**"
|
|
- **Timeline mismatch**: hero headline "67 days"; results block "90 days."
|
|
- Testimonial (owner): "The calls have roughly tripled and I did not touch a computer."
|
|
- Methods caveat: "Every number below is from the business's Bizl dashboard, 90 days after starting Stay Found." — self-reported dashboard figures, no independent verification (Tier-3).
|
|
- Product/service line named: **Stay Found**.
|
|
|
|
## Offer / Pricing Details (if applicable)
|
|
- No pricing on page. Free audit CTA: "Takes 4 minutes. Our team handles everything after."
|
|
- Product line named: **Stay Found**.
|
|
|
|
## Process / How It Works
|
|
- Free audit finds the AI gap → "step-by-step plan our team executed while the owner ran the business" → dashboard-tracked 90-day Stay Found window.
|
|
- Fully done-for-you: "Bizl handles all of it. I just answer the phone and show up."
|
|
|
|
## Notable Strengths or Patterns
|
|
- **Urgent-demand vertical** (emergency/2 a.m.): emotional weight of missing calls in an emergency.
|
|
- **Tech-aversion persona**: owner "I am a plumber, not a marketer. I do not have time to learn schema or whatever it is called." Blue-collar relatability.
|
|
- "Did not touch a computer" = fully done-for-you labor-removal message.
|
|
- "Beyond the numbers" qual section alongside quant headline.
|
|
- Dashboard numbers + 90-day window lend veneer of precision.
|
|
|
|
## Notes for Digital Operations Partner
|
|
- **Silent Customer Loss**: Compelling discovery-failure story — a reputable business financially bleeding emergency calls it never knew it was losing. DOP's central wedge; DOP should prove the loss with measured pre/post call data, not anecdote.
|
|
- **Evidence quality**: Score (21→70) and "calls tripled" sourced only to Bizl dashboard (Tier-3, n=1, self-reported). "Tripled" is survey-level; no baseline call volume shown. DOP can supply verified metrics and clear definitions.
|
|
- **Timeline inconsistency** (67 vs 90 days) is a minor credibility slip on the page worth noting; DOP's measured reporting should be internally consistent.
|
|
- **Human supervision vs black-box**: Black-box "handles all of it — I did not touch a computer" is sold as a benefit; DOP = human-supervised + agent-assisted where the owner understands and approves. Transparency differentiates.
|
|
- **PoC-style entry**: free audit ("Takes 4 minutes") mirrors DOP Cold Audit → PoC → Retainer.
|
|
- **Conversion patterns**: urgent-demand framing, tech-aversion persona, labor-removal ("did not touch a computer"), dashboard numbers, quick-audit CTA.
|
|
<!-- structured: 3770 chars, flags: 3 -->
|