Concept 02
One identity and one booking layer for a clinic group that grew by acquisition.
- Sector
- Healthcare services
- Disciplines
- Brand, Web, Software
- Year
- 2025
- Status
- Concept project
The premise
A clinic network acquires practices faster than it can absorb them. Nine sites run four booking systems and present seven visual identities. A patient moving between sites experiences it as seven different companies, and the group's marketing spend is divided against itself.
How we would approach it
- 01
One brand with room for local trust
A parent identity strong enough to unify, with a naming and endorsement structure that keeps hard-won local practice names visible rather than erasing them.
- 02
A booking layer above the chaos
Rather than migrate nine practices at once, an integration layer normalises availability across systems so the patient sees one calendar while the back office changes slowly.
- 03
Design for the anxious visitor
Healthcare interfaces are used by people who are worried. Plain language, honest pricing, obvious next step, no dark patterns and no stock photography of laughing strangers.
- 04
Publish as a network
A shared content system so a single article, protocol or clinician profile serves every location and its local search presence.
What we would build
Brand architecture and identity system
Unified booking and availability API
Accessible patient-facing web platform
Multi-location content and SEO structure
What it is meant to prove
Concept goal: make an acquired network legible to a patient before the back-office systems are consolidated, so brand integration stops waiting on IT integration.
Stated as an objective, not an outcome. This concept has not been delivered for a client, so there is no measured result to report — and we will not invent one.
Next concept
Forge
Start a project
A first conversation is a conversation, not a pitch. Bring the problem in whatever shape it is currently in — we will tell you honestly whether we are the right people for it.
- Typical first engagement
- 2–3 weeks
- Working model
- Embedded, in your tools
- Reporting
- Weekly demo, monthly review
- Handover
- Documented, always