Five days looking inside your system.
Three findings reproduced in your environment. Led by a partner.
You pick one. Five days do not cover five fronts.
Each focus is a question we already know how to answer, because it is one we have answered while operating. Picking one is what makes five days end with a reproduced finding instead of an overview.
Silent failure
What is succeeding in the log and failing at the destination?
Integrations · queues · webhooks · reconciliation across systems
Measurement and revenue
Does the number the board sees match the source?
Dashboard · events · click-to-contract attribution · consent
ERP and multi-company
Does each legal entity know what is its own, and does the invoice come out right?
Master data · tax rules · intercompany · ERP integrations
Cloud, cost and security
How much of this account is waste, and who has access to what?
AWS account · IAM · cost per service · integration credentials
AI agents
What can the agent do on its own, and what does each task cost?
Agent tools · permissions · evaluation · cost per task
A finding that was not reproduced does not enter the document.
Each finding carries how it was reproduced, what it costs to leave as is, and what it costs to fix. This is not a best-practices report: it is what is happening in your environment, with the path to watch it happen again.
Five business days, with a start date and an end date.
- Day 0
A thirty-minute conversation to pick the focus, sign the NDA and grant read access. Write access is never requested.
- Days 1 to 4
Investigation. Each finding is checked at the destination, never in the log of whoever sent it — because the destination is where the gap between declared success and real effect shows up.
- Day 5
One hour with the decision makers, and a three-to-five-page document. No eighty-slide appendix.
You take the document and fix it yourself, with another supplier, or with us. All three outcomes are expected, and none of them depends on hiring us.
What is included, and what we do not promise.
What is included
- Three findings reproduced in your environment, with the path to reproduce them again.
- The cost of leaving it and the cost of fixing it, for each finding.
- A partner and a technical lead, from the first day to the last.
- A short document you can use with any supplier, including none.
What we do not promise
- A savings figure before measuring. If we did not measure it, we do not write it.
- A full audit in five days. One focus done properly is worth more than five done halfway.
- A finding that was not reproduced, however likely it looks.
This infrastructure is ours, not a slide.
- 108
- CloudFormation stacks in active operation
- 252
- Lambda functions sustained in production
- 170
- DynamoDB tables in operation
- 15
- named specialists, senior and lead
- 3
- own products running at scale
- 6
- years operating, without interruption
Figures from our own AWS account and our own team, not from a client project. That is the difference between operating and advising — and it is why we can publish them without asking anyone.
Questions we hear before we start
- What if you find nothing?
- You get what was reproduced, and the document says where we looked and found nothing. That is information too: knowing the reconciliation is sound is worth what it costs to find out. What does not happen is us filling the space with best practices so the document looks full.
- Do you need write access?
- No. Read access, and only within the chosen focus. Nothing is changed, nothing is deployed, none of our scripts run in production. If a finding requires a test that touches something, it goes into the document as a proposed test for your team to run.
- Is this a full audit?
- No, and it should not be. A full audit in five days is either shallow everywhere or deep nowhere. The diagnostic picks one focus and goes to the bottom of it, with findings you can verify yourself afterwards.
- What happens afterwards?
- You take the document. You can fix it with your team, take it to another supplier, or call us. If it is with us, the natural path is an engineering residency by mission, with the exit agreed from signature. None of the three depends on the others.
- Who runs it?
- A partner and one of our technical leads, both from start to finish. There is no handoff from whoever sold it to whoever executes it, because whoever talks on day 0 is who investigates on days 1 to 4.
- Do you sign an NDA?
- Yes, on day 0, before any access. And the final document is yours: we do not publish a client finding, not even with the name changed.
Five days is time to find the problem. It is not time to describe your business back to you.
Decision makers already know something does not add up. What is missing is the address.
Start with the thirty-minute conversation.
That is day 0: picking the focus and seeing whether it makes sense. If it does not, we say so in that same conversation.
Request a time