Back to archivecertified generic

Case file

trychert.com

ShitScore 60 / 100SaaSCaptured 2026-05-19Submitted by communityVisit crime scene ↗

An iMessage API product whose metrics bar claims 40% average response rate on cold outreach (unsourced), whose FAQ opens with "Is this real iMessage, or just SMS branded as iMessage?", whose third FAQ is "What about deliverability and spam flags?", and whose subheadline promises to maintain personalized interaction at scale.

Chert provides iMessage infrastructure for bulk developer outreach. The metrics bar: 40% average response rate on cold outreach — no source given. FAQ #1: "Is this real iMessage, or just SMS branded as iMessage?" FAQ #3: "What about deliverability and spam flags?" The subheadline promises to maintain "quality, trust, and personalized interaction" while reaching people at scale.

Share this roast

PostShare

Exhibit A — Evidence

Captured 2026-05-19

Hero viewport of trychert.com on a cream-white background. Top nav: Chert logo (orange circle icon), Home, Blog, Contact, orange "Book a Call" button. Small label: "Backed by Y Combinator". Large serif headline: "iMessage infrastructure for reaching people at scale." Subheadline: "Build and deploy AI on iMessage to reach people at scale while maintaining quality, trust, and personalized interaction." Orange CTA: "Book a Call". Right side: iPhone mockup showing a blue iMessage conversation. Below hero: trusted-by logo row including Tour, Symbal, DCNHC, V, Whop.
Screenshot — trychert.com (1238×1080)

Score breakdown

Prompt residue6/10
Feature grid density7/10
Meaningless value prop5/10
Trust signal suspicion8/10
Founder face AI probability3/10
Product proof absence6/10
ShipFast resemblance7/10
Hero claim
"iMessage infrastructure for reaching people at scale." Subheadline: "Build and deploy AI on iMessage to reach people at scale while maintaining quality, trust, and personalized interaction." Metrics: 40% average response rate on cold outreach, 95% read rate, <10min setup.
Proof problem
40% cold outreach response rate is displayed without source, methodology, or sample size — an extraordinary claim in a category where 10-20% is considered strong. 95% read rate is plausible for iMessage but similarly unsourced. "Backed by Y Combinator" (listed as "Combinator" in footer) is a real and verifiable signal. Trusted-by logos include Whop and Tour — recognizable but small-to-mid-stage companies. Four developer workflow cards have no named customer. FAQ #1 being a legitimacy challenge suggests the product category has a known credibility problem.
Visual pattern
Cream-white background with orange accent color. Serif hero headline, minimal nav, iPhone mockup on right. Logo bar below hero (Tour, Symbal, DCNHC, Whop). "One API. Many features." feature grid: eight feature tiles (two-bubble messaging, typing bubbles, attachments, group chats, tapbacks, one-tap feedback, live delivery, sending attachments) plus a "+many more" overflow card. Dark blue metrics bar: 40% / 95% / <10min. "Used by Developers" four workflow cards. "One thread, everywhere your team works" integrations section (Salesforce, Slack, HubSpot, Clay) with iPhone mockup. FAQ section. Dark "Build with iMessage" CTA with embedded calendar. Footer with backer logos. Large Chert wordmark at page bottom.
Why it still might convert
iMessage has fundamentally higher engagement than email or SMS for consumer-facing products — if the infrastructure is real, the 95% read rate is plausible. Y Combinator backing is a genuine quality signal. Developers who have tried to build iMessage workflows and hit Apple's API restrictions understand the problem well and are willing to pay for a compliant solution. The calendar CTA is low-friction: a 20-minute call rather than a credit card. It converts for developers who know the problem and recognize that anyone who has solved iMessage infrastructure at scale has done the hard work.

Editorial roast

By Editorial Desk · Filed against trychert.com

¶ 01

"40% average response rate on cold outreach." Displayed in large font in the metrics bar, alongside 95% read rate and <10min setup time. Industry benchmarks for cold SMS response rates reach 10–20% by optimistic measurement. Cold email averages 1–5%. A 40% cold outreach response rate would be among the highest figures ever reported in the category. The number has no source, no methodology, no sample size, and no definition of what counts as a response.

¶ 02

"Is this real iMessage, or just SMS branded as iMessage?" — FAQ question number one. The first question Chert anticipates from potential customers is whether the product is actually iMessage. This is an iMessage infrastructure company. The first question it expects: is this iMessage? The FAQ exists because the concern exists. The answer is collapsed.

An iMessage API product whose metrics bar claims 40% average response rate on cold outreach (unsourced), whose FAQ opens with "Is this real iMessage, or just SMS branded as iMessage?", whose third FAQ is "What about deliverability and spam flags?", and whose subheadline promises to maintain personalized interaction at scale.

¶ 03

"What about deliverability and spam flags?" — FAQ question number three, after legitimacy and after the Twilio comparison. Apple's iMessage terms of service explicitly prohibit [redacted] bulk commercial messaging. "Cold outreach" is listed as a developer workflow use case. The product that claims 95% read rates and 40% cold response rates has placed a spam FAQ on its own page, third from the top, because customers ask.

¶ 04

"Build and deploy AI on iMessage to reach people at scale while maintaining quality, trust, and personalized interaction." Three things the subheadline promises to maintain: quality, trust, and personalized interaction. These are the three properties that bulk outreach at scale structurally compresses. Personalized interaction at scale is the definitional problem the product is positioned to solve. The subheadline holds both without acknowledging they are pulling in opposite directions.

— 30 —

More from the archive

Similar offenders on file.

imperfectly.appSaaSSS 65

An anti-AI-slop writing tool — packaged in a hero / feature-cards / pull-quote / pricing-table / FAQ SaaS template that any AI would generate unprompted, decorated with a typewriter stock photo to signal authenticity, whose product logic is: AI writes too perfectly, so pay $9 a month to add the imperfections back.

Open file →
supadrop.hostSaaSSS 62

A portfolio hosting product that says "30 seconds" twice in two consecutive section headings, positions its customers as "people, not developers" in a product named Supa-drop-.host, offers "beautiful templates" with beauty as the only descriptor, and closes with a footer asking if you are ready to use a product that, by its own repeated count, takes 30 seconds.

Open file →
latenode.comSaaSSS 75

An AI workflow automation tool whose hero defines itself as "automation that works" (implying competitors do not), whose value proposition is "intelligent automation — without the manual work" (the definition of automation), whose Zapier comparison claims to be "1k+ cheaper" without specifying the unit, and whose integration count of 6,000+ appears in at least two separate section headings on the same page.

Open file →

Correction channel

Wrong, unfair, or outdated?

Ask for a correction or update. Satire is more effective when the facts are not lazy.