Red Sovereign Research is the research and industry-outreach desk of Red Sovereign.
We write to editors on behalf of named clients, and we say so in the first note.
What we do
This desk exists so an editor who receives a short note from us can see who sent it, whom we represent, and what we will and will not ask.
- Identify public resources that are relevant to a beat — practitioner pages, tools, reports, and primary documents — and share them when they are a genuine fit for something the outlet already covers.
- Verify proposed factual corrections against primary sources before we email.
- Connect editors with a client subject-matter expert, or with client data, only when that person or that material is genuinely available and we have checked it.
- Keep the outreach itself transparent: named sender, named client, one purpose, easy to refuse.
We represent clients. We are not a newsroom, and we are not an independent research institute. This desk does not sell to the people we write to.
What we do not do
- Pay for links, or pay for a mention, citation, or placement.
- Offer sponsored material dressed as editorial coverage.
- Run a guest-post network, or send the same pitch in bulk.
- Invent data, or treat placeholder, modelled, or illustrative figures as findings.
- Pitch anonymously, or write as if we are on the client’s staff.
- Send more than one reminder, or continue after a “not interested.”
Editorial standards
A note from this domain should be checkable. Before we send one, we apply the following.
Corrections. We verify a factual correction before we email it. If we cannot show the error and the source, we do not write.
Sources. We link to the original or primary source. We do not ask an editor to take a secondary write-up as the evidence.
Disclosure. The first note names the client we represent. We do not hide the agency relationship, and we do not impersonate client staff.
Cadence. One reminder, at six to eight days. If you are not interested, say so — or ignore the note. Either way, we stop.
Provenance. We do not send a claim we have not traced to its upstream source. A published JSON file, a schema, or a well-formed public API is not proof that the underlying data is real. Those artifacts show how a dataset is presented, not how it was collected. We verify the collection process or the source system. If we cannot, we do not cite the figure.
Team
-
Rachel Morgan
Research Coordinator
-
Emily Carter
Editorial Outreach Coordinator
-
Jessica Bennett
Industry Research Associate
Contact
Questions about a note from this domain, or a request that we not write again, go to Rachel Morgan, Research Coordinator: