Engagement shapes
Project, hourly, or retainer. Pricing and fit examples for each are on the services page, useful background if you’re not sure which shape you need.
See servicesContact
That is the whole contact form. Project, second opinion, weird hardware question, or just a hello. All welcome. Email is the front door and 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.
- What you’re building.Two sentences is plenty. Skip the company pitch. Go straight to the system.
- 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.
- What success looks like.A metric, a date, an outcome: anything more concrete than “AI strategy.”
- Constraints if any.On-prem only? Budget ceiling? Security clearance required? Tell me up front so neither of us wastes a call.
Before you write
The resume
The full record since 1997, role by role. The PDF is the shorter cut: 2014 to the present.
Download the PDF revised 2026-10-24
Read the resumePrefer chat?
Open a GitHub issue on any of my repos and tag @isenbek, totally fine for technical conversations.
github.com/isenbek (another site, opens in a new tab)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.
Write to brad@bradley.ioOpens your mail program with the four prompts above already in the message. Delete what does not apply.