Every channel below reaches me directly. No forms, no assistant, no ticket queue. Pick the one that fits what you want to say.
Best for consulting and training inquiries, and anything worth writing properly. I read everything myself.
replies within 2 business days
Good for introductions and quick professional questions. Add a line about what you are working on when you connect.
checked on weekdays
For short questions and scheduling once we are already talking. Messages only, please. No calls.
messages only
If you are writing about a project
Most consulting mail I receive is missing the one detail that would let me answer it. A first email that covers these four things usually gets a same-week reply with a clear yes, a clear no, or a pointer to whoever you actually need:
- The problem, in a paragraph. What hurts today and what better would look like. Plain words beat a requirements document.
- Your stack and team. Languages, platforms, and rough team size. Enough for me to picture the codebase.
- The constraints that matter. Deadlines, budget range, and rules like “code and data cannot leave our network”. That last rule is my specialty, not a blocker.
- Where you are in the decision. Exploring options, comparing consultants, or ready to start.
The consulting page covers what an engagement looks like: scope, format, and focus areas.
Everything else
Questions about the books, comments on an article or a video, webinar and speaking invitations, workshop requests: all are welcome, and email is the right channel for every one of them. If you have found a mistake in a post or a book, say so in the subject line: corrections are the mail I answer first.