HMI MedicalRegency Specialist Hospital & Mahkota Medical Centre
A dual-brand WordPress ecosystem built on a shared design framework — engineered for patient-first navigation, multi-language depth, SEO preservation through migration, and the scale to absorb future hospital brands within the HMI group. This proposal sets out our recommended approach, two homepage directions, team structure, phased timeline and commercial offer ahead of the 9 October 2026 go-live.
Nick Rowe
CEO & Co-Founder / Saigon Digital
“Saigon Digital transformed how Ski.com shows up online. Beyond rebuilding our platform, they helped us rethink our entire search and AI visibility strategy. We saw a significant uplift in organic traffic, our content started appearing in AI-generated recommendations, and the quality of inbound leads improved dramatically. They understand where digital discovery is heading and how to turn visibility into real commercial results.”
15+ years building scalable, multi-brand and multilingual digital ecosystems across healthcare, enterprise, education and hospitality.
View Case Studies →The Brief Behind the Brief
Reframing the RFQ from "two website rebuilds" into the right strategic problem
This is not two websites — it is a hospital group platform
On the surface, the RFQ describes two website rebuilds — Regency Specialist Hospital in Johor Bahru and Mahkota Medical Centre in Melaka — sharing a parent theme and launching together on 9 October 2026. Read more carefully, and the real ambition is bigger: HMI Medical is building the digital chassis for the entire group. Future hospital brands need a route in; international patients across Singapore, Indonesia and beyond need a clearer journey; the marketing team needs to stop waiting on developers to publish a campaign page.
Treat each site as a one-off and the group inherits two more silos to maintain. Treat them as the first two instances of a shared healthcare platform — with a governance model, reusable templates, structured doctor and specialty data, and an SEO migration discipline — and HMI gets an asset that compounds in value with every new brand it adds.
What the RFQ really asks for
A design and development partner — not just a vendor — who can lead two hospital brands through discovery, design, build, content migration, multi-language rollout, SEO preservation and launch inside an 18-week window, while leaving HMI with a platform their team can run, extend and replicate without going back to a dev shop every Monday morning.
Six business outcomes driving this rebuild
Findability
Patients can't currently find the right doctor or specialty quickly — the doctor directory needs first-class search, filtering and discovery UX.
Conversion
Enquiries and appointments are leaking. Every page needs intent-aware CTAs (appointment, WhatsApp, emergency, international team) without becoming noisy.
International growth
Indonesia, Singapore and Chinese-speaking markets are real revenue. The platform needs proper market hubs, not just translated copy.
SEO equity
~640 unique English pages plus three translated versions per site means a migration of ~2,500+ URLs. Protect the ranking equity or pay for it in paid media for years.
Editorial independence
Marketing teams shouldn't need developers to ship a campaign page or update a doctor profile — the CMS needs to be a real authoring tool, not a developer's afterthought.
Repeatability
This is the template for hospital #3, #4, and #5. The parent theme, design system and content models must be built with that in mind from day one.
What Makes This Hard
The five things that quietly decide whether this project ships on time, on brand, and on equity
Five risks worth naming before week one
The brief is generous with detail, but most of the delivery risk lives in the white space between the bullet points. Here is what we believe deserves explicit attention from the outset.
01 · Two brands, one system, without flattening either
Regency and Mahkota cannot share a homepage. Regency is the modern specialist destination in Johor Bahru; Mahkota is the heritage anchor brand in Melaka with a deep Indonesian patient base. They serve different catchments with different brand promises — but they must share a component library, doctor data model, page templates and editorial workflow, or the group will pay for the same work twice. The design challenge is to express two distinct brand worlds inside one reusable system: same building blocks, different soul.
02 · ~2,500 URLs and four languages without breaking search
Across both sites, you have roughly 640 unique English pages — with parallel Bahasa Malaysia, Chinese and Indonesian versions. That is 2,500+ URLs to map, redirect and recover, plus structured hreflang, canonical and schema work. Without a disciplined SEO migration plan, double-digit traffic losses are the default outcome, not the exception — and traffic is patient pipeline.
03 · Doctor & specialty data is the spine, not a content type
~170 doctors, ~115 specialty/treatment pages, ~75 health-screening & condition pages. If these are built as freeform WYSIWYG pages, you'll be wrangling inconsistencies forever — and the directory search will never work properly. The right move is a structured content model (doctor ↔ specialty ↔ treatment ↔ condition ↔ location), so the same data powers the directory, related links, schema and AI-search citations.
04 · Translation governance, not just translation
Translating once is easy. Keeping four languages in sync across a doctor's schedule, a screening package price, a campaign promo, or a corrected specialty description — that is the real cost. The CMS needs to surface translation status per field, support per-language editorial workflows, and prevent untranslated content from going live silently.
05 · 18 weeks is achievable, but only with parallel tracks
From 8 June discovery to 9 October launch is 18 weeks. That works only if design, development, content migration, translation and SEO move as parallel workstreams from week three, with locked design system milestones, a content freeze gate, and a fully rehearsed staging launch two weeks before go-live. We’ve sequenced the plan accordingly.
What we explicitly will not do
We will not propose a like-for-like migration. The current sites carry years of accumulated pages that no longer earn their keep. Part of discovery is auditing what stays, what merges, what redirects and what dies — protecting the SEO value while shedding the dead weight.
One Platform, Two Brands, Four Languages
The architecture decision that unlocks everything else
A shared parent theme. Two independent child themes. One source of truth.
We recommend a shared parent theme + per-brand child theme WordPress architecture, running on two separate WordPress instances. The parent theme owns every reusable building block — component library, doctor and specialty data models, multilingual scaffolding, schema, accessibility primitives, performance budget. Each child theme owns the brand expression — typography, colour, photography treatment, motion and the brand-specific homepage and landing-page templates.
This is the same architectural pattern Mayo Clinic, Bumrungrad and Mount Elizabeth use across their group ecosystems, and it’s designed so that adding hospital #3 means a new child theme, not a new project.
🔗 Shared parent theme (group-owned)
Owns the platform. Built and maintained centrally so every hospital brand inherits improvements automatically.
- • Reusable component library (40+ blocks)
- • Doctor / Specialty / Treatment / Condition data models (ACF Pro)
- • Multilingual scaffolding (WPML or Polylang Pro)
- • Schema.org medical markup
- • Accessibility, performance & security baseline
- • Search, filter and directory engine
🎨 Per-brand child themes (brand-owned)
Owns the experience. Each hospital can express its brand fully without forking the platform.
- • Brand typography, colour, motion & iconography
- • Brand-specific homepage layout
- • Photography & art-direction system
- • Brand-led campaign & landing page templates
- • Brand-specific microcopy & tone
- • Localised market hubs (e.g. ID, SG)
Five parallel workstreams, one weekly cadence
Patient journey, IA, wireframes & UX research
- Stakeholder workshops — one per hospital, plus a group-level session
- Patient persona work across local, international & corporate audiences
- Information architecture refinement & sitemap sign-off
- Wireframes for all template types — doctor, specialty, treatment, screening, article, campaign
- Conversion-flow mapping for appointments, enquiries, screening bookings
Shared design system + two distinct brand expressions
- Master design system — tokens, components, motion principles, accessibility rules
- Regency child brand — modern specialist, premium clinical, calm precision
- Mahkota child brand — heritage anchor, warmth, established trust, regional resonance
- Homepage and template UI for both brands
- Design QA and accessibility (WCAG 2.2 AA) sign-off
WordPress parent theme, child themes & CMS configuration
- Shared parent theme — built component-first, version-controlled, documented
- Two child themes wired to the shared design system
- Custom post types & relationships — doctors, specialties, treatments, conditions, articles
- Doctor directory search engine (name, specialty, language, location filters)
- Multilingual setup, schema, sitemap, performance budget, analytics layer
- Headless option open via WordPress REST/GraphQL for future Next.js front-ends
Protect equity. Migrate content. Localise properly.
- Full URL audit — rank, link, value, intent — per hospital
- Keep / merge / redirect / kill decision per page, signed off with HMI
- 301 redirect maps for ~2,500 URLs across both sites
- Schema.org medical, doctor & FAQ markup baked into templates
- Translation governance: per-field translation status, fallback rules, hreflang
- Post-launch ranking monitoring & recovery (90-day window)
Stage. Rehearse. Train. Launch with confidence.
- Cross-browser, cross-device, cross-language QA matrix
- Performance, Core Web Vitals & accessibility certification
- Rehearsed launch in staging two weeks before go-live
- CMS training sessions (Editor + Marketing + IT) — recorded
- Launch playbook, monitoring dashboard, and 30-day warranty
Two Brands. One System. Two Stories.
Click each concept to view the full homepage mockup in detail
How we’d differentiate Regency & Mahkota
A homepage is not a brochure — it’s the patient’s first triage step. The job of each homepage is to answer five questions in under ten seconds: Am I in the right place? Can I find my doctor? Can I book a thing? Is this hospital for someone like me? What do I do in an emergency?
We’ve deliberately taken the two hospitals in two distinct visual directions — not the usual sister-brand wallpaper exercise. Regency borrows from the BUPA UK playbook: confident bright blue, search-first hero, clean white cards — a modern specialist destination built for the cross-border Singapore patient who expects clinical precision. Mahkota stays rooted in its hunter-green heritage and burgundy-gold accents — but introduces an industry first: Dr·Mahkota AI, a ChatGPT-style multilingual hospital concierge baked into the homepage. Same component library underneath. Two genuinely different brand worlds on top.
when it matters most.
Same component library, two genuinely different brand worlds — one industry-first feature
Underneath the surface, both sites share the parent-theme component library — hero patterns, doctor cards, screening cards, accreditation strips, sister-brand footer. On the surface, the two are deliberately distinct: Regency takes a BUPA UK approach (bright blue, search-first, white cards, yellow accents) signalling modern specialist confidence to the Singapore cross-border market; Mahkota keeps its heritage hunter-green, gold and burgundy gravitas — and adds the standout feature of either site, Dr·Mahkota AI. Built on Claude / OpenAI with a guardrailed clinical knowledge base, it answers symptom, doctor, cost and admission questions in 4 languages, books appointments inside the chat, and routes every clinical escalation to a human specialist. It’s the kind of differentiator most Malaysian private hospitals won’t ship for another 18 months — HMI ships it at launch. Build it once, brand it twice, lead the market.
Refining the Sitemap
Our recommended refinements to the IA framework in your RFQ
Building on your directional structure
Your RFQ provides a strong directional sitemap. Through discovery we’d expect to refine three things: the Find-a-Doctor experience, the Specialty / Treatment / Condition hierarchy, and the International Patient hubs. Below is how we’d evolve the structure.
1Find a Doctor
Promote from a nav item to a first-class search experience. Predictive search (name, specialty, language, condition), faceted filtering, day-of-week availability surfaced inline. Structured data feeds the directory, related-doctor blocks across the site, and schema for Google & AI search.
2Specialties & Centres of Excellence
Two-level structure: Specialty (e.g. Cardiology) → Sub-specialty / Centre (e.g. Interventional Cardiology). Each surfaces related doctors, treatments, conditions and screening — auto-populated from content relationships, not hand-maintained.
3Treatments & Conditions
The SEO engine room. Each treatment / condition page follows a structured template with FAQ, related doctors, related screening and clear CTA. Schema-marked for Google & AI citation. This is where most organic search value lives.
4Health Screening
Promote screening packages to a high-conversion product-like experience: filter by audience (men / women / executive / corporate), inclusions, price, duration. Inline booking, not a contact-form bounce.
5International Patients
Move from a single page to a hub with per-market spokes (Singapore, Indonesia, others). Each market gets its own value proposition, partner clinics, currency guidance, language and contact route — localised, not translated.
6Patient Information
The "before you arrive" section. Admissions, insurance, payment, facilities, visiting hours, emergency — combined into a single Patient Hub with clear cards and progressive disclosure rather than a long sub-nav.
7Health Library
Articles, news, events — with proper taxonomy (specialty, condition, audience) so content reinforces commercial pages through internal linking, not just sits in a blog silo.
8About, Careers, Contact
Streamlined. Careers gets employer-branding treatment with structured job listings (or ATS integration). Contact gets per-department routing, embedded maps & emergency information.
What the navigation pattern looks like at scale
One mega-menu pattern, two brand expressions. Doctors first, specialties second, treatments third, screening fourth, international fifth. The order of the top-five reflects how a patient actually decides — "who treats me?" before "where do I go?" before "what does it cost?". Bottom-of-page utility (Appointment / WhatsApp / Emergency) is sticky and global.
The Recommended Build Stack
Right for the brief, right for the timeline, right for HMI's editorial team
WordPress — configured the way it should be
Your RFQ specifies WordPress, which is the right call — both for editorial independence and for hospital-group repeatability. The risk with WordPress is not the platform itself; it’s the way it’s usually configured. We propose a modern, opinionated stack designed for governance, performance and content modelling — not a Frankenstein of off-the-shelf plugins.
| Layer | Choice | Why |
|---|---|---|
| Core CMS | WordPress 6.x (latest LTS) | Editorial familiarity, vast translation tooling, future-proof. |
| Architecture | Shared parent theme + per-brand child themes | Scales to hospital #3, #4, #5 without re-building the platform. |
| Content modelling | ACF Pro + Custom Post Types & Relationships | Structured doctor / specialty / treatment / condition data — not freeform pages. |
| Page building | Block library (native Gutenberg blocks, custom-built) | Editorial flexibility without the page-builder lock-in or performance penalty. |
| Multilingual | WPML or Polylang Pro (final choice in discovery) | Per-field translation status, hreflang, fallback rules, market-aware URL structure. |
| SEO | Yoast SEO Premium + custom schema layer | Editorial-friendly metadata + medical / doctor / FAQ schema baked into templates. |
| Forms & lead capture | Gravity Forms + CRM webhook layer | Appointment, enquiry, screening forms wired to HMI's CRM & tracking layer. |
| Search | Custom doctor / specialty / treatment search engine | Predictive, faceted, fast — not a stock WordPress search. |
| Hosting | Managed WordPress (WP Engine / Kinsta / Rocket.net) | Performance, CDN, staging, daily backups, malware scanning — standard. |
| Performance | Core Web Vitals budget enforced in CI | Hospitals are mobile-first — performance is a clinical-care signal. |
| Analytics | GA4 + GTM + server-side tagging option | Reliable conversion tracking, future-proof against ad-blockers. |
| Future option | Headless via WordPress REST / GraphQL + Next.js | If HMI ever wants a true app-grade experience, the data layer is already there. |
AI-search and discoverability readiness, baked in
Beyond traditional SEO, we instrument the platform for the next layer of search: AI Overviews, ChatGPT, Perplexity and Claude are increasingly the first place patients look. We bake in schema.org Medical / Doctor / FAQ / Article markup, llms.txt scaffolding, structured citation-friendly content blocks, and AI-bot crawl access (GPTBot, ClaudeBot, PerplexityBot). This is the work we’ve done for Ski.com that drove visibility in AI-generated travel recommendations — we’re proposing the same discipline for HMI.
We Own the Entire Data Layer.
Measurement, attribution, dashboards and insight cadence — built once across both hospitals
Analytics is not a plugin you bolt on at the end
Most hospital websites have broken measurement — events firing inconsistently, ad-blockers wiping out half the data, no link between “form submitted on the website” and “patient who actually showed up,” and a dashboard that nobody on the executive team opens twice. The cause is almost always the same: analytics was a checkbox at the end of the build instead of an architecture decision at the start.
On this project, Saigon Digital owns the entire data layer end-to-end — from the first GA4 event to the monthly executive dashboard HMI’s leadership reviews. No third-party analytics consultant. No “we’ll figure it out after launch.” The conversion model is defined in discovery, instrumented during development, validated at staging launch, and tuned in the first 90 days. By the time the sites go live on 9 October 2026, HMI’s leadership team has working dashboards on day one — not promises.
The Five-Layer ArchitectureHow the data layer is built
A unified server-side tracking layer for both hospitals. GA4 + Google Tag Manager (server-side container) means events are captured at our edge before the browser, immune to ad-blockers and iOS privacy-killers. One naming convention across Regency & Mahkota — comparable data from day one.
We define what counts as a meaningful patient action in discovery — not later. Booked appointment, enquiry form, screening package selected, WhatsApp click, doctor profile view, treatment cost-estimator completion, health library deep-read. Each event carries dimensions: language, hospital, specialty, source — so every report can slice by what matters.
A CRM webhook bridge closes the loop between “website behaviour” and “real patient.” When an appointment form submits, we attach the GA4 client ID + first-touch + last-touch source to the CRM record. HMI can finally answer: “Of the patients who actually walked in last quarter, where did they first find us?”
Three pre-built Looker Studio dashboards ready on launch day. (1) HMI Group Executive — both hospitals side by side, traffic, leads, top sources, language mix. (2) Per-hospital operations — Regency or Mahkota deep dive. (3) SEO & AI-search visibility — rankings, AI-citations, share of voice vs competitors.
Raw data is not insight. Each month for the first 90 days post-launch, we deliver a written executive briefing — what moved, why, what to do next. Beyond 90 days, the Care Plan includes ongoing insight reviews. We surface the findings; HMI’s team makes the decisions.
HMI executive view, day one
A directional preview of the group-level dashboard. Real metrics replace these placeholders when live traffic flows.
Looker Studio · Live PreviewHMI Group · Patient Acquisition Dashboard
The full capability set
🛡️ Server-side tracking
Events captured server-side — immune to ad-blockers, iOS privacy filters, and consent-mode dropouts. Restores the 30–40% of patient signal most hospital sites silently lose.
🎯 Defined conversion model
~14 primary conversion events and ~30 micro-conversions agreed in discovery, instrumented during development, validated before launch. Not invented after the fact.
🔗 CRM attribution loop
Form submissions write the GA4 client ID + source attribution into the CRM record. Closes the gap between “website said yes” and “patient actually arrived.”
🌏 Per-language insight
Bahasa, Chinese, English and Indonesian patient journeys reported separately. The Indonesian segment alone is the difference between Mahkota’s good year and great year.
📊 Group + per-hospital dashboards
HMI leadership opens one URL and sees both hospitals side by side. Hospital teams have their own focused view. Same data spine, different lens.
📝 Monthly insight briefings
A written executive briefing every month for 90 days post-launch: what moved, why, and what to do next. We surface the findings; you make the decisions.
Why HMI doesn’t need a separate analytics partner
Most agencies build the website and hand off analytics to a specialist — which is when measurement breaks, because the people who instrumented the events aren’t the people defining the dashboards. We do both, because they’re the same problem. The same engineer who configures the appointment form configures the GA4 event, the GTM trigger, the CRM webhook, and the Looker Studio data source. One throat to choke, one team accountable to one number: did the patient book?
What's In, What's Out
The deliverable list, by workstream
Scope by workstream
| Workstream | Included Deliverables | Volume / Notes |
|---|---|---|
| Discovery & Strategy | Stakeholder workshops, persona development, IA & sitemap, journey mapping, content audit, redirect strategy, KPI definition | 3 weeks · both hospitals + group |
| UX / Wireframing | Wireframes for 11+ templates: homepage, doctor profile, doctor directory, specialty hub, sub-specialty, treatment, condition, screening package, article, campaign / landing, contact, about, careers | ~12 unique template wireframes |
| UI Design | Master design system (tokens, components, motion, accessibility), two brand expressions (Regency, Mahkota), homepage designs, all template UI, mobile-first comps | Figma library + 2 brand kits |
| Engineering — Parent Theme | Component library, doctor / specialty / treatment / condition data models, multilingual scaffolding, search engine, schema layer, performance budget, security baseline | One shared codebase |
| Engineering — Child Themes | Two child themes (Regency, Mahkota) wired to design system, brand-specific templates, brand styling, child-theme documentation | 2 child theme codebases |
| Content Migration | Page-level keep / merge / redirect / kill decisions, content cleanup, structured data population, doctor & specialty content modelling, image optimisation | ~640 EN pages base + 3 langs |
| Translation Implementation | WPML / Polylang Pro setup, per-language editorial workflows, hreflang & canonical, market-aware URL structure, translation status tracking | 4 languages × 2 sites |
| SEO Migration | URL audit, 301 redirect maps, hreflang & canonical strategy, on-page SEO setup, schema markup, sitemap generation, 90-day post-launch ranking monitoring | ~2,500 URLs across both |
| Forms & Integrations | Appointment forms, enquiry forms, screening booking forms, WhatsApp click-to-chat, GA4 + GTM, call tracking readiness, CRM webhook layer | Per-brand & per-language |
| QA & Launch | Cross-browser, cross-device, cross-language QA, accessibility (WCAG 2.2 AA) certification, performance (Core Web Vitals) certification, rehearsed staging launch, launch playbook, monitoring dashboard | 2 weeks dedicated QA |
| Training & Handover | CMS training (Editor + Marketing + IT), recorded sessions, written editor handbook, role-based permission setup, draft / review workflow training, 30-day launch warranty | 3 training cohorts |
Out of scope (unless added)
Photography & videography production · Copywriting from scratch (we edit, structure and migrate — new long-form copy is an add-on) · Translation content (we implement the system; translation vendor co-ordinated separately or quoted as an add-on) · Paid media · ATS integration (Greenhouse / Workable etc. — quoted on request) · Hosting fees (passed through at cost or managed by HMI IT).
Who You'll Work With
Dedicated team, senior-led, with hospital-group experience
A senior, embedded delivery team
All roles are senior-led and have shipped multi-brand, multilingual platforms. You'll have one point of contact (the Account Director) and direct access to the leads of each workstream.
Nick Rowe
Account Director & Strategy Lead
CEO, Saigon Digital
Senior PM
Project Manager
Weekly cadence & escalations
UX Lead
Research, IA & wireframes
Patient journey owner
UI Design Lead
Design system + 2 brand worlds
Figma library owner
Lead Engineer
WordPress senior engineer
Parent theme owner
Engineers × 2
Child theme + integrations
Forms & search
SEO Lead
Migration, schema & AI-search
~2,500 URL discipline
QA Engineer
Multi-language QA matrix
Accessibility & performance
You speak to leads, not account managers
At Saigon Digital we don’t insulate clients from the people building the work. You’ll be in weekly working sessions with our design and engineering leads — not a layer of account managers relaying messages. That’s how the timeline holds.
18 Weeks to Go-Live
8 June 2026 → 9 October 2026 · phased, parallel, predictable
Six phases, five parallel tracks
The 18-week window is achievable — provided we run design, development, content migration, translation and SEO as parallel workstreams from week three onwards. Below is the phase-level view, with the Gantt overview underneath.
- Stakeholder workshops
- Persona & journey work
- IA & sitemap sign-off
- Content audit
- SEO baseline
- Brand discovery
- Wireframes — 12 templates
- Design system
- Regency brand UI
- Mahkota brand UI
- Design QA & sign-off
- Parent theme build
- Child theme × 2
- Data models & CMS
- Doctor search engine
- Forms & integrations
- Content migration × 2
- Translation implementation
- Schema population
- Image optimisation
- Per-language QA
- Cross-browser QA
- Accessibility & CWV cert.
- SEO migration QA
- CMS training
- Rehearsed staging launch
- Production cutover
- 301 redirect activation
- Ranking monitoring
- 30-day warranty
- 90-day SEO recovery
Key dates & gates
8 June: Kickoff · 26 June: IA / sitemap sign-off gate · 17 July: Design system locked · 14 August: Content freeze gate · 11 September: Staging launch & UAT begins · 25 September: Final UAT sign-off · 9 October: Go-live · 9 November: 30-day warranty closes · 9 January 2027: 90-day SEO recovery report.
Commercial Proposal
Pricing transparent, separated by deliverable category — per the RFQ
Investment by deliverable category
All figures USD. Pricing is fixed-scope for the deliverables in section 08. Excludes hosting, photography production, translation content fees, and any add-ons listed below.
| Category | Deliverables | Investment (USD) |
|---|---|---|
| Discovery & Strategy | Workshops, IA, sitemap, journey maps, content audit, KPI framework | $6,000 |
| UX / UI Design | Wireframes, design system, two brand expressions, all template UI, mobile | $24,000 |
| Development | Parent theme + two child themes, CMS, data models, search, forms, integrations | $40,000 |
| Content Migration | ~640 EN pages keep / merge / redirect / kill, structured content population, image opt. | $13,000 |
| Translation Implementation | Multilingual setup (BM / CN / ID) × 2 sites, hreflang, per-language workflows | $9,000 |
| SEO Migration & Redirects | ~2,500 URL audit & redirect map, schema, 90-day post-launch monitoring | $6,000 |
| Analytics & Data Layer | GA4 + GTM server-side, conversion model, dashboards, CRM attribution, multilingual segmentation | $7,000 |
| CORE BUILD TOTAL | End-to-end delivery, 8 June → 9 October 2026 | $105,000 |
This quotation — Regency Specialist Hospital
For procurement, the total project investment is split equally between the two HMI hospital entities. The scope above is identical across both documents; this quotation covers Regency Specialist Hospital Sdn Bhd’s 50% share.
| Billed to | Detail |
|---|---|
| Entity | Regency Specialist Hospital Sdn Bhd |
| Company Registration | 767174-W |
| Address | No. 1 Jalan Suria, Bandar Seri Alam, 81750 Masai, Johor, Malaysia |
| Attention | Isaiah Cheong · isaiah.cheong@regencyspecialist.com |
| Commercial summary | USD |
|---|---|
| Total project investment — full scope | $105,000 |
| Equal split across both entities | 50% |
| Regency Specialist Hospital — amount payable (this quotation) | $52,500 |
| Payment milestone | % | USD |
|---|---|---|
| On project kickoff | 30% | $15,750 |
| On design sign-off | 25% | $13,125 |
| On staging launch | 25% | $13,125 |
| On go-live | 20% | $10,500 |
| Total — Regency Specialist Hospital share | 100% | $52,500 |
One project, split for procurement
The total project investment of USD 105,000 is split equally between Mahkota Medical Centre Sdn. Bhd. and Regency Specialist Hospital Sdn Bhd for internal procurement. The scope of work is identical across both documents, and the two quotations together total the full project. This quotation represents Regency Specialist Hospital’s 50% share — USD 52,500.
Add-ons and post-launch support
| Item | Description | Investment |
|---|---|---|
| Post-Launch Care Plan | Hosting, monitoring, security, monthly updates, SEO monitoring, priority support — per hospital | $1,500/mo per site |
| Translation Content (vendor) | If HMI wants Saigon Digital to manage the translation vendor end-to-end | From $0.08/word |
| Copywriting | New long-form copy (treatments, conditions, screening, landing pages) | From $4,500 / 20 pages |
| Photography & Video | Production day in Johor Bahru / Melaka, hospital + doctor portraits | From $6,000 / hospital |
| ATS Integration | Greenhouse / Workable / BambooHR integration for careers section | From $3,000 |
| Third Hospital Onboarding | When you're ready to add Hospital #3 to the platform — new child theme + content build | From $28,000 |
How we’ve priced this — and why it’s a strong number
$105,000 for two production hospital websites, on a shared platform, with four languages, full SEO migration discipline, and the entire analytics & data layer owned end-to-end. Comparable single-hospital builds in the region typically land between $60K–$95K each — so HMI is getting two hospitals, plus group-wide measurement infrastructure, for roughly the regional price of one. The math works because the parent-theme architecture lets us build once and brand twice, and because we’re pricing for the HMI group relationship and the platform that will absorb future hospitals — not for a one-off project.
Payment terms: 30% on kickoff · 25% on design sign-off · 25% on staging launch · 20% on go-live. Invoiced in USD or VND-equivalent. Final scope, SoW and commercials confirmed post-NDA & full brief review.
What Happens After Go-Live
Warranty, SLAs and the long-term partnership model
A platform you can run — and a team behind you when you can’t
30-day launch warranty
Included free of charge. Any bug, regression or critical issue traced to our build is fixed at no cost within 30 days of go-live. Dedicated bug-triage channel.
90-day SEO recovery window
Active ranking and traffic monitoring for both sites for 90 days post-launch. Any equity loss against the baseline is investigated and remediated as part of the project.
Ongoing Care Plan
From $1,500/mo per hospital. Includes hosting management, monitoring, security patching, monthly platform updates, SEO health tracking, and priority engineering support.
| SLA | Response | Resolution Target |
|---|---|---|
| P1 — Site down / appointment booking broken | < 1 business hour | Same business day |
| P2 — Major function broken (search, forms, language) | < 4 business hours | Within 1 business day |
| P3 — Minor bug / cosmetic / non-blocking | Next business day | Within 3 business days |
| P4 — Feature requests / enhancements | Within 1 week | Scoped & quoted |
The long-term partnership we’re proposing
This RFQ is a starting point, not an end-state. The platform we’re building is designed for hospital #3, #4 and #5 to plug into. A long-term partnership model — quarterly roadmap reviews, ongoing CRO & SEO work, new hospital onboarding — is where the real compounding value sits. We’d be delighted to discuss that in person.
The Right Partner for HMI
Hospital-group scale, multilingual depth, and the discipline to ship on time
A senior, multi-brand, multilingual delivery team
Multi-brand ecosystems
Deep experience designing shared platforms that serve multiple sub-brands — from hospitality groups to education networks to multi-region SaaS.
Multilingual depth
We've shipped sites in English, Vietnamese, Bahasa, Mandarin, French, Spanish and German — with governance models that hold under pressure.
SEO & AI-search discipline
Migrations that grow traffic, not lose it. Schema-led, AI-citation-ready content architecture — the same playbook that lifted Ski.com’s visibility.
Editorial-led CMS
We configure WordPress for the people writing the content, not just the people building the site. Marketing teams stop waiting on developers.
Performance as a clinical signal
Hospitals are mobile-first patient journeys. We treat Core Web Vitals as a care-quality KPI — performance budgets are enforced in CI, not chased post-launch.
Senior-led, lean structure
You work with the people doing the work — no agency layers, no account-manager filter. That’s how the timeline holds.
Why we’d be a strong fit for HMI Medical specifically
We’ve led complex international website projects across healthcare, enterprise, education and multi-brand hospitality environments. The patterns are the same: structured content, multilingual governance, shared design systems, SEO migration discipline. We bring that pattern library to HMI — and pair it with a senior team that ships, on time, in 18 weeks.
Let’s build the platform together.
We’d welcome the opportunity to present in person to the HMI team in the first week of June — including a live walkthrough of these homepage directions, our recommended team structure and the delivery plan.
NDA signed, brief reviewed in full
Presentation & homepage walkthrough · W/C 1 Jun
Kickoff & discovery · 8 June 2026
or email nick@saigon.digital