Announcing o11's backing from Y Combinator.

AI for Klaviyo

AI that edits flows and segments inside Klaviyo.

Edit flow steps and conditional splits in place.
Build segments from store behavior and event data.

Flows/Welcome series Live · sending to 32,841 subscribers

Welcome series
Flow ID: WS-001

Live | Save Draft | Schedule

Analytics Action log

Trigger
List subscribed to
Newsletter signups
Triggered 1,847 times this month

Time delay
Wait
1 day
1,621 in delay

Send email
Welcome — get started
"Welcome to Acme — get started"
Subject: Welcome — get started
Sent 1,591 · Opened 47.2% · Clicked 18.4%

Time delay
Wait
3 days
1,420 in delay

Conditional split

opened welcome email
- YES 72% · NO 28%
  - YES
    Send
    Discount 10% off
    Sent 1,022 · Conv 14.1%
  - NO
    Send
    Helpful tips digest
    Sent 398 · Opened 31.2%

o11 for Klaviyo: an AI agent layer for ecommerce lifecycle execution

o11 is an AI execution layer that runs inside Klaviyo. The agent edits flows, builds segments, reads tests, and updates lifecycle programs — without sending a CRM manager into another tab to translate a brief into a flow node.

If you have searched for AI for Klaviyo, a Klaviyo AI agent, or an alternative to Klaviyo AI that does the work instead of suggesting copy, the difference comes down to one question: does the AI describe the next step or change the flow?

What teams use o11 for in Klaviyo

Lifecycle flow editing. Adjust welcome, browse-abandon, post-purchase, and win-back flows directly in the flow builder, including conditional splits and time delays.
Segment building. Build and refine segments from real store behavior, event data, and predictive signals, not from a static query.
A/B test analysis. Read test results in context and apply the winning variant to the live flow without exporting to a sheet.
Cross-system handoffs. Coordinate Klaviyo work with Shopify product changes, support context in Zendesk, and reporting workbooks.

Why o11 differs from Klaviyo AI

Klaviyo AI focuses on copy generation, predictive scoring, and recommendation. The actual edits — moving the flow node, switching the segment, applying the test winner — still land on a CRM manager clicking through the builder. o11 is built to drive the builder. The chat is the control surface, the flow is where the work lands.

Built for teams that live across systems

Klaviyo lives next to Shopify, a help desk, a CDP, and a stack of reporting workbooks. o11 is positioned to act across all of them. A new product launch can become a Klaviyo flow update, a Shopify segment, a Zendesk macro, and the next row of a launch tracker without the CRM manager stitching the tools together by hand.

Where Klaviyo teams typically start with o11

CRM and lifecycle managers with flow edits and segment refreshes.
Retention leads with win-back, repeat-purchase, and VIP flows.
Ecommerce founders running lifecycle themselves and needing speed.
Marketing leadership with rolling lifecycle performance reads.

How o11 respects Klaviyo permissions

The agent operates with the user’s own Klaviyo account and role. Account access, user role limits, and consent and suppression rules apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 safe to deploy on a contact list governed by consent, suppression, and channel preference.