From Idea to Launched HR SaaS in 14 Weeks
A former HR director had spent fifteen years watching Malaysian SMEs manage leave, claims, and payroll on spreadsheets and WhatsApp. She had a clear product idea, three signed letters of intent from prospective customers, and seed funding with a hard runway of sixteen weeks. What she didn’t have was an engineering team, a technology stack, or a technical co-founder. Nematix was engaged to design and build the MVP.
The product launched in week fourteen. The first paying customer converted before week sixteen. The second and third followed within thirty days.
The Situation
The target market was Malaysian SMEs with 20–200 employees — businesses large enough to feel the pain of manual HR administration but too small to justify enterprise HRMS licensing. The product had to handle three core workflows: employee leave management, claims and expense reimbursement, and payroll calculation with EPF, SOCSO, EIS, and PCB deductions under the Malaysian Employment Act 1955.
The Employment Act compliance requirement was non-trivial. Leave entitlements, overtime calculations, and termination pay formulas are governed by statute. An HRMS that calculates these incorrectly doesn’t just create administrative errors — it creates legal liability for the SME operator. Every calculation had to be correct and auditable.
The founder had done customer discovery with forty SME owners. The consistent feedback: they didn’t want more features, they wanted fewer clicks and an audit trail. The LOI customers had agreed to a twelve-month contract at MYR 350/month for up to fifty employees, conditional on the product being live and passing a basic functional review.
The Challenge
Three constraints shaped the engagement significantly.
Compliance first, then UX. The Employment Act has specific rules for leave accrual (different by years of service), overtime eligibility (only for employees earning below MYR 4,000 — a statutory threshold that changes with legislative amendments), and the calculation of ordinary rate of pay for claims purposes. These had to be implemented exactly before anything else was built on top of them.
Multi-tenancy from day one. The product would serve multiple companies from a single deployment. Each company had its own employee data, its own leave policies (within statutory minimums), and its own approval hierarchies. Tenant isolation — ensuring Company A’s data was never accessible to Company B — had to be architecturally enforced, not bolted on later.
No technical oversight on the client side. The founder had no engineering background. Decisions about architecture, infrastructure, security, and technical trade-offs all landed with Nematix. The product had to be maintainable and extensible after handover, without the client needing to make technical hires in the short term.
Our Approach
Weeks 1–2: Scoping, architecture, and compliance mapping
Before writing code, we mapped every Employment Act calculation the product needed to perform: ordinary rate of pay, annual leave accrual tiers, sick leave entitlement, public holiday substitution, PCB calculation under the Income Tax (Deduction from Remuneration) Rules 1994, EPF contribution rates by age band, SOCSO and EIS tables.
The output was a compliance specification document — a reference that every developer working on the project could verify their implementation against. The founder’s employment law background meant she could validate the document directly.
Architecture decision: a multi-tenant SaaS on AWS with tenant isolation at the database row level (shared schema, tenant ID on every table), PostgreSQL via RDS, Next.js frontend, and a Node.js API layer. Stripe for subscription billing. Malaysian cloud region (ap-southeast-1, Singapore) for data residency.
Weeks 3–8: Core product build
Three parallel workstreams:
Compliance engine: All statutory calculations implemented as a pure, testable module — no database dependencies, no side effects. Every function had unit tests verifying the output against hand-calculated reference cases from the Employment Act. This module became the source of truth for all downstream calculations.
Leave and claims workflows: Employee self-service (apply, view balance, upload receipts), manager approval flows with email notifications, HR admin overrides, and an audit log on every state change.
Payroll: Monthly payroll run with line-item breakdown (basic salary, allowances, claims, EPF employee/employer, SOCSO, EIS, PCB), downloadable payslips in PDF, and a bank file export format compatible with Malaysian commercial banks’ bulk payment systems.
Weeks 9–12: Multi-tenancy, auth, and billing
Tenant onboarding flow (company setup, department structure, employee bulk import via CSV), role-based access control (HR Admin, Manager, Employee), and Stripe subscription integration with a 14-day free trial.
Security review conducted in week 12: SQL injection testing, API authentication (JWT with short-lived access tokens and refresh token rotation), file upload validation (payslips stored in S3 with pre-signed URLs, never served directly).
Weeks 13–14: UAT and launch
The three LOI customers ran user acceptance testing in week 13 against their own data. Fourteen issues were reported; twelve were resolved in the same week, two in the first days of week 14. The product went live in week 14.
Outcome
| Metric | Target | Actual |
|---|---|---|
| Launch timeline | Week 16 | Week 14 (2 weeks early) |
| LOI customers converted | 3 | 3 (100%) |
| Employment Act calculations audited | All covered | 100% pass |
| Tenants onboarded at launch | 3 | 3 |
| Additional customers (30 days post-launch) | — | 2 |
| Infrastructure cost (monthly, at launch scale) | < MYR 800 | MYR 620 |
The founder secured a follow-on pre-seed round in the month after launch, using the three paying customers and the product as the primary evidence of traction.
Key Takeaways
Compliance specifications before code. Every compliance calculation was documented, agreed, and tested before UI work began. This sequencing avoided the alternative: building a UI over a calculation engine that turned out to be wrong, then having to retrofit fixes through every layer.
Testable compliance logic as a standalone module. Separating all Employment Act calculations into a pure, dependency-free module made them easy to unit-test and easy to audit. When regulatory updates require changes — and in Malaysian employment law, they do — the fix is in one place.
Scope discipline on an MVP. The founder’s initial scope included a performance appraisal module, an org chart visualisation, and integration with two accounting systems. We deferred all three. The paying customers validated the core loop — leave, claims, payroll — before any secondary functionality was built. Secondary features are now on a prioritised roadmap funded by revenue.
This engagement draws on our Innovation & Product Development services. If you’re a founder with a validated idea and a tight timeline, let’s talk.