A certified pre-owned dealer platform - governance system, adoption failure, honest reset (2021–present)
The situation
The Singapore NSC asked me in 2021 to design a digital governance system for the OEM's certified pre-owned programme, their used-car business. The stated brief was auditability. The used-car business, as the client put it, is a dirty one - transactions ran on phone and WhatsApp, and there were kickbacks and partiality in awarding bids. The system was meant to fix that.
The architectural read
I designed a three-part ecosystem: a Sales Consultant intake app, a Dealer bid app with invite-only access and filterable notification profiles, and a Purchaser dashboard with full audit trail, blind bidding, dealer identity masking until wholesale decision, minimum reserve enforcement, and quote-ranking signals (top three green, bottom three red). Draft-saving in the SC app to match how sales advisors actually work. Every override loggable. Every decision auditable. The system was built for governance, not tech for tech's sake.
The scraping request and the refusal
During implementation, the client team asked me to scrape vehicle PARF data from LTA's OneMotoring website - a common practice among Singapore automotive vendors. I refused. Scraping violated OneMotoring's Terms of Use, exposed the Company to compliance risk on a government-linked website, and would have required continual re-engineering as LTA changed its site to block the practice. I documented the refusal in email, cited the Terms of Use directly, checked with legal, ran a 100-attempt scraping test to validate that the technical approach was as unreliable as I suspected (30% of attempts blocked at submission, IPs banned progressively, incomplete data returned in a further third), and explored alternatives including third-party API services and a proposed direct sit-down with LTA. My position stayed the same across multiple pressure cycles: the Company as a Malaysian vendor could not be seen to violate a Singapore government website's terms of use, particularly one operated within a client's own principal ecosystem. The client eventually accepted the refusal.
The compromises that did happen
Over the course of the year, the client team requested a series of changes that eroded the governance layer of the system: removal of the minimum reserve; changing the top-three green signal to only the highest bid; disabling the notification to the winning dealer; removing the win visibility inside the dealer app so that off-platform WhatsApp bidders could be substituted in. I argued against each of these in real time, documented my objections in email, and implemented them only when the client insisted. Every compromise was owned by the client. The audit trail of the compromises themselves became part of the record.
The adoption failure
The dealers didn't move. They preferred the speed and familiarity of WhatsApp over downloading and checking a B2B app. The sales advisors found the data entry onerous. Off-platform WhatsApp bidding continued in parallel with the app, and the client team began accepting it. The system went live and stayed live but was worked around rather than used. By 2024 the platform existed as an artifact but the actual business had returned to manual processes.
The realignment (July 2025)
When a new client team took over and asked for "small fixes that might help," I refused. I said the system had failed, I wasn't willing to keep charging them a modest four-figure monthly fee/month for something that wasn't working, and I laid out three honest paths: patch it (treat the symptom), restart it (redesign around what the failure taught), or sunset it responsibly. I recommended a strategic conversation about intent and enforcement before touching the tools.
The subscription suspension was mine to offer. The contract was live. The Company had the legal and commercial right to keep issuing invoices while the system sat dormant. I offered the suspension anyway, before the client asked, because the subscription was for a working system and the system wasn't working. The client accepted. The client-side leadership has referenced that conversation since; it clarified who I was operating as, and who they were dealing with.
The V2.0 proposal (2026, awaiting client readiness)
The failure taught me something specific: forcing a behavioural shift creates friction the system can't survive. The V2.0 proposal - currently on hold pending client readiness - pivots on that insight. Instead of forcing dealers to use an app, WhatsApp becomes the frontend. A multimodal AI layer handles PARF screenshot OCR, voice-note parsing, and multilingual text extraction. The dealer never leaves WhatsApp. The audit trail runs through the AI intermediary, which also sanitises questions to prevent identification via slang. The governance layer moves from enforcement to invisible enablement. Total third-party operational cost, at 43 cars a month across 20 dealers: less than USD 15 monthly.
What this shows
Three things. First, the governance instinct - the system was designed correctly against the stated brief and I held the line on compliance under pressure. Second, the client-interest instinct - when the system failed, I refused to profit from patches, and I offered to suspend a live, contractually valid subscription before the client asked. That move cost the Company revenue in the short term and defined the relationship in the long term. Third, the architectural learning - the V2.0 design isn't a repeat of V1.0 with better UI. It's a fundamental re-architecture informed by what the failure actually taught about the 70% of this specific business. The technology was never the problem. The operational and cultural readiness of the client to enforce a new behaviour was. V2.0 designs around that reality instead of against it.