tl;dr Today we're launching Bryn, by Civic. Bryn is the Signal-Based GTM agent for Growth teams, and as of this morning it's generally available, self-serve, and live. Last week I promised the harder argument for why we built it. Here it is: the category learned to see, seeing is now cheap, and the next dollar a growth team spends shouldn't buy another way to watch. It should buy the ability to act. This is what we built, why, and how to see the gap it fills.
Today we're launching Bryn, by Civic.
Bryn is the Signal-Based GTM agent for Growth teams. It watches your product, your site, and your systems of record together, scores intent against your own definition of a good account, runs the Play you approved, and records every step. As of this morning it's generally available, self-serve, and live. You can start today.
It's built first for Heads of Growth at B2B SaaS companies with more signal than team capacity, especially mid-market PLG teams where speed matters. If that's you, the rest of this is the argument for why we built it, and a way to see the gap it fills in your own stack before you spend another dollar.
Last week I closed a Field Note by promising that argument. Here it is, and here's what we shipped.
Look at how the signal-based category grew up. Every dollar of innovation, and most of the budget, went into detection. Intent data. De-anonymized website traffic. Enrichment. Firmographic and technographic scoring. Dashboards that rank accounts by how interested they look.
All of it is real, and most of it works. We can now see intent at a resolution that would have looked like science fiction ten years ago. That race got crowded, and crowded means commoditized. There are hundreds of vendors in the martech and sales-intelligence space, and a typical revenue team runs a stack of more tools than it can name in a meeting.
Almost every one of those tools is an eye. Another way to watch.
Here's the part the procurement cycle hides. Detection has diminishing returns, and we passed the inflection a while ago.
The first intent feed is transformative. It shows you accounts you were blind to. The second adds coverage. The third overlaps the first two and adds noise. By the time you're evaluating the sixth way to see, you're not buying sight, you're buying a slightly different opinion about accounts you already knew were warm. The marginal account that the sixth tool surfaces, and you don't already have, is rounding error.
Meanwhile the thing that actually decides whether a signal becomes pipeline, the move that follows it, got almost none of that investment. We bought eyes until we could see everything, and left the hands to a person, a Slack channel, and a standup. So the number didn't move. You can't out-detect a broken handoff.
That's the gap Bryn was built to close. Not a better eye. A hand.
Hands is not another integration or a faster sequencer. It's a thing that closes the loop end to end, so a signal becomes a move without a person carrying it across four systems by hand.
Concretely, Bryn watches the product, the site, and the systems of record together. It scores intent against your own definition of a good account, not a generic model. It runs the Play you approved, carrying the moment into action. And it records every step, so the work record exists whether or not you go looking for it. One loop, run by one agent: watch, score, run, learn.
The unit is the Play. You define and approve the Play once. The agent runs each instance. Every run is logged.
```text PLAY pricing-revisit-x3 signal acme: pricing_view x3 in 1h, 2nd contact -> scored against YOUR definition of a good account -> action credible, relevant outreach + record update -> recorded audit log: what fired, what ran, why, when approve the Play once. it runs each instance. every run is logged. ```The operator keeps final say. Autonomy is bounded on purpose: Run mode is the default, Approve mode is an opt-in where you want a hand on it, and there's a kill-switch when you want everything to stop. The audit log isn't a compliance afterthought, it's the work record. It's how you answer why a given account got contacted on a given day, which turns out to matter as much as the speed.
```ts // you set the rules. the agent runs inside them. const play = { mode: "run", // default: runs approved Plays autonomously // mode: "approve", // opt-in: queue each instance for a human OK killSwitch: true, // stop everything, immediately audit: "every-step", // the work record, always on }; ```The thing I want to be precise about, because it's the whole point of the eyes-versus-hands argument: the product is the agent. Bryn is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack. There's nothing you log into to watch and then go act somewhere else. The watching, the scoring, the running, and the recording are one loop, run by one agent. That's what a hand looks like. Not a better eye. The thing that does the move.
We built it for ourselves first, because that's the only honest way I know to ship something you intend to put in front of other people. We were the first team it ran for. In our own workflows, Bryn moved high-intent signals from "we'll review this later" to action within minutes, while keeping the work record. It's no longer only for us. Today it's yours too.
Before you spend another dollar, here's a Monday-morning exercise that costs you nothing and will reframe your next budget conversation. It's how you see the gap Bryn fills.
Take your GTM stack and sort every tool into two columns.
Eyes: anything whose job is to detect, enrich, score, de-anonymize, or display. Tools that help you know.
Hands: anything that actually acts on a signal without a human relay. Tools that send the credible, relevant message, sequence it, route the account, update the record, and do it because a specific signal fired, not on a generic cadence that would have run anyway.
EYES (tools that help you know): Detect, Enrich, Score, De-anonymize, Display. HANDS (tools that act on a signal without a human relay): Send the credible, relevant message, Sequence it, Route the account, Update the record, and do it because a signal fired, not on a cadence.Now count each column. For almost every team I've shown this to, the eyes column is long and the hands column is one or two entries, and those one or two are usually a sequencer that fires on a schedule rather than on a signal. That ratio is the tell. It's a precise picture of where your budget went and why your time to action is measured in days.
Interactive stack audit: step the count of eyes tools versus hands tools to see the ratio update. Illustrative default, 9 eyes to 1 hand. Verdict: your stack is 9 to 1 in favor of watching. The ratio is the tell: everything in knowing, almost nothing in doing.The audit isn't an indictment of any tool. Each eye is good at being an eye. It's a picture of an imbalance: a team that invested everything in knowing and almost nothing in doing. Bryn is the hand that balances it.
If the stack audit came out lopsided, you already know what you're missing, and it isn't another feed.
Bryn is live and self-serve today. You can start a 7-day trial with no credit card on the Explore plan at $49 a month, point it at one signal you already trust, and watch it run the Play instead of routing the alert to a channel where it goes cold. Pick the signal your team argues about the most. That's the one worth seeing run.
Stop watching signals. Start running them.
You can start at civic.com/bryn.