SPA — Asset Management System
One client, one problem. But deep research revealed — this problem is faced by EVERY Malaysian government agency. Here's how we transformed a single custom build into a multi-tenant SaaS platform.
The Story Begins
Imagine being an asset officer at a government agency. Your job: track thousands of public assets — computers, vehicles, furniture, equipment. Each must have records, history, and compliance with KEW.PA (Asset Registration) and KEW.PS (Disposal Store) — official Treasury circulars of Malaysia. Sounds simple? Reality: you use Excel files that constantly break, manually compile forms every month for audits, and spend hundreds of hours typing data that already exists in other systems. When an asset goes missing? No audit trail. When auditors arrive? Panic mode. This was the challenge brought to us by our anchor client (a major defence agency) — and we accepted. But during development, we made a discovery that changed our entire strategy.
“Official circulars are a map. Read them carefully, and you'll see a market as big as the number of government agencies in Malaysia.”
— Razlan Razak, Founder Tech Lead
The Pivot — From Custom Build to SaaS
4 phases. One major pivot that changed the business model. Here's our journey:
Phase 1: Build For First Client
6 months custom build for the anchor client. Full feature set: registry, lifecycle tracking, multi-team inspection, KEW.PA/PS auto-generation. Production-ready. Client happy. Could stop here — many IT vendors would stop here. But we didn't.
Phase 2: Discovery — KEW Circulars Are Universal
We researched KEW.PA + KEW.PS deeply. Then it hit us: Treasury form formats are STANDARD. Asset lifecycle (receive → register → use → repair → dispose) — STANDARD. Audit requirements — STANDARD. Meaning: ALL Malaysian gov agencies have the same problem and the same SOLUTION. We just finished building a solution for one agency. What if we productized?
Phase 3: Multi-tenant Pivot
4 months of refactoring. Database tenant isolation, scoped routing per agency, isolated file storage. Single deployment, unlimited tenants. Cost economics changed drastically — no longer RM 100K+ per agency (custom build), but affordable subscription. We kept supporting the anchor client during refactor — zero downtime.
Phase 4: Validate With Tenant #2
Onboarded SAINS NS (Sistem Air Negeri Sembilan) — corporate utility sector, slightly different asset workflow from defence. Result: architecture flexible enough to handle gov + corporate. Multi-tenant proven. SaaS ready to scale.
Before vs After
Before SPA
- Scattered Excel files — versions out of sync between officers
- KEW.PA/PS forms typed manually every month for audits
- Lost assets = no audit trail
- Multi-team inspection chaos — who inspected what?
- Custom build per agency: RM 100K-300K, 6-12 months
After SPA
- Single source of truth — all officers access real-time
- KEW.PA/PS forms auto-generate from database
- QR per asset + complete history of every change
- Multi-team inspection with clear workflow
- Subscription SaaS: onboard in 2 weeks, price drops 5-10x
How Multi-tenant Works
Each agency (tenant) has its own sandbox in the database — tenant A's data cannot be accessed by tenant B, even though they share the same infrastructure. Authentication via Laravel Sanctum with tenant-scoped tokens. Queue jobs (Laravel Horizon) tag every task with tenant_id for isolation. File uploads (inspection photos, asset documents) use S3 storage with per-tenant bucket prefixes — proper isolation at the storage level too. Result: one Docker deployment can serve unlimited agencies, but each feels like their own dedicated system.
Tech Stack
Measurable Outcomes
Real Impact
Beyond features — what changed for clients and for Tech Lead.
For Asset Officers
- Audit prep from months to hours — KEW.PA/PS forms auto-generated
- When an asset goes missing/damaged — full audit trail from day one
- Multi-team inspection no longer chaos — clear workflows, accountability guaranteed
- Mobile-first — officers can work from the field, not chained to desks
For Agency Management
- Cost dropped 5-10x vs custom build per agency
- Onboarding in 2 weeks (not 6-12 months)
- KEW.PA/PS compliance audit-ready at all times
- Single source of truth — full visibility for command
For Tech Lead
- Business model shift: custom services → recurring SaaS revenue
- Real validation: 2 production tenants = product-market fit confirmed
- Knowledge moat: KEW circulars deeply integrated = hard to replicate
- Scalable: tenant #10, #100 = low marginal cost, high margin
For the Industry
- Setting a new standard for Malaysian gov asset management
- Reducing burden on asset officers across all adopting agencies
- Promoting Treasury circular compliance automatically
- Making the case for Malaysian vendors to productize, not just customize
Takeaway Lessons
- →Anchor client = validation, not limitation. You need a first user to prove the pattern. But don't stop there — if the pattern can extend, productize.
- →Government circulars are a gold mine. Official circulars = standards followed by all agencies. Understand the circulars, understand the market.
- →Multi-tenant architecture is 'earned'. Don't build a speculative platform without a first paying user. Start with one, refactor once the pattern is confirmed.
- →Pivoting from custom to SaaS requires commitment. Not easy. 4 months extra effort. But client cost drops 5-10x and revenue model becomes recurring — long-term win-win.
- →Stack consistency = leverage. We use Laravel + Vue + PrimeVue for ALL Tech Lead products. Meaning: knowledge transferable, bug fixes in one project apply to all, easier to hire developers.
Your Agency Still Using Excel?
SPA is ready. Onboard in 2 weeks. FREE demo. Customizable for your agency's workflow.
