Decision Review
- Type
- One-off work
- Result
- A written recommendation on one software decision, before you commit money to it.
You are about to sign a proposal or pick a direction, and want an independent view first.
What is in scope
- One decision: which of two proposals to take, or whether to fix or replace a system.
- Reading the proposals, quotations and documents you share.
- A discussion with the person making the decision.
- A short written recommendation: what we would do, why, and the risks.
What you bring
- The decision, in a sentence or two, and when you need to make it.
- The proposals or documents behind it.
- The person who will decide.
Not included
- Checking your code or logging in to your systems. That is a System Review.
- A full project price for the option you choose.
- Legal review of contracts.
- More than one decision. Each one is its own review.
Price and terms
RM1,000, paid before we start. Prices exclude SST.
How it starts
- 1.
Send us the decision
What you are deciding, the options and when you need to know.
- 2.
We check it fits
If the answer needs more than documents and a conversation, we tell you before you pay.
- 3.
Review and recommendation
We read, we talk it through with you, and you get the recommendation in writing.
Questions about Decision Review
No. A Decision Review works from your documents and a discussion. If the answer depends on what is inside the code, you need a System Review.
No. The recommendation is yours to use with any team or vendor.
Tell us what isn’t working.
A few lines is enough: the system, what’s going wrong and what it’s costing you. We’ll reply with where we would start.