Dental labs / Partner territory
How a dental lab decides which practices are worth a visit this quarter
Illustrative workflow
A working example of how a lab turns a delivery radius into a short list of practices that fit its case mix, sees which of them share an owner, and learns which role to approach first.
The question behind this page
Which practices near my lab are actually worth my rep's time, and who do I need to talk to?
Short answer
Start from the radius your courier can genuinely serve, keep only the practices whose visible services match the cases you want more of, group the ones that share an owner, and approach each account through the role that decides on lab work rather than the front desk.
Why it is worth your time
What this changes for a lab owner
Written for the person who runs the business, not for a data team. If none of these four is a problem you recognize, this page is not for you.
- 01
Your rep spends the week on practices that plausibly send the cases you want, instead of driving a list where every clinic looks identical.
- 02
Where shared ownership is visible in the evidence, you see it before you price three practices separately — and can put one agreement in front of the operator instead.
- 03
Where a public decision-maker path exists, you walk in knowing which role decides on lab work instead of starting at the front desk.
- 04
You can say out loud why each account is on the list, and when that reason was last checked.
The same week, two ways
What actually changes in how the week is run.
Without the model
- The territory is whatever the last rep remembered, plus referrals and a bought list.
- Every practice on the list looks the same, so the biggest full-arch account and a two-chair general practice get the same visit.
- Nobody knows which of the nearby practices belong to one owner until a pricing conversation goes strange.
- The first call reaches reception, and the person who chooses the lab never hears the pitch.
With the model
- The list is bounded by a radius your delivery can actually serve, not by a state line.
- Practices carry visible service signals — implant, all-on-X, cosmetic — so the case-mix conversation starts before the drive.
- Locations with a confirmed shared owner are grouped, derived groupings are labeled as derived, and the rest stay unknown rather than independent.
- Each account carries the role to approach and a public contact path where one exists, with the date it was last seen.
Use case / illustrative workflow
Illustrative workflow: a full-arch partner territory
A lab that wants more full-arch work has one business-development rep and a courier route that realistically covers about an hour's drive. The question is not who exists — it is which forty accounts that rep should work next quarter.
- 01
Draw the radius you can serve
Set the delivery boundary from courier reality and rep capacity. This is an operating constraint, not a forecast of demand.
- 02
Keep the case mix you want
Filter to practices whose visible services match full-arch and implant work, so the list reflects the cases the lab actually wants.
- 03
Group the doors that share an owner
Resolve which locations are siblings before pricing them separately, and treat a derived grouping as derived until it is confirmed.
- 04
Find the role, not the reception desk
Open the Outreach Profile for the practice owner, lead dentist or practice manager and check when that path was last seen.
- 05
Write one conversation a human sends
Draft a specific opening for the account and its role. A person reviews and sends it; the platform never sends for you.
10,400
practices with visible all-on-X / full-arch work
N=103,674 clinic profiles · public and website-derived · July 2026 snapshot
1,801
evidence-confirmed ownership networks
95.6% at ≤10 locations · graph snapshot 2026-08-01
723
US metros with market structure available
Rolling incremental collection · dated snapshots
These figures come from different populations and each carries its own denominator — clinic profiles and active clinic records are counted separately, which is why the totals differ. Full method, denominators and snapshot dates: hidden dental networks, measured national coverage evidence.
What you bring, what we show, what nobody can promise
Useful for deciding where to start. Honest about the rest.
You bring
- The delivery radius your courier can serve on a normal week — not the one you wish you had.
- The case types you want more of, and the ones you would rather not take.
- How many accounts one rep can genuinely work in a month, which sets how long the list should be.
The model shows
- Visible clinical service signals per clinic: 50,000 US practices placing implants and 10,400 doing all-on-X / full-arch work (N=103,674 clinic profiles, public and website-derived observations, July 2026 snapshot).
- Ownership structure: 1,801 evidence-confirmed ownership networks covering 4,176 clinic records, and 95.6% of those networks at 10 locations or fewer (graph snapshot 2026-08-01, monthly refresh).
- A public decision-maker path per account where one is available, with its source and the date it was last seen.
It does not prove
- A service signal is what a practice shows publicly. It is not a count of cases it sends, and it is not proof it sends any.
- Nothing here says a practice is unhappy with its current lab or is willing to switch.
- Public contact coverage varies by account. A missing contact is unknown, not an absence — and never a reason to guess an address.
- Network detection is a measured floor, not a census. Two practices with no visible link may still share an owner; absence of a link means nothing was found in public evidence.
- A connection is not the same as confirmed ownership. The wider relationship graph links 17,166 of 120,537 active clinic records by a verified link of some class; only the narrower confirmed-ownership layer of 4,176 clinic records supports a one-operator conversation.
- The list narrows where to look. Local knowledge, a visit and a price conversation still decide the account.
Every figure on this page is shown with its denominator and snapshot date. Observed, derived and unknown states stay distinct; unknown is not a negative finding and is never counted as one.
Outreach Profile
Know who to validate before you write.
Before a rep drives anywhere, the profile answers one question: who in this practice decides on lab work, and what do we already know about them from public evidence?
Availability note: public profile and contact coverage varies by account. We show what public evidence supports, keep unknown fields visible as unknown, and never guess a contact point.
Sending stays with you: the recommended angle is a draft for a person to review, edit and send. The platform does not send messages on your behalf.
Account preview
What a profile carries
- Account fit
- Why this account is on the list: the service, technology or market signals that matched your thesis.
- Territory context
- Where the account sits against the delivery or coverage boundary you set.
- Network relationship
- Unknown, independent, affiliated or derived grouping. Unknown is the most common state and does not mean independent; derived groupings are labeled as derived.
- Decision-maker path
- The role to reach, with a public LinkedIn or business contact point where one is available.
- Source, freshness, confidence
- Where each field came from, when it was last seen and how confident the model is.
- Recommended angle
- A role-aware opening for a human to review, edit and send. Nothing is sent for you.
Roles this workflow can help you validate
- Practice owner or lead dentist
- Practice manager
- Marketing or growth lead
- Network or regional contact
How to tell whether it worked
Check it in your own numbers.
Nobody can tell you this worked from our side. These are the signals you can read inside your own business.
Window: Judge it over one full sales cycle, not one week. For most labs that is 60 to 90 days.
- 01 The share of first meetings that reach the person who decides on lab work, rather than reception.
- 02 How many accounts you removed from the list before spending a drive on them, and why.
- 03 Whether multi-location conversations moved to the operator instead of being repeated per door.
- 04 Whether your rep can state, per account, why it is on the list — that is the part that survives staff turnover.
What kind of page this is
This is a worked example of how the product is used, written by DentalCensus. It is not a customer story, not a measured result and not a forecast of case volume.
Built from
- Published DentalCensus coverage and network figures, each shown with its denominator and snapshot date.
- Product capabilities that exist today, described as they behave.
- No customer data, no private records and no contact enrichment beyond publicly available business information.
And what a verified customer case would require
We publish customer results only when all four hold. Until then this page stays labeled as an illustrative workflow — which is why it makes no claim about your outcome.
- A named customer who has approved the story and the numbers in writing.
- A stated measurement window with the baseline it is compared against.
- Every figure traceable to a source the customer and we can both point at.
- Domain and legal review before publication.
Next step
Try it on your own territory before you believe any of this.
Questions before you spend time on this
Straight answers.
Will this bring my lab new cases?
It does not promise cases. It changes which accounts your rep spends time on and who they speak to first. Whether that turns into work depends on your pricing, turnaround, relationships and the visit itself.
Is this a real lab's results?
No. It is an illustrative workflow written by us to show how the product is used. A verified customer case is published only with the customer's approval and named provenance, and is labeled as such on the page.
Will every practice have a named contact?
No. The profile shows a public role or business contact path where one is available and marks the rest as unknown. Unknown means we did not find it in public evidence — it is not a statement that the person does not exist, and we do not guess addresses.
How current is the underlying data?
Collection is rolling and incremental, and every figure on this page carries the snapshot date it came from. Anything older than its stated snapshot should be treated as needing a local check.