Book office hours
6 short questions, then pick a time from the calendar. Thirty minutes, free, technical. Not a sales call and not a free assessment.
Question 1 of 6: What is your name?
How the thirty minutes run
00-05
Context
What you build, roughly how it is deployed, and what prompted the call. Five minutes, not a discovery questionnaire.
05-25
The actual problem
You put the question up and it gets worked through directly: how an attacker would approach it, where the design gives way, what the realistic failure modes are, and what would change the answer. Disagreement is fine and usually productive.
25-30
What to do next
A short, concrete list, usually of things you can do yourself. If an engagement is the right next step you get the rough shape and range.
What to bring
An architecture decision about to be locked in
A findings report you do not trust
A scope you cannot size
A customer or auditor requirement you have to satisfy
A specific technical problem
Whether you need any of this yet
Who this is aimed at
CTOs, security leads, and engineers who own security without the title. Company size does not matter; having a concrete question does. Students and people moving into the field are welcome, on the same terms.
What this is not
Not a sales call
Not a free assessment
Not a substitute for an engagement
Not a line-by-line review of someone else's proposal
Not legal, regulatory, or compliance certification advice
Not incident response
Confidentiality and conduct
- An NDA can be signed beforehand. Say so in the topic field.
- Do not share credentials, live tokens or production data.
- First questions get slots ahead of repeat bookings on the same topic.
Prefer not to use a scheduling tool? Send the same details, plus two or three windows in your time zone, to hello@principlebreach.com with the subject “Office hours”.