The displacement board
A ranked competitive-displacement board for Wiz that scores 24 companies by how many of three independent leaks fired on them — someone arriving from a rival CNAPP vendor, someone…
- Built in
- 28 min
- Capabilities
- 8
- Live API calls
- 87
The prompt
Paste it into any coding agent with the Trayo MCP connected.
- + any MCP client
Use Trayo to build a competitive displacement board. Given my list of competitors, run three separate sweeps and combine them: who left each competitor in the last 90 days and where they went; public posts where people express frustration with each competitor, plus the commenters on those posts and their companies; and a signal for hiring or announcements that suggest a company is re-evaluating tooling in my category, run as discovery over every company the first two sweeps surfaced. Score each company by how many of the three leaks it shows, because one is noise and two is a conversation. For the top rows, map the committee and get emails. Present it as a ranked steal list where every row shows which evidence fired, with the actual quote, move or posting as proof — never a score on its own. Known constraints for this build: discovery only runs on accounts that exist in the workspace, so the third sweep writes the surfaced companies in first. Keep that batch under a few hundred or the run gets long.
What this app asked Trayo for
Every name, number and email on the page came back from one of these. None of it was typed in.
- Reads your workspace
What you sell, who you sell to, and the buyer personas already saved in Trayo.
- Finds companies
Surfaces accounts that match your ICP, plus lookalikes of the ones already working.
- Researches an account
A live snapshot per company — size, stack, why-now signals and why it fits.
- Finds the right people
Named stakeholders at an account, matched to the buying roles you care about.
- Gets verified emails
Work addresses with a confidence signal, so a bad match is visible rather than sent.
- Builds your account list
Imports, updates and organises accounts so the work survives the session.
- Watches for buying signals
Standing watches for job changes, funding and the other moments worth a reply.
- Reads social activity
Posts and the people engaging with them, for plays that start from a conversation.
Take the tour
The same run as the video above, one stop at a time.
- 01
This is the displacement board for the Wiz sales team. It ranks 24 companies by how many of three leaks fired in the last 90 days, and every row shows the quote, move or posting behind it.
- 02
Scroll down and the ranking is one point per leak. Buying companies rank above the services firms and security vendors that resell the category.
- 03
Frustration is the verbatim quote. Here, Logitech's Lead Cloud Security Architect replies "Man, I like you, but this is AI slot" under a post about a competitor's free-year pricing.
- 04
The evidence log flattens all 55 records into one newest-first list. Nothing on the board is a bare score.
- 05
That's the whole board: three leaks, 24 companies, and the proof behind every row. It ran on a real Wiz Trayo workspace, and the same prompt against your own workspace gets you this for your accounts.
How it was built
The data behind each screen, and what's faked for the demo.
If you sell cloud security at Wiz and you’re about to work a territory, this is the list you’d open first. It ranks 24 companies by how many of three leaks fired in the last 90 days: someone who arrived from a rival cloud-security vendor, someone publicly complaining about an incumbent tool, and a sign that the tooling decision is being reopened. Every row opens onto what it rests on: the verbatim quote, the named move with both job titles, or the announcement. The top five rows also carry a mapped buying committee with emails. Companies that buy in this category rank above the services firms and security vendors that resell it.
Two leaks is a conversation and one is noise, and this replaces the work of finding that out by hand: searching posts, checking who moved where, reading job boards and news, and keeping the result in a spreadsheet that goes stale. Nothing shows as a bare score. The ranked list is at /, and /evidence flattens all 55 evidence records into one newest-first log, so a rep can check a claim before repeating it to a prospect. One example is Logitech’s Lead Cloud Security Architect replying “Man, I like you, but this is AI slot” under a post about a competitor’s free-year pricing.
I didn’t pick the competitor list. I took it from the workspace’s saved ICP (buyerProfile.competitorTerms): Prisma Cloud, Lacework, Orca, CrowdStrike Falcon Cloud Security, Defender for Cloud, CloudGuard, Tenable, Sysdig and PingSafe. The workspace was empty, so I built the account pool from the companies the post sweep surfaced plus 140 ICP-matched accounts from company search, and imported 157 before running discovery. The post sweep ran 5 topic searches and opened 7 posts for their commenters. I kept 21 posts after dropping rival vendors, which surfaced 24 companies. Sweep 1 couldn’t run in the direction I was asked for. A source-only job-change search reads a fixed sample that can’t be paged. It came back empty for Sysdig, Orca, Lacework and CrowdStrike, and Palo Alto, Tenable and Aqua returned retry_later on every attempt. So I inverted it: I searched each account as the destination and kept rows whose previous employer is a security vendor, which gave 4 moves. Sweep 3 ran as specified, with 157 accounts, 3 signals and a 90-day lookback. It settled clean with 0 events and no blocked signals. A deliberately broad control run over 20 of the largest accounts also returned 0 in two seconds, so the jobs and news sources are dry for this workspace. I took the re-evaluation leak from company research instead, which covered all 24 companies. That is research with no event date, not a monitored signal, and the page treats it that way. The six sharpest re-evaluation signals in the whole run, including an explicit Prisma-to-Wiz migration spec, were all posted by staffing firms or under confidential clients. I put them in their own panel instead of crediting them to the recruiter that posted them. For the top five accounts, stakeholder search mapped 25 committee members, and email enrichment returned 21 addresses: 19 verified and 2 flagged with an identity conflict.
The searches, moves, quotes, research items, committee members and emails are real Trayo results from a real workspace. The Salesforce push and the committee email are stubbed. The buttons show their confirmation state and a toast naming what would have been sent, tagged demo, and nothing leaves the page. I stubbed them because a demo shouldn’t write to someone’s CRM or send mail to real people.