Does Galavate work outside Kuching?

Yes. We work in person across Sarawak and remotely, with site visits at the start and at the first release, for Peninsular Malaysia and Sabah.

What does working with Galavate look like week to week?

One process at a time: a morning with the owner and the field staff, a first version in staff hands within days to two weeks, adjustments with them, then the next process.

Which companies is it a fit for?

Established companies with field operations, their own way of working, and a director willing to name one person to own the first process.

Working with a software team based in Kuching

Why Kuching

Galavate is built in Kuching and works from here. Sarawak's established companies, in construction, engineering, plantations, logistics and services, run large field operations on systems that have not kept up with them, and many of the software vendors serving them are in Kuala Lumpur or overseas. Being here means we can sit with the people who do the work, watch the process at the site, and come back the same week with something running.

Kuching is also where the platform runs every day. The system that carries an engineering consultancy's field operations across Sarawak and the peninsula is built and supported from this office, so a question from a site does not travel through a reseller or a ticket queue before it reaches the person who can answer it.

In person across Sarawak

For companies in Kuching we work on site: a morning with the process owner and the field staff, then the build, then back on site when the first version is ready. For Sibu, Bintulu and Miri it is the same, arranged around visits. A change asked for at an 08:30 walkthrough on site being live on staff phones by that evening is possible because we were in the room when it was asked.

Remote, with site visits, for Peninsular Malaysia and Sabah

Most of our work for the peninsula is done remotely, on video calls and through the system itself, with site visits at the start and at the first release. The company we build most for runs operations across Sarawak and Peninsular Malaysia on our system, and its peninsula teams were brought on remotely, one group at a time, led by the people running them there. Same time zone, same languages, same working week.

Who it suits

Established companies with field operations and documents that get signed.
Companies whose process is their own, not a standard one that a product already covers.
Directors who want to see something running before they commit, and who can name one person to own the first process.

It suits less well companies looking for a large vendor's name on the contract, or for a system to be configured rather than built around them. We say so early, because a build that is not going to be used is not worth starting.

How we work with your team

We start with one process and the person who owns it. We build the first version, usually in days to two weeks, and put it in staff hands. We adjust it with them, then move to the next process. Staff on both sides talk directly: the site reaches us on WhatsApp, and questions raised inside the system reach us the same day, so nothing is lost in a thread.

What you can check before you call

Everything on this site about speed is counted from the commit history of systems in production, and the numbers are in How long does custom software take to build?. The system itself runs an 800-person engineering consultancy's daily field operations, on both public app stores. Ask us for a walkthrough of it on a phone.

Getting in touch

WhatsApp is fastest. Email works. If you want to know whether your first build would be free, the template takes two minutes and we reply within 48 hours.