---
title: Reader-Centered Outreach Asks
created: 2026-07-01
updated: 2026-07-13
type: concept
status: compiled
namespace: agent-workflows
source: Knowledge/concepts/reader-centered-outreach-asks.md
confidence: high
---

# Reader-Centered Outreach Asks

A **reader-centered outreach ask** is a cold DM, cold email, intro request, or help request drafted from the recipient's mind rather than the sender's need.

Core rule:

> Put yourself in the reader's mind. Make the recipient want to help **you**, understand the context quickly, accept at low cost, and decline without pressure.

Use this when drafting cold outreach for Jamie or when an agent is asked to turn a vague “can you help me?” into a message someone can comfortably answer.

## Drafting contract

Before drafting, identify:

1. **Recipient mind** — what this person already cares about or has context for.
2. **Proof of work** — the strongest real evidence that the sender is serious.
3. **Tiny context** — the unsummarizably short reason this message exists.
4. **Specific bounded ask** — one small action, answer, intro, resource, or review.
5. **Easy no** — a graceful exit that keeps the relationship clean.

If a field is missing, use a placeholder or ask for it. Do not invent facts.

## Credibility hierarchy

1. **Proof of work** — strongest: shipped project, model, case study, blog post, prototype, analysis, repo, demo, portfolio piece, or other real artifact.
2. **Personal connection** — useful only when real and safe; it borrows the connector's credibility.
3. **Institutional credibility** — weakest; schools, employers, and titles can situate someone but should not be the whole case.

For Jamie, use true project artifacts and portfolio proof. Do not fake metrics, inflate titles, or manufacture familiarity.

## Context rule

Keep context so short it is hard to summarize further. Connect the message to what the recipient already knows.

Avoid life story, vague passion, internal drama, or generic admiration. Prefer a specific bridge between the sender's work and the recipient's world.

## Ask rule

Make the request easy to accept:

- small magnitude;
- specific;
- low friction;
- bounded to one instance.

“Could you point me to one resource?” usually beats “Can I pick your brain?” If asking for an intro, include a forwardable blurb.

## No-pressure rule

Make it easy to say no. A pressured yes is worse than a clean no because it poisons the relationship and produces half-hearted help.

Good exits: “Totally fine if not,” “No worries if you are not the right person,” or “A pointer to a better resource/person would also help.”

## Message formula

```text
Hi [Name] — I saw [specific work/context].
I’m [who the sender is + real proof of work].
I’m trying to [tiny context connected to their world].
Would you be open to [specific bounded ask]?
[Low-friction artifact/question/blurb]. Totally fine if not.
```

## Agent behavior

- Start from the recipient's perspective, not the sender's biography.
- Use the strongest true proof of work available.
- Keep context shorter than feels comfortable.
- Replace “pick your brain” with a concrete written question or bounded next step.
- Include an easy no.
- Never lie.
- If the request is too large, shrink it before polishing the prose.

## Source

Canonical source: `Knowledge/concepts/reader-centered-outreach-asks.md`.

Primary article source: `Knowledge/raw/articles/how-to-ask-for-help-from-people-who-dont-know-you.md`.

Related pages: [[concepts/agent-skill-routing|Agent Skill Routing]], [[concepts/agent-tooling-plan|Agent Tooling Plan]], [[../../ai-native-product-surfaces/wiki/concepts/verb-first-product-positioning|Verb-First Product Positioning]], [[../../ai-native-product-surfaces/wiki/concepts/find-the-lock-problem-first|Find the Lock Problem First]], [[../../ai-native-product-surfaces/wiki/syntheses/side-doors-make-useful-work-legible|Side Doors: Make Useful Work Legible]].