Social proof, embedded

One line of script on a shop and it starts showing what other buyers are doing right now — purchases, people viewing, stock running out. The shop sells more, so the shop keeps it. And because a tiny badge ships with the widget, our growth surface is their traffic, not ours: one store with 40k monthly visitors introduces us to 40k people a month for free.

The buyer's view WIDGET RUNNING

brassandoak.store/p/copper-kettle
Brass & Oak Cart (0)
🫖

Hand-hammered Copper Kettle

★★★★★ 412 reviews
€89€119
🛍️
verified by Proofwave
×
Everything in that frame is the demo's own simulation — no shop was called. The point to judge is the widget: timing, restraint, and the fact that it looks native to a store that isn't ours.

The growth surface why it compounds

buyers see the badge each month from one shop's traffic
of them run a shop themselves ~3% of online buyers sell too
install it at a 4% badge click-to-install rate
new shops from those installs second generation, zero spend
That's the whole thesis in four rows: the widget is an ad for itself that the customer pays to display, and it's displayed to the exact population that might install it. The numbers move with the traffic slider below.

Configure it

Position
Theme
Pace
Events to show
Your embed

        
      

What it's worth to the shop

Extra orders
per month
Extra revenue
per month
ROI on €19/mo

Honest position

Who does this today: Fomo (€19–79/mo), TrustPulse (€5–39/mo), Provesrc, Nudgify — plus a long tail of Shopify-only apps. So the category is validated and the price point is known. What isn't taken: every incumbent is a paid SaaS with a trial funnel and no reason for a customer to spread it. The free tier with the badge on is the wedge — the incumbents can't copy it without cannibalising the paid plan they already sell, and we have no revenue to protect.

The real risks, not the pitch: the lift number is the whole product and it's contested — published A/B results range from ~0 to ~15%, and a badly tuned widget annoys buyers; fake-looking events destroy trust faster than they build it, so events must come from the shop's real orders (webhook, not invention), which is the part not built here; and platform app-stores are gated by KYC, so distribution has to be self-serve script installs, which is exactly why the badge loop matters.