01
The dilemma
A practising doctor wanted a professional website, the ability to sell products online, and lead inquiries that reached the right person. What they did not want, and should not have had, was any responsibility for hosting, servers or technical maintenance.
What was breaking
- No responsive, professional web presence. The clinic needed a site that worked properly on the phones most patients would use to find it.
- No route to selling products online. The practice wanted to sell to patients directly and had no storefront.
- Inquiries had nowhere to go. Website interest was not being captured into any system or assigned to anyone.
- No technical capacity, and none wanted. A clinic should not be administering hosting. Any solution that required it would fail within months.
- A cross-region delivery problem. The site was built in a US-region development account and had to end up in the client's own Europe-region account without being rebuilt.
The cost of standing still
A clinic with no online presence and no inquiry capture loses patients silently, they search, they do not find, and nobody ever knows. The technical maintenance question matters just as much: a site the client cannot maintain becomes an abandoned site within a year.
02
The idea
We chose the platform for what would happen after handover rather than for what was possible during the build. A site the doctor could edit without technical skill, a store integrated rather than bolted on, and no hosting to administer. The cross-region transfer was the awkward part, and we resolved it through the vendor's own support channel rather than rebuilding the site in the target account.
The principles we worked to
- Optimize for the client after handover. Editable without technical skill, or it will not be edited.
- Integrated store rather than a separate storefront. One system, one login, one place where inquiries and orders live.
- CRM capture from day one. Lead capture and email assignment configured as part of the build, not as a later addition.
- Transfer, do not rebuild. The account migration was handled properly instead of being solved by duplicating work.
What we ruled out, and why
| Option considered | Why we did not take it |
|---|---|
| A self-hosted content management system | More flexible, and it would have handed a medical practice a maintenance and security obligation it had no capacity to meet. |
| A separate e-commerce platform alongside the site | Two systems, two logins, two sets of data, for a clinic selling a modest product range. |
| Rebuilding the site in the client's own account | The straightforward workaround for the region problem, and it would have charged the client for the same work twice. |
03
The build
Three parts, plus a migration handled properly.
Responsive website
A fully responsive site built on a managed platform, editable by the clinic without technical skill and with no hosting or server administration required.
Integrated online store
A store feature incorporated into the site, allowing the practice to sell products online within the same system that runs the website.
CRM lead capture and assignment
Website inquiries captured into the CRM with assignment by email, so an inquiry reaches a person rather than an inbox nobody owns.
Cross-region account transfer
The completed site transferred from the development account in the US region into the client's own Europe-region account through the platform's support process, preserving the build rather than recreating it.
04
The impact
| Measure | Before | After |
|---|---|---|
| Web presence | None or inadequate | Fully responsive, professional site |
| Product sales | In person only | Online store integrated with the site |
| Inquiry handling | Uncaptured | CRM capture with email assignment |
| Content editing | Required a developer | Self-service, no technical skill needed |
| Hosting and servers | Would have been the clinic's problem | None to manage |
| Account ownership | Site in a developer's account | Transferred into the client's own account |
Beyond the numbers
- The clinic owns and controls its own site. Design and content can be changed without a developer, in the client's own account.
- The online store runs alongside the practice. Product sales added without adding operational burden.
- No infrastructure responsibility. Nothing to patch, host, back up or renew.
05
What comes next
The engagement continues. These are the next moves on the table.
- Appointment booking integrated with the practice calendar.
- Patient communication sequences from the same CRM.
- Product subscription and repeat ordering.
Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.
