When it is not a website, it is a system.
Database, user roles, payments, e-invoicing, integrations and internal tooling. Built and then maintained by the same person, because handing a live system to a stranger is how systems rot.
From RM30,000 · fixed-quoted by defined outcome · monthly improvement available after release
Real production systems, not case studies. You can visit all six from the portfolio.
6
production systems under care today
3–9
months, phased and fixed-quoted per phase
1
person who built it and still maintains it
Where system projects fail
The build finishes and the knowledge leaves.
A website can survive neglect for a year. A system with payments and user data cannot — and the people who understand it are usually gone by month four.
Risk 01
Webhooks failing silently
A payment succeeds and the order is never recorded. Nobody notices until a customer complains, and by then reconciliation is a manual job.
Risk 02
Scope, not build cost
At this size the money is lost to changing requirements, not to development hours. Phased fixed quotes exist to stop that.
Risk 03
One person who knows how it works
True of every small system, including ours. The mitigation is written documentation and access you hold — not a promise about headcount.
What you actually get
What a platform engagement includes.
Same ownership rules as everything else: the database, repository and pipeline are yours from the first commit.
Data model and user roles
Designed before anything is built, and written down. Most system rewrites happen because the original data model could not answer a question the business later needed.
Payments and e-invoicing
Real gateway integration with webhook handling, retries and idempotency — the parts that matter when a payment succeeds and your database does not hear about it.
Integrations that fail loudly
CRM, WhatsApp, courier APIs, accounting. Each one monitored, with an alert when it stops working rather than a silent gap in your data.
Staging, pipeline and rollback
Nothing reaches production without running somewhere else first, and everything can be rolled back. Non-negotiable on a system holding customer data.
Documentation you could hand over
Architecture, environment variables, runbook for the three things most likely to break. Written for whoever comes after us, including if that is not us.
How it runs
Phased, so the risk is bounded.
Each phase is separately fixed-quoted. You can stop after any of them with something that works.
Phase 0
Scope, paid
Data model, integration list, phase plan. Delivered as a document you own.
Phase 1
Core
Database, auth, roles, the one workflow that earns money. Live and usable.
Phase 2
Payments
Gateway, webhooks, reconciliation, e-invoicing where required.
Phase 3
Integrations
CRM, messaging, courier, accounting — each one monitored.
Ongoing
Monthly improvement
Available after release from RM13,000/month. Priorities continue through the reviewed request queue.
The number
From RM30,000
phased and fixed-quoted per phase, excluding SST
- ✓Each phase separately quoted — stop after any one
- ✓Monthly System Improvement available from RM13,000/month
- ✓Database, repository and pipeline yours from the first commit
- ✓Documentation written for whoever comes after us
Included
- ✓Data model and architecture, documented
- ✓Auth, roles and permissions
- ✓Payments, webhooks and reconciliation
- ✓Staging, pipeline and rollback
- ✓Monitoring on every integration
- ✓Runbook and handover documentation
Quoted separately
- —Mobile apps — related, but a different build
- —Data migration from a legacy system, until we have seen it
- —Third-party licence and infrastructure costs, billed to you at cost
- —Ongoing data entry or operations staffing
Questions
Is one person really enough for a platform?
For systems of this size, yes — UrusHQ and Trexon Energy are both live and maintained this way. What one person cannot do is deliver quickly under pressure, which is why phases are fixed-quoted and the queue caps at one request. If you need a team on a deadline, hire a team.
What happens if you are unavailable?
You hold the repository, the database, the pipeline and the documentation, so another developer can pick it up. That is not a comfortable answer, but it is the honest one, and it is why the ownership rules exist.
Can you integrate with our accounting system?
Usually. Tell us which one at scoping. Malaysian e-invoicing via LHDN is built and running in UrusHQ today, so that specific one is known ground rather than a promise.
What happens after the fixed-scope release?
A live system with payments needs an accountable owner. Monthly System Improvement starts from RM13,000/month and provides prioritised progress, reviewed releases and Monday updates.
Systems need an owner, not a vendor.
From RM30,000, fixed-quoted by outcome, with monthly improvement available after release.