Can you build shade-specific conditional content in Klaviyo?
+
Yes. We use Klaviyo's dynamic content blocks and conditional splits to personalize email content based on purchase history — specifically what shade or SKU category the customer bought. For brands with 10+ shades, we build a shade expansion matrix in the post-purchase flow that surfaces complementary products based on the original purchase. This requires Klaviyo's catalog sync to be active, which we'll confirm in the intake form.
How do you structure UGC requests that actually get responses?
+
The timing and the ask matter. A review request sent 72 hours after delivery when the customer has barely opened the product gets ignored. We time UGC requests at 14–21 days post-delivery (product lifecycle dependent), make the ask specific ("show us your look in [product name]" not "leave a review"), and include a clear low-friction path to the review. We also build a photo submission incentive block for brands that offer a loyalty discount in exchange for UGC.
Do you write for indie beauty brands with small product lines?
+
Absolutely. A tight product line (5–15 SKUs) actually simplifies the conditional logic and means we can go deeper on individual product storytelling. Smaller lines benefit from "complete the collection" framing, founder story integration, and ingredient-first narratives. The welcome series for an indie brand with 8 SKUs is often stronger than a large brand's, because we can be specific about what makes each product worth owning.
Can the flows handle seasonal launches and limited-edition drops?
+
We build the automated flows (welcome, cart, post-purchase) which are always-on and evergreen. Seasonal launches and limited drops are typically handled by your campaign sends, not automated flows. That said, the post-purchase flow can include a "new launch alert" module that you activate during drop periods — we build that hook into the flow structure so it's easy to switch on without rebuilding the whole sequence.
What if I'm using Omnisend instead of Klaviyo?
+
All deliverables include HTML + plain-text exports that import into any major ESP including Omnisend, Mailchimp, and ActiveCampaign. The Klaviyo JSON is a bonus for Klaviyo users. Shade-specific conditional logic and catalog-based dynamic content are Klaviyo features — on Omnisend, we'll architect the same intent using Omnisend's segment-based branching. The flows work; the personalization depth is slightly shallower without Klaviyo's catalog variables.