ABM microsites
Nine per-account ABM microsites for Notion, each with the company's logo, a headline written for them, their why-now signals, the stakeholders and why each one matters, and the…
- Built in
- 17 min
- Capabilities
- 7
- Live API calls
- 41
The prompt
Paste it into any coding agent with the Trayo MCP connected.
- + any MCP client
Use Trayo to build personalised microsites for an ABM list. I give you a list of target accounts; you generate one page per account. Each page carries the company's logo and a headline written for them specifically, the signals that make this the right moment, the people who matter and why, and a short section on the challenge they appear to be facing in their own public words. It should read as if someone spent an afternoon on that one account. Give me an index of all the pages and let me open any one full-screen.
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.
- 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 app runs on Trayo. Here's the receipt.
- 02
Trayo's company search found 70 matching companies.
- 03
This is Field Notes: one page per target account.
- 04
Open DigitalOcean: logo, headline, and why it matters now.
- 05
Four things that changed there this quarter.
- 06
Four leaders just arrived, straight from AWS and Salesforce.
How it was built
The data behind each screen, and what's faked for the demo.
A rep working a named list of accounts, five minutes before a call, opens Field Notes and sees nine target accounts in an index. Clicking one gives a single page for that company: its logo, a headline written only for it, the handful of things that changed there recently, the people who decide and a written reason for each, the company’s own description of itself read as a statement of the problem, and what to lead with. There is a full-screen button for presenting the page in the call, and next and previous links for walking the list.
It replaces the tab-switching and the stale spreadsheet. Before this, getting ready for one account meant a company site, a LinkedIn search for who’s there, a news search for what changed, and a doc to paste it into, and that was redone for every account. Here the research, the people and the reasoning behind each person sit on one page per company, so the prep is already done when the rep opens it.
No account list was supplied, so I built one from the workspace’s saved ICP, which is Notion selling to knowledge-work organisations. trayo_find_companies returned 70 US software, IT-services and internet companies at 250-3,000 employees. I imported the 59 clean rows with trayo_import_accounts and worked up nine in full. Everything on the pages comes from Trayo. trayo_research_company gave me 31 “why now” lines and 18 fit lines across the nine accounts. trayo_search_stakeholders gave me 44 people, each with a written rationale matched against the workspace’s buyer definition. trayo_search_job_changes gave me 21 director-and-above arrivals from the last 90 days, with the role each person left. The “in their own words” quote on each page is the company’s own LinkedIn description, as POST /v1/find returned it. I wrote all 44 stakeholders back into the workspace with trayo_add_people: 44 created, 0 skipped.
One part did not work. I created two signals and fired a discovery run over all 59 accounts against nine signals with a 180-day lookback. It settled in 17 seconds with zero events, no blocked signals and no error. A smaller re-run over eight accounts at 365 days did the same. So the “why now” sections are built from company research and job-change data, not discovery events, and the /#/sources route in the app says so. Trayo’s post search is market-wide rather than per-account, so it couldn’t give me a quote from anyone at these nine companies. The “own words” section uses each company’s published About text instead, and is labelled that way.
The four outbound buttons are stubs: draft intro, push to Salesforce, share to Slack, and add to sequence. Each shows a toast saying exactly what would have been sent, tagged “demo”. Nothing leaves the browser, and I spent no email lookup allowance. The account data, stakeholders, job changes and research are real Trayo output against a real workspace, and the 44 people are really written back into it.