First, a review free of charge
Before we propose a full audit, we spend about 60 minutes talking to the person who runs the process or the system. This first review needs no access to your code or your data.
Afterwards we send you a one-page summary of what we saw and whether we think it is worth going further. If it is not, we will tell you.
When it makes sense
People usually call us when there is a decision on the table and not enough information to make it.
- You are about to buy new software or rewrite what you have, and you are not sure it is needed.
- The important information lives in spreadsheets and emails. Only one or two people know how it all fits together.
- Two reports give different figures for the same thing.
- You have a system that works, but it is slow, fails now and then and nobody dares to touch it.
- The supplier who built it has gone and you need to know what you have inherited.
- A regulatory deadline such as Verifactu is coming and you do not know how much has to change.
What we review
Depending on what the first review shows, the audit focuses on the operation, on the software or on both.
Operations audit
How information moves today between people, departments and tools.
- The steps, hand-offs and approvals of each process.
- Data typed in more than once or copied between spreadsheets.
- Who decides what, and where it is recorded.
- Which figures are used to make decisions, and where they come from.
Technical audit
How an existing system is built and how much load it can take.
- Architecture, code and dependencies.
- Database: model, slow queries, indexes and integrity.
- Performance, security, backups and deployment.
- Technical debt: what it costs to maintain and what it risks to leave it as it is.
We know systems built with Laravel, Livewire and PostgreSQL particularly well, although we review other technologies too.
Specific audits
- Verifactu What has to change in the way you issue invoices, corrective invoices, cancellations and pro formas to comply.
- AI readiness Where your company’s knowledge lives, who may see what, and whether your documents are fit for an assistant.
- Integrations Which systems you have, which one owns each piece of data and what is passed on by hand today.
- Handover of an inherited system What you are receiving, what is left to document and what risks come with taking it on.
How it works
- First reviewA conversation of about 60 minutes and a one-page summary. Free of charge.
- ProposalIf it is worth going on, we tell you what we will review, who we need to talk to and what access we need.
- ReviewWe talk to the people who run the process, look at the systems and, for a technical audit, at the code and the database.
- ReportWe send it to you in writing and go through it together in a session with your team.
What you get
- A written report on what we found and why it matters.
- A map of the process or the architecture as they stand today.
- A list of improvements ranked by impact and effort, with the ones to tackle first.
- An estimate of the next step, if there is one.
Sometimes the conclusion is that nothing needs rewriting. That goes in the report too.
And then what
The report is yours. You can act on it with your own team, with another supplier or with us. If we work together, the project starts with the problem already understood, and that shows in the timescale and the cost.
Where we’ve done it
- The analysis that recommended not building yet Sports · Sports organisation The recommendation was to put the internal information flows in order first.
- A public funding process, from requirements to execution Public sector · 140 employees · 2017 Responsibilities and workloads redistributed across departments.
- Verifactu, inside invoicing software that already worked Invoicing · LATIDE in-house project 100% of invoicing confirmed with the Spanish Tax Agency.
Frequently asked questions
How much does an audit cost?
The first review is free of charge. A full audit depends on the size of the process or the system. We give you a fixed quote before we start.
How long does it take?
It depends on how many people and systems are involved; it can take up to a month. We give you the timescale in the proposal, after the first review.
What access do you need?
None for the first review. For an operations audit, time with the people who run the process. For a technical audit, read access to the code and to a copy of the database or a test environment.
Who needs to take part on our side?
Whoever knows the day-to-day running of the process and, for a technical audit, someone who can give us access and answer questions about the system.
What happens to the information you see?
We treat it as confidential and can sign a non-disclosure agreement before we start. We never name our clients.
Do I have to hire you afterwards?
No. The report is yours and you can act on it with whoever you prefer.
Do you review systems you did not build?
Yes. Many of our technical audits are of systems built by another supplier or by a team that has since left.
Tell us what you want reviewed.
A few lines about the process or the system are enough for us to prepare the first review.