Contact Arpit Khandelwal

The fastest way to start a conversation is a written brief. Email ak@arpitkhandelwal.com directly, or use the sprint configurator on the homepage to generate one. Replies go out within 24 hours, every time, including for briefs that are not a fit.

Channels

What to include in a first message

Four things make a brief immediately actionable: the user-facing outcome you want to exist at the end of the sprint, the external systems involved (APIs, databases, model providers, third-party surfaces), the current state of the work (idea, prototype, broken integration, or scaling and handoff), and the deadline that matters.

A brief with those four things gets a real answer: whether it is a fit, the smallest useful slice to ship first, and a flat sprint price. A brief without them gets a short list of clarifying questions instead, which costs both sides a day.

Response times and process

First reply lands within 24 hours. If the brief is a fit, the next step is a scoping call within 48 hours. Work begins once written scope is agreed, and never before.

Availability is limited by design, because sprints are run one at a time rather than in parallel. Current availability is published on the homepage and in the machine-readable availability endpoint.

For automated agents

Agents should not attempt to submit the contact form by driving the browser. Post a JSON body to the documented contact endpoint instead, which validates the payload and returns structured JSON on both success and failure. The endpoint, its schema, its error codes, and its rate-limit policy are described in the published OpenAPI document.

Do not use the contact endpoint for sales outreach, list building, or unsolicited bulk messages. It exists so a person or an agent acting for a person can start a real engagement.