Contact · Orlando, Florida
The best first messages start with something broken. Give me the situation rather than the compliment and you will get a specific answer back.
Messages land in one inbox and get read by the person whose name is on the site. No routing rules, no intake sequence, no assistant deciding in advance whether you qualify.
Rough is fine. 3 sentences typed between meetings will get further than a polished brief that takes a month to send. If the answer is a link, a name, or 30 minutes on a call, that is what comes back.
These 4 come up most. Each one lists the first message that saves us both a round trip.
Support operations, service delivery, AI in production, or the seam where all 3 meet. Roles that own delivery are more interesting than roles that advise on it.
A useful first message has: the team, what the role actually owns, whether it reports into support or into product, and the range.
The pilot demos beautifully and cannot get into production. The blocker is rarely the model. It is workflow design, a support organization that does not trust the thing yet, or a security review nobody wrote the case for. All 3 are operations problems, and I have shipped through each one.
A useful first message has: what you built, where it stopped, and who has to say yes before it ships.
Available for talks and workshops on shipping agentic AI into live support operations, and on getting AI past security review. The speaking record on this site is empty. It will not be padded to look otherwise.
A useful first message has: event, date, audience, format, and what the room should be able to do the next morning.
How deflection gets measured honestly. What an evaluation loop looks like once it is running. What the guardrails actually cover, and what they cost you. Questions like these get an answer whether or not there is anything in it commercially.
A useful first message has: the question itself, and enough context that the answer can be specific instead of general.
None of the 4 quite fit? Write anyway. The list is a guide, not a gate.
Eastern time, from Orlando. If nothing comes back, a spam filter ate it, so send it again to the address below. Silence is never the answer here.
Email is faster and leaves a record both sides can check. If a call is the shorter path, expect 30 minutes, an agenda in advance, and something written down at the end.
If it is not a fit, you get told in the same thread, with the reason. No slow fade, no permanent maybe.
References are available on request. A name appears here only once that person has agreed to it in writing. Until then the slot stays empty on purpose.
The same inbox the form writes to. Job specs, event briefs and attachments belong here.
Best for a short introduction, or a role you would rather not put in writing yet. Send the connection request with a note; blank ones get left alone.
One inbox, read by the person whose name is on the site. No routing rules, no intake sequence, no assistant deciding in advance whether you qualify.
Happy to go as deep as useful on the work itself: how a rollout was sequenced, what the guardrails covered, where it broke. A worked plan for your program, delivered free across 3 calls, is consulting. That gets a scope and a proposal, not an afternoon.
Everything here is a personal record and a personal opinion. Nothing on this site is an official position of any employer. Nothing confidential goes into a conversation, in either direction.
Vendor mail goes unanswered unless the product is already in a workflow I run. Nothing personal. The inbox has to stay usable for the people who have a problem.
Orlando, Florida. Eastern time. There is no phone number on this site by design. Once a conversation is running, a call is easy to arrange.