From a thirty-minute look at your files to a system you own.
Here is exactly how it runs. We look at your files first, then diagnose, then quote. No build is sold until the scope is written down. At the end you choose how the system stays alive. Nothing on this page is a surprise later.
The whole road
Five steps, then a choice. You can stop after the first two at no further cost.
Workflow Review
Thirty minutes. You bring the files.
Diagnostic & Blueprint
The scope, written down. Yours to keep.
The quote
Tied to the Blueprint, paid by milestone.
Built to your method
Checked against your own past jobs.
Handover
Source code, training, documents.
Then a choiceAt handover you choose between Fixed and Done or the Continuous Development Plan. Both are explained below, with the sums.
Step 1 · free · thirty minutes
Bring the actual work.
You show us how the job happens today — the spreadsheet everyone is afraid to touch, the quote template, the drawings, the folder of past jobs. We look at the real thing, not a description of it.
By the end you have a straight answer to two questions: can this be turned into software that gives the same answer every time, and is it worth doing. If the answer is no, we say so, and you have lost half an hour. If it is yes, you know what the next step costs before you leave the call.
What to bring
- The spreadsheet or calculation you use most, exactly as it is
- One finished job, start to end — enquiry, quote, drawings, invoice
- The last time it went wrong, and what it cost
- Whoever actually runs it today, if they can join
No slides, no specification, no budget line. The files are the preparation.
Step 2 · RM 2,500 · credited in full against the build
The scope, written down — yours to keep whatever you decide next.
We go through the work properly: where the hours go, which rules are written down and which live in someone's head, what breaks and how often. You get two documents.
The Diagnostic Report
- What the process costs you now, in hours and ringgit, from your own numbers
- Where the errors come from, and how often
- What is worth automating, and what is not
- How many of your rules are documented, and how many are in someone's head
The Workflow Blueprint
- What gets built, and what does not
- Every rule we found, written down
- What "finished" means, in terms you can check
- The quote for the build, sized to your job
You keep both documents and owe nothing more. The Blueprint is written so that any competent developer could build from it. If you go ahead with us, the RM 2,500 comes off the build price in full.
Step 3 · the quote
Quoted for your job, from the Blueprint.
Every job is different, so every quote is. The price comes from what the Blueprint found — how many rules there are, what it has to produce, what it connects to and who uses it — not from a price list. It is agreed with you before the build starts, and if the scope changes it is re-quoted. You pay by milestone. The first payment starts the work; the other two are each against something you can see running on your own data.
| Milestone | What you have seen by then | Share |
|---|---|---|
| Start | Blueprint signed, scope agreed, the RM 2,500 credited | 40% |
| First working version | The tool runs on your real data. You use it, we adjust. | 30% |
| Validated handover | Twenty of your past jobs re-computed and matched within a tolerance agreed in writing — the Re-quote Test | 30% |
Step 4 · the build
Built on your rules and templates, then checked against jobs you have already done.
We build to the Blueprint, on your rate tables and your document templates. Before the final payment, the system re-computes twenty jobs you have already done, and the results are laid side by side with what you actually issued.
Where they differ, we find out why — sometimes the spreadsheet was wrong, sometimes the build is — and you see the comparison in writing before you pay the balance.
Step 5 · handover
At handover the source code is yours outright.
What you leave with
- The source code, yours outright — no licence, nothing that stops working if we disappear
- Training for the people who will use it, and a written guide for each role
- The ability to change your own rates, materials and document wording without calling us
What is true at every step
No build is quoted before the diagnostic, and the final payment is not due until the system has matched your past jobs.
The quote is for a written scope, agreed before work starts. The final payment is not due until the system has reproduced your own known results. You own the source code on either option, from the day of handover. If the review says it is not worth building, that is what we tell you.
After the build
Two ways to keep it alive. You choose at handover.
The difference is whether the system has to keep up with the business, or can run as built for years without changing.
Fixed and Done
The build price. No recurring charge.
- Thirty-day warranty — any bug found in the first thirty days is fixed free
- After that it stays exactly as built unless you ask for a change
- No monthly cost and no contract
What it costs laterChanges, new features or fixes after the warranty are quoted at RM 450 an hour, with a minimum charge of half a day (four hours, RM 1,800). The rate covers re-reading a system we have not worked on for a while before we change it, and you get a written quote before any work starts.
Continuous Development Plan
20% of the build price a year, billed monthly. Cancel any month.
- Every bug fixed, for as long as you are on it — not thirty days
- Continuous development — new features, new rules and new report formats as the work changes
- Monitoring, backups, and updates when a supplier changes a form or a bank changes a file
- New users added, and your staff re-trained when they change
What stays trueIt is a service, not a licence. Cancel it and everything keeps working exactly as it did. You are paying to keep it alive and moving, not for permission to use it.
The sums
| Build price | Continuous Development Plan, a year | Per month | Fixed and Done: one later change of two days |
|---|---|---|---|
| RM 12,000 | RM 2,400 | RM 200 | RM 7,200 |
| RM 30,000 | RM 6,000 | RM 500 | RM 7,200 |
| RM 60,000 | RM 12,000 | RM 1,000 | RM 7,200 |
One two-day change at the change rate costs more than a year of the Continuous Development Plan on a RM 30,000 build. That is the whole comparison, and you can do it yourself. A Fixed and Done client can move to the Continuous Development Plan later. We first do a code review, quoted in writing at the change rate before it starts, so both sides know the state of the system.
The questions a careful buyer asks
Straight answers, before you book.
What if the review says it can't be done?
Then you have had a free half-hour with someone who looked properly, and you know. We would rather say no on a call than have you find out on an invoice.
What if I stop after the diagnostic?
You keep both documents. No obligation, no follow-up calls. The person who wrote the scope already knows it, which keeps the build quote down — but going ahead with us is not a condition.
What counts as a bug, and what counts as a change?
A bug is the system doing something the Blueprint says it should not. A change is anything the Blueprint did not cover. The Blueprint is the referee, which is why it is written first.
Can I switch from Fixed and Done to the Continuous Development Plan later?
Yes. We first review the code so we know its state; the review is quoted in writing at the change rate before it starts, and the Continuous Development Plan begins the month after.
Do I have to use Valtrin for the build after the diagnostic?
No. The Blueprint is yours, and it is written so any competent developer could build from it.
How is the build price worked out?
From the Blueprint: how many rules have to be encoded and proven, how many documents it produces, what it connects to, and who uses it. Every quote is for a written scope, agreed before the build starts, and re-quoted if the scope changes.
Start with the thirty minutes
Bring the file you are most tired of.
No slides, no pitch. You show us the work, we tell you whether it can be fixed and what it would cost to find out properly.
calvin@valtrintechnologies.com
+60 11-1122 6683 · Kuala Lumpur, Malaysia
The review is free, and “not worth automating” is an answer you may get.