Send a message
Best when the details matter.
Use the form for project ideas, technical questions, collaborations, or anything that needs more than a sentence. It comes directly to me.
Let's talk
A polished brief is not required. Tell me what you are trying to make, what is getting in the way, and where things currently stand. We can figure out the rest from there.
Send a message
Use the form for project ideas, technical questions, collaborations, or anything that needs more than a sentence. It comes directly to me.
Book a call
Grab a thirty-minute introduction. No sales deck and no elaborate preparation; bring the problem and whatever context you have.
Open source
Bugs, feature ideas, and implementation questions are most useful when they stay close to the code. Open an issue so the answer can help the next person too.
No perfect brief needed
Enough context helps me give you a useful answer, but you do not need to solve the problem before contacting me. That would rather defeat the point.
What are you trying to build, fix, or figure out?
A live site, codebase, design, rough idea, or nothing yet are all valid answers.
A rough timeline, fixed launch date, current stack, or important limitation.
Share anything public that helps explain the problem. Keep credentials out of it.
Prefer regular email?
Please do not include passwords, API keys, private customer data, or other credentials in the first message. I reply personally, and if I am not the right fit, I will tell you.