Web development shop calling playbook: call blocks, cadence and KPIs

What this playbook covers

A web shop’s calling has three motions: prospecting local businesses with one observable finding per row, protecting the maintenance and hosting base that pays the quiet bills, and re-engaging churned clients once, honestly. This playbook structures the week around all three, with the hygiene and cadence rules that keep owner-operators answering. Output may be absent, delayed or wrong; verify details before you rely on them.

List hygiene, finding-first

The prospect list is built finding by finding: each row names one specific, publicly observable issue, the PDF menu, the expired certificate, the hours that contradict the map listing, plus the owner’s name where known. Vague findings, “outdated site,” “not mobile friendly,” produce hang-ups, so the weekly list review grades finding quality before any dialing happens. Dedupe across verticals, apply your internal DNC list, and set attempt caps per list.

Two craft rules keep the calling clean. First, describe only what any visitor can see on the public site; no scanning, probing or testing beyond the visitor’s view. Second, honor every stop request the moment it lands. Most of this calling is business-to-business and much of it sits outside the FTC rule under the B2B exemption at 16 CFR 310.6, but the exemption is narrow and owner cells are personal phones, so the TCPA’s wireless restrictions at 47 CFR 64.1200 still govern. Human-dialed lines are the design.

The calling week in blocks

Local prospect block, two to three mornings. The finding-prepared list on three lines, mid-morning before the lunch rush. Finding first, business cost second, seasonal deadline third, who signs fourth. The close books the consult around a working mockup, and the small fix gets sold where the budget only fits the small fix, because a fixed menu page this month is the redesign conversation next year.

The call prevents the silent churn of clients who forgot what the plan does, and it doubles as the scope conversation for the year ahead: the client who wants e-commerce in spring is a project, not a renewal. The recording settles the annual dispute about what the plan was supposed to include.

Churned-client block, monthly, small. Clients who left a year or more ago get one honest call: what changed, is the site still theirs, anything worth a look. The outcomes get logged: migrated to a cheaper host and now broken in ways the owner notices, a new marketing person who wants a vendor they can call, or the business closed, which ends the record permanently. Attempt caps keep the one honest call exactly one.

Seasonal block, six to eight weeks ahead of each vertical’s window. Restaurants before tourist season, retailers before holidays, tax offices before April.

Attempt cadence and the local reputation

Prospects: two attempts two weeks apart at different hours, then a dated re-entry tied to a season or a new finding; a new finding restarts the conversation honestly, and it is how the shop’s second call to a business sounds like service instead of nagging. Renewals: one call per year plus the scope conversation. Churned: one call, ever, per departure. The do-not-call disposition is permanent everywhere, and in a local business community the shop’s manners are a referral asset or a liability, chosen by the cadence.

Dispositions sales and delivery both read

Consult booked, audit delivered, fix sold, maintenance renewed, has a developer, doing it themselves, deferred to next season, churned closed, wrong number, do not call. “Fix sold” stays separate from “consult booked” so the shop can see which motion pays for the calling hour.

Three lines clear the voicemail layer on a local list, which doubles the conversations per block. The caller verifies deadlines and decision structure against the recording before the next dial, because a consult staged for one spouse when both sign is a wasted Thursday. Outputs can be missing, delayed or wrong; verify important details before you rely on them.

The Friday review covers the finding inventory as much as the calls: which findings booked consults, which got fixes, which produced nothing. Over a quarter that inventory becomes the shop’s real lead-gen answer, and it costs one morning block a week to maintain.

KPI ranges and the production benchmark

• Dials per active calling hour: 70 to 100, median near 85 in The team’s own daily use, single line, 90 days.
• Dials per caller day: 200 to 500 depending on list prep load; finding work happens outside the block, and it shows in the connect quality.
• Person-connect rate: 17.8 percent measured over the last 30 days; mid-morning windows run best for owner-operators.
• Consults booked per week: your own baseline from the first month, judged by finding type.
• Maintenance renewals saved: the quiet number that pays the rent; one saved plan covers the calling hour for a month.

The production figures come from 37,411 dials over 90 days to 2026-09-26 in DialBreeze operation, aggregate activity, not customer results and not a promise about your list.

Compliance checklist for the web shop

Human-dialed calls to owner cells, stop requests honored and logged same-day, calling hours respected, recording disclosure for all-party states. Findings discipline: public observations only, no probing. Keep list provenance documented, and when a vertical list is purchased rather than built, the hygiene rules get stricter, not looser. Nothing here is legal advice; run the list policy past counsel where your calling territories are strict.