Home / Contact
CTA/ — Contact
Tell us what's going on.
One email address, read by the person who would do the work. No contact form that routes into a CRM, no discovery call that turns out to be a sales call.
Replies within one business day, Monday to Friday. If we're not the right fit, you'll be told that plainly — and pointed elsewhere where we can.
USE/ — Make the reply useful
What to include.
None of this is required — a two-line email is completely fine. But the more of it you include, the more useful the first reply can be, and the fewer rounds it takes to get to an actual answer.
If you're a business in Bengaluru
- How many people, and how many locations
- Your timezone — all work is remote, so overlap matters more than location
- What prompted the call — something broke, you're moving, or you inherited a mess
- What you're running — Google or Microsoft, any server, any specialist software
- How urgent — a plan for next quarter and a dead server are different conversations
If you're a company hiring engineering
- What the system does, and roughly how big it is
- The constraint — capacity, a specific skill, a deadline, a system nobody understands any more
- Your stack, so we can say honestly whether it's ours
- Timezone and working hours you'd want overlap with
- Retainer or fixed project, if you already know
- Budget range — stated up front, it lets us design something that fits it
DTL/ — Details
Practical information.
ASK/ — No obligation
Questions are free.
If you have a question that one of the notes nearly answered, ask it. We answer questions from people who aren't customers and have no intention of becoming customers — it costs us very little and it's how most of that writing came about in the first place.