Skip to main content

A Play is a pattern with an outcome.

You decide what happens once. Bryn delivers it every time the pattern shows up, without waiting on you.

pricing → comparison → repeat (7d)

The name reads left to right: the behavior, then the window it happens in. Your decisions ride along, which destinations, which guardrails. Author it once, approve it once. Bryn carries it from there.

Named by their parts, ready to run

Five Plays ship with the product today, each named by its trigger, window, and destinations. Every run ends in a record you can replay.

expansion

viewed docsinvited teammatecomposite ≥ 70

A known account reads the docs, opens the integrations catalog, and invites a teammate. Files an expansion task on the account.

crmcompleted · 09:41:12Z

trial-rescue

trial returnedcomposite ≥ 70

A trial goes quiet for three days, then the account comes back. Pings the owner and personalizes the landing surface toward the unfinished setup step.

chat2 runs · 7dcompleted · 10:22:08Z

seats

invited teammate ≥ 2composite ≥ 70

An active trial invites its second seat. Files the task and arms the upgrade prompt.

crm2 runs · 7dcompleted · 22:15:08Z

outbound

high intentfit ≥ 70

Outside interest and a resolved identity on your site, in the same window. Pings the owner and hands the account to your sequencer.

chat · sequence

trigger → score → output → audit entry

One worked example, end to end. Every Play breaks into the same four parts, and every run files the same kind of record.

A1 ⬩ Trigger

pricing → comparison → repeat (7d)

The named behavior, with its window. Literal parts, not a paraphrase: three pricing visits, comparison material, repeated inside seven days.

A2 ⬩ Score

Fit 100 ⬩ Intent 60 ⬩ Timing 100

Three visible axes against your ICP, who you actually sell to, composite 91. The Play sets the threshold; this one fires at 70.

A3 ⬩ Output

Slack ping, CRM task, landing personalization.

Only the channels this Play names, nothing open-ended.

A4 ⬩ Audit entry

Filed at 14:02 UTC, replayable.

What it saw, why it scored that way, what it did. The entry is the work proof and the substrate Bryn learns from.

demo-intent ⬩ pricing → comparison → repeat (7d)

Point and click, or define it in code

Explore+

The visual builder.

Compose trigger, threshold, destinations, and guardrails from the signals Bryn already catches. Every tier includes it.

Growth+

Code and YAML.

Plays as files: versioned, reviewable, diffable. The same primitives as the builder, living in your repo.

Not ready to run one yet?

Get new Plays and release notes as they ship, by email, nothing else asked.

Run your first Play this week

Five come ready, and the sixth is the pattern only you know about.