Skip to main content

[verdict][curated prompt][source: sendcore.me]

Can I vibecode Sendcore?

// the value is the network, the data or the infrastructure

The editor is the copyable part. A coding agent will happily build a private Shopify app that pulls your products, composes an HTML campaign and sends it with your own provider key, and for one store that is genuinely useful. What does not fall out of a one-shot is everything that makes it a product a merchant can run a business on: a listed App Store app with OAuth, mandatory GDPR data webhooks and billing that lands on the merchant's own Shopify invoice, per-tenant domain authentication with the DNS handholding it needs, and the consent, suppression and bounce records that keep sending both legal and delivered. Worth saying plainly: Sendcore is small and recent, with no audience network and no proprietary dataset to hide behind. It survives on platform surface, compliance plumbing and the unglamorous backlog that only real merchant sending reveals, which is a narrower moat than Klaviyo's and an honest one.

confidence: medium

what it is: Campaigns, automations, popups and store attribution, installed into a Shopify or WooCommerce shop

Buildability index · an editorial game

  • Price from 16 $ · usage-based weight: plus 2
  • Time one sitting for a single store; not a multi-tenant product weight: plus 3
  • Category newsletter no weight
  • Moat integrations · compliance and regulation · infrastructure scale weight: minus 5
  • Confidence medium weight: zero
  • What you lose 5 items weight: minus 2
  • Site sendcore.me (si apre in una nuova scheda) no weight
Indice: minus 2. think twice

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

Build a private Shopify app that syncs your products and customers, composes an HTML campaign with a product block, and sends it to a consented segment through your own email provider key.

what you need

  • Node.js 22
  • SQLite
  • Shopify custom app Admin API token (read_products, read_customers, read_orders)
  • Bulk email provider key in .env
  • A sending domain you control, with SPF and DKIM already verified

Credibility row: a small, recent app in a category owned by incumbents, listed because the reason it survives is structural rather than clever interface work.

The prompt

The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.

One-shot prompt EN
Build me a private Shopify campaign sender for one store I already own. Not a SaaS, not multi-tenant, no signup. Requirements:

- Node 22 + Fastify + better-sqlite3, server-rendered HTML, no client framework.
- Read the store with a Shopify custom app Admin API token I create myself
  (read_products, read_customers, read_orders); no OAuth, no App Store install flow.
- Send through one bulk email provider with my API key and my already-authenticated
  sending domain; both in .env, ship a .env.example.
- SQLite tables: contacts (email, consent state, source, created_at), products cached
  from Shopify, campaigns (subject, body_html, status, sent_at), and sends
  (contact_id, campaign_id, status, error).
- Every contact carries an explicit consent state. Never send to an unsubscribed or
  unconsented contact, and prove that with a test.
- Every email gets a working one-click unsubscribe link plus List-Unsubscribe
  headers, backed by a signed token and honoured immediately.
- The composer is a plain HTML textarea plus a product picker that inserts image,
  title, price, and link from the synced cache. Render with inline styles and a
  table layout so it survives Gmail and Outlook; no external stylesheets or web fonts.
- Always send a test to myself first, and require a typed confirmation of the
  recipient count before any real send.
- Send in batches with retry and backoff, one send row per recipient, so a crash
  resumes instead of double-sending. Report delivered and failed from the sends
  table only; do not invent open or click tracking.
- CSV import and export for contacts so the data is never trapped in the app.
- Tests: the consent gate, the unsubscribe token, batch resume, and one end-to-end
  campaign against a mocked provider.
- README states what this is not: no deliverability operations, no bounce or
  complaint processing, no App Store distribution, no billing. Say plainly that real
  volume from a cold domain lands in spam, and warmup is now the reader's job.

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

  • App Store distribution: OAuth install, app review and the mandatory GDPR data webhooks
  • billing that appears on the merchant's own Shopify invoice instead of a separate card
  • domain authentication onboarding and per-tenant sender reputation
  • bounce, complaint and suppression handling
  • order-level revenue attribution and automations that fire on real store events

Why people still pay

Merchants pay for the parts nobody enjoys building: staying installed and billed inside Shopify, keeping consent and suppression records defensible when a customer or a regulator asks, and getting mail into inboxes from a domain the merchant owns. The campaign editor is the part that demos well and the part an agent reproduces in an afternoon, right up to the moment other people's content meets other people's inboxes. Pasted rich text with mixed inline formatting, merge tags that must not eat the punctuation around them, product blocks that survive Outlook, automation timing that has to line up with a real order: none of these are design problems. They are a backlog you only discover by sending mail on behalf of other businesses, and grinding through it is what separates a demo from something a shop trusts with its list.

moat: Integrations Compliance and regulation Infrastructure scale what a moat is

platform surface and compliance plumbing, plus the merchant feedback loop behind automations and the editor

Who has already built it

Starting from here is still vibecoding: the prompt is for when you want it exactly your way.

Do you agree?

The vote balance

Ancora nessun voto: il tuo è il primo.

Nessun voto ancora — il primo pesa.

Related apps

From a Confusing Brief to a Complete UX/UI A vague brief becomes a navigable app. Product Ad From a Single Photo A photo becomes an animated ad, no code required. Get Claude to Watch Your Videos Claude watches your videos and turns them into text. Higgsfield Inside Claude Code Generate images and video while you code in Claude Code. Turn a Loom Recording Into a Web Page A screen recording becomes a web page, no code. Vertical Shorts With NotebookLM Your sources become a vertical short. Luxury Landing Pages on Lovable A luxury landing page from a single prompt. Excalidraw Running Locally Excalidraw free on your computer, no code. Mistral OCR in Your Workflow Extract text from documents with Mistral OCR. Claude SEO in the Terminal 25 free SEO skills inside Claude Code. Google Search Console inside Claude Code Search Console data inside your terminal. Claude Code Routines Claude working on its own, computer off. Clone a Landing Page in React With v0 Clone a real landing page into React code. Context Economy With Claude Work light and don't burn through Claude's limits. From Prompt to Self-Improving Skill Claude skills that learn from your mistakes. From NotebookLM to Canva: Presentations NotebookLM slides, finally editable in Canva. The Map for Understanding Every AI Tool 12 categories for placing any AI tool. Transparent PNGs With ChatGPT Real transparency, not a fake checkerboard. Animated Infographics With Gemini Infographics that loop, animated with Gemini. Market Research With Deep Research Deep Research as your market analyst. Get Cited by AI Search Engines (AEO) Become a source that ChatGPT and Perplexity cite.