start · sheet 05
Start with the component you’d least like to be asked about under oath.
Routing, auth, billing, the parser everything goes through. You know which one it is.We scope it with you, agree a fixed fee before work starts, and spend roughly four weeks with the engineers who own it. You keep the requirements and the tests, whatever happens afterwards.
A person replies. Then a scoping call, or an honest no.
Within two working days
Leonid reads every request and replies personally. If the component you named is not a fit, we say so and tell you why.
The scoping call
Thirty minutes with the engineers who own the component. We agree the boundary, the access we need, and the fixed fee before any work starts.
Before any code is read
We countersign your NDA. Private code stays private; the only thing that is ever public by default is the jsonparser audit you have already seen.
What we need from you
Access to the component and its history, and a few hours a week from the engineers who own it. Their reading and approval is where the accuracy comes from.
Request an audit.
An email address is enough to start. The rest is optional, and everything you write stays between us.
Prefer email? [email protected]Read the receipts first →
proof · reqproof.com · sheet 05 of 05 · rev continuous