What Editors Look For in a Product Submission

Editors read a great deal. Faced with forty submissions in an afternoon, a person does not read every word of every page. They sort, quickly, and then give proper attention to the few that earn it. Understanding how that sorting works is not about gaming it. It is about making sure that a good product does not lose its place because the page was hard to read.

This guide describes what a human selector looks for in a submission, in the order they tend to look for it, and what a founder can do to meet each point honestly.

The first minute

Most selection decisions begin in the first minute. In that minute an editor wants to know three things: what is this, who is it for and is it real?

If the answer to any is unclear, the editor must work harder, and a tired editor tends to move on. That is not unkindness. It is the same reaction a visitor has to a gallery card that is too long to read while standing up.

So the first test is simple: can a stranger say what your product does after reading the opening line and looking at the first screen? Try it on someone who has never heard of it. If they hesitate, rewrite.

Quality one: clarity

Clarity is the quality editors mention most often and founders achieve least often. It is the plain statement of what the product is.

• Lead with the thing. "A browser extension that turns long articles into audio" is clear. "Reimagining how people consume content" is not.
• Name the audience. "For people who commute by train" tells the reader whether to care.
• Use ordinary words. Jargon suggests either a narrow audience or a lack of precision.
• Show one concrete example. A single sentence about what a user does and what happens next is worth a paragraph of adjectives.

A selector who understands your product in thirty seconds is a selector who can speak up for it.

Quality two: care in making

Editors, like gallery visitors, read small signals of care. A product that has been made with attention tends to look it.

• The page loads quickly and works on a phone.
• Images are sharp and meaningful, not stock filler.
• The text is free of obvious mistakes.
• Buttons do what they say.
• The product handles a first use without confusing error messages.

None of this requires a large budget. It requires someone to have looked at the page as a stranger and fixed what was awkward. Attention is visible, and so is its absence.

Quality three: honesty

Editors are wary of overstatement, partly because they have been misled before and partly because they are accountable for what they choose. Honesty is therefore a practical advantage.

• State only what you can show. If you claim a number, be ready to say where it comes from.
• Be modest about newness. If your product resembles others, say what is different rather than claiming to be unique.
• Be open about stage. "An early version used by around thirty people" is better than a vague claim of traction.
• Name limitations. An honest note that something does not yet exist builds more trust than a promise.

A statement an editor can verify in a minute will do more for you than a grander one they cannot. The guide on verified data on this site covers how to prepare the evidence.

Quality four: usefulness

Editors tend to favour products that solve a specific problem for a specific group. Usefulness is not the same as popularity. A narrow tool that does one thing very well for a small community can be more notable than a broad product that does many things adequately.

Show the problem and the person. A description such as "Shift workers can see at a glance which colleagues are free to swap" gives the editor something to picture. It lets them think of an actual reader who might benefit, which is how a selector justifies a choice.

Quality five: a reason to exist now

Curators ask why this product, and why now. Newness need not mean an invention. It can be a clearer way, a kinder way, a faster way or a way for a group that has been overlooked. The editor is looking for something that adds to what is already available.

Say what is different in a sentence, plainly. If you cannot, consider whether the difference is real, or whether you have not yet found the words for it. Either is worth knowing before you submit.

Preparing the submission

Treat the submission like a small, well-hung exhibit.

1. Write the one-sentence description first. Everything else depends on it.
2. Choose the right category. A mismatch wastes the editor's time and yours. The category pages show how products are grouped.
3. Check every claim and link. Click each link from a fresh browser and read the page aloud once.
4. Prepare a single strong image. One clear picture of the product in use is better than six cluttered ones.
5. Give an easy way to try it. If sign-up is required, say why, and make it quick. If a demonstration is possible, offer it.
6. Provide a contact that works. An editor with a question must be able to reach someone.
7. Read it as a stranger, after a day away.

What does not help

Some habits work against a submission.

• Superlatives. "The best", "revolutionary" and "game-changing" tell the editor nothing and invite suspicion.
• Pressure. Repeated messages, claims that others have already agreed to feature you, or deadlines you invented are counterproductive.
• Padding. A long description does not make a product seem substantial. It makes the real point harder to find.
• Hidden basics. If the price, the audience or the main function is buried, the editor assumes it is awkward.
• Fake proof. Invented testimonials or inflated numbers will be caught, and they end the conversation.

Bias, and how to think about it

Selection is never perfectly neutral. Selection bias arises when the way items are chosen makes the chosen set unrepresentative. An editor who sees only what is submitted, or who favours a familiar style, will unintentionally narrow the picture.

For a founder, this means that a no is not a measurement of your product's worth. For an editor, it means that stating criteria and rotating attention across categories helps. Peer review in academic publishing is built on the same acknowledgement: that judges are fallible, so that their reasons should be explicit and open to challenge.

A worked example

Two teams submit similar tools for sharing playlists. The first writes: "A revolutionary new way to experience music with friends, powered by the latest technology." The page opens with a large animation, and the product cannot be tried without a long sign-up.

The second writes: "A shared playlist that lets four people add songs and removes any song three of them skip. For friends on a long drive." The page shows a single screenshot, a one-click demo and a plain note: "This is version one. It works with the major streaming services but not yet with all of them."

The editor spends ninety seconds on the first and gives up when the sign-up asks for a phone number. She spends five minutes on the second, tries the demo, laughs at the skip rule and checks that the stated services are supported. The second is clearer, more honest and more useful, and the difference did not require a larger team, only a more careful description.

Questions founders ask

Should I submit more than once? Resubmit when something real has changed, such as a new version or a new feature, not as a reminder.

Does the order of submission matter? Not in a well-run selection. Readers should look at all of them.

What if my product is hard to explain? Then the description is the work. Try giving one example of a user, one action and one result.

Is it acceptable to ask for feedback? Politely, once, and accept that an editor may not have time to give it.

A final read-through

Before you send, do one last pass with fresh eyes. Read the opening sentence aloud and ask whether a stranger would know what the product is. Count the adjectives in your description and remove half. Open the link on your phone with the wifi turned off and see what happens. Check that the contact address belongs to someone who will read it within a day. Finally, ask yourself what you would want to know if you were the person deciding, and make sure the page answers it. This ten-minute pass catches most of the small problems that cause a good product to be passed over.

What to do when the editor asks a question

Sometimes an editor writes back with a question before deciding. Treat it as good news: it means the submission earned attention. Answer promptly and directly, in the fewest words that are complete. If you do not know, say so and say when you will find out. Do not attach new claims you cannot support, and do not use the reply as an occasion to repeat the pitch. If the question reveals a gap in your page, such as an unclear price or a missing explanation, fix the page as well as answering, because the next reader will have the same question.

Summary

Editors look first for clarity, then for care, honesty, usefulness and a reason for the product to exist now. They decide quickly and fairly, and they respond to what they can verify. Write the one-sentence description first, check every claim, make the product easy to try and avoid pressure and padding. A no is not a measurement of worth, and a plain, truthful submission is the best case you can make.