Creator and commerce decision

Gifts Qr

A small team or single competent engineer can replicate the core paid workflow (surprise pages + QR + one-time payments) in ~28 hours; the vendor’s content, templates, and audience are the main nontrivial assets you’d give up.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$50one-off28 h to build

$15/mo3 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Create a surprise landing page (photos, music, message), generate a QR/unlock link, accept a one-time payment to make the link persistent and remove ads/watermarks.

What it still won’t have

  • The vendor’s catalogue of 30+ polished surprise templates and UX polish
  • Built-in affiliate program and blog/SEO guides
  • The product’s existing user base and marketing reach
  • Any proprietary mobile/web optimizations and tracking the vendor provides

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Gifts Qr does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal Gifts QR clone using Next.js (React) frontend + Node.js backend, Postgres for metadata, Amazon S3 (or MinIO) for media, Stripe for one-time payments, and a JS QR library (e.g. kazuhikoarase/qrcode-generator). Core features in scope: (1) authoring UI for a surprise page template (upload images, add text, optional audio), (2) media upload and CDN delivery, (3) ephemeral preview links and persistent paid links, (4) QR code generation for each link, (5) payments integration that toggles link persistence and removes ads/watermarks, (6) access control and link expiry enforcement, (7) basic sharing actions (WhatsApp/URL copy). Out of scope: matching all 30+ template variants, affiliate program, multilingual blog/SEO content. Require error handling, input validation, and automated tests for payments, link access, and media upload flows.
How we checked2 sources · 2/3 runs agreed · evidence score 82

How the score was reached

  • Build verdict base78
  • 2 cited sources+1
  • Price verified on pricing page+3
  • Evidence score82

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded