How far the software has to reach decides the size of the build.

One tool for one person is Essential. The same tool with roles and approvals across a team is Standard. The same tool again, with your customers logged into it, is Advanced. That is the whole scoping logic, and it is the same in all four lines — so the question is never “what kind of software is this?”, it is who has to touch it?

Lines4
What sets the scopeReach, not category
First stepWorkflow Review · Free
QuotesPer job, after the diagnostic

Solutions · how the levels work

How far it reaches sets the scope. Not the category.

Reach sets the scope
Quoted per job, after the diagnostic
You own the source code
Custom engineering software on screen Illustrative
Four lines. One method underneath them all.

Why it is scoped this way

The category does not tell you how big the build is.

Most vendors quote by what the software is called — an ERP costs this, a CRM costs that. It tells you nothing, because two systems with the same name can differ tenfold in work. What actually drives the size of the build is how far the thing has to reach: how many people log in, whether anything gets approved before it leaves, whether it has to talk to another system, and whether anyone outside your company sees it.

1

One person, one job

One login. Nothing gets approved, nothing is connected, nobody outside sees it. The smallest thing that genuinely removes the work.

2

Your team, with a check

Everyone who touches the job has their own login and sees only what their role needs — and something gets approved before it leaves. One system you already run is connected.

3

Your customers too

People outside your company log in and see their own jobs. That is the step that changes the build most, and it is why it sits at Advanced.

Machines & Equipment is the honest exception. Its three levels are not reach — they are three stages of one purchase: find out whether a machine pays, buy the right one, then see what it produced. We would normally suggest the assessment first, then sourcing, and the assessment is credited in full.

An illustration of a build pipeline: capture, process, action and deliver stages joined by streams of light
An illustration of the shape every build takes — capture the input, process it, act, deliver

Before any of that

Two steps in. The first is free, the second is credited.

Workflow Review

Thirty minutes. You show us the actual files and we say honestly whether it is worth automating at all — including when it isn’t.

Freeno invoice, no obligation

Diagnostic & Blueprint

If the review says the job is worth doing, we go through the work properly and write it up: what it costs you a year, every rule we found, exactly what gets built, and the quote for the build. Yours to keep even if you never build with us.

RM 2,500credited in full against the build

Machines & Equipment is the one exception: the line assessment there includes a day on your floor, so it is quoted for your job rather than the RM 2,500 — and credited in full against whatever follows.

Deliberately not for us

E-commerce stores. Marketing websites for non-engineering businesses. Mobile apps. Generic CRM configuration. Social-media anything. If that is the brief, we are the wrong firm — happily. Specialists are defined by what they refuse.

Not sure which line?

Start from the problem instead of the product.

The ten problems we’re usually shown → Your industry →