Contact · open inbox

Drop me a line.

Project, second opinion, weird hardware question, or just a hello — all welcome. Email is the front door; GitHub is the side door; both lead to the same room.

What helps a first email

None of this is required — but a paragraph hitting these four points means I can reply with something useful instead of a follow-up question.

  1. What you're building.
    Two sentences is plenty. Skip the company pitch — go straight to the system.
  2. What hurts right now.
    The specific failure, the slow query, the box that won't talk. The reason you're reaching out today and not last month.
  3. What success looks like.
    A metric, a date, an outcome — anything more concrete than "AI strategy."
  4. Constraints if any.
    On-prem only? Budget ceiling? Security clearance required? Tell me up front so neither of us wastes a call.

One paragraph. That's all I need.

Bring the problem. I'll bring the questions. Worst case you walk away with a clearer picture of what to do next — and that's free.

brad@bradley.io →