[verdict][curated prompt][source: proofling.com]
Can I vibecode Proofling?
// buildable in a weekend, but real gaps stay open
A collection form, approval queue, wall, and embed are one-session work. The real Proofling loop adds payment-triggered asks, dependable email follow-ups, consent history, video processing, and integrations, which makes an honest replacement a weekend project with ongoing operational work.
confidence: high
what it is: Automated testimonial asks, follow-ups, approval, and embeddable proof
Buildability index · an editorial game
- Price 19 $/month weight: plus 2
- Time multi-day weight: plus 1
- Category testimonials no weight
- Moat integrations · infrastructure scale · execution quality weight: minus 4
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site proofling.com (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Accept a payment webhook, schedule one testimonial request and follow-up, collect consent, approve replies, and render them on a hosted wall and embed.
what you need
- Node.js 22
- Stripe account and webhook signing secret
- Resend API key
Founder-submitted · the simple wall is easy; dependable automation is the part worth paying for.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
Build a self-hosted testimonial automation app inspired by Proofling.
Use Node.js 22, TypeScript, Fastify, better-sqlite3, server-rendered HTML, and vanilla CSS.
Keep it single-tenant and deployable as one small service on a VPS.
- Add an .env.example for ADMIN_PASSWORD, APP_URL, STRIPE_WEBHOOK_SECRET, and RESEND_API_KEY.
- Create POST /webhooks/stripe and verify Stripe signatures before processing events.
- Idempotently store completed checkout customers and ignore duplicate webhook deliveries.
- Let the admin configure an ask delay, one optional follow-up delay, sender name, and message copy.
- Run a database-backed worker every minute; queued jobs must survive restarts and retry with backoff.
- Send email through Resend, with MAIL_MODE=log for local development without an API key.
- Give each customer an expiring signed /r/:token response link; never expose sequential database IDs.
- Collect name, role, company, optional 1-5 rating, testimonial text, avatar, and explicit publication consent.
- Resize avatars to 128px WebP, discard originals, and reject oversized or non-image uploads.
- Add a Basic Auth /admin page with pending, approved, private, and failed-delivery views.
- Allow approve, unpublish, delete, and resend; nothing public appears before approval and consent.
- Render a mobile-friendly /wall page with approved cards, dark mode, and honest buyer-context badges.
- Serve /embed.js so one script plus a div creates a sandboxed, auto-resizing wall on another site.
- Expose approved data at /proof.json and /proof.md without private contact details.
- Exclude multi-user accounts, billing, non-Stripe integrations, video, AI rewriting, and referrals.
- Add tests for signature verification, webhook idempotency, scheduling, consent gates, and public filtering.
- Include SQLite migrations, seed data, a Dockerfile, and a README covering setup, backups, and permissions. Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- polished onboarding and multi-tenant workspaces
- payment integrations beyond the single Stripe webhook
- managed email delivery, retries, scheduling, and suppression
- guided video capture, processing, captions, and retention controls
- long-lived consent history, proof exports, and referral workflows
Why people still pay
They pay to avoid operating the unglamorous parts: verified webhooks, timed sends, email delivery, retries, consent records, media handling, and integrations. The wall itself is easy; making customer requests arrive reliably and safely is the service.
moat: Integrations Infrastructure scale Execution quality what a moat is
automation/integrations/deliverability
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.