Web Design

Dental Website Design Only or a Full Build: What to Commission

Separate dental website design, frontend, CMS, content and external services. Define deliverables, ownership and the work needed for a dependable enquiry route.

Choose dental website design only when a named implementer will turn the approved layouts into a working site. Choose a broader build scope when you also need responsive implementation or an agreed CMS setup. In either case, define who handles content, appointment tools, publication and maintenance.

“Complete website” is not a precise deliverable. It may mean finished design files, a frontend ready to deploy or a published CMS site. It should not be assumed to include a clinical system, custom booking engine or ongoing care of every connected service.

Start with the capabilities already available

List the practice’s existing website platform, domain and hosting arrangements, appointment provider and technical contacts. Identify who can approve clinical information and who can confirm the administrative process for enquiries.

Then record what is missing. A practice with a retained developer may need a stronger design and clearer content hierarchy. Another may need implementation and a way for staff to update approved information without editing code.

Use the dental website content checklist to establish what the practice will supply. A provider cannot estimate the full assignment accurately if “content ready” actually means several unreviewed documents and outdated team photographs.

Understand what design-only provides

A design-only commission defines the agreed interface for someone else to build. At SavianoDesign, the standard offer includes the scoped Figma design, desktop and mobile layouts and an organised .fig handover.

Agree which page types and states are included. A service page, a team profile and a request form may need different layouts. A form also needs instructions, error feedback and an accurate completion message, not only an empty set of fields.

Design-only can fit when the implementation team and platform are already chosen. Bring that team into decisions that affect feasibility. A clickable prototype demonstrates a proposed journey; it does not send a real appointment request or confirm availability.

Define what frontend development adds

Frontend work turns the interface into working pages and agreed browser interactions. It can include responsive layouts, navigation and the visible behaviour of the scoped controls.

A visible form still needs a delivery mechanism. A booking button still needs an agreed destination. A patient account still needs more than a sign-in screen. Name the external service or specialist work required for each function rather than treating it as an automatic part of HTML, CSS and JavaScript implementation.

SavianoDesign’s Website Design service separates design-only, design plus frontend and WordPress CMS options. Custom backend systems, patient databases and advanced integrations are outside the standard offers and require separate assessment.

Decide whether staff need a CMS

A CMS is useful when the practice wants to update agreed text, images or pages without changing source code. Define the real tasks: revising opening information, updating a professional profile or publishing an approved service explanation.

SavianoDesign’s WordPress option uses Themify and is quoted around the required layouts and editing needs. A separate Figma file or standalone frontend export is not included by default in that option; any additional design phase should be agreed.

An editable site still needs an approval process. The person able to publish a paragraph is not necessarily the person responsible for confirming its clinical accuracy. The template versus custom-design guide helps evaluate the design starting point within the chosen platform.

Draw the boundary around the appointment journey

Describe the intended route in plain language. Does the visitor call reception, submit a request or use an existing external booking provider? What happens next, and who confirms it?

For an external system, identify who owns the account, configures availability and handles support. For a request form, identify who implements delivery, checks receipt and responds. The website’s wording should match that process.

Do not expand a general website commission into collection of clinical documents or detailed health histories by adding fields informally. Such functions need a separately agreed workflow and suitable provider arrangements with the practice’s responsible team.

Assign responsibilities before they fall between suppliers

Workstream Responsibility to name Evidence of completion
Team and service content Practice approver and content coordinator Current, approved material for the agreed pages
Interface design Designer Reviewed layouts, states and source deliverables
Implementation Developer or CMS provider Working pages and agreed editing functions
Enquiry or booking route Implementer, practice and relevant provider Tested handoff, receipt and truthful outcome wording
Publication Person with authorised domain and hosting access Agreed live checks and a recovery plan
Ongoing updates Practice, support provider or both Access, instructions and clear support boundaries

One person may cover several roles. The important point is that every necessary task has an owner and an observable finish line.

Include success and failure states in the handover

A request journey should explain whether the action succeeded, what information needs correcting and what to do if the route is unavailable. The W3C guidance on form notifications highlights the importance of clear feedback for successful and unsuccessful submissions.

For a practice, the message must also describe the correct event. “Your request has been received” is different from “Your appointment is confirmed”. Review the page, acknowledgement and staff process together.

The guide to contact-page response expectations develops that distinction. Include the required wording and behaviour in the design and implementation scope so it is not improvised at launch.

Use portfolio examples to discuss interaction clarity

Vocadira is a self-initiated learning app whose portfolio presentation explains the difference between a demonstration and saved progress. That is a useful reference for making the consequence of an action explicit.

For a dental website, the transferable principle is to state what a button actually does. The app is not a clinical booking system, and its technical setup should not be treated as a ready-made solution for patient information.

The Web Design portfolio provides other references for hierarchy and responsive presentation. Use them alongside the responsibility map, not in place of a functional specification.

Define the handover and continuing work

Ask which files, accounts, instructions and backups are included. Confirm who publishes the site, who can make changes and how support requests are handled after the agreed handover.

Separate routine content editing from technical maintenance and external-service administration. A practice may manage its own opening hours while a provider handles platform updates. Both responsibilities need a clear arrangement.

Use the dental website quote-comparison guide to compare the costs, then the project-timeline guide to schedule content approval, implementation and provider testing in a workable order.

Questions about what to commission

Can we hire design first and development later?

Yes, but identify the likely platform and implementation constraints early. The handover should give the future developer enough information to build the agreed experience.

Does a WordPress site include appointment software?

Not automatically. Specify whether the site links to a provider, embeds an agreed tool or needs additional integration work.

Who should write the clinical information?

Agree content creation separately and have the practice’s appropriate professional approve clinical statements. A website design fee should not be read as clinical authorship or approval.

Define the right assignment with SavianoDesign

Share the existing tools, the people involved and the deliverables you need. SavianoDesign can scope the website design, frontend or WordPress work and identify external responsibilities before the project begins.

Define your dental website project scope

From the portfolio.

More Web Design work
Vocadira Italian landing page with a sample English vocabulary flashcard and purple calls to action

Web Design

Vocadira

Self-initiated project

A vocabulary learning web app for Italian speakers, combining word discovery, Italian meanings and spaced repetition in a focused, browser-based experience.

3dskillup homepage introducing 3D assets, learning resources and tools with bold black typography

Web Design

3DSkillUp

Self-initiated project

A separate creative platform bringing together game-ready 3D assets, practical tutorials and resources for artists.

Aster House boutique hotel homepage with Mediterranean architecture, large serif text and stay-booking links

Web Design

Aster House

Personal concept

An editorial hospitality concept, combining a Mediterranean visual direction with responsive front-end development.

Keep exploring.

All insights
All services

Have a website in mind?

Let’s make your
next step clear.

A short outline is enough to start a conversation.

Discuss your project View my 99designs profile

5.0 / 5 from 25 reviews on 99designs. Read client feedback.