§shoulditbeaprompt
shoulditbeaprompt.comruling № givefeedback

in the matter of — GiveFeedback — a feedback widget for web apps where users leave voice notes and screenshots and it organizes the feedback for product teams. Won a $100k build competition against 5,800 builders.

A beautifully onboarded feedback box that a good dev clones in a weekend. The $100k proved you can ship, not that this can't be shipped by someone else.

rung 3 · a weekend clone with a hell of an origin story✕ died on question 2, where the weekend clone left a head start and a nicer UI and not much else.

opinion of the court

GiveFeedback is a real, working app with a genuinely great story, and the story is doing a lot of the lifting. The product itself, voice and screenshot feedback with the storage and auth handled, is a weekend build for a competent team, which is where rung 3 lives. The six-figure win is proof the founder can ship and a real distribution head start, but a head start is not a moat. The climb is turning the feedback flowing through it into something that compounds.

the examination

q1. A feedback widget is a form, a file upload, and a dashboard. What's here that a developer doesn't just build into their own app in an afternoon?

"The voice and screenshot capture with the auth and storage handled, plus the organizing. It's the convenience of not building it. But the core is not exotic, I won't pretend it is."

↳ Appreciated honesty, and 'convenience of not building it' is a real wedge, though it's also the first thing a competent team builds for itself.

q2. Two devs and a weekend with Claude Code rebuild this, audio uploads and all. What do you still have that they don't on Monday?

"After that weekend, mostly a head start and a nicer onboarding. The $100k win gives it credibility and some early users, but the code is not the hard part."

↳ So the honest answer is a head start and a story, which is a great place to start a climb and not yet a moat.

q3. Where does this compound? What gets better the more teams use it that a cloner starts from zero on?

"If anything, it's the aggregated feedback patterns across products, and a wedge into teams that I keep. Right now it's a great tool with a great story, not a moat."

exhibit a — the weekend build

a decent dev clones this in a weekend. the build was never the moat.

▍

the founder: could out-run it. A solo builder who shipped this and won $100k against 5,800 others has the velocity to out-run most cloners. The kinetic moat is strong, the structural one isn't built yet.

the path up

4
a real system

above the moat line. it can't be typed into existence.

the moat line
3
a weekend cloneyou are here

a builder rebuilds the demo by Sunday. the code isn't the moat.

2
just a skill

a SKILL.md or a custom GPT is the whole product.

1
just a prompt

the model already does this.

what's missing

A reason the feedback gets more useful the more teams use it, a data loop only you have.

the move

Mine the aggregated feedback across products for patterns no single team can see, and sell that insight, so the data becomes the product and the widget becomes the way in.

post the verdict
try another case