An independent review before you commit your budget
A quote to check, an offer to compare, an architecture to validate: an outside view, with nothing to sell you afterwards.
Who reads the quote?
A quote takes a minute to sign. What it leaves out gets paid for later.
You have a quote for a new tool, several responses to a tender, or a proposal to rebuild your application. If nobody in-house can read them with a technical eye, or your technical team is too busy with current projects to dig into them, you compare the totals, and you choose on price or on trust. If you have a technical team, we review alongside them, not instead of them.
What is missing shows up later: moving the data across, the hosting, maintenance after delivery, the source code that stays with the provider. It comes back as extra quotes, at a point where you can no longer say no. Nobody is to blame: an offer is written to be chosen.
- What is not in the quote, and who will pay for it?
- Does the quoted price cover the first year, hosting and maintenance included?
- Who will own the code, the accounts and the domain name?
- If this provider is no longer around in three years, can someone else take the tool over?
If one of these questions has no answer, now is the time to ask for a review.
What we review
-
A quote
What it covers, what it leaves out, and whether the price fits the work described.
-
A tender response
Several offers, compared on the same criteria, and not just on their total.
-
An architecture
The technical choices on the table: do they fit the size of your business, your budget, and whoever will have to maintain them?
-
An existing application
A new project has to build on it: can it carry the project, or does it need putting back on its feet first?
What you get
A short written opinion, with figures. An answer, not an inventory.
- What the offer covers, and what it leaves out.
- What the project will really cost you: the quoted price, and what will be added to it (hosting, maintenance, licences, data migration).
- The risks, ranked by what they could cost you.
- The questions to ask the provider before you sign.
- Our opinion, in plain words: sign, negotiate, or rethink the project.
And we will tell you when a project is not worth starting.
Why not a technical audit?
You may have searched for a "technical audit". An audit records findings, point by point, and leaves you with the list. Before you commit a budget, you do not need an inventory: you need an answer. Is it the right project, at the right price, with the right provider?
That is why we give an opinion, and put figures on it. If the answer is no, you will hear that too.
Independent review or health check?
One looks at a project that has not started yet, the other at an application that is already running.
-
The independent review
Before you commit: a quote, an offer, an architecture. It answers one precise question, at the moment you decide.
-
The health check
For a tool you already use every day: what it costs you, what will break first, and three priced proposals.
No quote yet? A rebuild or a tender starts with a requirements specification.
Replacing an existing tool? See also when to rebuild.
Frequently asked questions
What if your opinion contradicts my provider's?
We tell you why, with figures, and we give you the questions to ask them before you sign. Their answers let you decide: sign, negotiate, or rethink the project. We have nothing to sell you afterwards, and the decision is yours.
How long does a review take?
It depends on what there is to read: a single quote, several offers to compare, or an architecture. Tell us at the first conversation when you have to decide: a review is useful before you sign, not after.
Do I need to show you the quote?
Yes, the full quote, with any appendices: what is missing shows in the detail, not in the total. If you have received several offers, send them all: we compare them on the same criteria.
A quote on the table?
Talk to us before you sign.
The self‑assessment is about a tool you already use: ten questions, your score straight away.