Your move
Write the five-sentence ask
Test one truthful, specific note before building a larger campaign.
Write a short, specific note: why them, what you noticed, the problem you solve, the bounded offer, and one easy next question. Five sentences is a PickBits drafting constraint, not a conversion formula.
The situation
Start where the choice gets difficult.
You have a buyer list and a small offer, but the empty message box makes you reach for campaign language. You write a warm opening that could describe anyone. You add a paragraph about your background so the recipient will trust you. You explain every part of the offer because leaving details out feels risky. Then you ask for a thirty-minute call. The note is accurate, yet it sounds like a performance rather than one person noticing something useful for another. You are tempted to solve that by drafting one perfect message and sending it to all thirty names. That would finish outreach for the day. It would also spend every relationship on an ask nobody has answered yet. Instead, imagine sending the draft to three people. One replies, “What made you think this is a problem for us?” That question reveals the weak second sentence. With three sends, you can repair it for the next group. With thirty sends, the same vague claim has already reached everyone. The wording matters, but the size of the first send determines how safely you can learn what the wording actually does.
What changes the decision
Read the evidence before you add more work.
A useful first note does not need to carry the entire sale. It needs to make five things easy to understand: why you chose this person, what you genuinely noticed, which problem that observation may point to, what small result you can offer, and what simple question they can answer. That is why five sentences works as a drafting constraint. It forces each sentence to do one job. It is a PickBits starter default, not a conversion rule. If the note needs six clear sentences, use six.
The first send is also part of the draft. Three recipients can show whether the opening feels real, whether the observation is supported, and whether the last question is easy to answer. They cannot prove a general response rate. They can expose a sentence that confuses people before the same confusion reaches the rest of your list. Read their replies without arguing with them. If a person asks how you know, your evidence sentence may be too broad. If they ask what you mean, the offer may be vague. If they politely decline, respect the no; do not treat it as permission for a sequence.
The number at risk is not only a send count. It is the set of relationships that can be affected by an untested claim, awkward tone, or difficult ask. A batch of three keeps that effect contained while you learn. A batch of thirty spreads the same mistake across the whole list before you can respond. This is called blast radius.
Do this now
Three moves, in order.
- Open with the real reason this person is on your list.
- Name the observed situation and your proof-sized offer without pretending you know more than you do.
- End with one question they can answer without booking a call.
Working session
Build it from the evidence in front of you.
- Assign one job to each sentence
Sentence one gives the truthful reason for writing. Sentence two states the observation. Sentence three connects it to the problem without pretending certainty. Sentence four offers the bounded result. Sentence five asks one low-pressure question.
- Remove campaign residue
Delete fake familiarity, broad compliments, invented urgency, and background that serves only to impress. Replace any claim about the recipient with the evidence you recorded. If you cannot support it, remove it.
- Choose the first three recipients
Pick three evidence-rich rows with an appropriate contact route. Three is a PickBits starter default, not a required batch. Use a smaller group if the relationships are especially important or the message carries more risk.
- Pause and read before widening
Record replies and questions in the recipient’s exact words. Change one unclear sentence if the evidence supports a change. Then send the next small group. Do not rewrite from silence alone or turn one reply into a rule.
Inspect the finished shape
A five-sentence ask ready for a small send
Subject: A quick question about [observed situation]
1. I’m writing because [truthful connection or specific reason this person is on your list].
2. I noticed [evidence-backed observation] in [source you are allowed to use].
3. That can sometimes make [plain-language problem] harder, although I may be missing context.
4. I offer [proof-sized result] for [price and delivery window you chose], with [main boundary] left outside this first piece.
5. Is [the observed problem] something you are working on, or have I read the situation wrong?
FIRST SEND
Recipients: [evidence-rich row], [evidence-rich row], [evidence-rich row]
Pause after: 3 sends, or your smaller chosen batch
Read for: unsupported claim / unclear offer / hard-to-answer questionBuild the artifact
Outreach message
Copy these fields into a note, document, or sheet you already use.
Give AI the bounded job
Prompt from your artifact—not from vibes.
Draft a five-sentence outreach note from these fields. Keep every claim inside the evidence I supplied. No fake familiarity, urgency, compliments, or guaranteed outcomes. End with one answerable question.
Before you use it
The work leaves your hands only when:
- Delete any sentence that could be sent unchanged to everyone.
- Verify every personal or business claim against its source.
- The recipient can say no without entering a sales sequence.
Failure patterns
Watch for the move that looks useful but is not.
The compliment costume
- The tell
- The opening praises the recipient in a way that could be copied to anyone, then turns immediately into your offer.
- The fix
- Use the real reason they are on your list. If there is no truthful reason beyond fit, say that plainly and keep it brief.
The hidden calendar demand
- The tell
- A short note ends with a call request that requires the person to inspect a calendar before they can answer anything.
- The fix
- Ask a question they can answer in the reply. Discuss a call only after they show interest or ask for one.
The thirty-send debut
- The tell
- You use the whole list for the first live test because sending once feels efficient and waiting feels uncomfortable.
- The fix
- Send to a small first group, read the actual response, correct one supported weakness, and only then widen the batch.
Use the boundary
When this rule does not fit.
Do not use a five-sentence note when the recipient has asked for a detailed proposal, when a warm introducer has already set a different context, or when the channel makes another format more natural. Do not split an urgent operational message into outreach batches; this method is for learning from a new ask, not delaying information someone needs. And do not treat a small batch as harmless. A message can still damage trust for one person. Check every claim, use an appropriate channel, and make refusal easy before you send anything.