HHow to Write an Ask That Gets Answered

An Ask is the smallest unit of value transfer in a working community. If your Asks are vague, your network compounds slowly. If your Asks are sharp, they compound at a rate that surprises you twelve months later. Most people in our community write Asks that are technically requests but functionally noise. This is the operating manual to fix that.

¶The four-part anatomy

A well-formed Ask has exactly four components. The specific outcome you want, the context that helps the responder calibrate, the deadline by which a response is useful, and the format you want it delivered in. Drop any one of them and your conversion rate falls by roughly half. Drop two and you are essentially writing a journal entry. The structure does not need to be visible, it can be three sentences in WhatsApp, but all four must be present.

Compare two Asks. The first: I am looking to chat with anyone who has done enterprise sales in BFSI, would love intros. The second: I am closing a paid pilot with an Indian private bank next month and I am stuck on procurement timelines. Looking for one twenty-minute call with someone who has sold AI tooling into ICICI, Axis, or HDFC in the last eighteen months. Need to do this call before Tuesday, May 18. Happy to do WhatsApp voice or Google Meet. The second Ask gets answered. The first gets forgotten in three hours because no one knows whether they are a fit.

¶Specificity is the unlock

Specificity does two things at once. It tells the responder whether they are the right person, and it tells them what success looks like. Both are gifts. When you say I want to chat with founders, you have created a search problem for the reader. When you say I want to chat with one Series A founder who has raised from Accel or Peak XV in the last twelve months and is operating from Bengaluru, you have collapsed the search to maybe four or five names in your reader's head. They either know one of them or they do not, and they can respond in seconds.

In the Indian context, specificity also includes the geography and the language. Saying I want to do a customer research call with an SMB owner is too broad. Saying I want to do a forty-five minute call in Hindi or Hinglish with a Tier-2 city retailer who runs a kirana doing more than three lakh rupees a month in revenue is the kind of frame your reader can act on. The specificity is not pedantic. It is mercy.

¶Context calibrates trust

The context line answers the unspoken question: why should I help, and what stage are you at? You do not need a paragraph. One sentence is enough. I have done this twice before for D2C brands and I am extending the playbook to financial services. Or: I have been heads-down on this for six months and I have hit the wall on distribution. Context lets the responder decide whether a twenty-minute call solves your problem or whether you need a six-month engagement they cannot offer. Without context, the responder assumes the worst and quietly opts out.

¶Deadlines and format

Open-ended Asks are open-ended on both sides. They feel polite, but they convert badly because they sit in the responder's bottom inbox forever. A deadline does three things. It tells the responder when their help becomes useless, it gives them an out (I cannot help by Tuesday, sorry), and it gives them a forcing function. Make the deadline real. Not a fake urgency. If you genuinely need an intro before your investor meeting on the twenty-second, say so. If you have three weeks, say three weeks.

Format is the fourth piece and the one most people skip. Tell the responder how to deliver. Do you want them to forward your message? Do you want them to copy a one-line intro into a new WhatsApp thread? Do you want a voice note? A LinkedIn intro? When you specify the format, you cut the responder's decision cost from minutes to seconds. The lowest-friction format in India in 2026 is still the double-opt WhatsApp intro: you write the forwardable blurb, they forward it to the contact, the contact replies if interested. If you want this format, write the blurb and attach it. Do not make them write your pitch for you.

¶A working template

Here is the template I use, in WhatsApp form. Line one: the outcome (One twenty-minute call with a CFO who has implemented an AI finance copilot in the last year). Line two: the context (We are about to deploy at a 400-person SaaS company and I want to pressure-test our rollout plan). Line three: the deadline (Need to do this call before Friday, May 22). Line four: the format (I have written a forwardable blurb below, just paste it if you have a name). Then the blurb itself, three sentences max.

Try this once this week. Pick the one open Ask that has been sitting in your head for a month. Rewrite it in this format. Send it to five people in your most active chat. Watch what comes back within twenty-four hours. The compounding starts on the second Ask.