Klaviyo Email Developer — Build a Modular Master Template + Canva Image Workflow

# Klaviyo Email Developer — Build a Modular Master Template + Canva Image Workflow (from existing Figma design) ## About us Tafelzeilonline.com is an e-commerce company selling custom-cut tablecloths, oilcloths and table-protection products. We operate seven European webshops (NL, DE, AT, FR, IT, PL and an international EN store) and run our email marketing in Klaviyo. ## The project We have a finished email design system — created in Claude Design and now available as a Figma file — containing roughly 20 modular sections: brand hero, promo hero, editorial block, category tiles, product grid, single-product spotlight, recently viewed, inspiration block, campaign/coupon, countdown, sample request, how-to/education, standalone CTA, Trustpilot/reviews, UGC + upload, NPS/review request, USP bar and footer. We need an experienced Klaviyo developer to turn this design into a clean, reusable **master template built with NATIVE Klaviyo blocks** — not an image-only email — so our (mostly non-designer) team can quickly assemble new campaigns and flows on brand, without rebuilding anything from scratch. Important: this is a **living design system**, not a one-off. We will keep designing new sections and modules over time, and we run the same template across seven markets in different languages. So the build must be set up to grow and to localize easily — both are core requirements, not afterthoughts. ## What you'll deliver 1. A master email template in Klaviyo built with native drag-and-drop blocks: - Live, editable text for all headings, body copy and CTAs (no text baked into images where it can be avoided). - Native button, divider, spacer and row/column blocks. - Our brand colors applied: #282359 (primary deep blue), #EF8177 (salmon accent), #90ACAA / #A5BBBA (sage), #E7D6C0 / #DEBC98 (sand), backgrounds #F6F5F3 / #ECEBE8, Trustpilot green #00B67A. - Our brand font is League Spartan. We understand custom fonts don't render reliably in most email clients, so we expect a sensible web-safe fallback stack for live text, with Spartan reserved for image assets where typography matters visually. 2. The ~20 sections rebuilt as **reusable / saved blocks (Universal Content)** so any module can be dragged into a new email or flow. 3. Fully responsive and tested: mobile + desktop, dark-mode safe, and checked across major clients (Gmail, Apple Mail, Outlook). Good deliverability practice — real text, alt text, no spammy image-only layouts. 4. Built multilingual from the ground up: the **same** master template must work for all seven markets — switching market should be a quick **logo swap + language/copy swap, never a rebuild**. Each market is its own brand with its own logo (Tafelzeilonline.com NL, Wachstuchonline.de DE, Wachstuchonline.at AT, Toileciree.fr FR, Tovagliacerata.it IT, Ceratastolowa.pl PL, Oilclothonline.com EN), so the logo must be an easily replaceable element and no copy may be locked inside images where it can be avoided. Setting up one market from the master should take minutes. 5. A simple, documented **Canva image workflow**: set up reusable, on-brand Canva templates and specs (correct dimensions — 600px content width, exported at 2x — with our colors and font) so our team can quickly produce banners, hero images and tiles that drop straight into the Klaviyo image blocks. 6. A short handover (written guide + Loom video) showing how to: build a new email from the blocks, localize it for another market, and add a Canva-made image. 7. Built to grow: because this is a living design system, the template and block library must be structured so that **adding new sections/modules later is clean and low-effort** — following the same conventions you set up, consistent with the existing blocks, and without breaking emails or flows already in use. Document those conventions so we (or another developer) can extend it later. ## What we'll provide - The Figma file with the full design system. - Brand assets (logos, color codes, font). - Klaviyo access (or an agreed sandbox / template export route). - A reference list of the 20 sections. ## You should have - Proven Klaviyo template development experience — a portfolio of native, modular Klaviyo templates. - Strong responsive HTML/CSS email skills, with dark-mode and cross-client testing (Litmus / Email on Acid a plus). - Demonstrated ability to translate a Figma design into native Klaviyo blocks (not just dropping in images). - Working knowledge of Canva for setting up reusable, on-brand templates. - Clear written English. ## Nice to have - Experience with multi-market / multilingual Klaviyo setups. - Experience building reusable block / Universal Content systems in Klaviyo. - E-commerce email experience (Magento / Shopify). ## To apply, please include - 2–3 examples of native, modular Klaviyo templates you've built (links or screenshots). - 2–3 sentences on how you'd approach turning a Figma design into reusable Klaviyo blocks. - Your estimated timeline and a fixed price for the scope above. - Your answer to this screening question: *How do you handle a client's brand font in email when that font isn't web-safe?*