{{ Data.Content[0].DatePostedDisplay }} | {{ Data.ContentParam.static_translation_data.blog_appsiteblog_main_view_label_by || 'By' }} {{ Data.Content[0].Author.Name }} {{ Data.ContentParam.static_translation_data.blog_appsiteblog_main_view_label_anonymous || 'Anonymous' }} | {{ Data.ContentParam.static_translation_data.blog_appsiteblog_main_view_label_in || 'In' }} {{ Data.Content[0].Category.Name }}
Two people at a whiteboard sorting project notes into three columns

Every digital project starts with a problem, and the problem is rarely about technology. A national brand needs reliable information from hundreds of stores. A youth movement needs to manage a very large membership across many states. A property group needs to see its assets in several countries in one place. Here are three projects we have delivered, what each organisation needed, what we built, and what we learned along the way.

Key Points

  • Heineken Malaysia: a field web application supports daily audit operations across 450 stores.
  • Young Malaysians Movement: one membership system manages 140,000 members centrally, with clear state-division controls.
  • Threenity: their own SaaS across countries and currencies, with eight report variants reconciled against the data.
  • Each project started with the operation, brought scattered information into one system of record and was built to grow.

Heineken Malaysia: Daily Audits Across 450 Stores

The need. Heineken Malaysia's merchandisers carry out daily audits in stores across the country. That information has to reach the company's backend and its business intelligence reporting reliably, from wherever the merchandisers are working.

What we built. A field web application used by merchandisers in the stores, with data flowing from each store to the backend and on to business intelligence.

The result. Daily audit operations run across 450 stores through the app.

What we learned. When people use a system in the field, simplicity decides everything. Every extra step on a phone in a busy store is a step that gets skipped, so a field application has to follow what the user actually does in the store.

Young Malaysians Movement: One Home for 140,000 Members

The need. Membership data was scattered and difficult to manage, and there was no way to take payments online for events or merchandise.

What we built. A digital membership subscription management system, together with an online store for merchandise connected to a payment gateway.

The result. Centralised management of 140,000 members, with clearly defined state-division controls.

What we learned. In a large organisation, who can see and change what matters as much as the data itself. Clear access rules for each division are what make a system like this trusted by the people who depend on it.

Threenity: Their Own SaaS, Unlimited Countries

The need. Threenity, a property group, needed acquisition, tenancy, ledgers and performance to come together in one system that works across countries and currencies, and an earlier application had to move onto a platform that could keep growing with the group.

What we built. The earlier application was converted onto NagaCloud as custom microservices, with portals for managers and clients, workflows, a ledger for each asset, performance dashboards, and reports in PDF, Excel and CSV formats.

The result. Their own SaaS, ready to take subscriptions from their own customers, for unlimited countries and currencies, with eight report variants reconciled in June 2026. The system was launched in 2025.

What we learned. A system that spans countries and currencies has to be exact in its reporting before anything else. Reconciling every report variant against the client's own figures is slow, careful work, and it is what makes the system something the group can rely on.

What the Three Projects Have in Common

Three projects and their results: Heineken Malaysia, daily audit operations across 450 stores; Young Malaysians Movement, 140,000 members under central management; Threenity, 8 report variants reconciled on their own SaaS
  • Each started with the operation. We first understood how merchandisers, members and asset managers actually work.
  • Each brought scattered information into one system of record. One current version of the truth, with the right access for each role.
  • Each was built to grow. On a platform that can be extended as the organisation's needs change, without starting again.

These are the same principles behind our RIDE framework: review where the organisation stands, identify what will make the biggest difference, digitalise it properly and keep elevating it. You can read more in our guide to digital transformation in Malaysia, and see more of our work on our success stories page.

Facing a problem like one of these? Take the free RIDE Digital Scorecard, or book a free consultation with us today.

Frequently Asked Questions

More on Web Apps & Platforms

{{ item.CategoryName }}
{{ item.DatePostedLongDisplay || item.DatePostedDisplay }}
There are no posts at the moment.

{{ Data.ContentParam.static_translation_data.blog_appsiteblog_main_view_label_faq || 'Frequently Asked Questions' }}


{{ Data.ContentParam.static_translation_data.blog_appsiteblog_main_view_link_back || '« Back' }}