How to Write a 150-Word Pitch That Gets a Reply

Key Takeaways

• A 150-word pitch carries five things: one claim, the timely question, your original evidence, the reader who benefits, and competence tied to this exact argument.
• Rough word budgets: 25 for the claim, 35 for evidence, 30 for fit and timing, 20 for credentials, 40 for greeting, links and sign-off.
• Cycle time shapes the target. A newsbrief wants a hook that expires in weeks; a journal review will not land inside that window.
• When an outlet publishes no submission guidance, treat word count, payment and response time as unknown. Guessing produces wasted weeks.
• Editors reply when they can see the argument, the evidence and the deadline on one screen.

1. Introduction

Most pitch emails to think tanks lose the reader in the first line. They open with the author's job title, or with a broad topic, and leave the editor to work out whether there is a claim, whether the claim is new, and whether it has to run this month. Editors read pitches in a queue, often on a phone, and they decide quickly. A 150-word format works because it forces the writer to settle the argument before writing a single line of prose.

The pain point is not that external authors lack expertise. It is that expertise arrives as a biography and a topic instead of a claim and a deadline. This article sets out what a think tank pitch email has to contain to survive triage, walks through a complete example with a breakdown by word budget, compares how different policy outlets handle outside contributions, and lists the checks to run before you send anything.

2. What a 150-word think tank pitch email has to carry

Editors triage on three questions at once: is there a claim, why now, and why this author. Five components answer those questions inside a tight word count.

Write the claim first. If it takes three sentences, you are holding two claims, or none. The claim should be falsifiable: someone should be able to disagree with it in one line.

The evidence block does the heaviest lifting, because it separates a submission from an opinion. Competence can come from research, professional practice, language access or a documented dataset. A policy analyst who spent four years inside a procurement agency has competence for a piece on tender rules; a researcher holding three years of unpublished survey data has competence for a piece on how those numbers contradict the published totals. A long biography never substitutes for that link.

Naming the reader matters more than most authors assume. Editors choose between two good pitches by asking which one their audience will argue with. "The parliamentary committee reviewing the bill resumes evidence sessions in March" tells an editor the shelf life of the piece. "Policymakers would find this timely" tells them nothing.

3. A worked example with a breakdown

The figures in this template are placeholders. Replace them with your own verified counts, and keep the names of the registers, datasets or interview sets you actually hold.

Subject: Why the connection queue, not the 2030 target, decides the deadline

Dear Dr [Editor],

Your piece last month on the 2030 target left open where the delay starts. My claim: the binding constraint is the grid connection queue, and the permitting bill now before committee does not touch it.

The live question for your energy desk is whether ministers can still fix the schedule. I hold connection waiting times for 1,200 projects drawn from three national registers, 2019 to 2025, and the queue kept growing through two previous reforms.

Your readers include the committee reviewing the bill. Its evidence sessions resume in March, which is when the argument matters most.

I research grid regulation at [institution] and advised [body] on the 2022 connection rules. A 900-word comment piece is ready, with the dataset and a methods note available on request.

[Name], [affiliation]

The pitch runs just under 150 words. Each block maps to one job: the first line names a gap in the outlet's own coverage and follows it with the claim; the second paragraph carries the timely question and the evidence; the third names the reader and the deadline; the fourth links the author's background to this specific argument and offers the finished piece.

Three edits turn most drafts into this shape. Cut the opening sentence about who you are, and move that material into the final paragraph. Replace any adjective describing importance with a date or a body that will act. Delete the paragraph explaining that you have followed the outlet for years. That paragraph consumes roughly 30 words and answers no question the editor is asking.

Offer the full draft in one line rather than attaching it. An attachment competes with the pitch for attention, and the editor still has to read the argument before opening anything.

4. Matching the pitch to the outlet

Cycle time decides which outlets are worth a pitch. A hook that expires in three weeks cannot survive a journal review, and a research paper is not an opinion piece simply because it has been cut to 900 words.

Publication-specific guidance beats general advice every time. Read the outlet's current contributor page before adapting your draft, because the word count, the exclusivity terms and the response window may all differ from what a template assumes.

5. Checks to run before you send

Six checks separate a pitch that gets a reply from one that disappears.

1. Read the outlet's own instructions. Where they differ from any general template, follow the outlet.
2. Confirm the route. Do not infer an email address from a naming pattern. If no public route is confirmed, record the gap and spend the time on channels you can verify.
3. Test the evidence line. Can you name the dataset, register, interview set or language source in ten words? If not, the evidence is not yet a pitchable asset.
4. Check the cycle against the hook. A review process and a two-week news window do not fit together. Shortening a research paper does not preserve its evidentiary contribution unless you decide in advance which findings survive the cut.
5. Write down what you do not know. Payment, response time and standard length are unknown quantities when an outlet publishes nothing. Treating a guess as settled leads to pitches sent to the wrong desk.
6. Read the claim aloud. If a colleague cannot state your position back to you after one hearing, the sentence is doing two jobs.

6. FAQ

Q1. Is 150 words a hard rule for think tank pitch emails?

No. It is a working target that keeps the claim, evidence and timing inside one screen. Some outlets publish their own length guidance, and that guidance takes priority. The number matters less than the constraint it creates: five components, no filler.

Q2. What should I do when an outlet publishes no submission guidance?

Treat the missing details as unknown. Do not assume a word count, a fee or a reply window, and do not send a guess to an address you assembled from a naming convention. Record the uncertainty, and prioritise outlets where a published route exists.

Q3. How do I show competence without a long biography?

Link one credential to this argument. Research, professional practice, language access or a documented dataset all work. The test is whether the credential explains why you can substantiate this specific claim, not whether it lists where you have worked.

Q4. Can I turn my research paper into a comment piece?

You can, but the two formats carry different evidentiary weight. A journal article reports findings in full; a comment piece selects one claim and defends it in 900 words. Decide which parts of the evidence survive that cut before you pitch, and say so if the editor asks what the longer version contains.

7. Conclusion

The 150-word limit is a triage tool, and it works in both directions. It lets an editor decide in under a minute, and it forces the author to find out whether the argument holds before writing the piece. Start with the claim, attach the evidence you can name, then state who acts on it and when. The remaining components, competence and the offer of a finished draft, take two sentences.

Where an outlet publishes its own guidance, that guidance governs. Where it publishes nothing, the honest position is uncertainty, and the effective position is a pitch sent through a route you can verify to an editor whose desk covers your question.