Strategy

Why Publishers Stop Responding and What to Do About It

Publisher silence is the most common outcome after a submission, and it almost never means what you think. Here is what the quiet usually signals and how to respond without damaging the relationship.

Vectra Play 6 min read
An email inbox showing several sent messages with no replies and a clock

Publisher silence after a submission usually means one of four things: your game did not clear the first filter, the reviewer has not reached it yet, the team is debating internally, or your contact left and nobody picked up the thread. Only the first is a judgement on the game. The other three are operational, and each has a different follow-up.

Why silence is the default

Publishers receive hundreds of submissions. Most do not have the capacity to respond to every one, and a form rejection costs them time without benefiting either side.

This means silence is the most common outcome even for games that cleared the first look. A team might flag your game for further review, get pulled into a launch for another title, and never return to the queue.

That is not personal and not a reflection of quality. It is a capacity problem dressed as a communication one.

Understanding this changes how you respond. The right follow-up is not persuasion. It is a reminder that costs the reader almost nothing to act on.

The four usual causes

The game did not clear the first filter. This happens within the first few days. If the concept, genre, or metrics do not fit what the publisher is looking for, it is set aside without a response. The research in How Publisher Submission Bars Differ helps you avoid this by submitting to publishers whose bar matches your game.

The reviewer has not reached it yet. Queues are real. A submission sent during a busy period can sit for weeks before anyone looks at it. This is the most common cause of silence in the first two weeks.

Internal debate. Your game interested someone, and they brought it to a team review. That review depends on schedules, competing priorities, and internal consensus. This can take weeks and produces no outward signal while it is happening.

Contact turnover. The person you emailed left the role, and the thread was not handed over. This is more common than most developers expect, especially at publishers with high team turnover.

Silence for two weeks means nothing definitive. Silence for two months usually does.

How to follow up without being pushy

The follow-up email is a skill, and most developers either do it too often or not at all.

Timing. Wait at least a week after your initial submission. Two weeks is safer. Following up the next day signals anxiety, and publishers notice.

Content. Keep it short. Reference your original submission, mention one concrete update if you have one, and ask a direct question.

A good follow-up template in four lines:

  1. Reference the original email with the date and game name.
  2. One sentence of new information: a metric improvement, a build update, or a milestone.
  3. A direct question: "Is this still under review?"
  4. A line making it easy to decline: "If this is not a fit, no problem at all."

That fourth line matters. It gives the publisher permission to say no quickly, which many prefer to silence but do not feel comfortable offering unprompted.

Frequency. One follow-up after two weeks. A second after another two weeks if you have new information. After that, stop. More than two follow-ups to the same person without a response damages the relationship.

What to include in a follow-up

New information makes a follow-up worth reading. Without it, the email is just a nudge, and nudges have diminishing returns.

Good additions to a follow-up:

Bad additions:

The goal is to give the reviewer a reason to reopen the thread and a quick path to a decision in either direction.

When the contact left

If your contact left the publisher, your thread likely died with their inbox. This is fixable but requires a specific approach.

Find the current person in that role. LinkedIn is usually the fastest route. Then send a fresh email that references the original submission briefly and treats the new contact as a new relationship.

Do not express frustration about the previous contact or the gap. The new person is not responsible for their predecessor's inbox.

A clean restart lands better than a forwarded thread with history the new person did not participate in.

When to move on

Three signals that the relationship has run its course for this game.

Moving on does not mean cutting ties. A brief, professional close keeps the door open for your next game.

"Thanks for your time on this one. If it is not the right fit, no hard feelings. I will reach out when the next project is ready."

That email costs nothing and preserves the relationship for later.

What we would do

Send the first follow-up at the two-week mark with one piece of new information. If no response, send a second at four weeks with a different update. After that, move on to other publishers for this prototype.

Keep the contact on a list for future submissions. A publisher who was silent on one game may respond quickly to the next, especially if you reference the earlier submission to show continuity.

Track every submission and every follow-up in your pipeline tracker. The pattern across submissions tells you more than any single silence does.

The short version

Send your two-week follow-up this week if you have one pending. If you want help structuring your publisher pipeline, reach out.

#Publishing#Strategy#Communication#Business
Your turn

Got a game idea? We build it.

You bring the concept. We design, build, test and launch it, and you own 100% of the finished game.

Share Your Game Idea  →