the platform
Every signal, how it is scored, and what happens next.
The homepage shows the shape. This page shows the whole machine: every source watched, every agent that watches it, the arithmetic that ranks what they find, and the pipeline that turns a ranked account into a message worth sending.
Nothing here is a shared list. The catalog below is the design space I work from. At kickoff I pick the signals that mean something in your market, configure them to your keywords, competitors, titles and geography, and build new agents for the ones nobody sells.
the map
Three Tasty Layers
Every stage, in order, with the real component names: what reads the source, what scores it, what finds the people, what writes, what checks the writing, and what carries the result back to the start. You can buy most of these boxes on their own from somebody. The work nobody sells you is making each one hand off cleanly to the next.
Sources
Public, checkable evidence plus your own first-party data. No purchased intent feed, anywhere in this diagram.
The signal agents
Each runs on its own schedule against your configuration, deduplicates, and resolves every event back to a company and, where there is one, a named person.
Your signal database
One isolated database per client. Separate schema, separate keys. Everything downstream reads from here, and you can export all of it on any day, including your last one.
The scoring agent
Scores your whole account universe against a fit rubric you tune: industry, size, geography, technology, company type. Then priority is computed per account from what actually fired.
The interpret agent
Reads each new signal once and writes down what it means: strength, confidence, why now, and what not to assume from it. Kept deliberately out of the arithmetic, so a model’s opinion can never quietly move your rankings.
Straight to your team
The feed tier stops here, and for a lot of teams that is the whole job. Nothing to operate, nothing to log into.
Or on into the committee
Roles resolved per account against your committee definition. Titles verified live at the source, emails verified or dropped.
Your context library
The other input to everything below. Your offers and their proof, ICP rules, personas and their pains, competitors, terminology, voice rules, plus a research file per account. Each writing step reads only the slice it needs.
The copy desk
Research the account into a cited brief, match one offer angle to the evidence, write it for each committee role in your voice, then strip the AI tells by name.
The judge, and the reader test
A separate model scores every draft against a rubric and bands it. The writer never grades its own work. A simulated recipient also reads the draft and reacts, so you see how it lands before a real person does. Advisory only, it never gates.
You edit. Nothing moves until you sign off.
Sample copy comes to you as a spreadsheet you edit directly. Sign-off is a single, audited moment that records who, when, and against which version of the spec. Change the copy and the version resets, which revokes any prior sign-off by construction.
The play runs
All of it ships as a play: one strategy, one audience, one approved set of copy. The playmaker builds it. The orchestrator then decides every hour what actually goes out, across channels and across the people on each committee.
It paces the waves, pauses a whole account the moment one person replies, stops the play if bounces climb, and works the best accounts first. Then it measures what happened and feeds channel, timing and angle back into the next run. The orchestration teaches itself.
↩ And then it feeds itself
This is the part that does not exist in a tool you buy. Every edit you make is captured as a rule. Every reply is classified. Offers are tested against each other and tracked per signal type, so the signals that actually produce conversations start outranking the ones that merely fire. A platform that does not close this loop scores exactly the same way in month twelve as it did on day one.
the catalog
147 buying signals, in 12 categories, and still growing.
Every signal worth watching in a B2B market. Not every one applies to you, and none of them carry a fixed weight: how much each is worth is tuned to your market and, once you are live, to what actually turned into conversations. Choosing the handful that matter, and what they are worth, is the discovery call.
trigger a dated event that creates a reason to reach out now · intent behaviour that shows an evaluation is under way · context fit or background that shapes what you say
Hiring and team growth
9
A company hiring is a company that has decided to spend money on a problem.
The surge names the tools and skills you sell into. The strongest form of the signal.
triggerA senior specialist arriving is a company deciding to take the problem seriously.
triggerSeveral roles at once means a funded initiative, not a backfill.
triggerSome of the roles touch your world. Worth a look, not a drop-everything.
triggerSomeone is being hired to solve a problem. If your product solves it, that is a reason to call.
triggerThey are growing, but not where you play. Kept deliberately quiet so it does not crowd the list.
contextA reduction in force. Often read as a no, but budget for consolidation and replacement tools tends to follow it.
triggerA role you were watching got filled or pulled. Either the problem was solved in-house or the budget moved.
contextHow many roles, and where. Growth in the team you sell to is the number that matters.
contextPeople on the move
12
Signals about one specific human, not a logo. Job changes, promotions, board seats.
Your champion just landed somewhere you want to sell. The highest-value person signal in the model.
triggerYou lose a champion at one account and gain intel on another.
triggerA warm path into a target account that does not require a cold anything.
contextHeld quietly until their new company is assessed, then it promotes itself automatically.
contextSomeone just left a competitor. They know the renewal dates, the gaps, and who is unhappy.
triggerA customer or champion lands somewhere new, and usually brings the tools they liked with them. If you stayed in touch.
triggerA promotion means a bigger remit and, usually, a budget line that did not exist last quarter.
triggerThe budget holder shows up in public: engaging with your content, joining a trial, following the founder. Rare, so it ranks.
intentThe budget holder shows up in public: engaging with your content, joining a trial, following the founder. Rare, so it ranks.
intentThe person you sell to just started. New hires want an early win and are still choosing their stack.
triggerA deal you lost on timing walked into a new company. Same buyer, clean slate.
triggerThe person carrying your open opportunity just left. Re-find the champion before the deal dies with them.
triggerMoney, filings and news
23
Funding, filings, contracts, coverage. What a company has publicly committed to.
A procurement that matches what you build, with the agency and scope attached.
triggerPublic money, a named principal investigator, and the exact project description.
triggerFilings say what a public company has committed to, in language their lawyers approved.
contextCoverage that names a target account and a topic you sell into.
contextNew money, and an investor whose other portfolio companies you may already know.
triggerRecognition is a reason to write, if you make it relevant. Soft on its own.
contextNew money. Overused as a trigger, but real: scaling follows funding, and scaling buys tools.
triggerWhat a public company tells investors it will do next year, in language its lawyers signed off.
contextA tool disappears from their stack. It failed or it is being replaced, and you want to be the replacement.
triggerA new rule lands on your market. If you are the easy way to comply, the deadline does your selling.
triggerTwo companies becoming one need everything reconciled. That is a year of gaps a good tool can fill.
triggerBad press forces change, and change needs new tools. Reach out with help, not a pitch.
triggerPublic personal news. Use it only when it is natural, and only if you would say it in person.
contextA platform changes its rules and a whole segment scrambles. Be the fix before they finish panicking.
triggerA buyer talks for an hour about how they think. Listen, then open with something they actually said.
contextGood press tells you where the company is heading and gives you a reason to write this week.
contextA launch changes what they need next: new customers to support, new hiring, new gaps.
triggerTenure, an award, a press mention. A reason to say something human before you say something commercial.
contextA new market means new rules, new hiring, new vendors. Every one is an opening.
triggerWhat they already run tells you whether you are the missing piece or the replacement, and which pain to open with.
contextA new investor or board seat brings a playbook, and the playbook brings vendors.
triggerYour topic named in their own press release. They wrote it down; you can quote it back.
contextA new tool in their stack. If it neighbors yours, you have a reason and a hook.
triggerCompetitors and switching
10
The moments when somebody else's customer becomes available.
Engaging with a competitor in public is a conversation you can join.
intentA public mention is usually an evaluation in progress.
intentTells you who chose them, and who is now locked in for a term you can time.
triggerPositioning intel, and a list of who reacted.
contextA competitor shuts down or gets bought. Their customers re-enter the market whether they wanted to or not.
triggerA competitor drops a feature. Everyone who depended on it is shopping this quarter.
triggerA new follow of a competitor's page is a conversation starting without you.
intentFollowing a competitor's rep or leadership usually means they are already talking.
intentHard to see directly, easy to infer: renewal windows are when an account will listen to an alternative.
triggerEven a reaction on a competitor's post is attention you can see. Weak, and worth stacking.
contextYour own website
14
First-party intent. The pages people read right before they buy.
The clearest hand raise there is. Usually the strongest thing in the whole catalog.
intentA human answered or reacted. Fed back in as a signal, not just a metric.
intentFirst-party, and the only click signal that requires a browser to actually render the page.
intentAn ad pixel appears. They are about to spend on acquisition and will need everything around it.
triggerA new analytics tag usually means a new marketing or growth lead who wants numbers. Someone with a budget just arrived.
triggerA new brand is a new direction. Nobody rebrands to keep doing the same thing.
triggerReading the docs is trying to solve something with you. Lend a hand before they give up.
intentTime on an integrations page is someone checking whether you fit their stack. Offer to answer.
intentLinkedIn's site tag matches more visits to target accounts than reverse-IP alone. Better attribution, not new intent.
contextPricing-page visits, especially repeated ones with plan toggling, are purchase math being done out loud.
intentNobody reads the security or terms pages for fun. Someone is clearing a purchase.
intentTraffic spiking or falling is demand arriving or leaving. Either way the account is in motion.
contextA rebuilt site is a strategy change made public: new audience, new packaging, new positioning.
triggerThey opened chat and asked something. Read the transcript before the follow-up.
intentYour own product
22
For product-led motions: usage, limits, integrations, and the moments before an upgrade.
The first moment the product clicked: a data source connected, a teammate invited. Retention starts here.
intentEarly access is a retention tool and an upsell warm-up in one.
triggerSecurity or IT shows up in the product. They do not use it; they approve it. A purchase is being checked.
intentPersonal-email sign-ups hide real buyers. Enrich them and the ideal customers separate from the hobbyists.
contextMore than one person working in the same place. Shared value is what gets budget.
intentSeveral teams at one company each signed up on their own. Consolidation, and a bigger contract, is the conversation.
intentA trial or free account. The oldest intent signal in software, and still one of the best when the domain fits.
intentConnecting a CRM or a warehouse means a real use case and an ability to pay.
intentApproaching a seat, usage, or plan limit is the most reliable expansion signal a product produces.
intentA declined card at a growing account often means a card limit, which means it is time for a contract.
intentA card on file. The clearest step from trying to paying, and worth knowing who did it.
intentA self-serve upgrade. Find out why; the reason is usually a bigger deal waiting.
intentThe top slice of your users, by usage. Underpriced seats and expansion live here.
intentQuiet for months, then back. A new initiative just got prioritized.
intentLinks to work made in your product, passed around. The value is spreading to people you have not met.
intentRepeated, frustrated clicks. Something is broken for them right now. Fix it in front of them.
intentA burst of heavy use, then silence. Enterprise teams test like that. You were probably being evaluated.
intentStarted signing up, stopped partway. Ask what happened; it is often something small.
intentLog-ins spike before initiatives and when seats are being shared. Both are conversations.
intentUsage jumps fast. A proof of concept, a rollout, or a team that just found the value.
intentA trial ending with real usage inside it. Convert, or trade an extension for a conversation.
intentThey looked at the upgrade and did not click. On the fence is exactly where a call helps.
intentYour CRM and pipeline
10
Signals already sitting in your own systems that nobody is watching.
A new case study of yours is a reason to contact everyone who looks like that customer, starting with their competitors.
triggerThe hand raise. Straight to a conversation, no scoring required.
intentThey started a form or a chat on your site and stopped. Interest with a snag in it. Find the snag.
intentA deadline you set. A price change or an expiring offer is a reason to decide now instead of next quarter.
triggerA bounce at a good account is usually a departure. Find out who has the seat now.
triggerA deal that went quiet on timing or budget. The cheapest pipeline you have, especially once you have something new to reopen it with.
triggerOne email opened many times is not one person. It is being forwarded to the people who decide.
intentA no-show is not a no. It is a calendar problem until proven otherwise.
intentThey opened the agreement. Watch the clock, not the inbox.
intentAn unsubscribe closes the email channel, not the account. Switch channel, drop the cadence.
contextDeveloper and community
14
Where practitioners go when something is broken and they need help today.
Vendor and community forums are where evaluation frustration goes public.
intentSomeone filed a problem in public, with the error text attached.
intentCategory-level attention, occasionally from the buyer.
contextA specific technical blocker, dated, with the person attached.
intentWeaker, but often the most candid thing a practitioner will say publicly.
contextA complaint is a user who cares enough to ask for help. Help, and learn what they are trying to do.
intentPeople who answer questions are your experts and advocates. Some are also your next expansion.
contextA question in a public forum is help being asked for. Answer it before a competitor does.
intentStars, forks, and pull requests on repos in your space. Interest in the technology, sometimes from the buyer.
intentA target persona joins your community. They came looking for people who solved what they are facing.
intentJoining a support forum is a step past joining a community: they need something fixed.
intentA ticket from a high-fit account is a conversation your sales team is not in yet. It should be.
intentA star or fork on a repo in your space is a developer bookmarking the problem. Volume is high; fit decides.
contextContributing code is the deepest interest a developer shows. Usually a practitioner, occasionally the buyer.
intentSocial and dark funnel
19
Public posts, comments, follows and engagement, resolved back to a person and a company.
They engaged with you, by name, in public.
intentYour target named in public, by someone with an opinion.
contextSomeone publicly wrote about the problem you solve.
intentEnough conviction to put your idea in front of their own network.
intentLower commitment than a post, still a person raising their hand on the topic.
intentWho is engaging with the people shaping your category.
contextContext on where the category conversation is going.
contextPassive, but a follower who fits the ICP is worth a look.
contextPage-level interest, company attached.
contextWeak on its own. Useful stacked with anything else.
contextThey read the post, clicked the email, watched the video. Passive alone; stacked with anything else, it moves.
contextFollowing the people who shape your category. Weak alone; strong stacked with fit.
contextEngagement with content built around the terms you care about: your category, your competitors. Early, but real.
intentReactions on Medium, Substack, or Dev.to posts about your problem. Readers with names.
contextSomeone at a target account looked at your profile. Not every lurker is a recruiter.
contextEngaged with a post about the problem you solve. A raised hand, in public, with a name on it.
intentA person at a target account writes in public. Engage before you email; it is the cheapest warm-up there is.
contextA topic you can solve for takes off, and the people engaging with it are a prospect list.
intentFollowing a person on your team rather than the logo. Personal interest, and usually a real evaluation.
intentPartners and network
5
Shared investors, shared advisors, partner overlap. The warm paths you already have.
You are their customer. That is the warmest intro you will get to the right buyer.
contextAn advisor you both know will make the introduction. That is what advisors are for.
contextA colleague already knows them. More coincidence than signal, and still the easiest door.
contextA company connected to one of your customers through a shared investor or parent: the same parent company, the same private-equity owner, or an investor that backs both, including a lender or a minority holder. We read the investor's own list, cite the page, and keep the connection labelled by kind, so the intro is a fact about who backs both, not a favour to ask.
contextWhere your partners' deals overlap yours, you get a picture of what an account is really doing.
contextEvents
7
Who spoke, who sponsored, who registered, who showed up.
A named practitioner, their topic of interest, and the audience they invested in reaching.
triggerRegistered for a webinar on your problem. Lower effort than a live event, still a raised hand.
intentThey attended an event on your topic. Learning, or shopping.
intentSponsoring an event is a marketing team buying an audience. If you help them reach it, say so.
triggerRegistered for or attended an in-person event on your topic. Interest with a date attached.
intentSigned up or showed up to learn about the problem. Evaluating, or about to.
intentThe meeting is real once the invite is accepted. Until then it is a hope.
intentReviews and third party
2
What buyers say about your category in public, on the sites they trust.
A public complaint about a competitor names the pain in the reviewer's own words. Answer it.
intentReview-site intent data. Third-party, inferred, and sold by the seat. Listed so you know it is not what we run on.
contextcustom signals
The one that matters most to you is probably not on that list.
The catalog is where we start, not where we stop. The signal that actually predicts a deal in your market is usually the one no vendor has bothered to productize, because it only matters to about forty companies and you are one of them.
Build your own.
Tell me the thing you notice right before a good deal starts. If it leaves a trace anywhere public, it can be watched, scored and delivered like everything else here.
All new ideas welcome. A new agent is a scoped build against a real source, not a roadmap request, and it joins the same scoring model as the rest.
Tell me the signal you wantcommittee and context
The committee tells you who. The context library tells you what to say to them.
Usually two products, from two vendors, with the joining left to you.
The buying committee
A signal alone is a logo and a timestamp. This turns it into people you can contact this morning, in the roles you define: seniorities, functions, anchor titles, who goes first. Hospitals and game studios are not the same committee.
- Titles verified live at the source, never off a stale record
- Emails verified or dropped, never built from a pattern
- Enrichment included, no separate data bill
- Recently touched by your team, held for review
The context library
A versioned library of how you sell, built with you and growing every time you edit a draft: offers and their proof, ICP rules, personas and their pains, competitors, terminology, voice rules, and a research file per account.
- Each writing step reads only the slice it needs
- Read-only for your whole team through Context MCP
- Every change visible, and revertable
- Your IP. Full export any time, including the day you leave
The join: one angle, three framings
The evidence picks one offer angle your context library says you can support, then rewrites it per persona: the buyer hears cost and risk, the champion hears what hurts on their team, the product owner hears the technical version. Same evidence, same claim, same week, so the account reads as one conversation instead of three strangers pitching three different things.
the playmaker
How a campaign gets built, approved and put in the air.
A play is one campaign: a strategy, an audience, and the copy that goes to it. The playmaker builds it. Every judgment call is front-loaded into one place before launch, so once you sign off the back end can run without asking you to approve things one at a time forever.
stage 1
Intake
A guided conversation that produces one play spec: the strategy, who it targets, whether it runs once or on a cadence.
intake
stage 2
Audience
Build and size the audience before anything is spent. Reports the size, the makeup, and every exclusion by name.
audience
stage 3
Finalize
Lock the audience and pin the spec version. Re-finalizing bumps the version, which revokes any prior sign-off automatically.
finalize-play
the gate
Sample and edit
Real copy for a real subset, exported as a spreadsheet you edit directly. Your edits are applied and captured. Iterate until you are happy.
sample · apply-edits
the trigger
Sign-off
The single launch trigger and the audit anchor: who signed, when, against which version. External sends stay separately gated.
sign-off
stage 6
Launch
The full pipeline runs: enrich, generate, stage the whole audience, push to the send layer. Evergreen plays re-fire on their cadence.
launch · smartlead-push
stage 7
Triage
The only recurring human surface after launch. Safety exceptions divert here: CRM-engaged, name and email mismatch, terminology. Dead rows drop themselves.
triage
always on
Learning
Replies reconciled and classified, edits turned into rules, offers tested against each other, results tracked per signal type.
learn · reconcile · experiment
Why the gate sits where it does
Approving individual emails forever does not scale, and it trains everyone involved to skim. Approving the copy pattern once, against real sampled output, with the version pinned so it cannot drift underneath you, is a judgment a senior person can actually make well.
After that the only thing asking for your attention is the exception queue, which is exactly the set of things a human should be looking at.
the operator’s bench
None of this is a dashboard you log into.
It is a bench of commands I run on your behalf. Each one exists because the same job kept coming up and doing it by hand kept producing a different answer.
Commands
The working surface: build a play, size its audience, research an account, generate and judge the copy, apply your edits, sign off, stage, send, reconcile, learn.
- intake
- audience
- sample
- apply-edits
- sign-off
- triage
- roast
- learn
- experiment
Scheduled jobs
The part that runs whether or not anyone remembers. Agents sweep their sources, the orchestrator ticks hourly, digests post in the morning, replies reconcile overnight.
- agent sweeps
- orchestrator tick
- daily digest
- reply reconcile
- nurture sweep
Conversational surfaces
Where plain English beats a command: ask the signal database a question, retune the scoring rubric and see the diff before it commits, walk a new client through provisioning.
- ask the database
- tune the rubric
- research signals
- build a seed list
- provisioning
See what would fire in your market.
Bring your ICP and your competitors. I will tell you which of the 147 I would build for you, what each would be worth, and what would land in your Slack.
Talk to us
gtmmm · Adam Silverman · adam@gtmmm.ai · home