Plaid scored 6.0/10.

Plaid’s strongest dimension is Craft.

Craft scores 7.0 / 10. The dim covers 4 signals in the rubric; the page still has 1 finding in this area, but the overall score is strong relative to peers.

What’s costing Plaid, quoted from the page.

1. 01
   Your hero subheadline describes the category, not Plaid.

   “Connect to real-time insights on the Plaid Network to create fast, safe, and smart financial experiences.”

   The subheadline is the first thing a developer reads after your headline, and it spends that moment on three adjectives — fast, safe, smart — that every competitor uses too. Your actual moat is right there in the stats below: 12K banks, 1M daily connections. The subheadline ignores all of it and sounds like a category description, not a reason to pick Plaid.

2. 02
   The page is built for developers; nearly half the traffic is consumers.

   “The page is aimed squarely at product and engineering teams ready to evaluate an API — 'Get the API keys,' 'Read the docs,' code snippets, B2B social proof. But 24.02% of inbound traffic arrives on problem-aware queries like 'ach payments,' 'checking and routing number,' and 'pay…”

   The page has one nod to consumers — a single footer line pointing to Plaid Portal — and nothing else for the 44% of visitors who arrive looking for help with ACH payments, routing numbers, or cash advance apps. That's a consumer-information need, not a developer-evaluation need, and the page skips straight to API keys. The awareness-gap mechanism here is cold-to-hot compression: the page assumes a buyer who already knows what Plaid does and why they'd use it, but nearly half the audience hasn't reached that frame at all.

3. 03
   The named customer logos — Venmo, Robinhood, Carvana, H&R Block — never appear as a direct proof row.

   “Customer logos are confirmed available but appear only inside an animated notification mockup, not as a static, scannable logo bar. A developer skimming the page at speed will not register these as customer endorsements — they read as UI illustrations.”

   The named customer logos — Venmo, Robinhood, Carvana, H&R Block — never appear as a direct proof row. Visitors who don't catch the animated notification mockup miss your strongest trust signal entirely.

4. 04
   Page claims reliability at scale; buyers flag API instability and breaking changes

   “"Connect to real-time insights on the Plaid Network to create fast, safe, and smart financial experiences." / "A network that gets more powerful daily"”

   The marketing page leads with 'real-time insights,' '1 million daily connections,' and 'reliable' network language, while buyers rank 'reliable API and webhooks' (88%) and 'API and system integration that actually works in production' (62%) as top unmet needs — and explicitly red-flag 'frequent breaking changes to UI or API without notice.' No uptime SLA, reliability track record, or webhook documentation is surfaced on the landing page.

5. 05
   One stat in your proof block has no source and weakens the ones that do.

   “25% higher conversion Increase sign-ups by up to 25% with easy onboarding”

   Your network scale stats — 1 in 2 banked U.S. adults, 1 million daily connections — are verifiable platform facts. But "up to 25% higher conversion" is unattributed and hedged with "up to," the classic tell of a marketing claim with no named source. When an analytical reader spots one number that can't be checked sitting alongside numbers that can, it casts doubt on the whole row.