Contact
Let's talk.
Email is the most reliable way to reach me. I read everything and reply within a couple of days.
What to include
A short email is enough. These details help me reply with something useful instead of a list of questions:
- What you are building and who it is for.
- The part you need help with — product, API, fix, or an audit.
- Any deadline or launch date.
- A link to the product, repository or a document, if one exists.
- A rough budget range if you have one. It shapes the scope conversation.
Hiring for a role rather than a project? Mention it in the subject line and include the role, location and time zone.
No form, just email
Tell me what you're building.
A few sentences and a link is enough to start. If it is not a fit, I will say so and point you somewhere better.