Submitting your product to ShipFeed starts with a product profile. Prepare a clear explanation of the software, its real website, a suitable category, and a recognisable logo. After review and approval, the profile becomes a public home for the product’s progress.
This checklist covers that first submission. Product updates are a separate step: they explain a launch, feature release, improvement, or milestone after the product has been approved.
Check that your product fits ShipFeed
The submission form describes ShipFeed’s focus as software, SaaS, AI tools, developer tools, apps, and other digital products with real product progress to share. It excludes local businesses, offline or non-tech services, physical products, and SEO-only pages made to collect indexed listings.
Make the software itself easy to identify. A reviewer should be able to open the website and understand what someone can use. A page that describes an unrelated service or exists only to attract search traffic does not explain a software product.
Your product does not need a new launch announcement every time you share progress. Start with an accurate profile; later updates can describe the meaningful changes around it.
Prepare the five profile details
The current New product form has these fields:
- Name: use the product’s public name consistently with its website and logo.
- Description: explain what the software does, who it is for, and the main task it helps people complete. Include enough detail to distinguish it from a broad category.
- Website: provide the real product URL. Open it yourself and check that it leads to the intended product, rather than a placeholder, unrelated page, or broken destination.
- Category: choose the closest product category from the available options. Use the product’s main purpose to guide the choice.
- Logo: prepare an identifiable product logo. ShipFeed supports PNG, JPG, and WEBP logo uploads; a logo is needed before product approval.
Name and Website are marked as required in the form. Preparing the complete profile gives the reviewer and future readers the context they need. Treat the checklist as preparation, not a promise of approval.
Write a description someone can understand
Lead with the product and its use case. “MapleTasks is a task manager for small support teams. It turns incoming requests into an assigned queue, where teammates can sort requests by priority and follow their status.” MapleTasks is fictional; this is an illustrative description, not a claim about a real product.
That description gives the reader a product category, an audience, and a concrete workflow. Broad phrases such as “the future of productivity” leave those questions unanswered. Add current limitations or availability details when they are necessary to understand what someone can use.
Keep claims supportable. A capability can be described directly without inventing customer numbers, time savings, testimonials, or ranking promises. Our software-evaluation guide shows the kinds of questions prospective users may bring to a product page.
Submit the profile for review
- Sign in to ShipFeed and complete email confirmation if prompted.
- Open your Workspace and choose New product or Submit product.
- Enter the profile details, check the website and logo, and reread the description.
- Choose Submit product for review, then check the status shown in your workspace.
Review any validation messages before trying again. Submitting the profile requests a review; it does not publish the product immediately or establish a guaranteed review time.
Understand what happens after approval
As explained in how ShipFeed works, an approved product gets a public page and its launch appears in the homepage feed, even before it has a published update. You can then share separately reviewed product updates when there is something useful to announce.
A profile describes the product. An update describes what changed. For the next release, use the product-update writing guide to explain the change, who benefits, how to use it, and any relevant limitations. Follow the current publishing controls and allowance shown in your workspace.
Product submission also does not reserve a place in a roundup or other editorial coverage. Approval and publication should not be read as promises of traffic, backlinks, rankings, or business results.
Handle corrections with the review state in mind
If a product is rejected, read the reason shown in the workspace and address the actual issue. Clarifying a software description or correcting a website can resolve an information problem. Rewording an offline service does not change whether it fits the platform’s focus.
The workspace explains that saving changes to a rejected product resubmits it for review. For an already approved product, the edit screen warns that saving sends it back for review: its public page and homepage launch are temporarily hidden, and article publishing remains locked until approval again. Read that warning before changing a live profile.