# Contact

How to reach Xocket, what to include in a first email, and what happens after you send it.

[Home](/)

# Contact Xocket

Email is the way in. Tell us what you are building and we will tell you honestly whether we are the right studio for it.

## Email

For new projects, scoping questions and anything commercial, write to [remotevansh@gmail.com](mailto:remotevansh@gmail.com). For questions about work already under way, use [remotevansh@gmail.com](mailto:remotevansh@gmail.com).

## Book a call

If you would rather talk it through, book a 15 minute call at [cal.com/vanshpatelai/15min](https://cal.com/vanshpatelai/15min). Email first is fine too, and often faster if you can describe it in writing.

## 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](/llms.txt), the case study API is documented at [/docs](/docs), and the schema is published at [/openapi.json](/openapi.json).

[Xocket](/)

[About](/about)

[Docs](/docs)

[Contact](/contact)

[llms.txt](/llms.txt)

## Email

For new projects, scoping questions and anything commercial, write to [remotevansh@gmail.com](mailto:remotevansh@gmail.com). For questions about work already under way, use [remotevansh@gmail.com](mailto:remotevansh@gmail.com).

## Book a call

If you would rather talk it through, book a 15 minute call at [cal.com/vanshpatelai/15min](https://cal.com/vanshpatelai/15min). Email first is fine too, and often faster if you can describe it in writing.

## 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](/llms.txt), the case study API is documented at [/docs](/docs), and the schema is published at [/openapi.json](/openapi.json).
---

Source: https://xocket.sh/contact
Site index: https://xocket.sh/llms.txt · Sitemap: https://xocket.sh/sitemap.xml · API: https://xocket.sh/openapi.json
Contact: remotevansh@gmail.com