Write for us

Write for VoiceSnap Pro

We publish a small number of guest posts about dictation, accessibility and the way people actually get writing done. This page is the whole deal — what gets in, what does not, and what happens after you send the email.

What we publish

Anything a person who dictates for a living would stop and read.

  • Dictation and speech-to-text in practice: how you use it, what breaks, what you did about it.
  • Accessibility and assistive technology — voice input for RSI, carpal tunnel, tremor, low vision, or any keyboard you cannot rely on.
  • Ergonomics and recovery: reducing keyboard load without reducing output.
  • Writing and productivity workflows — email, documentation, notes, meeting follow-ups, anything where the words are the bottleneck.
  • Developer workflows where prose is the slow part: commit messages, PR reviews, issue write-ups, technical docs.
  • Working in a second language, and multilingual writing workflows.
  • Desktop software craft on macOS and Windows — shortcuts, focus, automation, the small things that compound.

What we turn down

Not judgement calls — these are automatic.

  • Spun, rewritten or scraped articles.
  • Drafts generated wholesale by an AI model and sent without a human writing and editing pass.
  • Anything already published elsewhere, including on your own blog or LinkedIn.
  • Casino, betting, adult, payday loans, crypto tokens, replica goods, and essay-writing services.
  • Link-building placements dressed as articles — 600 words of preamble wrapped around one anchor text.
  • Requests to buy a link, a review, or a position in a comparison table. We do not sell any of the three.
  • Unsourced statistics. If a number appears in a post, it needs a link to where it came from.
  • Posts about using VoiceSnap Pro written by people who have not used VoiceSnap Pro — which, until it ships, is everybody.

The editorial standard

Short version: write something only you could have written, and let us edit it.

Write from something you did
The posts we publish are specific — a workflow you changed, a setup you tried, a thing that failed and what you replaced it with. Generic advice is the one thing the internet already has plenty of.
Roughly 1,000 to 2,000 words
Long enough to say something real. Shorter is fine if it is finished; padding to hit a word count is not.
Name real tools, including our competitors
You are allowed to say a competing app does something better than ours. We would rather publish an honest post than a flattering one.
Source anything checkable
Numbers, studies and quotes get a link to the original. We cut claims we cannot verify, and we will ask you first.
One link to your own site, in context
It goes where it is genuinely useful to the reader. We decide the rel attribute case by case, and we do not run affiliate or tracking links inside guest posts.
We edit, you keep the byline
House style, headings, and the occasional cut. You see the edited version before it goes live, and your name and bio stay on it.
It stays up, or it comes down properly
We do not quietly swap your links out months later. If we ever unpublish a post, you get an email saying so and why.

How to pitch

One email. No form, no portal, no account to create.

  1. 1

    Send a pitch, not a finished draft

    One paragraph on the angle, a working title, and a line on why you are the person to write it. Unsolicited full drafts get read last, because they usually fit nothing.

  2. 2

    Include two things you have written

    Links are fine. A personal blog counts. We are reading for whether you write like a person, not for where you have been published.

  3. 3

    Say what you want out of it

    A link, a byline, readers, an audience for something you built — all fine, and none of it disqualifying. Just say so up front rather than three emails in.

  4. 4

    Expect a plain answer

    We reply to pitches we want to publish. If two weeks pass and you have not heard back, it is a no, and a follow-up will not change it — we would rather tell you that here than leave you waiting.

Send your pitch to

support@voicesnap.pro

VoiceSnap Pro is pre-launch and this is one person's inbox, so the queue is short and slow at the same time.

Affiliate and disclosure policy

Stated plainly, because a page about editorial standards that hides its own money is not worth much.

  • Affiliate links exist and are disclosed

    Some outbound links to other companies' products earn a commission if you buy through them. Every page on this site carries that disclosure in the footer, on every page, not only the ones with links in.

  • Commission never decides a recommendation

    Comparison pages are written from publicly available information about each tool, and where a competitor is the better choice for a particular job, the page says so.

  • We do not sell links, reviews or table positions

    No paid placements, no sponsored rankings, and no arrangement where a product appears in a comparison because someone paid for it to be there.

  • Guest authors disclose too

    If you have a commercial relationship with a product you mention — you work there, you own it, you are an affiliate — it goes in the post, in plain language, near the mention.

  • Our own bias is on the label

    This is the marketing site for a product we sell. Everything here is written by people who would like you to buy VoiceSnap Pro. Read it accordingly, and hold the guest posts to the same test.