Client stories

Testimonials

“They refused to rubber-stamp a full rewrite. Instead we got a phased portal cutover that kept our member login stable through Thai New Year peak traffic.”

Nattapong K. — Head of Digital, Bangkok mutual society

“The architecture assessment caught a brittle single sign-on path we had ignored for years. Fixing that first made the later rebuild far less risky — though the written report was denser than I wanted for the board pack.”

Elena M. — Programme sponsor, regional logistics portal

“The roadmap workshop forced our product and operations leads into the same room for two days. We left with owners against each phase, not another vague backlog.”

Pranee S. — Product director, education partner hub

“Portal Riverpoint asked uncomfortable questions about content ownership early. That slowed week one, and it saved us from planning a migration nobody could approve.”

Marcus L. — Engineering lead, hospitality booking portal

Extended story: Mutual society member portal

A Bangkok mutual society ran a fifteen-year-old member portal that still handled claims status and contribution history. Leadership wanted a “modern rebuild” before the next membership renewal season. Discovery showed the authentication path depended on a vendor library that would not survive a lift-and-shift, and claims content was owned by a separate operations unit with no migration capacity that quarter.

We recommended a three-phase cutover: harden identity first, rebuild claims read-paths second, then migrate contribution history under a quieter calendar window. The society deferred decorative redesign work until after identity stability was proven. Peak renewal week completed without a full outage; one partner feed still required a manual reconciliation day, which we had flagged in the risk register.

Extended story: Logistics partner hub

A regional logistics firm planned to replace its partner hub after repeated integration failures. An architecture assessment showed most failures originated from undocumented callback assumptions rather than the hub UI itself. Rebuild planning therefore prioritised a contract-first interface layer and a freeze on new partner onboarding until the callback catalogue was complete. The programme later hired a delivery vendor of its own choosing; our plan remained the sequencing reference.