Prospecting Bucket Taxonomy
Every prospect gets one lead bucket, and the lead bucket decides the finding, the email and the fix SC offers. It is derived, not chosen: the caller ticks every bucket the evidence supports and the lead is the highest-ranked tick.
This document defines the buckets and the rank order. The desk-research procedure that gathers the evidence is the Prospect Bucket Slotting Checklist; the caller is who records the result, at call prep, in Execution SOP, Reading the audit.
This sits above the cadence, not beside it. Touch structure, stop rules, tags, and the ICP screen are unchanged and live in the outreach cadence SOP. The taxonomy changes only which finding leads.
Why buckets
The Review Response Play collapsed every prospect onto one finding: unanswered Google reviews. That is the right instinct and the wrong scope. It is excellent for a business with forty reviews and no replies. For a business with one review it is absurd, and the play knows it, which is why it set a review floor and sent the operator away with no alternative. (That floor is now 15, not three, and the play routes anyone under it to Bucket 1 rather than rejecting them — this sentence described the original behaviour and outlived it.)
That disqualification was throwing away good prospects. A well-rated business with almost no reviews is not a weak lead. It is the strongest lead SC has, because the gap is enormous, the prospect can confirm it in ten seconds, and the fix is cheap and fast. Buckets exist so that prospect gets an offer instead of a rejection.
One bucket per prospect, recorded on the contact, is also the only way to learn which offer works. Five findings mixed across one batch produce an unreadable result.
Bucket choice and offer eligibility are two questions, not one. This document decides which finding leads. Whether a prospect can be offered Results-First is decided by the seven gates in the offer §5, placed at the point each can actually be answered by the Prospect Qualification Standard. A prospect can slot B1 and fail the offer's gate 3 — Talarico, the worked example below, does exactly that. Both answers are correct.
The gate
Before any of this: the prospect card's AI conversion score must be above 60%. That is the agent's own estimate, read off the card in Marketing > Prospecting before the report is opened. Below it, park the prospect and spend the time on a better one.
Do not confuse this with the audit report's Overall Score. Different number, opposite meaning. The card score estimates whether they will convert. The report score measures how healthy their online presence is, and a low report score means more to sell, not less. Talarico scores 44% on the report and is a first-rate prospect.
Disqualifiers
Checked first, in the report and on the live profile. Any hit stops the prospect. These are additions to the Audit Accuracy SOP red flags, not a replacement.
| Disqualifier | Why |
|---|---|
| The audit resolved the wrong business | GBP, Reputation and geo-scoped SEO are all void. Log wrong-business and flag the report |
| Permanently closed, or the site is down | Nothing to sell |
| Marketing agency, web designer, or CRM consultant | Competitor |
| Already an SC client or an open lead | Check before every send |
| Outside the ICP screen | Revenue, headcount, vertical, deal value, authority |
| No Google Business Profile at all, and no path to one | Four of the five buckets depend on it |
Before a Results-First call: the pre-dial list
Every cold call now carries the Results-First offer, so the caller also checks these before dialling. Any hit means: tick disqualified on its own, note which line it failed, and do not dial.
| Do not call when | Why |
|---|---|
| Rating below 4.0 | More reviews can make the profile worse, and SC does not sell reputation repair |
| Fewer than 10 Google reviews | Demand unproven (offer gate 3). Review-engine still applies from 10 to 14 |
| More than 150 Google reviews | Office staff answer every call, and a review tool is likely in place |
| 3 or more new reviews in the last 60 days | Their own pace would meet the offer's review trigger without SC |
| No new review in the last 90 days | Business in decline |
| Another company's call-tracking number or review widget on the site | They have it, and probably a contract |
| A franchise or chain branch without local buying authority | Cannot say yes |
The over-150 and fast-reviewing lines mean "not now", not "never". They are good businesses on standard terms.
Florida, Ohio and Pennsylvania are not on this list on purpose. A record from those states should never reach a caller. If one does, it is a configuration fault: do not dial, and flag it.
The decision tree
Tick every line that is true; the highest one leads. Walk the tree top to bottom and tick each bucket whose trigger is satisfied — most prospects satisfy more than one, and each extra tick is another thing the caller can raise when the first does not land. Do not weigh which problem is "worse". The order already encodes that judgement, and re-litigating it per prospect is what makes slotting inconsistent between two people.
The rank is the order below, and it is no longer visible in the stored values. The live field dropped the B1- to B5- prefixes on 2026-10-30, so review-engine no longer announces that it outranks no-booking. The order is canon here and nowhere else:
review-engine → review-response → missed-calls → no-contact-path → no-booking
B1 Review Engine GBP rating >= 4.0 AND review count < 15
B2 Review Response review count >= 15 AND fewer than 5 of the newest 10 carry an owner reply
B3 Missed Calls listed number is not SMS-capable, OR no after-hours path, AND trade is emergency-shaped
B4 No Contact Path no contact form AND no chat widget on the website
B5 No Online Booking no scheduler AND trade is appointment-shaped
If nothing matches, the prospect has no wedge worth leading with. Park it. That is a real outcome and it is better than inventing a finding.
parked-no-match and disqualified are exclusive. Either is recorded on its own or not at all. Ticked alongside a real bucket they contradict it — they say both that there is nothing to sell and that there is.
Why this order
| Rank | Bucket | Gap the prospect can see | Cost to deliver | Time to value |
|---|---|---|---|---|
| 1 | Review Engine | Largest and most numeric. One number against three competitors | Near zero | Days |
| 2 | Review Response | Large, and visible on their own profile | ~$0.01 per response | First week |
| 3 | Missed Calls | Real revenue, but they must take our word on the volume | Low | Blocked on A2P, 7-10 business days |
| 4 | No Contact Path | Obvious once named, but feels minor to an owner | Minutes | Minutes |
| 5 | No Online Booking | Weakest. Many trades genuinely do not want it | Low | 30-60 minutes |
Reviews rank first because the gap is a number the prospect can verify on their phone before finishing the email, and because reviews feed the map ranking that everything else depends on.
The rating floor on B1
A business rated below 4.0 never routes to B1. Asking a 2.8-star business to solicit more reviews is a different service, it carries real risk of making their profile worse, and SC does not sell reputation repair. Those prospects fall through to B2 if they have volume, and to the capture buckets if they do not.
This matters upstream. The live Prospect AI agent currently filters on GBP ratings Below 3.0, which selects almost exclusively for businesses that cannot be sold B1 and are a poor fit for B2. The filter and the offer set are close to opposed. Changing it is a live-account change and belongs in its own single-variable edit, after the agent's counters have been read.
The buckets
Each bucket names one finding, one fix, and one thing never to say.
B1 — Review Engine
Trigger: GBP rating >= 4.0 and fewer than 15 Google reviews.
The finding: their review count against the three businesses above them in the local pack, both hand-counted.
The fix: a post-job review request that goes to every customer, by SMS, email, or a QR code on the invoice. Governed by the Manual Google Review Request SOP, which is active and deliverable on every tier.
Never say: anything that implies filtering. SC asks every customer and every customer goes to Google. The no-gating rules are policy, they are in that SOP, and they are the reason this bucket is sellable at all.
The tell that makes this bucket land: a business in this bucket usually already wants reviews. Look for written testimonials on their website, a "leave us a review" button, a sign in the office. That is an owner who has tried and whose method is not working, which is a far better conversation than telling someone they have a problem they had not noticed.
B2 — Review Response
Trigger: 15 or more reviews, and fewer than 5 of the newest 10 carry an owner reply.
The finding: a hand-counted number of recent unanswered reviews, with the date of the most recent one.
The fix: Reviews AI on a 24-hour delay, with anything under three stars held for a person. See the Review Response Play, which is this bucket in full, and the AI Review Response SOP.
Never say: the widget's response-rate percentage. It lags. An owner who replied last week will check, find it wrong, and discard the whole report. Count by hand or do not make the claim.
This is the only bucket with a guarantee attached, and that guarantee is still draft and must not be quoted.
B3 — Missed Calls
Trigger: the listed number is not SMS-capable, or there is no after-hours path, and the trade is emergency-shaped.
The finding: what happens to a call placed after hours. Stated as an observation, never as an estimate of how much money they are losing.
The fix: missed-call text back. Also available standalone as Text Back Pro at $99/month. Never mention Text Back Pro on a Results-First call: its $99 is monthly, and it clashes with the offer's $99 to start.
Never say: that it can be live tomorrow. A2P registration takes 7-10 business days and it is not optional. Describe the mechanism, not a date.
B4 — No Contact Path
Trigger: no contact form and no chat widget.
The finding: the only way to reach them is to pick up a phone. True of the whole site, verified by hand, not from the report's technology detection, which produces false negatives on delayed and embedded widgets.
The fix: a LeadConnector form and chat widget, routed into the CRM. Minutes to stand up.
Never say: that they are losing a specific number of leads. It is unknowable and the claim is checkable in the wrong direction.
B5 — No Online Booking
Trigger: no scheduler on the site, and the trade is appointment-shaped.
The finding: a customer who wants to book has to call during business hours.
The fix: a calendar with routing, per the Calendar Setup SOP.
Never say: that booking suits every trade. It does not, which is why this bucket is last and trade-gated.
Trade shape
B3 and B5 both depend on what kind of business it is. Emergency-shaped work arrives unplanned and the caller will not wait. Appointment-shaped work is scheduled in advance and a form or calendar is a genuine convenience.
| Shape | Trades | Priority bucket |
|---|---|---|
| Emergency | Plumbing, HVAC, electrical, septic, water damage and restoration, garage door, locksmith, storm tree work | B3 |
| Appointment | Landscaping and lawn, cleaning, flooring, painting, home watch, pest, remodeling, inspections, roofing, general construction | B5 |
A trade that is genuinely both — HVAC in a heat wave, for example — is emergency-shaped. Take B3.
Roofing sits in the appointment column despite the storm exception. A roof replacement is a quoted, considered purchase and behaves like an appointment. Storm damage is the exception rather than the shape of the trade, and classifying the whole trade by its exception would route every roofer to B3.
Watch what this does to the bucket spread. The agent currently targets roofing, landscaping and construction, and all three are appointment-shaped, so B3 will rarely fire on the present supply. Combined with the GBP ratings Below 3.0 filter, which blocks B1 outright, the live batch is likely to concentrate in B4 and B5 — the two weakest offers in the set. That is a supply problem rather than a taxonomy problem, and it is the reason the bucket spread is a reported number in the execution SOP.
What gets recorded
| Field | Value |
|---|---|
audit_finding_used | The hand-counted finding as a short noun phrase, written to read inside a sentence |
prospect_bucket_options | Every bucket that applies. CHECKBOX on live (2qVe4MeQvpFtZP9awZfj), created 2026-10-30, in the C-021.Prospecting folder. Seven values, so a parked or disqualified prospect is recorded too rather than left blank. Written by the caller at call prep, not by the desk. The lead bucket is derived from the ticks and is never stored separately |
| Contact City | Merged by every touch-1 template as the geo-anchor. Populated by the agent; verify rather than enter |
⚠️ The consistency rule no longer binds the email, because the email no longer carries a finding. The cadence was merged to a single generic send on 2026-10-30 — one email that delivers the report and names no bucket. Bucketed emails exist as templates but the workflow that would route them has never left draft.
So the bucket's job has narrowed to one thing: what the caller leads with on the phone. That is also why the caller records it. Nothing upstream of the call consumes it today, and a field set by the desk three days before anyone dials was being written for a reader that no longer exists.
If a bucketed email ever ships, the consistency rule returns and it binds the lead bucket to that email — the same finding in the email and on the call, or the prospect hears two pitches.
Percentages stay internal
The audit's section scores are triage inputs. They do not appear in anything a prospect sees. The marketing audit PRD bans numeric percentages from SC-facing output because the widget's precision is not real, and a false 0% reads as a genuine zero. Read the scores to find the bucket, then throw them away and put a hand-counted number in the email.
Thresholds are tunable
The two numbers that decide B1 against B2 — a rating of 4.0 and a count of 15 — are starting positions, not findings. They are recorded here so they can be changed deliberately from one place, with a version bump, once a batch has produced reply-rate data. Do not adjust them per prospect.
Extending to another segment
The method is segment-independent: gate, disqualify, walk a first-match tree, record one bucket. What changes per segment is the bucket table and the trade-shape table.
To add professional services, add a bucket table scoped to that segment rather than editing this one. A law firm's buckets will not be these: intake response time and consultation booking matter far more than review volume, and "emergency-shaped" does not translate. Keep the shared method, replace the contents.
Related Documents
- Prospect Outreach Execution SOP - the daily operating loop, roles, and escalation
- Prospect Bucket Slotting Checklist - the procedure that assigns a bucket
- Prospecting Review Response Play - B2 in full
- Prospecting Outreach Email Templates - the per-bucket touch-1 emails
- Outreach Cadence SOP - touches, tags, stop rules, ICP screen
- Audit Accuracy SOP - section confidence and red flags
- Manual Google Review Request SOP - the review solicitation policy
Document History
| Version | Date | Changes |
|---|---|---|
| 1.6 | 2026-11-04 | The Results-First pre-dial list is added beside the disqualifiers, because every cold call now carries the final offer: rating below 4.0, fewer than 10 or more than 150 reviews, 3 or more in the last 60 days, none in 90, a competitor's tracking number or review widget, and no local authority. B3 gains a rule never to mention Text Back Pro on an offer call |
| 1.5 | 2026-10-30 | One bucket becomes one lead bucket, derived. The live field was replaced with a multi-select prospect_bucket_options (2qVe4MeQvpFtZP9awZfj, CHECKBOX) and a contact already carried three values, so "exactly one bucket" was false against live. The tree is unchanged — it is now a rank order over the ticks rather than a stop-at-first walk, which keeps the judgement it encoded while giving the caller the other findings instead of discarding them. The rank is written out explicitly because the new values dropped the B1- to B5- prefixes and no longer announce it. Ownership moves to the caller at call prep. Withdraws the consistency rule's claim over the email: the cadence merged to a single generic send the same day, so the bucket now decides only what the caller leads with on the phone. Records that the old jCdKeYfwzNaTPWn6j5o5 is gone from the field list while three contacts still carry orphaned values on it |
| 1.4 | 2026-10-09 | Separates bucket choice from offer eligibility, which were being read as one question — a prospect can slot B1 and still fail the Results-First gates, as the document's own Talarico example does. Points at the new Prospect Qualification Standard for where each gate is answered. Corrects a stale sentence that still described the Review Response Play as disqualifying anyone under three reviews; that floor is 15 and routes to B1 rather than rejecting |
| 1.3 | 2026-09-16 | trade removed from the recorded-fields table. The templates no longer merge it. Trade shape still decides B3 against B5 in the tree, as a judgement the slotter makes rather than a field anyone stores |
| 1.2 | 2026-09-10 | Roofing and general construction added to the trade-shape table, both appointment-shaped. Two of the three niches the agent currently targets were missing from the table the tree depends on. Notes the resulting concentration in B4 and B5 |
| 1.1 | 2026-09-10 | prospect_bucket is live (jCdKeYfwzNaTPWn6j5o5), with seven values so parked and disqualified prospects are recorded rather than left blank. Templates 12-14 written, so all five buckets are sendable |
| 1.0 | 2026-09-10 | Initial taxonomy. Five buckets, first-match tree, home services scope. Generalizes the Review Response Play into B2 and adds B1, which the play previously disqualified with no alternative |