Scoping call
Book a call about
testing your application
Thirty minutes with Guy Nachum, CRO. We map what you have built, agree what is worth testing, and follow up with a fixed scope, timeline and price.
Thirty minutes
What happens on the call
Bring the person who knows how the system is built. That one detail makes the difference between a rough estimate and a real scope.
What we cover
What the application does, who its users are, where the sensitive actions live, and which parts you already worry about. Enough to scope properly — not a questionnaire.
What you get after
A written scope with a fixed price and dates, usually the same week. Retesting of every reported finding is part of the engagement, not an extra.
What this is not
Not a sales sequence. If a test is the wrong thing for you right now, we will say so on the call and tell you what we would do instead.
Pick a time
Times are shown in your own time zone. If nothing suits, send us a note and we will find a slot.
Useful to have ready
None of it is required. It just means the call ends with a number instead of a follow-up.
- What the application is — web, API, mobile, cloud, or an AI feature inside one of them.
- Roughly how big it is: how many user roles, whether tenants share data, whether there is an admin surface.
- What is driving the timing — a customer requirement, an audit deadline, or a release you want covered.
- Anything already tested, and what that test missed.
Not ready for a call?
Ask an engineer a question instead — a person who does the testing will answer it.