Start a project
Three steps, then a review. You end up with a written brief you can send by email or WhatsApp, and a copy of it for yourself.
Where
Engineered in Malaysia
MYT
Or use the brief above.
Questions
What people usually ask before we start.
What do you actually build?
The operational software a business runs on: inventory, invoicing, dispatch, production scheduling. The systems that stop the company when they stop. Not marketing sites.
How does a project start?
Discovery first, where we learn how the business actually operates. Then architecture — schema, API structure, user flows — before any interface gets built, so there are no surprises during the build.
Will it work with the software we already use?
That’s usually the point. Where the books are already in SQL Account, the system reads from there directly rather than asking anyone to type the same figure twice.
Where does it run?
On infrastructure we manage ourselves, not a platform we’d have to file a ticket with when something needs fixing. SSL, monitoring and backups are part of the deployment, not an add-on.
What happens after launch?
Launch is the start. Systems get second versions, new modules and audits as the business changes, and we’re still in the codebase long after handover.
What don’t you take on?
Work where nothing is measurably broken. If there isn’t a real operational cost to fix, we’re the wrong people and we’ll say so early.