Hackerbane

Request a scoping call

We need the surfaces, the stack, and when you ship. A pitch deck is not useful here. We reply within two business days with a call or a decline.

What happens next

  1. 1Two people read it. We do not route it through a queue.
  2. 2You hear back within two business days: a scoping call, or we decline. That reply is not a proposal deck.
  3. 3Nothing starts until scope, threat model, and out-of-scope are written down and agreed.

Before you write

What is the call?
Thirty to forty-five minutes. Two of us, including someone who would do the review. Bring the surfaces and the date. It is not a demo.
Do I need an NDA first?
Send the request. If the stack cannot travel, write that in “What must stay private” and we will use a channel you name.
What does it cost?
We quote after the brief is written, not from this form. If the timeline or the surface does not fit, we decline.
Will you publish the report?
Only if you clear it. Publication is the default we will ask about, not a surprise.
I am not ready to scope.
Use office hours. Same people, no repo required.

We may decline work that is a simple token stamp or a chatbot governance memo.

Protocol, company, or lab.

Surfaces in play

Chains, languages, model hosts, agent tools.

What is going to production, and the date or event it must meet.

Names, unreleased features, or None.

Optional.

Telegram or X, if that is how you reply.

Lines of code, or the agent plus what it can sign.

Earliest day the code or artifact is stable enough to review.

Role