Blake Buchert
Contact

Let's talk about
what could
go wrong.

Direct

blakebuchert@yahoo.com

For sensitive reports, ask for my PGP key in the first message and send details in the encrypted reply. I read everything and answer within two business days.

Elsewhere

LinkedIn in/blake-buchert GitHub @blakebuchert Instagram @blake.buchert Facebook Blake Buchert X @blakebuchert Signal On request

How engagements usually start

01

A thirty-minute call

You describe the system and what is keeping you up. I tell you whether an engagement is the right instrument, or whether a workshop or a single review would serve you better.

No charge
02

A scoped proposal

One page: what gets tested, what is out of bounds, what you receive, and what it costs. Fixed fee, fixed dates, named deliverables.

Within a week
03

The work, then the handover

Findings arrive as they land, not in a final-week dump. Every engagement ends with a regression suite or a documented process your team owns.

2 to 6 weeks typical

Before you write

What kind of systems do you test? Anything where a model touches untrusted input or privileged actions: agents with tool access, retrieval pipelines, fine-tuning workflows, and the inference infrastructure underneath them.
Do you work through an NDA? Always, and I will sign yours. Published case studies only name clients who explicitly cleared it, and findings are summarized at whatever level you approve.
Can you work with our existing security team? That is the preferred arrangement. Most of my value is transferring method — your team should be able to rerun the testing after I leave, and that is what the handover is for.
Availability? Booking new engagements a quarter ahead. Short reviews and workshops can sometimes fit sooner, so ask.