· Farah Iskandar
Tenants that appear without an order are still admissions
Self-serve signup sitting beside a sales-led onboarding application will create live accounts the commercial file never authorised. Completeness testing has to start from both doors.
Many Malaysian SaaS operators run two doors. Sales closes a deal and a success manager walks the customer through a checklist. At the same time the marketing site still offers “start free”. Both doors write to the same tenant table. Only one of them writes to the order book.
If you test onboarding completeness from closed-won deals alone, you will never see the self-serve tenants. If you test from the tenant table alone, you will treat every signup as intended. The useful test is a join: tenants created in the period, matched to orders, trials, and staff-created exceptions, with every unmatched row given a reason that existed on the create date.
“It was a demo” is a reason only if the tenant is flagged as a demo in the application, not in someone’s memory. Demo tenants that later received production data are admissions. They belong on the exception log.
In Subang Jaya engagements we ask for the create-source field first. If the application does not store one, that is the first finding. You cannot complete a population you cannot classify.