METHODOLOGY
How we ship in 2 to 3 weeks. And what that does — and does not — mean.
Orkids is a Philippine AI engineering firm that builds custom, agent-native operations software for Philippine enterprises — owned outright, with source code on day one — replacing SAP, Salesforce, Oracle, and Odoo in two to three weeks at ten to thirty percent of leading-ERP cost. This page defends every number on the receipts wall and is honest about the edges.
How a 3-week deployment actually works
- Day 0–2Discovery30-min call + technical deep-dive
- Day 3–5ScopeFixed-price proposal · SOW + DPA
- Day 6–12PrototypeWorking prototype in your data
- Day 13–18BuildProduction hardening + integrations
- Day 19–21CutoverGo-live. Ownership transfers.
Three weeks is signed-SOW to production cutover on a scoped module of comparable surface area to a top-ranked Philippine private hospital’s. It is possible because of architectural decisions, not heroics: we start from a hardened, multi-tenant foundation rather than a blank repository; AI accelerates scaffolding, tests, and data migrations under senior review; and we scope to one module at a time so there is no 400-table discovery phase. Larger scopes take longer and we say so in the proposal. We have never missed a stated date.
See the 3-week a top-ranked Philippine private hospital engagementHow we ship features in 24 to 48 hours
We tell you on the call which bucket your request falls into.
Once a system is live, a new report, a new workflow inside an existing module, a new API integration, or a UI change behind a feature flag ships in 24 to 48 hours. This is a deployment pipeline designed for fast iteration: every change is previewed in a real environment before reaching your production, and an on-call account manager tells you on the call which bucket your request falls into. New core modules are not in this bucket, and we say so.
See the 24-hour feature ship cadence on the Enterprise B2B Provider engagementWhat “ERP replacement” actually means at Orkids
When we say we replace Oracle or Epic, we mean a scoped module of comparable surface area to what the incumbent was quoted for — not Epic’s full 400-module suite. At a top-ranked Philippine private hospital we replaced the patient-feedback module HappyOrNot had been running at ₱500K/mo and delivered the tamper-evident audit layer Oracle and Epic had quoted ₱15M–₱50M to provide. Each receipt names the exact scope shipped and the exact scope the incumbent quote covered. We will not let a headline number imply more than we delivered.
If your need is the entire integrated suite — registration, billing, pharmacy, lab, imaging, EMR, and revenue cycle as one certified product — that is not a three-week module. We will tell you that on the first call.
See exactly which scope was replaced at a top-ranked Philippine private hospitalYou own what we build
Like buying a building versus renting an office. When you buy a building, the deed transfers to you. You can hire any contractor to renovate it, sell it, or knock down a wall. When you rent, you are paying for access and the landlord keeps the asset. Oracle, Epic, and Salesforce rent you access. Orkids sells you the building.
Technically: at cutover we transfer the source code, the database schema, the deploy keys, and the GitHub repository to your organization. No license. No annual increase. No exit fee. You can run the system without us, fork it, audit it, or hand it to another vendor. If you keep us, it is by choice every month, not by contract. For Optimize engagements there is no new code to transfer — the configuration changes, runbooks, and playbook are yours.
GitHub repository transfer at cutover
“Upon Acceptance, Developer shall transfer to Client all right, title, and interest in the Source Code, Database Schema, Deployment Credentials, and the GitHub Repository…” [sample IP-transfer clause — full text available under NDA]
Honest limits
Where we lose. Where we don’t go. Why incumbents take longer.
Where we say no
- No hardware. We do not supply, install, or maintain physical devices, networking, or on-floor equipment.
- No org-wide change management for 5,000+ people without a partner. We build the system; rollout at that scale needs a change-management partner, and we say so.
- No US HIPAA or EU GDPR engagements without local co-counsel. We will not pretend to carry jurisdictions we are not staffed to carry.
Why incumbents take 18 months
The 18-month timeline is rational for the incumbent’s model, not snark. A global vendor sells one configurable suite to thousands of customers, so every deployment becomes a configuration-and-integration project across hundreds of modules, run through a systems integrator who bills monthly. Discovery alone maps a 400-table schema you mostly won’t use. That fits when you need the full certified suite — and is expensive overkill when you need one module.
When we’re not the right answer
A regulatory mandate names a certified system
When a regulator requires a named, certified platform — a Joint Commission-certified US hospital EMR — you must run that product. We are not it.
A BSP-required certified core banking platform
Where BSP or your risk framework mandates a certified core banking system, the certification is the point. We integrate with it; we do not replace it.
You need the full integrated suite at once
If the requirement is every module, certified and supported as one product, deployed org-wide simultaneously, the incumbent’s model fits and ours does not.
Start here
Three ways to take the next step.
- 01
Read a receipt
See exactly what we delivered for a top-ranked Philippine private hospital, an Enterprise B2B Provider, or a Manila Financial Group.
Receipts - 02
Talk to a founder
We name what we’d replace, what we wouldn’t touch, and what success looks like. No procurement loop.
Book - 03
Email Dr. Po directly
Senior-team-only. The founder reads and responds within 24 hours.
helen@orkids.ph