Contact

Start with the problem you want to solve.

The best first message is concrete, but it does not need to be polished. A rough idea, existing workflow pain, or unclear product direction is enough to begin.

What to include

These questions keep the conversation useful and help filter for projects where product judgment and practical implementation both matter.

  1. What are you trying to build or improve?
  2. What exists today?
  3. What would a useful first prototype, improvement, or automation prove?
  4. Where are you based?
  5. What budget or timeline constraints matter?
  6. How should I contact you?

Privacy note

Once the Tally form is connected, submissions will be handled by Tally and used only to understand the project fit and reply to the conversation. This static site does not run a custom backend or database.