Competitor complaint radar

This is a prospecting screen for a Supabase AE. It lists 21 LinkedIn posts from the last 30 days in which a developer or engineering leader said something sour about a backend or database platform Supabase competes with, ranked Hot or Worth a look. Each row carries the author, their employer, which competitor the gripe names, the themes it touches (cost, lock-in, scaling, reliability, frustration) and a one-line angle to open with. Clicking a row opens the post text Trayo returned, the account, and anyone else at that account who matches Supabase’s own buyer personas. A second screen shows the competitor roster Trayo ranked for supabase.com and which of those names actually turned up in the posts.

Everything on both screens came back from four Trayo operations. trayo_get_workspace supplied Supabase’s positioning, the five buyer personas and the ICP’s competitor terms. trayo_find_competitors on { self: true } ranked 12 companies against supabase.com — Neon Postgres, Appwrite, Nhost, Nile, Xano, Xata, EDB, Yugabyte, Hasura and three Postgres service vendors — with a direct/adjacent verdict and product and ICP alignment scores. Six trayo_search_posts topic searches over 2026-09-08 to 2026-10-08 returned 300 rows, 264 of them distinct posts. 91 of those named a competitor next to a pain cue; dropping posts written by people who work at those vendors (MongoDB, Percona, Google, PlanetScale and so on — a lot of the raw matches are vendor marketing, not buyers) left 37, and reading those by hand left the 20 gripes plus 1 counter-signal shown here. Finally trayo_search_stakeholders_batch ran Supabase’s persona definition against eight of the named employers and returned 8 people; 6 of them sit under the accounts in this list, including a VP Cloud Infrastructure and an SVP Software Engineering at o9 Solutions. Firebase (7 posts) and MongoDB Atlas (7) dominate, with Neon, AWS RDS, PlanetScale and Appwrite behind them.

Two things are worth saying plainly. The names developers actually complain about — Firebase, MongoDB Atlas, AWS RDS — are not on Trayo’s ranked competitor roster; they come from the workspace’s own ICP competitor terms, so the post searches were run against the union of both lists rather than the roster alone. And the tier, the named competitor and the angle on each row are my reading of the post, not a Trayo field: Trayo returned the posts and the first 600 characters of each, and the judgement on top is mine. One post points the other way — a developer who scrapped Supabase for Firebase over Postgres RLS friction and missing offline sync — and it is kept and labelled as a counter-signal rather than quietly dropped. Push to Salesforce, Draft intro and Share in Slack are stubs: no CRM, mail or Slack integration is wired, and each one raises a preview toast naming what it would have sent. The brand call reported that #3ECF8E is too light to use as text on a white page, so the kit derived #007248 for links, accent text and focus rings; #1C1C1C took the ink and top-bar role.