Keep the team informed without turning analysts into a status desk
Scheduled, configurable experiment digests — delivered to any webhook-enabled channel. The whole team sees what's running, what finished, and what's next. Without anyone writing it manually.
The same questions, every week
Every experimentation analyst knows this pattern. Developers, designers, and PMs ping the chat. Not because they're curious — because there's no other way to find out. The analyst becomes a human status API, manually collecting updates and posting them on request.
This is a solved problem. The information already exists in the experiment workspace. It just needs to be published automatically.
There's a second effect, less obvious but more important: when the whole team sees experiments running, finishing, and producing results on a regular basis — experimentation stops feeling like a specialist activity. It becomes visible infrastructure. That's how a testing culture actually forms.
Weekly experiment status digest.
🔬 Ready for analysis
1. New product recommendations engine (05.07 → 19.07)
2. Checkout button colour test (08.07 → 22.07)
🚀 Running this week
1. Gamification badges on product cards (14.07 → 28.07)
2. Free shipping banner above cart threshold (17.07 → 04.08)
🧪 In development, launching next week
1. Guest checkout flow simplification (28.07 → 11.08)
What a digest looks like in the channel
One example of how a team configured their digest: three sections, every Monday at 09:00. Your setup might look completely different — more sections, different filters, different schedule. The template editor is a constructor, not a template.
- Each section has a custom title and its own filter — status, dates, any combination
- Show dates, hide them, add a link to the experiment — each section is configured independently
- Nobody wrote this. Nobody will need to write next week's either.
Built in three steps
One digest template covers any recurring report your team needs.
General settings
Name the digest, set the channel, add an intro.
Schedule
Pick day, time, and timezone for delivery.
Sections
Each section is a filtered list with its own title.
What teams configure it for
Weekly experiment status
A Monday morning summary of what's running, what finished, and what's coming — posted to the team channel before standup.
Ready for analysis
A daily or twice-weekly list of experiments that have finished collecting data and are waiting to be analysed.
Upcoming launches
Experiments planned to start in the next 7 days — so developers and QA know what's coming without asking.
Ending soon
Experiments finishing in the next 2–3 days — so the team is ready to act on results without delay.
Works with any webhook-enabled channel
Not a Slack-only integration. If your tool accepts an incoming webhook, AB-Labz can post to it.
Just a URL
Paste the webhook URL — no bot installation, no OAuth flow, no app approval required.
Multiple channels
Create separate digest templates for different channels — one for analysts, one for leadership, one for developers.
No data leaves AB-Labz
Only the formatted digest text is sent to the webhook. Raw experiment data stays inside the platform.
Available on Corporate plans
Start on Solo, upgrade to Corporate when your team is ready to connect the channel.