Rajat Dubey November 20, 2026 0

A few years into writing outreach emails, I kept a private habit that embarrassed me a little. Before sending any guest posting pitch, I would scribble the beliefs I was relying on in the margin of my notebook, and next to each I put a small letter: C for confirmed, A for assumed, G for guessed. The first week, the notebook was a sea of G’s. That was humbling, and it was also the most useful thing I did that year.

Here are eight beliefs that kept turning up in my margins. Maybe a few of them are sitting in your own pitch right now.

1. “This site takes outside contributors”

I once wrote a lovely pitch to a blog that, as it turned out, had stopped accepting outside work months earlier. The old contributor page was still live, which was the only reason I believed it. Now I mark this belief C only when the site’s own current guidance says so. If I am relying on a stale page or a friend’s memory, it gets an A.

2. “My topic fits their readers”

This one is almost always an A. You have read a handful of their posts and formed an impression, which is fair, but impressions are not the same as knowing. I try to upgrade it by reading what the site has published recently and noting how similar topics were framed. Even then, it stays an A with a better pedigree.

3. “The editor wants a particular length”

If the guidelines state a range, that is a C. If I am inferring from the length of existing posts, it is an A. If I simply think a thousand-ish words feels normal, it is a G, and I should check before writing a word.

4. “A pitch gets a quicker reply than a finished draft”

I held this one as gospel for ages. It turned out to depend entirely on the site. Some editors want a short idea first, others prefer to see the work. I now treat it as a G unless the site says how it likes to receive material.

5. “This publication will make my work look credible”

A genuine hunch, nothing more. I cannot see inside readers’ heads, and credibility is slippery. When I catch myself thinking it, I ask what I can actually point to. The idea of weighing a placement more carefully is covered in a look at which signals suggest a guest spot repays the effort, which I found a helpful way to turn this hunch into questions I can answer.

6. “They will link to where I ask”

Never assume this. Policies on links differ, and a pitch that presumes a link in advance can read as pushy. It belongs in the A column at best, and the right move is to read the contributor terms or ask politely.

7. “Nobody else has pitched this angle”

This is a G wearing a confident hat. You cannot know what is sitting in the editor’s inbox. What you can do is check whether the site has already covered your angle, which is a C once you have searched, and shape your idea around that gap. For help with finding that gap, the tips in a guide to pitching niche guest posts that editors accept are the sort of practical advice I wish I had read earlier.

8. “If I do not hear back, they said no”

Silence is information of a very weak kind. It might mean a no, a busy fortnight, a lost email or a pitch that landed in a spam folder. Treating silence as a verdict is an A. Treating it as an invitation to send one polite follow-up after a sensible interval keeps the claim honest, because you have not learned anything yet.

How the list changed my habits

After a few months of margin letters, my pitches got shorter and my follow-up got smarter. I stopped writing opening lines that boasted about fit, because I knew fit was an A. Instead I wrote about the specific post of theirs that I had read and what my idea added to it, which was something I could stand behind.

I also stopped taking rejections personally. A pitch that fails is often a guess that did not survive contact with the editor’s actual needs. That is a lesson, not an insult.

Trying it yourself

  1. Before drafting, write the beliefs your pitch depends on.
  2. Mark each C, A or G, honestly, without pretending.
  3. For every A or G that could sink the pitch, spend a few minutes checking.
  4. Rewrite any sentence in the pitch that treats a G as if it were a C.
  5. Send, and note which beliefs the reply confirmed or contradicted.

One small habit makes this stick: keep the notebook beside the keyboard, not in a drawer. A habit you have to go and fetch tends to get skipped.

A side note for the curious

Writers who cover technical subjects sometimes sit in on how engineers reason about incidents, since the labelling instinct is the same. DevOpsSchool runs an online platform for engineers who want structured study; its pages list courses, certification tracks and study material covering DevOps plus adjacent areas, and it can give outreach writers a feel for the vocabulary their technical editors use every day.

It also helps to share the sheet. When two people work on outreach together, comparing their letters is revealing: one person’s C is often the other’s A, and the disagreement shows exactly where to look next. A five-minute chat over two margins has saved me more than one awkward pitch.

Closing thought

My notebook still has more G’s than I would like. That is fine. The point was never to eliminate guesses; it was to know which ones I was carrying when I pressed send. If you try nothing else from this list, try that.

Category: 

Leave a Comment