A phased route to a nursing-home matching platform that starts by selling homes something they already want, and builds the directory as a by-product.
What we agreed in the meeting, written down so we can hold each other to it.
The goal is clear: when a family needs a nursing home for a parent, they come to one place and get matched to a home that can actually take them. Nobody disagrees with that. The question is the order of operations, and the order decides whether the platform ever has anything in it.
A matching platform lives or dies on the supply side: homes, with accurate and current information about what they can take. Families are the easy half. They arrive stressed, once, and want an answer this week. Homes are the hard half. They have no reason to fill in a profile on a directory that has no families on it yet, and even less reason to keep it up to date.
So this proposal sequences the build around four positions.
Nobody searching for a nursing home downloads an app to do it. The need is occasional, stressful and one-off. An app is the wrong first surface for the demand side, and the most expensive one to build.
Meet them where they already are. A number they message, a short conversation, an introduction to a suitable home. No install, no account, no learning curve, and it works on the phone they already hold.
A two-sided marketplace has a cold-start problem, and here it sits squarely on the supply side. A home will not maintain a listing for a platform that has not yet sent it a single family.
Sell homes a tool they want and will pay for. Onboarding to the platform becomes a side effect of the sale, and the data the tool produces every day is exactly the data matching needs.
Supply pays to be onboarded. The data stays current because the home uses the tool to run its day.
The usual directory has two failure modes. Either homes never sign up, or they sign up once and the listing rots: beds shown as available are full, a home that stopped taking dementia cases is still listed for dementia care, the contact person left last year. Families call, get turned away, and stop trusting the platform.
The wedge fixes both at once. A home buys SS Care because it wants families to stop phoning the ward and wants records with photo proof. To use it, the home registers its residents and its staff, and carers record vitals every shift. From that point on the platform knows, without anyone filling in a form:
The home never "updates its listing". It just runs its day, and the listing follows.
A home that is not ready to buy the tool can still join by a light path: one WhatsApp message to the Homes First number when a bed opens or fills. It costs the home a little, and its listing says exactly how fresh it is.
The platform's supply side is paid for by the supply side. The demand side is added only once there is something to match against.
Nothing later starts on hope. Each phase has a condition the phase before it has to meet first, so the expensive work is never begun on optimism.
Homes buy SS Care and run their day on it. Every sale is one home onboarded, with live operational data as a by-product.
One public number. A family answers a few questions and is introduced to a home that can actually take their parent.
Public pages with availability that is true today, and an enquiry console for homes. The app, if it is built, is for homes — never for families.
The two gates are the whole discipline of this plan. N and M to be agreed with Choong
SS Care is the product. Each sale is one home onboarded with live operational data, whether or not the word "platform" is ever mentioned.
What a carer and a family actually see, one shift, about twenty seconds end to end:
Only residents assigned to you
Tan Ah Kow · Room 3 Bed A
One photo per machine — camera only
Saved · Tan Ah Kow
BP 145/80 · HR 72 · 1:25pm
The family group has been updated.
This is the live product, not a design. Tan Ah Kow is a demonstration resident.
Very little that does not already exist. SS Care is built, deployed, and verified end-to-end with a real nursing home. What a carer does today:
/care to the home's WhatsApp number. A WhatsApp Flow (Meta's in-chat form) opens. Picks a resident, enters blood pressure, heart rate, SpO₂, temperature, and optionally glucose.Work needed for Phase 1 to scale beyond one home: multi-tenant hosting (one instance per home today), a hardened bot supervisor and re-linking path, backups and a photo-retention policy, and an onboarding runbook for Meta business verification.
The home. A monthly subscription per home pricing to be decided with Choong, possibly tiered by resident count. Setup (WhatsApp Business registration, staff and resident onboarding) as a one-off to be decided.
The point is that the home pays for a tool, not for a listing. Platform participation is included in the price and never sold separately.
Per home, continuously: resident roster and count; registered staff, roles and shift coverage; the record types in daily use, which is how care capability is inferred; time-of-day activity; and the home's own WhatsApp number, already verified with Meta, ready to receive enquiries in Phase 2.
The first home recording real residents on SS Care every day (not a demo). Then a second and third home onboarded from a runbook rather than by hand, each on its own verified WhatsApp Business number, each with a supervisor-managed bot and nightly backups. At that point Phase 1 is a repeatable sale.
Meta business verification is the slow gate for every new home. It is an account-state problem, not a code problem, and lead time is outside our control. Onboarding should start the verification on day one and run staff training in parallel, so it never becomes the critical path twice.
The answer is already in their group, every shift, with the evening summary at nine.
Every reading carries the instrument photo and a second opinion from the vision model. Disputes about what was recorded go away.
Carers already use WhatsApp. The form opens inside the chat they have open all day.
Carers never leave WhatsApp; the home's admin gets a web dashboard. It is built and in use for the current deployment. Records with the instrument photos and the vision check beside each reading, CSV export, residents bound to their family groups, staff and roles, and the WhatsApp connection page.
| Time | Resident | BP | HR | SpO₂ | Temp | Carer · shift | Photos | Photo check | Family |
|---|---|---|---|---|---|---|---|---|---|
| 1:25 pm | Tan Ah Kow · R3A | 145/80 | 72 | 97% | 36.6 | SN Sheila · PM | agrees | sent 1:25 pm | |
| 1:22 pm | Wong Mee Lan · R5B | 128/76 | 68 | 98% | 36.4 | SN Sheila · PM | agrees | sent 1:22 pm | |
| 1:18 pm | Abdul Rahman · R7A | 152/88 | 81 | 95% | 37.1 | SN Sheila · PM | differs · BP read 132/88 | sent 1:18 pm | |
| 8:10 am | Tan Ah Kow · R3A | 138/78 | 70 | 98% | 36.4 | SN Aida · AM | agrees | sent 8:10 am | |
| 8:06 am | Lim Siew Hong · R2B | 119/70 | 64 | 97% | 36.2 | SN Aida · AM | unreadable · glare | sent 8:06 am |
"Differs" does not change the record; it flags it for the admin to look at the photo. The carer's number stays the number of record, and a person stays accountable. Residents and staff names are sample data.
Not every home will subscribe on day one. A home can still be listed on Homes First with nothing to install and nobody to train: it messages the Homes First WhatsApp number when a bed opens or fills, and the listing shows what the home last confirmed, and when.
What the home pays. A small fee per day listed, or a light monthly subscription price to be decided with Choong. Paying, even a little, is what separates a home that means it from one that filled in a form once.
What the platform gets. Declared availability with a timestamp. Weaker than an SS Care home's live count, and shown as such: families see "confirmed by the home Tue 9:40am", not a bed count that pretends to be live.
An SS Care home. The roster changes on the day a resident is admitted or leaves — nobody types anything.
A light-path home. “2 beds free, confirmed Tue 9:40am” — true as of when the home last said so, and shown that way.
No reply for a set period. Marked unconfirmed and dropped out of matching, so nobody is sent to a bed that is not there.
Mock exchange, not built yet. Golden Years Care is fictional. This does not replace Position 4; it widens the front door so the directory is not empty while the tool is being sold.
No app. A family messages one number, answers a few questions, and is introduced to a home that can take their parent. Runs on KengAPI, the same WhatsApp Business API platform that already sends the SS Care Flow.
The conversation, as a family would have it. Home names and budget bands are placeholders:
What kind of care does she need?
Mock conversation, not built yet. Damai Care Residence, Golden Years Care and Serene Lodge are fictional homes; the budget bands are illustrative, not proposed prices.
A matching conversation on a single public WhatsApp number:
A family looks for a nursing home perhaps once or twice in their life, usually in a bad week. They are already on the phone with siblings, the hospital, and the homes they are considering — all in WhatsApp.
And the whole exchange sits in the same thread they will forward to their brother.
It also means zero acquisition friction for Choong: the number goes on a flyer at a hospital discharge desk, a Facebook post, a clinic notice board, and it works immediately.
Families: free. Charging the stressed party at the point of need kills the demand side.
Homes: a referral fee per admission, or a higher subscription tier that includes enquiries fee to be decided with Choong. This is the second revenue line and the one that makes the platform, rather than the tool, the business.
The referral fee is collectable because it is verifiable: when a referred family is admitted to an SS Care home, the new resident appears in that home's roster the same day, so the platform knows without asking. Light-path homes report admissions themselves.
Demand by area, budget band and care need; conversion from enquiry to introduction to visit to placement; which homes respond and how fast; which needs go unmatched. That last one tells Choong which homes to recruit next, and what to build for them.
The number is public. A family can go from first message to a confirmed introduction without a human in the loop, and the home receives the introduction in its own WhatsApp with the family's needs summarised. Enquiry volume and conversion are measured from day one, because they set the trigger for Phase 3.
Too few homes to match against. If Phase 2 launches with two homes, every family gets the same two answers and the bot looks like an advert. Phase 2 should not go public until Phase 1 has enough homes across enough of Petaling Jaya to give a real choice threshold to be agreed.
A web directory with live availability from Phase 1 data, for families who search on Google before they message anyone. The app, if it is ever built, is for homes managing enquiries, not for families searching.
What the platform layer could look like once the trigger is met. Nothing below is built, and every figure is sample data:
The availability line is the point. Nobody at the home edited a listing; the timestamp is the last vitals card that went to a family group. Light-path homes show what they last confirmed and when, in a different colour, so a family can tell live from declared. Damai Care Residence, Golden Years Care and Serene Lodge are fictional homes.
| Received | Family | Care need | Budget band | Status |
|---|---|---|---|---|
| Today 10:05 | Mdm Limvia WhatsApp · for her mother | Dementia care | RM 3,000 – 5,000 | New |
| Yesterday | Mr Bongvia directory · for his father | Post-stroke · mobility | Above RM 5,000 | Visit booked · Sat 11am |
| 2 Sep | Ms Nurulvia WhatsApp · for her grandmother | Tube feeding | RM 3,000 – 5,000 | Visit booked · Thu 3pm |
| 28 Aug | Mr Wongvia WhatsApp · for his mother | Dementia care | Under RM 3,000 | Placed · Room 5 Bed B |
3c · The one place an install earns its keep: the home's admin, not the family.
This is where an app makes sense: the supply side, managing leads every day. The occupancy widget is the same count Phase 1 already keeps, so "2 beds free" is not typed in by anyone. Families never see this screen and never need an install.
Phase 3 starts only when both hold for two consecutive months numbers to be agreed with Choong:
Until then, a directory would be a page of empty listings and an app would be a store entry nobody opens.
Homes, through the Phase 2 model, which by now has proven whether referral fees or subscription tiers work. The directory and console are what make the platform worth a higher tier to be decided.
Search demand by area and need (from the directory), and a full placement funnel from first search to admission. With Phase 1 data on the same residents, this becomes the only source of truth on nursing-home capacity and demand in the Klang Valley that is current rather than surveyed.
A family can find a home on the web, message it, be matched, visit, and be admitted, and the home's occupancy on the directory changes on the day of admission without anyone editing anything.
Homes unwilling to show occupancy publicly. Some homes will not want "2 beds free" on a public page. The directory can show availability as a band, or only through the bot after needs are known, with public occupancy an opt-in per home.
Nothing here has a number in it yet, on purpose.
An MVP is not a smaller version of Phase 3. It is the shortest path to a home that pays, a family that gets matched, and a referral fee that can be invoiced — with as little built as that takes.
The one deliberate shortcut: the family number opens with a person behind it, not a matching engine. Choong makes the first matches himself from a structured WhatsApp intake. That is not a retreat from Position 2 — families still never install anything — it just refuses to build a matcher before there is enough supply for it to have anything to choose between. The conversations it produces are what the bot is later built from.
Eugene · starts on go-ahead
Not blocked by any of the above
Three lines. The build is a fixed price so the scope is a conversation about what gets built, not about the bill.
| What | Who pays | Shape | Amount |
|---|---|---|---|
| The Homes First build The WhatsApp bot, the listings, and Choong’s dashboard — the three items in the build track above |
Choong | One-off, to start | RM 5,000 For the scope above. Anything added beyond it is quoted separately before it is built, never after. |
| Running the platform Hosting, monitoring, keeping the numbers connected, support |
Choong | Monthly | to be decided Starts when the family number goes live, not at signing. |
| SS Care per home The subscription and the one-off setup, per home onboarded |
The home | Monthly + one-off | to be decided Billed by SoftSupplies; Choong takes a reseller margin on every home in his territory. |
Then we meet again with two months of real usage and decide the matching bot on evidence: which needs went unmatched, which homes replied, and what a placement is actually worth. Phase 3 stays shut until the gate in the roadmap is met.