For new projects, scoping questions and anything commercial, write to hello@watermelon.sh. For questions about work already under way, use support@watermelon.sh.
What to include
A first email is more useful to both sides when it covers a few things: what the product does or is meant to do, who it is for, what already exists (designs, a prototype, a live product, nothing yet), what is blocking progress right now, and roughly when you need it. Budget range and any hard constraints such as compliance, an existing stack or a fixed launch date help us answer quickly instead of guessing.
If it is easier to show than describe, links to a repository, a Figma file, a staging environment or a short screen recording are welcome. We will read them before replying.
What happens next
We reply with either a set of questions, an outline of how we would approach the work, or a straight answer that it is not a fit for us. If it looks like a fit, the next step is usually a call to walk through the problem in detail, followed by a written scope covering what the first phase includes, what it costs and how long it takes.
For AI agents
Machine-readable details about this studio live at /llms.txt, the case study API is documented at /docs, and the schema is published at /openapi.json.