How to prep for your free intro call

You do not need a perfect inventory to book a free intro. You do need enough context that we can recommend a sensible first review. Ten minutes of prep usually beats an hour of vague conversation.

Write four short answers

What does the business do? What do you want reviewed? Which domains or systems are in play? What deadline or pressure exists — customer questionnaire, launch, incident worry, insurance, gut feeling after a near-miss? Put that in a note before you join. It keeps the call concrete.

If you already suspect the category, say so. Website or client portal points toward Web. Unknown internet exposure points toward External Infrastructure. Public company data and phishing fuel point toward OSINT. Messy rules and remote access point toward Firewall. If you are unsure, that is fine — sorting that is part of the call.

Bring constraints into the open

Mention change freezes, production sensitivity, who can authorise testing, and whether environments are shared with clients. Authorisation issues are easier to solve early than mid-scope. Remember: we only work on authorised assets and we refuse third-party targets without permission.

What not to prepare

You do not need a formal RFP. You do not need to pretend you want a full pentest if you do not. You do not need marketing slides. Founder-led buying can be direct. Also skip any request that implies we look at any company; that is not the model.

After the call

If there is a fit, we schedule the scope and prerequisites call before assessment work begins. If there is not, you should still leave with a sharper sense of next steps. Either outcome is useful. The intro call is free because clarity is the product of that first conversation, not a paid proposal ritual.

Book a slot when you can speak freely for half an hour. If email is easier first, use hello@boundaryproof.co.uk or the site contact form with the same four answers. We will meet you where you are — then keep services within Web, External Infrastructure, OSINT and Firewall.

Optional extras that help

If you have a network diagram, even a rough one, keep it handy. If you know your cloud providers and where DNS lives, note that. If there was a recent incident or near-miss, summarise it without blame. If a customer security questionnaire triggered the call, say which controls they asked about. Those details steer the recommendation without turning the intro into a free assessment.

Finally, decide what success looks like for you: peace of mind before a launch, a cleaner firewall, a public exposure tidy-up, or a web portal check. One sentence on success keeps the call aligned.

Common prep mistakes

Over-preparing a slide deck wastes time you could spend listing real systems. Under-preparing so thoroughly that you cannot name a domain wastes the call the other way. Aim for a one-page note. Another mistake is bringing a hidden agenda to assess a third party — we will refuse, and the call becomes awkward for no benefit.

If multiple stakeholders join, nominate one decision-maker for next steps. Free intros work best when someone can say “yes, let’s scope Web next week” or “not now”. Committee silence is how good conversations die.

Finally, treat the call as confidential business discussion. Share what we need to advise; do not paste secrets into a calendar invite description. Use the meeting itself or a follow-up email for sensitive detail.

← Back to blog index · Home