Bogdan Birtom

After repeated Klaviyo outages, the complaint was not that things break but that nobody said what was happening or whether it was being handled.

• Customers can accept failure, but not silence.
• The post connects the outage to their own work: post-purchase emails were not going out, making churn harder to predict.
• It contrasts Klaviyo’s silence with Attentive’s communication standards.

A post urging Klaviyo to communicate about outages instead of building “the next Super Agentic 9000 AI” campaign tool.

Read original

Custom Objects, which consolidates subscription and loyalty data in one tab, is treated as a real gain for segmentation.

• Klaviyo Analytics is called out as a rebrand of Advanced Analytics, with AI recommendations layered on top.
• Customer Hub is named the most exciting update, but flagged as beta and paid; the post asks whether the new capabilities will come with a fee increase.
• The same eye for detail appears in a shorter post noting that Klaviyo’s new font colours appear to match Yotpo’s dashboard.

Custom Objects is described as genuinely useful for consolidating subscription and loyalty data, while Klaviyo Analytics is described as a refresh rather than a new product.

Read original · Original 2

With order, subscription, and engagement data in one CRM, billing reminders can go only to loyal subscribers, while an anniversary package can be offered to customers whose renewal is due next week.

• Marking emails as transactional keeps renewal messages reaching people who unsubscribed from marketing.
• The post also warns against treating revenue attributed to routine billing reminders as marketing results worth boasting about.

A billing reminder sent only to loyal subscribers, and an upsell timed to a customer’s subscription anniversary.

Read original

The worked example builds a segment of customers who have opened multiple support tickets, triggers an internal Klaviyo alert when someone enters it, and sends the service team a message template that fills in the customer’s name and email so the case can be picked up quickly.

• The aim is to turn reactive support into proactive retention rather than wait for churn.
• The post suggests the same pattern for high-value purchasers, sample follow-ups, and zero-party-data properties.

An internal alert with the subject line “Customer with Multiple Support Tickets” and dynamic name and email fields, plus three more alert ideas.

Read original

Their reaction covers both sides: they say they trust ChatGPT’s product recommendations to be impartial, but a paid tie-up could erode that trust quickly.

• Rising acquisition costs make a new channel attractive, given the roughly 400 million weekly ChatGPT users cited.
• The post closes by asking readers how the change would shape ecommerce, with a joke about a checkbox for email and SMS opt-in.

A post weighing trust in ChatGPT’s recommendations against a new acquisition channel for direct-to-consumer brands.

Read original

The breakdown shows the analytical, hands-on lens they bring to product releases and their focus on how new features affect real retention workflows.

Bogdan Birtom breaks down Klaviyo's latest feature announcements, separating genuinely new capabilities from marketing refreshes.

• They walk through Custom Objects (a consolidated customer profile tab for subscriptions and loyalty data), Channel Preferences and Engagement Ranking, AI-powered SMS Automatic Conversations, an Omnichannel Campaign Builder, Customer Hub in beta, and Klaviyo Analytics (rebranded Advanced Analytics).
• They call Customer Hub the most exciting update but flag that it and Klaviyo Data Platform are paid-only, raising concern about future fee increases.

For brands planning a campaign

A vendor collaboration would work best if a campaign lets Bogdan Birtom test features and voice pricing or usability concerns. A scripted endorsement would clash with this critical breakdown style.

It is a concrete operational comparison that shows their preference for honest, workflow-level detail over inflated metrics.

Bogdan Birtom describes migrating some Recharge flows into Klaviyo and lists seven practical differences: cohesive branding across transactional and marketing emails, a unified customer view, advanced segmentation (for example, billing reminders to loyal subscribers and anniversary upsells), better deliverability by marking emails as transactional, split-testing renewal subject lines, consolidated reporting, and a caution against attributing revenue from billing reminders. They joke that influencers who boast about such attribution should be punished with Mailchimp and Attentive.

For brands planning a campaign

A subscription platform or ESP could use a migration teardown or walkthrough. A campaign should permit candid comparisons and avoid pressuring Bogdan Birtom to inflate attribution numbers.

It is a reusable recipe that connects email automation to a broader customer experience problem.

Bogdan Birtom shows how to create a segment for customers with multiple support tickets and trigger an internal alert in Klaviyo.

• They provide a real example subject line and dynamic tags, then list three other internal alerts: big-ticket purchasers, sample review follow-ups, and zero-party data triggers.
• The post turns a customer-service signal into a retention action.

For brands planning a campaign

A CS or retention tool could collaborate on a practical tutorial. The value is in the workflow and the internal alert examples, not a product feature list.

They publicly hold vendors accountable and connect product reliability directly to retention outcomes.

Bogdan Birtom criticizes Klaviyo for frequent outages and a lack of official communication, saying they are not getting post-purchase buyer's remorse emails and that churn predictability increases. They contrast the situation with Attentive's communication standards and push back on new AI features while reliability suffers.

For brands planning a campaign

A vendor considering a partnership should expect honest criticism if service issues arise. A brief that demands only positive messaging would be a poor fit.

The post shows strategic curiosity balanced with skepticism about platform trust.

Bogdan Birtom reacts to reports of Shopify-specific code hidden in ChatGPT that could let users browse, compare, and purchase products without leaving the chat.

• They raise a trust red flag if recommendations become non-impartial, but note the acquisition opportunity given ChatGPT's 400 million weekly active users.
• They ask how the collaboration might shape ecommerce.

For brands planning a campaign

A thought-leadership collaboration on AI and retention could work if it includes genuine skepticism and practical implications. Pure hype would miss Bogdan Birtom's angle.

It is a short, observant post that shows attention to product detail and depends on the visual comparison.

Bogdan Birtom asks whether Klaviyo changed font colors to match Yotpo's platform and accommodate clients who switched, calling it diabolical. The post compares dashboard screenshots, noting Yotpo on the left and Klaviyo's new colors on the right.

For brands planning a campaign

A design or brand tool could use a lightweight commentary format. Ask for the visual comparison alongside the post so marketers can assess the design detail.

They separate features that change the work from those that are mostly a rename. The coverage notes that Customer Hub and the data platform are paid and asks whether pricing will rise; a shorter post records Klaviyo's font and colour changes, which appear to mirror Yotpo's dashboard.

Numbered walkthroughs split by marketing, service, and analytics, with a plain read on which changes matter and open questions about pricing and beta status.

For brands planning a campaign

Useful for a software brand seeking a launch or feature walkthrough with a sceptical eye: what is genuinely new, what is renamed, and what costs extra, rather than an announcement read straight from the release notes.

Examples: Source 1 · Source 2

Bogdan adds three more uses for internal alerts—high-value purchasers, sample follow-ups, and zero-party-data properties—each framed as turning reactive service into proactive retention.

Step-by-step instructions with a copy-ready message template and a short list of why the approach works.

For brands planning a campaign

Strong fit for a hands-on collaboration built around something the audience can copy into their own account: a walkthrough, template pack, or teardown of an alert or flow they already run.

Examples: Source 1

They close with a jab at influencers who inflate attributed revenue from billing emails.

Numbered differences drawn from an actual migration, with a promised follow-up comparing subscription platforms.

The post recounts one practitioner's migration, not a benchmark across subscription platforms. Ask for comparative evidence if a platform-wide benchmark is important.

For brands planning a campaign

Relevant to an email service provider or subscription platform seeking a migration or comparison angle. Keep any revenue-attribution claims modest: Bogdan has publicly criticised inflated numbers in this exact area.

Examples: Source 1

They contrast the vendor's silence with a competing platform's communication standards.

For brands planning a campaign

Any collaboration needs room for this kind of critique. A format requiring unqualified endorsement conflicts with Bogdan's established pattern of naming vendors when their work is affected.

Examples: Source 1

They weigh trust in ChatGPT's product recommendations against a new acquisition channel for direct-to-consumer brands, cite roughly 400 million weekly ChatGPT users, and end with an open question about how the change would shape ecommerce.

Short opinion post that states both sides—trust risk and acquisition upside—and invites reader responses.

For brands planning a campaign

Suited to a discussion-led or thought-leadership collaboration on channel shifts. The post is commentary, not tested operational content; ask for results or measured tests if those are required.

Examples: Source 1

They summarise a Klaviyo feature livestream (custom objects, channel preferences, SMS automatic conversations, the beta Customer Hub), show how to configure an internal alert inside Klaviyo so a customer-service team reacts to at-risk accounts, move subscription billing flows into Klaviyo, and publicly complain when Klaviyo outages go uncommunicated. No paid or contractual relationship is disclosed; ask whether one exists before considering a campaign.

View example

They promise a later comparison of subscription platforms. The post does not say whether the migration was client work or their own account; ask which before assessing the case study.

View example

They weigh the acquisition opportunity against the trust problem it creates for product recommendations. No commercial relationship with Shopify is disclosed; ask whether one exists before considering a campaign.

View example

No commercial relationship is disclosed; ask whether one exists before considering a campaign.

Original disclosure

*ChatGPT only used for proofreading purposes.

View example

Aminat Hammed's post on AI-driven product discovery and the companion post on automations out-earning campaigns sit in the same territory as Bogdan Birtom's Klaviyo release and AI commerce posts: what changes for a brand's email and lifecycle programme, and what the numbers behind the change look like.

Aminat Hammed stays at the strategy and funnel level, describing how discovery and automation economics are moving, while Bogdan Birtom works inside the tool with segments, flows, alert templates and migration steps, and is willing to criticise a named vendor. Hammed's posts are arguments for a direction; Birtom's are closer to build instructions.

Read original · Original 2

Vira Sadlak's holiday-flow checklist and post on email as long-term relationship building share Bogdan Birtom's focus on flows, lifecycle timing and the difference between campaigns and automations that respond to customer behaviour.

Vira Sadlak's posts are largely pointers into Flowium's own podcast and agency content, with a focus on building relationships over the long term. Bogdan Birtom's posts stand on their own as written analysis, with technical detail about specific platforms and a habit of calling out tool vendors directly.

Read original · Original 2

Lindsey Lopez's cross-channel orchestration post, walking through an abandoned cart email followed by timed SMS and a product recommendation, covers the same ground as Bogdan Birtom's internal alert recipe and subscription flow migration: what to send, when, and why the sequence matters.

Lindsey Lopez frames the work around email and SMS working together across channels, with client outcomes and agency positioning. Bogdan Birtom concentrates on Klaviyo platform mechanics, transactional versus marketing email, and vendor behaviour, and is more likely to question the measurement behind a result than to report one.

Read original · Original 2

Hammed's posts address Shopify and DTC brands directly and open with the funnel moving "before the customer even reaches your website," citing 203% year-over-year growth in GenAI referrals to retail ecommerce and 51% of U.S. consumers using an AI shopping tool in the past month.

• A second post breaks down Omnisend's 2026 report finding that automations were 2% of email sends but 30% of email-driven revenue, then draws four practitioner conclusions and tells brands to ask "what customer behavior are we not responding to yet?" instead of "what email should we send this week?"
• A vendor whose product is about automating responses to behavior gets a clearer strategic frame here than in a feature walkthrough.

The format is conceptual and trend-led, with no step-by-step build instructions, copy-ready templates, or named tool configurations.

• The only named source is an industry report, not a tested product setup.
• If implementation detail or a critical read of a specific platform release matters to the brief, ask for that layer separately.

Examples: Source 1 · Source 2

Both posts are tied to Flowium's podcast, one co-hosted with Andriy.

• They cover reviewing every discount-code flow before the holiday rush, keeping campaigns and flows consistent, using Klaviyo universal content blocks, price-drop and back-in-stock flows, and post-BFCM retention promos, with claimed real brand stories and examples listeners can apply.
• A vendor selling holiday-readiness or flow-building capability could fit a bundled content-plus-audio format here.

The content is agency-framed and off-platform: the posts summarise podcast episodes and point to an external player, so Flowium's service offering may shape any vendor involvement rather than an independent product walkthrough.

• The posts do not assess a platform's failures or pricing.
• If credibility through honest critique is essential, ask for that assessment before choosing this route.

Examples: Source 1 · Source 2

Lindsey Lopez describes a three-part educational sequence built for a DTC client that "drove significant revenue growth" while generating reviews, then lays out a worked sequence: an abandoned-cart email at 11:00am, an SMS follow-up after two hours if unopened, then a dynamic product recommendation at 5pm if opened without purchase. The posts argue that cross-channel orchestration raises revenue without sending more messages, that brands "don't need fancy AI or expensive tools," and speak directly to seven-figure brands still batching email and SMS.

The client outcomes are asserted rather than shown: the posts give no figures for revenue growth or review volume, and the positioning leans toward consultancy and agency services for established DTC brands.

• There is no platform-specific feature breakdown, copy-ready configuration template, or public criticism of a tool.
• If a neutral, tested product review with room for critique matters, ask for evidence and a platform assessment; otherwise, this route offers less than Bogdan Birtom.

Examples: Source 1 · Source 2