Submit to Make.rs: Fields, Timeline and What You Get

Make.rs is a maker showcase: products built by individuals, presented to peers. The audience is builders, which changes what a good submission looks like.

The short answer

Make.rs belongs in the batch, not in the plan. Ten of these in one sitting costs an hour; treating each one as an event costs a week for the same dozen listings.

Write the build note ahead of the listing: the constraint, the shortcut you rejected, what broke. Maker showcases publish the note as the entry, and a product with no build story gives peers nothing to read.

What Make.rs is

A community showcase where makers publish their projects, browsable by category and recency. Sign-up and submission both live at makers.com.

What it is good for

Community audiences are small, opinionated and technical. They will tell you what is wrong with the product, which is worth more than a citation.

Submitting, in order

Write a build note with technical detail
Prepare one screenshot
Choose the closest category
Submit with the live URL
Reply to feedback

One thing that catches people out

Show the build, not the brand. A short note about what you made and how it works earns attention from a maker audience; a launch announcement does not.

Mistakes that waste the submission

Submitting before the pricing page exists
Filing the product under a category with no comparable tools in it
Reusing a logo that fails the card’s aspect ratio
Never returning to the listing, so a broken link stays broken
Counting citations as link equity

Checking what you actually got

Load the listing in a private window, as a stranger would
Check the screenshot or logo renders at the size the card expects
Inspect the outbound link, not the button, if it routes through a redirect
After six weeks, run a site: query on the listing URL
Record followed or not followed — that field predicts value

Where SaasHunt fits

The other half of this decision is timing. SaasHunt takes submissions for a fixed 08:00 UTC go-live, so the listing goes on a calendar instead of a hope list. Approved listings are dofollow; paid tiers from $9.9 skip the queue, and $49 adds a newsletter slot.

SaasHunt

The build note is the entry

Maker showcases publish the story, not the product. The note appears beside the listing and it is what peers read before deciding whether to click.

Write it before submitting: what you built, under what constraint, and the one decision you are unsure about. Three short paragraphs is the right length.

What makers want to read

Constraints, shortcuts and failures. A note that says "built this in a weekend with one database and no tests" is more interesting to a builder than a feature list, and more likely to produce replies.

The audience has built things. They are reading for the parts they recognise.

Constraints make the story

The story is always the constraint: no budget, one person, a deadline, a customer waiting, a technology that did not work as advertised.

Without a constraint, a build note is a description. With one, it is a narrative, and narratives get shared.

Show the build, not the brand

A logo and a tagline belong on a launch board. A maker showcase wants the working thing, a screenshot of the awkward part, and an honest sentence about what is missing.

That honesty is a positioning strategy: it makes the product credible to people who can tell the difference.

Responding to technical questions

This audience asks implementation questions first. Answer them properly, in the thread, even when the answer is unflattering.

A thread with six substantive answers is read by people who never post, and those readers are the ones who later try the product.

What this audience converts into

A small number of highly engaged users, occasional contributors, and feedback that would cost money elsewhere. Rarely revenue on the day.

Judge the submission on whether it produced a conversation, not on whether it produced signups in the first week.

After the showcase

The listing persists as a dated reference with a link. Check it once a quarter, and return with a new note when the next meaningful thing ships rather than reposting the same product.

The follow-up note

A week after the showcase, post once more with what you changed based on the thread. That single update is read by the people who skipped the first post, and it converts curiosity into a trial.

It also establishes the habit of shipping in public, which is the audience you are addressing.