Service file

DSO website design has to satisfy two audiences that want different things

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

  • Plans$137 a month
  • Build fee$797, after launch
  • Live in7 days
  • Revisions5 a month
  • Domain and hostingIncluded

One component set, many practices

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.

Local identity where it actually matters

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.

Governance the support center can actually run

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.

Governance a support center can run: portal for center and offices, brand rules in components, one request, every office. Tiffy stamps one card for every office.

Compliance lines that stay where they belong

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

Who dSO website design 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.

  • DSO marketing teams managing many affiliated practices
  • Affiliated practices that keep their original names
  • Regional managers who need a clear approval path

Symptoms

Signs your group needs this now

Out of scope

What dSO website design does not include

So nobody is surprised after ordering. Each of these is a deliberate line, not an upsell waiting to happen.

  • Clinical content we would have to vouch for

    We do not write treatment recommendations, success rates, outcome claims or before-and-after captions. Your clinicians own every statement about care.

  • Patient health information in web forms

    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.

  • Paid ad management

    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.

  • Your practice management system

    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.

  • Photography shoots

    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.

  • Per-office fees or hourly billing

    There are none. One fee covers every office in the group; extra revisions beyond 5 a month are a flat $20 each.

Reviews

What groups say about dSO website design

  • 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

    Gregory FrostPractice administrator, Multi-surgery family dental practice
    Ann Arbor, Michigan
  • 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

    Rakesh PillaiPatient care coordinator, Denture and prosthetics dental practice
    Frederick, Maryland
  • 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

    Abigail ThorpePatient coordinator, Emergency and general dental surgery
    Ann Arbor, Michigan

Built in, not bolted on

Compliance built into the site

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.

  • Privacy policy and terms

    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.

  • Cookie policy with consent that really gates scripts

    Analytics and marketing tags load only after a visitor agrees, and the cookie policy lists what the consent banner controls.

  • Accessibility statement and an accessible build

    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.

  • No patient health information in forms

    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.

  • SMS consent wording

    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.

  • General-information disclaimers

    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

The guarantees behind dSO website design

Each promise is written with its condition in plain sight, so nothing is discovered after the invoice.

  • Build fee only after you approve the live site

    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.

  • 90+ PageSpeed, held

    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.

  • Local rankings within 3 to 5 months

    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

What you get

Thirty minutes

See dSO website design on your own offices

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.

Book a demoCompare the options

How the work is done

From order to live, step by step

The same four steps for every service. The only thing paid before launch is the first month.

  1. Day 0

    Pay the first monthly invoice

    Pick a plan and pay the first month. That is the whole commitment; the $797 build fee waits until your site is live.

  2. Day 1

    One onboarding call

    Thirty minutes with your operations lead: offices, providers, services, brand, where each office's requests should go, and hub or one site per location.

  3. Build

    We build

    We design the site, write the pages, configure the finder for each office and connect each front desk. You review, we revise.

  4. Day 7 to 15

    Live, then the build fee

    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

How long it takes

Counted from the onboarding call, not from purchase. Revisions after launch are completed within 2 to 5 working days.

  • 7 daysChairside the website, fully managed
  • 10 daysOperatory Suite everything, plus the ai engine
  • 15 daysGroup everything, plus the content engine

Cost

What dSO website design costs, and what drives it

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.

Every line on the pricing page

What changes the price

  • The plan: Chairside $137/ month, Operatory Suite $297/ month + usage, Group $747/ month.
  • The one-time $797 build fee, invoiced after launch, charged once per group.
  • Extra revisions beyond 5 a month, $20 each.
  • AI usage on Operatory Suite, billed monthly at cost with no minimum.
  • Not the number of offices, pages or providers. The fee is per group.

What's in each plan

The plan features that matter here

What each feature does, the everyday problem it removes, what you have to do (usually nothing), and which plan carries it.

  • Chairside $137/ month
  • Operatory Suite $297/ month + usage
  • Group $747/ month

The website

A page for every officeChairsideOperatory SuiteGroup
What it does
Each location gets its own page with address, hours, parking, providers, services and its own dental business schema.
The problem it removes
Satellite offices hidden in an address list never show up for their own town.
What you do
Tell us your offices on the onboarding call.
How it works
Service and provider pagesChairsideOperatory SuiteGroup
What it does
A page per service and per clinician, each linked to the offices where it happens.
The problem it removes
Patients cannot tell which office offers implants or which dentist works on Saturdays.
What you do
Send provider bios and the services each office offers.
How it works
Location and provider finderChairsideOperatory SuiteGroup
What it does
A patient picks a service and a town and gets the nearest office, its providers, today's hours and a request button.
The problem it removes
Front desks spend calls explaining which office is closest.
What you do
Nothing beyond the onboarding answers.
How it works
90+ PageSpeed pagesChairsideOperatory SuiteGroup
What it does
Hand-coded static pages served from Cloudflare's edge, fast on mobile and desktop, guaranteed.
The problem it removes
Slow pages lose patients, and paid clicks, before the phone number appears.
What you do
Nothing.
How it works
SEO, AEO, GEO and schemaChairsideOperatory SuiteGroup
What it does
Technical and on-page SEO, answer-first copy, visible FAQs, an llms.txt file and structured data generated from the page data.
The problem it removes
Search engines and AI assistants cannot cite what they cannot parse.
What you do
Nothing.
How it works

Running it for you

Booking requests routed per officeChairsideOperatory SuiteGroup
What it does
Every form and finder request carries the office, provider and service and lands in that office's CRM or practice system by API, Zapier or Make.
The problem it removes
A shared inbox means the wrong office calls back, or nobody does.
What you do
Tell us where each office wants its requests.
How it works
Weekly detail updatesChairsideOperatory SuiteGroup
What it does
Hours, closures, providers, insurance plans and office notes applied every week to the page, schema and finder together.
The problem it removes
Wrong hours send a patient to a closed door.
What you do
Email the change from any office. It does not use a revision.
How it works
5 revisions a monthChairsideOperatory SuiteGroup
What it does
Any size of change, across every office, completed within 2 to 5 working days. Extra revisions $20 each.
The problem it removes
Small changes wait months when nobody owns the site.
What you do
Raise it in your client portal or by email.
How it works
Researched articles every weekChairsideOperatory SuiteGroup
What it does
2 a week on the first two plans, 3 on the third, 2,500 to 3,200 words each, with cited sources.
The problem it removes
The blog stopped the month after launch.
What you do
Nothing. Review any article if you want to.
How it works
Hosting, SSL, backups, domainChairsideOperatory SuiteGroup
What it does
Cloudflare hosting with SSL, CDN and DDoS protection, backups and monitoring, plus a free domain registered in your name.
The problem it removes
Hosting renewals, SSL lapses and a domain held by a former vendor.
What you do
Nothing.
How it works
Client portal and a person who repliesChairsideOperatory SuiteGroup
What it does
Revisions, support tickets, files and messages in one place. A person replies within one working day.
The problem it removes
Requests lost in email threads.
What you do
Log in to the portal, never to the website.
How it works

AI Engine

AI receptionistChairsideOperatory SuiteGroup
What it does
Answers calls a front desk cannot get to, per office, knows each office's hours, providers and services, and takes the booking request.
The problem it removes
Calls during procedures and after hours go to voicemail and are not returned in time.
What you do
Approve the script for each office before it goes live.
How it works
Site chatChairsideOperatory SuiteGroup
What it does
Answers questions on the website and sends requests to the office the patient chose. Loads after the page is interactive.
The problem it removes
Visitors with a quick question leave instead of calling.
What you do
Approve the answers it may give.
How it works
SMS, Messenger and Instagram repliesChairsideOperatory SuiteGroup
What it does
Replies to texts and social messages and routes booking requests per office.
The problem it removes
Slow replies on social lose patients who message instead of calling.
What you do
Connect your pages once.
How it works
Call-analysis PDFChairsideOperatory SuiteGroup
What it does
Shows what patients asked, which office they wanted and where calls were missed.
The problem it removes
Nobody knows when the phones go unanswered.
What you do
Read it.
How it works
A2P 10DLC registration filedChairsideOperatory SuiteGroup
What it does
The carrier registration needed to text patients from a business number, filed by us, carrier fees passed through at cost.
The problem it removes
Unregistered business texts get filtered or blocked.
What you do
Supply the business details we ask for.
How it works

Case studies

Case files related to dSO website design

All case studies
  • No. 16Periodontics

    Harrisburg, Pennsylvania General and periodontal dental practice

    Giving staff control of dental office selection changes

    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.

    • Structured change request
    • Named approver
    • Before-and-after preview

    25 working days

  • No. 19Pediatric dentistry

    Worcester, Massachusetts Children's dental practice

    A tested fallback for dental office selection contact

    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.

    • Alternative contact method
    • Useful failure message
    • Form delivery check

    20 working days

  • No. 20General dentistry

    Chandler, Arizona Dental hygiene and preventive care clinic

    Keeping dental office selection maintainable after launch

    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.

    • Page inventory
    • Maintenance notes
    • Backup reviewer

    25 working days

Questions about dSO website design

Can affiliated practices request changes themselves?

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.

Do you work inside our existing brand standards?

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.

How do you handle practices that keep their original name?

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.

Can the site cover practices in more than one state?

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.

Do you write clinical or outcome content for affiliated practices?

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.

Can the site cover affiliated practices across several states?

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.

Who approves changes, the practice or the DSO?

Whoever you decide. Office managers can send weekly detail updates while brand and service language changes go through the DSO marketing team first.

Can requests go to a central DSO platform?

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.

See it built for your group

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 demo

Or email and a person replies within one working day.