Join the waitlist

Your buyers get the wrong answer.

Comparison pages get your product wrong. Models read them and repeat them as fact. We find the pages making false claims about you, draft the correction, and keep watching after it is sent.

One email when we launch. Nothing else.

That didn’t go through. Try again in a moment.

A cropped screen of an assistant answering a buyer who asked whether Plunk supports workflow automation. The answer, taken from email-platform-reviews.co, states it is transactional-only. It is struck through in red and stamped false.
Ask

Does Plunk have workflow automation?

Plunk is transactional-only. You'll need Customer.io or Mailchimp for automated sequences.

email-platform-reviews.co/plunk

False

None of these sentences are true.

Pages like these take minutes to generate and about forty seconds to disprove. Nobody spends the forty seconds, so they rank, and they stay up.

  1. Falsesaas-stack.io/email-tools/plunk

    “Plunk doesn't handle inbound email. You'll need a separate service for receiving and processing.”

    TruthBuilt-in inbound email with webhook notifications. Included on all plans.

  2. Falsethe-stack-guide.com/plunk-vs

    “API access limited to paid plans only.”

    TruthFull REST API and SDKs on Free plan.

  3. Falsecompareemailtools.co/pricing

    “Contact-based pricing like Mailchimp. Expect $0.004 per email.”

    Truth$0.001 per email flat. Unlimited contacts, no minimums.

Examples. The failures are real ones; the publishers are invented.

A wrong page used to reach one reader. Now every model that reads it repeats it.

Comparison pages have always been sloppy. What changed is how fast they are written, and who reads them next.

  1. A page gets it wrong

    Generated in bulk, never checked, published to rank for your name.

  2. A model reads it

    It has no way to tell your documentation from an affiliate’s guesswork.

  3. The answer repeats it

    It arrives stated as fact, with no citation and nothing linked behind it.

  4. A buyer believes it

    They never visit your site. You never learn the deal existed, and there is no one page you could go and fix.

From your URL to a corrected page.

We build the record from your own pages, find the claims that contradict it, and write to whoever published them.

Three cropped screens of the product. First, the record of truth: Plunk's facts filed under a canonical key, each with the value read from the page, a consensus score and the number of the customer's own pages that agreed. Second, a claim published on saas-stack.io/email-tools/plunk set against the record row that refutes it, marked false. Third, the correction letter drafted from that pair, addressed to the publisher, carrying the quotation and the source, and held for approval.

Corrigend reads your site first.

Every fact starts on a page you already wrote, and stays traceable to the line it was read from. Nothing is typed in by you, and nothing is assumed.

Record of truthuseplunk.com
capability18pricing7integration9support4
  1. capability.workflow_automationsupportedSources3Consensus96
  2. capability.inbound_emailsupportedSources2Consensus94
  3. capability.dedicated_ippro and aboveSources1Consensus62
  4. pricing.per_email_usd0.001Sources4Consensus91

Then it reads everybody else's.

Comparison pages, roundups, alternative-to posts. Each claim about you is held against the record, and the ones that contradict it are marked.

Needs you3 wrong on this page
saas-stack.io/email-tools/plunkFalse

They published

“Plunk doesn't handle inbound email. You'll need a separate service for receiving and processing.”

Your record says

capability.inbound_email

supported

read from useplunk.com/features

CorrectionBuilt-in inbound email with webhook notifications. Included on all plans.

Then it hands you the letter.

The letter is written, addressed and cited before you see it. It goes nowhere until you send it, and that is the only step in the whole run that needs you.

Correction letterDraft
To
editor@saas-stack.io
Re
Inbound email on your Plunk page

“Plunk doesn't handle inbound email. You'll need a separate service for receiving and processing.”

Built-in inbound email with webhook notifications. Included on all plans. It is documented in the Features section of useplunk.com, which is linked below.

Held for your approval1 claim · 1 source · 1 fact

The web keeps publishing. So Corrigend keeps reading.

New comparison pages, roundups and posts go up every week, so it reads them again, and again. Anything new that contradicts your record is drafted and held until you send it.

A cropped screen of a sweep in progress. Seven numbered phases: planning the searches, finding forty-one mentions, choosing twenty-four to read, fetching them - nine of which had not changed since the last run - and reading eighteen of the twenty-four so far. The last two phases are still queued.
Runsweekly sweep · useplunk.com
Runningstarted 4 minutes ago
  1. 01Working out what to search for12/12
  2. 02Searching for mentions41/41
  3. 03Choosing what to read24/41
  4. 04Fetching those pages24/24 · 9 unchanged
  5. 05Reading what they claim18/24
  6. 06Indexing those claims
  7. 07Checking them against your record

From the founder

I also run Plunk, an email platform. There are hundreds of comparison pages about it, and I was never going to keep up with them on my own.

That is the part nobody warns you about. Correcting one is easy. Finding all of them, checking each against what is actually true, and noticing when a new one appears is not something you do beside a full-time job.

So I built the thing I wanted for Plunk. It reads all of it, tells me what is wrong, and drafts the correction. I still send them myself.

Image

Dries Augustyns

Founder of Corrigend and Plunk, useplunk.com (opens in a new tab)

Find out what the internet is telling your buyers.

A record of what is true
Built from your own pages, every claim in it traceable to the line it was read from.
A ledger of what the web says
Every page making claims about you, judged against that record and marked.
Letters, drafted and waiting
Addressed to whoever published it, quoting the line, citing your source. You send them.

One email when we launch. Nothing else.

That didn’t go through. Try again in a moment.