First the audit, then the build.
We look at what you run today, at what a quote from another firm actually contains and at which step should come next. You get a report your management can read, and when that is the honest answer, the advice to build nothing for now.
- Independent of your supplier
- A written, prioritised report
- Fixed price after the consultation
Four situations where a decision is due and the basis for making it is missing.
A quote sits on your desk
An IT firm has quoted, and you cannot judge whether the price and the approach make sense. The question is rarely whether the firm is any good, but whether the right things are on the paper.
The software keeps playing up
It is slow, it drops out, somebody patches it by hand, and nobody can explain why. While the cause stays unknown, every repair is guesswork.
Going digital with no starting point
You know something has to happen, but not what comes first. Ten good ideas with no order to them are not a plan, they are a wish list.
No technical lead of your own
Systems, contracts and suppliers get decided without anyone in the building able to judge the technical consequences. The bill for that arrives years later.
Six pieces of work, and all of them begin with somebody looking closely.
A technical audit of what you run
Architecture, code, security, dependencies and the jobs left half finished in the software you use today. What comes out is not an impression but an ordered list of findings.
Audit of an AI project
When an AI project stops moving, the model is rarely the reason. We look at the data, the model, the integration and the running costs, and tell you what is actually holding it up.
Digital roadmap
What comes first, what waits and what gets dropped, with the effort and the benefit of each step, so the plan holds up in front of the board and in front of the budget.
Rescuing a stalled project
A project that has come to a halt: stabilise it first so the business keeps running, then say plainly whether carrying on or starting again works out cheaper in the end.
Interim technical leadership
Technical leadership by the day for organisations without an IT lead of their own: in the room when decisions are made, and the voice that asks the awkward questions.
Reading third-party quotes
Another firm’s quote read in technical terms before you sign: what is included, what is missing and which questions you should still put to the supplier.
What you get in writing
The report is not written for software people, it is written for the people who have to decide. Technically backed up, but in sentences that need no translation.
Ordered by urgency
What matters this week, what can wait until the autumn and what is merely cosmetic. Without that order, every finding causes the same amount of alarm.
What it costs to do nothing
Each point says what happens if it is left alone: downtime, manual work, an open security hole, or dependence on the one person who knows how it works.
What the existing system can still do
A great deal can be saved. We say what can be repaired, connected up or simply configured differently, before anyone starts talking about building it all again.
A second opinion on another firm’s quote
We do not judge the firm, we judge what is on the paper. A quote is a technical statement, and it can be read properly before it turns into a contract.
What is not in it
Moving the old data across, training, hosting, maintenance after launch. Whatever is missing from the quote is missing from the fixed price too, and gets invoiced later.
Who owns the code
The most important question in the contract: do you receive the source code, or are you renting it? And are the accounts with third-party services in your name or the supplier’s?
The day you want to change supplier
Ask before you sign how a handover works and what comes with it. If the answer stays vague, that vagueness is the answer.
Four stages, and the decision at the end is yours.
- 1
A conversation about the decision
Free and without obligation. First we work out which decision is actually due: buy, build, repair or leave it for now. After that we both know what we are looking for.
- 2
The review, with access
We look into the system, into the code and into the numbers, and we talk to the people who use it every day. Without that access, an audit is only an opinion.
- 3
Report and options
You receive the report in writing, with priorities and with routes to choose between, and we present it in person. Questions get answered where they come up.
- 4
Support if you go ahead
If you decide to act on it, we stay alongside you: with us as the developers or with the supplier you already have. The report is yours and it works without us.
When our advice will not help
- If the decision was made long ago and you are only looking for hands to carry it out: then we should be talking about the development work instead.
- If what you want is confirmation of a decision already taken: we will write down the opposite as well, when the opposite is true.
- If we cannot have access to the system and cannot speak to anyone who works with it: guessing from a distance is something anyone can do.
- If the report has to be on the table in two days for a system that has grown over years: a quick diagnosis here would only be guesswork.
What does an audit cost?
It depends on how large the system is and how deep we are meant to look, which is why we do not name a figure before we know that. At the free initial consultation we settle the scope, and after that you receive a fixed price for exactly that scope. Reading a quote is a small piece of work; auditing a platform that has grown over years is a considerably bigger one.
Free initial consultationCan you be independent when you build software yourselves?
That is the right question to ask. It is why the report always includes the route that works without us, and why we write it down when your current supplier is doing a good job. Whether we build anything afterwards is something you decide after the report, not before it.
We have a quote for a large sum. Is a second opinion worth it?
Especially then. Reading another firm’s quote in technical terms is a contained piece of work, and the questions it raises are better asked beforehand than afterwards: what is not included, who owns the source code, what happens if you change supplier, and who carries the running costs after launch.
What do you need from us?
Access to the system and to the code, whatever documentation exists, and one or two conversations with the people who work with it daily. If your current supplier grants access, it goes faster. If they do not, we tell you in advance what can still be judged without it and what cannot.
Can you rescue a project instead of rebuilding it?
Often, yes. First it gets stabilised so the business keeps running, then we cost out both routes: carry on or start again. We tell you plainly which one works out cheaper in the end, even when the honest answer is the smaller job for us.
And if you conclude that we should not build anything at all?
Then that is what the report says. Sometimes the answer is a setting in the existing system, a different way of working in the team, or a standard product that already exists off the shelf. Finding that out in time is the whole point of an audit.
Tell us which decision is on the table.
At the free, no-obligation initial consultation we listen to what it is about and tell you whether an audit will help here or whether the answer is already in front of you. We reply within 24 hours.
Book an initial consultationJust a quick question? The AI assistant in the bottom right answers straight away.
Ready for the summit?
Tell us about your project. We reply within 24 hours with an honest assessment. Free and without obligation.
hallo@aurphi.chAurPhi MoukrimMarktstrasse 18, 8853 Lachen SZ, SwitzerlandPostal address, no walk-in service. Appointments by arrangement.