Skip to content
Orkids

CASE · TOP-RANKED PH HOSPITAL · CEBU

ACT ONETHE QUOTE ON THE TABLE

A top-ranked Philippine private hospital, Cebu. Oracle and Epic had ₱30M on the table and an 18-month calendar. The hospital gave Orkids three weeks and ₱3M.

The systems Oracle and Epic quoted did not exist yet. The problems the hospital had — a ₱500,000-a-month feedback subscription that could not answer a PhilHealth audit question, a patient app in security debt, no unified booking, and a website Google could not even see — existed on Monday morning. Orkids fixed all of it. The hospital owns the source code.

The transformation

What the incumbent quoted, against what Orkids shipped.

Incumbent quote

Oracle Health & Epic proposals (₱15M–₱50M, 12–24 months)

HappyOrNot patient feedback subscription (₱500K/mo)

What Orkids shipped

₱3M · 3 weeks · live in production

₱3,000,000

Owned outright

ACT TWOTHE REAL PROBLEM WAS FRAGMENTATION

The client is a 600-bed top-ranked Philippine private hospital in Cebu. It did not have one problem. It had the problem almost every large Philippine institution has: fragmentation. A different vendor for feedback. A different vendor for the patient app. A different vendor, or no one, for booking. A separate system for PhilHealth attestation. None of them spoke to each other, and every vendor's answer to a new problem was the same — add another vendor.

The ₱15M–₱50M Oracle Health and Epic proposals were that pattern at the top of the market: a new ₱30M layer bolted on over an 18-month calendar, removing none of the existing sprawl. The hospital would have paid enterprise capex to make the estate bigger, not simpler — and still not owned any of it.

The single most expensive piece of that sprawl was patient feedback. The hospital was paying a third-party vendor, HappyOrNot, more than ₱500,000 a month for feedback terminals across forty-plus departments. Free-text comments in English, Filipino, and Cebuano arrived daily, were categorised by hand by a junior analyst, and reached department heads two weeks late — by which point the quarterly committee had already moved on. Meanwhile the audit team assembled every PhilHealth compliance review by hand, pulling attestation records out of three different systems.

And while Orkids was mapping the estate, it found something nobody had flagged: the hospital was effectively invisible on Google. A web application firewall, tightened after an earlier security incident, had been left aggressive enough to silently block the search crawler. The institution everyone in the city knew by name could not be found by the patients looking for it.

The feedback console — trilingual classification, urgency routing, department view.
The feedback + PhilHealth system, side by side
DimensionOracle / Epic proposalOrkids engagement
Quote₱15M – ₱50M₱3M
Timeline18 months (estimated)3 weeks (actual)
OwnershipVendor-hosted, licensedHospital-owned source code at cutover
Language supportEnglishEnglish, Filipino, Cebuano
PhilHealth alignmentRoadmap itemLive on cutover

ACT THREEWHAT ORKIDS CONSOLIDATED

One team. Four systems. One owner.

Instead of four vendors and a fifth proposal, Orkids spent the first week inside the operation — with the clinical team, the audit lead, the PhilHealth liaison, and IT — then replaced the sprawl with four systems the hospital owns. The core build ran three weeks.

01 · FEEDBACK ENGINE

₱500K/month, 40+ departments → ₱1.3M once, then ₱0

The hospital was paying over ₱500,000 a month for patient-feedback terminals across more than forty departments — a subscription that produced PDF reports a committee skimmed once a quarter. Orkids replaced it with a system that reads free-text feedback in English, Filipino, and Cebuano, classifies it by department and urgency, routes escalations the same day, and produces an audit-grade PhilHealth attestation log reviewers can verify on demand. ₱1.3M one-time. Nothing monthly after.

02 · SECURITY + SEARCH RESCUE

Invisible on Google, and nobody knew why

While mapping the estate, Orkids found the hospital was effectively invisible in search. A web application firewall — tightened after an earlier security incident — had been left so aggressive it was silently blocking Google's crawler, so patients couldn't find the hospital's own pages. Orkids diagnosed it, restored indexing, and re-hardened the security posture properly, so protection no longer meant invisibility.

03 · PATIENT APP V2

Years of security and UX debt, cleared

The hospital's patient app carried a backlog of open security issues, bugs, and a UX that fought the people using it. Orkids shipped V2: the outstanding vulnerabilities closed, the bug backlog cleared, and the interface rebuilt around how patients actually move through care — admission, results, follow-up.

04 · BOOKING SYSTEM

Scheduling, out of spreadsheets and phone lines

There was no unified way to book an appointment. Orkids built a custom booking system the hospital owns outright — appointments, availability, and confirmations in one place, wired into the rest of the estate instead of bolted on beside it.

ACT FOURWHAT THE HOSPITAL OWNS NOW

At production cutover, Orkids transferred the source code, the database schemas, and the deployment keys for all four systems to the hospital. The hospital's IT team can audit them, modify them, or move them to a different cloud provider without asking Orkids for permission. There is no annual license. There is no per-patient fee. What used to be four monthly bills to four vendors is now four systems the hospital owns outright — and the next vendor who walks in with a proposal will be quoting against working production software, not a blank page.

If you run a large Philippine operation, you have a version of this estate. A subscription nobody has re-tendered in three years. An app limping on a vendor's timeline. A compliance report still assembled by hand. A proposal on your desk to make the sprawl bigger. The hospital's win was not a cheaper feedback tool — it was refusing the premise that every problem needs another vendor. One team scoped the whole estate, built what was missing, fixed what was broken, and handed back software the institution owns. That is the engagement. Bring us your worst-fragmented workflow and we will tell you, in 30 minutes, what consolidating it actually looks like.

The receipt is public. The engagement is referenceable. Contact us for a reference call with the hospital's IT team.

Executive summary

Scope
Patient feedback AI, security + search rescue, patient app V2, and a custom booking system
Engagement
₱3M total · fixed scope · single engagement. The feedback engine alone was ₱1.3M one-time against the ₱500K/month it replaced.
Timeline
3-week core build · Cebu
Replaced
HappyOrNot ₱500K/month across 40+ departments + Oracle Health / Epic capex proposals ₱15M–₱50M
Outcome
Four consolidated systems, hospital-owned at cutover — source code, database schemas, and deployment keys. No licenses, no per-patient fees.

Take the teardown with you.

One email. The full peso comparison and the PH Enterprise Software Cost Index 2026 as a PDF. Nothing else.

One email. No sequence. Unsubscribe in one click.

Before you sign that quote, talk to a founder.

30-minute fit call. Free prototype if we agree on scope.

hello@orkids.ph · Cebu City, Philippines