Software & Automation | Dominic Belavendram

What this looks like in practice

I have built software around a real operation. Here is what that looks like.

A telecom tower contractor

They survey and strengthen telecom towers for network operators — crews on the road across several states, and clients who want a report for every site with the evidence behind it.

The work used to move on WhatsApp, shared folders, and one coordinator's memory.

A technician opens the job on their phone at the tower and captures the evidence on site.
A coordinator reviews every document individually — approved or rejected, with the reason recorded against that file and the person who decided it.
A site cannot be approved until every required document exists and every one has been reviewed. The system refuses. It does not warn and let you through.
Batches of 62 sites run through it at once.
Purchase orders, invoices, petty cash, payroll and a statutory holiday calendar built to Malaysian employment law sit in the same system as the engineering work.
Every status change and every document decision is written to a record that can be read back months later.

And here is what it does not do.

It takes a job from the field to the client's survey report. The structural analysis and the strengthening design happen outside it, in the engineer's own hands — because that is where they belong, and because nobody had yet established what those steps actually require.

I know precisely where that system stops, because I went and mapped it. That is the same thing I would do for you, and it is the reason I don't guess.

How this would work

It starts with a conversation. What comes next depends on what you already know.

Step one · free

Talk to me for 10 minutes.

Tell me what happens today. Not what you want built — what actually happens now, and where it goes wrong.

I'll tell you whether this is something software can help with. Sometimes the answer is no, and I'll say so on the call.

Free. Ten minutes. No proposal follows unless you ask for one.

Step two · paid · only when it's needed

The Operations Reality Map

A written account of what your operation actually does today — where the work travels cleanly, and the exact point it stops.

This is a way to understand an operation before building it. If your requirement is already clear enough to scope, you don't need one — see below.

Fixed price

RM 5,000

Typically

5 working days

Depending on the operation and the material to review.

You get a document, not a slide deck:

What your operation demonstrably does — with the evidence for each finding, not an opinion
Where a job travels cleanly, and the exact point it stops
What your current tools know, and what they cannot establish
What is genuinely missing from the software — kept separate from what simply hasn't been explained to me yet
The questions only your own people can answer, written so you can ask them yourself
An honest view on whether software is the answer at all

Fixed price. The document is yours whether or not I ever build anything.

Step three

Then I build what's needed.

Scoped from what has been established — a Map if one was needed, or your own requirement if it was already clear. Either way you'll know what you're buying, because you'll have read the same thing I'm building from.

If it turns out software isn't the answer, there is no third step — and that is a good outcome. It cost you a conversation, or one document, instead of a system nobody uses.

Priced per build.

The shorter route

Already know what you want built?

Tell me what it is. If the requirement is clear enough to scope, I'll go straight to a build proposal. If it isn't, I'll tell you what needs to be understood first.

The 10-minute conversation is free either way. The Reality Map is not a compulsory purchase.

You know your business. I build the system that runs it.

Which one is you?

I don't start by selling you software.

You show me the work. I find out what it actually is. Then you decide what gets built.

I have built software around a real operation. Here is what that looks like.

And here is what it does not do.

It starts with a conversation. What comes next depends on what you already know.

Talk to me for 10 minutes.

The Operations Reality Map

Then I build what's needed.

Already know what you want built?

Talk to me for 10 minutes.