SHADOWCORE_
OFFENSIVE OPERATIONS · ADVANCED MODE

Detailed scoping
for a reviewed proposal

The quick calculator gives a preliminary band. This questionnaire gives us what we need to price the engagement properly — the same questions we'd ask on a scoping call.

  1. 01
    You describe the scope

    10–15 minutes. Only the sections for the targets you pick are shown; blanks are fine — we state the assumption.

  2. 02
    We review it as engineers

    A senior tester checks the scope for gaps and risks before any number is put on paper.

  3. 03
    You get a scoped proposal

    Hours, price and timeline within 2 business days, then a 30-minute call to confirm.

Step 1

Who are we scoping for?

We reply to this address with the proposal.

Step 2

What should we test?

Select everything in scope — a section opens for each. Mobile apps, GCP/Azure and physical testing are outside our specialization.

Step 3

How should we test?

Grey-box is the usual choice — it finds logic flaws faster than black-box.

Step 4

Deliverables beyond the report

Every engagement includes an executive summary, CVSS-scored findings with reproducible evidence, and remediation guidance.

Step 5

Timeline

Testing starts after the NDA and accesses are in place.

Step 6

Context

Doesn't change the hours — it shapes the proposal and what we look for first.

Helps us propose the right depth, not a different price.

Give a colleague's details only if they know you are sharing them. We will contact them during testing and tell them how we got their details, as set out in our Privacy Policy.

By submitting you agree that we process your details to reply, as described in our Privacy Policy.

No number appears on this page by design — our team reviews the scope and replies with a proposal (hours, price, timeline) within 2 business days. Your answers are used only to prepare that proposal.

Prefer the quick version? Back to the calculator — or book a scoping call instead.