Forward-Deployed Engineering & IT as a Service in Malaysia

§ 01 — What you get

A team, without the headcount.

Most Malaysian mid-sized companies need about a third of a software team. Hiring one is expensive and risky; hiring none means the systems quietly rot. This is the middle path.

01 / Cadence

Continuous delivery, not milestones

Work ships weekly, sometimes daily. Small changes reviewed by the people who asked for them, while the reason for the request is still fresh. No six-month build revealed at the end to a business that has since moved on.

02 / Domain

An engineer who learns your business

The hard part is rarely the code — it is knowing why an inspection needs two approvals, or which exception the finance team tolerates. An embedded engineer accumulates that knowledge instead of relearning it each engagement.

03 / Ownership

You own everything, throughout

Code in your repository, systems on infrastructure you control, documentation written as the work happens. Nothing is held hostage, and there is no handover event because there was never a handover gap.

04 / Operations

Run, not just build

Deployment, backups, monitoring, upgrades and incident response are part of the retainer. Software that nobody maintains becomes a liability within eighteen months, which is precisely when most project engagements have ended.

05 / Integration

Connected to what you already run

Your accounting system, WhatsApp, email, spreadsheets people refuse to give up, and whatever legacy database predates everyone currently employed. The integration layer is usually where the real work lives.

06 / Scale

Scales down as easily as up

Busy quarter, more days. Quiet quarter, fewer. A hire cannot flex like that, and a fixed-scope contract certainly cannot. The retainer is sized to the work, month by month.

§ 02 — How it works

Start small, earn the rest.

Nobody should sign a long retainer with a studio they have not worked with. Engagements start deliberately small.

01 · Immersion

Learn before building

A few days walking the actual process — watching the work, reading the spreadsheets, meeting the people who will use the thing. Often this alone surfaces changes worth more than the software.

02 · First win

Ship something useful in weeks

One narrow, visibly painful problem, solved and in production quickly. It proves the working relationship on something small before anything larger is committed.

03 · Rhythm

Settle into a cadence

An agreed number of days per month, a short weekly check-in, a visible backlog your team can reorder. Priorities come from the business, not from a contract signed last quarter.

04 · Compounding

Let the knowledge accumulate

Year two is cheaper than year one for the same output, because the domain understanding is already there. That compounding is the entire point of embedding rather than contracting.

§ 03 — Who this is for

Operationally complex, no software team.

This model is a poor fit for a one-off website and an excellent fit for a company whose operations have outgrown its tools.

Companies running the business on spreadsheets

Dozens of workbooks, one person who understands them, and a growing sense that something important will eventually be missed. The replacement cannot be bought off the shelf because the process is genuinely yours.

Firms with compliance or audit obligations

Inspections, approvals, certifications, incident records — anything where you must later prove who did what and when. These systems need continuous change as regulations and internal policy move.

Businesses that tried outsourcing and got a dead system

Something was built, delivered, and slowly stopped matching how you work. Nobody maintained it, so people quietly went back to email. The fix is continuity, not another rebuild.

Teams not ready to hire a developer

You need engineering capacity but not a full salary, and you would rather not be the company where one developer holds every system in their head. A retainer gives capability without that concentration of risk.

§ 04 — What it looks like in practice

Twenty-one months, one system.

An anonymised look at our longest-running embedded engagement — a safety-critical industrial operator with strict audit obligations and no internal software team.

Cadence

4,100+ changes shipped

Between September 2024 and June 2026, more than four thousand commits reached production — averaging close to ten working changes a day. Not one big release: thousands of small ones, each reviewed by the people who asked for it.

Scope

Fourteen modules, one platform

Incident notification, inspection reporting, root-cause analysis, safety observations, contractor assessment, document control, PPE issuance, training records, plant management, action tracking and metrics reporting — grown one at a time, not specified upfront.

Integration

Wired into what they already used

Two-way Jira ticketing, automated email notification chains, and role-scoped access across plants, contractors and internal departments — so the system fits the existing organisation rather than asking it to reorganise.

Why it worked

Nobody wrote a 200-page spec

The first module solved one visible problem. Each subsequent module was requested by people already using the last one. That is only possible when the engineer stays long enough to be asked.

§ 05 — Common questions

Frequently asked.

What is forward-deployed engineering?

A forward-deployed engineer works inside your business rather than at arm's length from it. Instead of taking a written brief and disappearing for three months, the engineer joins your operational rhythm — sits in on the problem, learns your domain, and ships small changes continuously. The model comes from enterprise software, where the hard part was never the code but understanding the customer's actual work. It suits mid-sized companies with real operational complexity and no internal software team.

How is this different from hiring a developer or outsourcing a project?

Hiring in-house means recruiting, salary, EPF and SOCSO, equipment, and a single person who takes all the system knowledge with them if they leave. Outsourcing a fixed-scope project means the work stops the day it is delivered, and the next change costs a new quotation. A retainer sits between the two: continuous capacity without a hire, and no restart cost every time the business changes.

How much does an IT-as-a-service retainer cost in Malaysia?

Retainers start from around RM1,500 per month for a few engineering days — enough to stabilise a system, clear a backlog and learn the domain. Larger embedded engagements, where we effectively act as the software team, run substantially higher and are quoted against an agreed number of days. Either way it is materially less than the fully loaded cost of an in-house developer once salary, EPF, SOCSO, equipment and recruitment are counted — and unlike a hire it scales down or stops with notice.

What happens to our code and data if we stop?

They are yours throughout, not at the end. Code lives in your repository, systems run on infrastructure you own, and documentation is written as the work happens rather than assembled during a handover. Ending the retainer means the work stops, not that access does.

Do you replace our existing IT support?

Usually not. General IT support covers laptops, networks, email and licences. This is software engineering — building and running the systems your business operates on. The two sit alongside each other, and we are happy to work with an incumbent IT provider.

How long do these engagements typically last?

Years rather than months, because the systems keep evolving with the business. That said, there is no lock-in — the retainer runs month to month with notice, and the value has to be earned continuously rather than argued at renewal. If you want the fixed-scope alternative instead, see custom software.

An engineer inside your business.