Initial situation: B2B SaaS service for financial teams (subscription $49-299/month). Now mailings come from Mailchimp, the base is 38,000 contacts (EU/US), there are already three main events from the product, but letters are sent irregularly. Problems: drop in deliverability in Gmail/Outlook, complaints about spam, low conversion from onboarding. There is a web application on Node.js, event data in Segment, CRM - HubSpot, landing pages on Webflow. We will provide access, the domain for sending a separate subdomain has already been prepared. Task: transfer and build an e-mail marketing system to Klaviyo with an emphasis on trigger chains, segmentation and deliverability in order to stabilize inboxes and increase conversion to activation/payment. Technical environment and restrictions: sending only through a dedicated subdomain (for example, mail.example.com). You cannot use purchased databases or aggressive email subject lines. Compliance with GDPR/CCPA and double opt-in logic for the EU segment are mandatory. You cannot change texts on the site and product, only e-mail and event/audience settings. All letters should be in a corporate style, but without complex layout, preferably Klaviyo modular templates. Stages and result: 1) Audit of the current database and submissions - analysis of sources of subscriptions, activity, unsubscribes, complaints, distribution by domain, identification of risky segments and recommendations for domain warming up. 2) Setting up deliverability - SPF/DKIM/DMARC for subdomain, alignment, recommendations for BIMI if available, setting up tracking domains, checking for typical reasons for getting into Promotions/Spam, warming up plan and limiting sending speeds. 3) Integrations and events - checking Segment -> Klaviyo events (minimum: Signed Up, Trial Started, Key Feature Used, Subscription Started, Invoice Paid/Failed). Normalization of event names and properties, setting up user properties (role, tariff, country, lead source, MQL/SQL from HubSpot), testing the correctness of triggers on test profiles. 4) Building segmentation - a set of segments for communications: new registrations, trial without a key action, activated trial, paid, risk of churn (no activity for N days), high-intent (frequent logins/use), EU double opt-in, suppression lists (inactive 120/180 days, complaints/unsubscribes, hard bounce). 5) Implementation of trigger chains in Klaviyo (minimum 3): - Onboarding after registration - 5-7 letters with forks in events (if you took a key action - one way, if not - another), with personalization by role and source. - Trial nurture - 4-6 letters with an emphasis on value and activation, stopping the chain when proceeding to payment. - Dunning/payment notifications - 3-4 letters for failed payment with correct pause logic and termination upon successful payment. 6) A/B testing - at least 2 A/B tests on chains (topics/preheader, CTA or first screen), setting up metrics and interpreting the results. 7) Documentation and transmission - event map, description of segments, logic of each flow, recommendations for 30 days on warm-up/frequency and plan for further tests. Measurable acceptance criteria: - All three chains work end-to-end on test contacts, correctly enter/exit flow according to events and suppression rules. - Valid configured domain authentication for subdomain: SPF, DKIM, DMARC with alignment (provide screen/verification through public checkers). - Events from Segment are recorded in Klaviyo and used in flow conditions, at least 5 key events and 6 profile properties are available and verified. - Implemented at least 8 segments and 2 suppression audiences described in the documentation. - At least 12 letters are laid out in Klaviyo in the same style and are previewed for Gmail/Outlook/mobile without critical breakdowns. - Provided a database and deliverability audit report, as well as a warm-up plan and sending limits. Important: texts can be rewritten/improved, but without promises or risky language. Need a focus on pure analytical setup, events, segments, deliverability and managed tests.