Five moments on your site that already mean someone's ready.
A good-fit visitor doesn't send a memo. They come back to your pricing page a third time this week. They invite a teammate into a trial that was supposed to be a solo evaluation. They go quiet for three days and then, out of nowhere, come back. Every one of those moments already happens inside your site, your product, and your CRM: the only question is whether anyone notices in time to do anything about it.
Bryn watches for exactly these moments and turns each one into a rule you approve once: when this happens, do this. We call that rule a Play: set it up a single time, and from then on Bryn runs it by itself, every time the pattern repeats, inside the same minute, with a record of what it saw and what it did.
"A good-fit account keeps returning to your pricing page, and your sales channel hears about it in Slack with the evidence attached. The same identification can update your CRM or personalize the page the visitor is looking at."
— docs.civic.com/brynThese five ship today. Per-Play detail pages and outcome numbers are next on our list.
When any of these five things happens on your site, Bryn already knows what to do.
Each Play below is named for the moment it watches for, not for a code. What follows the name is what actually happens: who gets pinged, where the task lands, and what the visitor sees next.
When a good-fit account keeps circling back to pricing
They've looked at pricing, then comparison material, then pricing again: three times inside a week. That's the moment Bryn pings your #growth-signals channel, files a CRM task with the full signal chain attached so nobody has to reconstruct the story by hand, and personalizes the landing page for whatever they look at next. Inside the same minute, on the record.
When a trial account starts acting like a team, not one person
A known account reads the docs, opens the integrations catalog, then invites a teammate: inside 48 hours. That's team formation happening inside a single trial. The Play files an expansion task on the account and arms an in-app prompt for the new seat, ready the moment they log in.
When a quiet trial suddenly comes back
Three days of silence, then a return visit. That return is the moment that matters: most tools would have already written the account off. The Play pings the account owner and personalizes the landing surface toward whatever setup step was left unfinished, so the next visit picks up where they left off.
When a second teammate joins mid-trial
An active trial invites its second seat inside 24 hours. Team formation partway through a trial is one of the strongest convert signals there is, so the Play files the task on the spot and arms the upgrade prompt before anyone has to ask for a bigger plan.
When outside interest and a resolved identity line up
A third-party topic surge lands on a company, and inside the same window your site resolves that same company's identity. The Play pings the account owner and hands the account to your sequencer. Inside the partner posture Bryn keeps everywhere: your outbound stays your outbound.
Every Play above breaks into the same four parts.
Five different scenarios, one shape underneath. It's the same anatomy whether the trigger is a pricing revisit or a quiet trial waking back up.
What the account did.
The named behavior, with its window: literal parts, not a paraphrase. "Three pricing visits, comparison material, repeated inside seven days," not a vague sense that someone's interested.
Who it applies to.
The account has to look like your ICP, your ideal customer profile, in plain terms: the kind of account that actually becomes a customer, before a Play fires at all. That's the guardrail you set once, so a random visitor never triggers the same response you built for a real prospect.
What happens.
A Slack alert, a CRM update, a personalized page: only the destinations the Play names, nothing else. Outbound-facing actions can hold for a one-click human review first, if that's how you set it up.
What it's proven to have done.
Every run writes an entry: what it saw, why it applied, what it did. That entry is replayable: the thing you or your CFO points to when someone asks whether this is actually working.
Approve one Play. Watch it run itself.
Your first identified visitor in Slack in about 30 minutes. Turn on one of the five Plays above and the next matching visit runs itself: no contract minimum, no procurement gauntlet.