About
404 Tech Sdn. Bhd. designs and builds custom software in Kuala Lumpur. This page covers how we work, what we hold to, and the tools we use.
How we work
Every piece of work, from a new system to a change on an old one, goes through the same five stages in the same order. You always know which stage it is in.
Request
POST /enquiry202 AcceptedYou describe what is slow, manual or missing. We reply with questions about how the work runs today, not with a price list.
- What we need from you
- A few lines on the problem, who it affects and any deadline.
- What you receive
- Our questions, and a time to talk them through.
Scope
GET /how-it-runs-today200 OKWe map the work as it runs now: who does each step, which data moves where, which rules must hold, and what must not change.
- What we need from you
- Time with the people who do the work, and the forms and spreadsheets they use.
- What you receive
- A written scope listing the screens, roles, rules and stages, with the cost and timeline. Nothing is built until you agree it.
Build
PUT /system206 Partial ContentThe work is built in stages. Each stage goes up on a preview link with test data, and the next one starts after you have used it.
- What we need from you
- Feedback on each preview, from the people who will use it.
- What you receive
- A working preview at every stage, never only screenshots.
Release
POST /deploy201 CreatedWe deploy to your hosting, move existing records across and check them against the originals before the old process is switched off.
- What we need from you
- Access to the accounts the system will run on, held in your name.
- What you receive
- The live system, its source code and its documentation.
Look after
PATCH /system200 OKThe business changes and the system changes with it. Fixes and new work go through the same scope, preview and release steps.
- What we need from you
- Tell us what has changed.
- What you receive
- Support, changes and the documentation kept up to date with them.
What we hold to
Four rules that decide most of the small choices in a build.
Honest data
A number on screen is a claim. If it did not load, the screen says so instead of showing zero.
In practice
- Empty, failed and not-allowed states each read differently
- An error tells you what went wrong, never a false success
Built to the business
The software follows how your business runs. Your team should not have to change its work to fit a template.
In practice
- We map the work before we design a screen
- Roles, rules and documents come from your process, not a package
Maintainable
Systems outlive the first version. We choose plain, widely used tools so the next developer, ours or yours, can pick it up.
In practice
- Every database change written as a script you can read
- One design system per product, not one-off pages
Handover documents
You own what we build, and ownership means being able to run it without us.
In practice
- Source code in a repository you own
- How to run, configure and deploy it, written down
Stack and tools
The same tools on every project unless the work calls for something else. Each one is open source and widely used.
- Interface
- NuxtVueTailwind CSS
- Server and API
- Nest.jsSwagger
- Data
- PrismaMySQL
- Mobile
- React NativeExpoEAS Build
- Checks
- PlaywrightLighthouseaxe
- Source control
- Git
Kuala Lumpur, Malaysia
3.139° N, 101.687° E