A governed component set
Brand rules encoded in the components so an office page cannot drift off-standard by accident.
Service file
Head office wants consistency and control; the patient wants the office down the road. A DSO site design works when a single set of components carries brand standards across every affiliated practice while each local page still leads with the address, the hours and the clinicians a patient recognizes. We build the system so support-center teams can roll a change across every office at once, and so an affiliated practice never looks like a directory entry inside somebody else's website.
What it costs
A DSO cannot design each affiliated practice separately and cannot afford them to drift. We build one component set: office header, hours block, provider card, service block, insurance panel, booking request. Brand rules live in the components rather than in a PDF nobody opens, so an office page cannot accidentally use the wrong type scale or a non-brand color. When the support center changes a legal line, a disclosure or a phone treatment, it changes in one place and appears on every affiliated practice page in the same week.
Consistency should not flatten the thing a patient came for. Each affiliated practice page opens with its own name where it trades under one, its own address and hours, its own photography and the clinicians who work there. Reviews and articles can be scoped to the office rather than the group. The rule we apply is simple: anything a patient uses to decide whether to call is local, and anything that protects the brand is central. That line keeps head office comfortable and still gives the office something a patient recognizes.
Most DSO website problems are operational rather than visual: nobody knows who is allowed to change what, so nothing changes. Every group we work with gets a client portal. Office managers can raise a request for their own page, the support center sees everything, and we apply it. Hours, closures, provider moves and insurance changes go through weekly detail updates without using a revision. Larger work, such as a new service line rolled out across twelve offices, is one revision with the copy attached, completed in the standard turnaround.

Affiliated practice sites carry ownership disclosures, clinician credential lines and state-specific wording, and those must not depend on whoever last edited a page. We hold them as components tied to the office record, so a change to a disclosure updates every page that carries it. We do not write clinical claims, outcome statistics or treatment recommendations on any site we build, and content is general information rather than advice. Where a request would amount to advice, the page and the AI Engine both hand it to a person at the practice.
Who it is for
DSO support centers and affiliated practices that need brand consistency without losing the local office a patient recognizes.
DSO groups often span states. Practices in Texas, Florida, California, New York and Illinois can share one component system while each keeps a page written for its own town.
Symptoms
Out of scope
So nobody is surprised after ordering. Each of these is a deliberate line, not an upsell waiting to happen.
We do not write treatment recommendations, success rates, outcome claims or before-and-after captions. Your clinicians own every statement about care.
Request forms ask for a name, contact details, the office, the service and a preferred time. Medical history, insurance IDs and consent forms stay in your own intake system, never on the website.
We build pages that are fast and relevant enough to be good landing pages for your ads. Running and bidding on the campaigns themselves stays with you or your ads partner.
We route requests into the system or CRM each office already uses, by API, Zapier or Make. We do not sell, host or administer the practice software itself.
We use the office and team photos you own and have consent to publish, sized for their slots. Where you have none yet we use neutral, non-clinical images until yours arrive.
There are none. One fee covers every office in the group; extra revisions beyond 5 a month are a flat $20 each.
Reviews
Converting our dental office selection attachment into proper pages was overdue. I can send the exact section someone needs, and they can read it without downloading anything. A printable copy still exists for those who ask.
Got Structured reference pages for dental office selection
The scenario I cared about was the one nobody demos, the dental office selection form going down. There is now a visible backup route, honest error wording, and a test that proves mail arrives. We now know the fallback exists before the day we need it.
Got Contact resilience and delivery checks for dental office selection
The documentation for the dental office selection pages assumes nothing about the reader. It covers who to contact, how to request a change and what to check after publication. A colleague followed it without a single phone call, which is the real test.
Got Staff handover and maintenance notes for dental office selection
Built in, not bolted on
A dental website carries obligations a brochure site does not. These ship with every plan, written for your practice and reviewed by you before launch.
These pages and practices help you meet common US requirements for a dental practice website. They are not legal advice, and we recommend your own counsel reviews the policies before launch. We are not a dental practice, dental group, dentist or healthcare provider, and we are not a law firm.
A privacy policy and site terms written around what your site actually collects, drafted for your review and your counsel's sign-off. Built with state privacy laws such as the CCPA in California in mind.
Analytics and marketing tags load only after a visitor agrees, and the cookie policy lists what the consent banner controls.
Real contrast ratios, visible focus states, keyboard navigation and alt text, built with the Americans with Disabilities Act (ADA) and WCAG 2.2 AA in mind, plus a statement telling patients how to report a problem.
Request forms are designed not to collect health information. That keeps the website out of your HIPAA scope as far as a website can be, while your intake system handles records.
Where a form or the AI Engine sends texts, consent wording sits next to the phone field, and we file the A2P 10DLC carrier registration for you on plans with the AI Engine.
Service pages and articles say they are general information, not a diagnosis or treatment plan, and send patients to your providers for anything about their own care.
Risk reversal
Each promise is written with its condition in plain sight, so nothing is discovered after the invoice.
The $797 one-time build fee is invoiced after launch, once you have seen the site live and are happy with it.
Condition The first monthly fee is paid up front to start the plan.
Every page we build scores at or above the target on mobile and desktop at launch.
Condition If a page drops below it because of our work, we fix it at no charge and it does not use a revision.
The site starts ranking for local searches in your area within the window.
Condition If it has not, we keep working on it at no charge. We never promise a specific position.
Deliverables
Brand rules encoded in the components so an office page cannot drift off-standard by accident.
Local name, address, hours, photography, clinicians and services, with its own Dentist schema.
A new service line, a new disclosure or a new phone treatment applied across every office in one revision.
Requests, tickets, files and messages in one tracked place instead of a shared inbox.
Ownership and credential lines tied to the office record, so a change lands everywhere it should.
Each affiliated practice keeps its own booking destination even while the brand stays central.
Thirty minutes
We open a site built for a group like yours, walk the pages a patient would, and tell you which plan fits. Plans from $137 a month; the $797 build fee is invoiced after launch.
How the work is done
The same four steps for every service. The only thing paid before launch is the first month.
Pick a plan and pay the first month. That is the whole commitment; the $797 build fee waits until your site is live.
Thirty minutes with your operations lead: offices, providers, services, brand, where each office's requests should go, and hub or one site per location.
We design the site, write the pages, configure the finder for each office and connect each front desk. You review, we revise.
Your site goes live in 7, 10 or 15 days depending on the plan. Only then is the $797 build fee invoiced. Weekly updates start the same week.
Timeline
Counted from the onboarding call, not from purchase. Revisions after launch are completed within 2 to 5 working days.
Cost
Priced per group on the same three plans. A DSO with several regions can run each region as its own group plan or one plan across all, which we settle on the onboarding call.
What's in each plan
What each feature does, the everyday problem it removes, what you have to do (usually nothing), and which plan carries it.
Case studies
No. 16Periodontics
When it comes to dental office selection, whoever published an update had to interpret the request, while whoever approved it could not easily compare old and proposed wording side by side.
25 working days
No. 19Pediatric dentistry
Day to day with dental office selection, visitors hitting an error scavenged the footer for alternatives. Staff had no routine check, so a failed form could go unnoticed for days.
20 working days
No. 20General dentistry
When it comes to dental office selection, staff avoided routine changes because nobody could say who approved them or how to check them. Staleness was safer than error.
25 working days
Yes, if you want them to. Portal access can be given to individual office managers, to the support center only, or to both. Everything raised is visible to the support center, so local speed does not cost central oversight.
Yes. We build the component set from your standards and tell you where a rule will not survive a real page, usually contrast or line length. Anything we change, we show you before it ships.
The page leads with the trading name the patient knows, with the group relationship disclosed where required. If several practices keep strong independent names, one site per location is often the better structure and we build that instead.
Yes. State-specific wording is held per office rather than globally, so a disclosure that applies in one state does not appear on a page in another.
No. We are not a dental practice, dental group, dentist or healthcare provider, and we never write treatment recommendations, success rates or clinical comparisons. Content is general information, and anything clinical is handed to your clinicians.
Yes. Practices in Texas, Florida, California, New York and Illinois can sit on one structure, each with its own page, its own details and its own booking destination.
Whoever you decide. Office managers can send weekly detail updates while brand and service language changes go through the DSO marketing team first.
Yes. Every request carries the office, provider and service, and can be delivered to a central CRM, a regional pipeline or the local desk, by API, Zapier or Make.
A live walk-through of the site you would get, in about 30 minutes. Plans from $137 a month, the $797 build fee invoiced only after launch, domain and hosting included.
Book a demoOr email and a person replies within one working day.
ChairsideWeb uses the cookies below. Necessary cookies keep the site working and cannot be turned off.
Saved on this device only. Press Esc to close.