Paudelmar Creative House · CRM Implementation
YAKSOK
Where skincare becomes a kept promise.
The Klaviyo engine,
built in two weeks.
The scope, the schedule, the reviews and the handoff for the CRM and email lifecycle build — so the work is clear, the dates are fixed, and nothing is left to assumption.
Prepared for
Luke · CRM & Email
Prepared by
Paudelmar Creative House
Built on
The Yaksok Klaviyo CRM strategy
Window
15 → 29 June 2026
Klaviyo CRM Implementation · For LukeThe mandate · ii
ii — The mandate
One engine, one voice.

Yaksok is editorial, considered, silent luxury — The Gentlewoman and Cereal as register references. The customer is the 30–55 European woman buying evidence of an identity she already holds. The CRM speaks to recognition, never transformation.

The scope is the CRM and email engine: the Klaviyo flow architecture, broadcasts, segmentation, and lifecycle. It is a focused, self-contained build sitting on top of the existing Yaksok strategy — translating it into a live retention system. The four workstreams below define exactly what is in scope.

Flows
Flow architecture
Four foundational automated flows, built, tested and live in Klaviyo.
Broadcasts
Campaign cadence
Broadcast structure, sending cadence and a first reusable template.
Data
Segmentation
Core segments defined and built against list and behavioural data.
Lifecycle
Retention logic
The lifecycle map that governs who receives what, and when.
Out of scope
Ongoing campaign visuals are handed to Polina after the build. Paid media, site/UX work and content production sit outside this scope. The clean Shopify ↔ Klaviyo integration is a prerequisite confirmed in week one, not a deliverable.
The mandateii
Klaviyo CRM Implementation · For LukeThe engine · 01
01 — The engine
Four flows that do the quiet work.

Every flow earns its place by greeting, recovering, deepening or returning. All copy is written in the Yaksok register and tested with internal accounts before it goes live.

01
Welcome series
The first promise. Introduces the brand, the ritual and the formulation philosophy to new subscribers — recognition over hard sell, with a considered first-purchase invitation.
02
Abandoned cart
The gentle return. Recovers intent without pressure — reminding, not chasing — reinforcing why the product was chosen rather than discounting it away.
03
Post-purchase
The kept word. Confirms, reassures and educates after the order — usage ritual, what to expect, and the beginning of a relationship beyond the transaction.
04
Winback
The return invitation. Re-engages lapsed customers with restraint and relevance — timed to lifecycle, not to the calendar.

Each flow is built with branching logic where the data supports it, tested end-to-end on internal test profiles, and reviewed against the brand voice reference before activation.

The four flows01
Klaviyo CRM Implementation · For LukeThe engine · 02
02 — The engine
The layer around the flows.

Flows run automatically; broadcasts, segments and lifecycle logic are what make them precise. Three sub-systems, each handed off in a state the brand can operate without supervision.

BroadcastsCampaign cadence
A defined sending cadence and a reusable broadcast template structure in the Yaksok voice. The first broadcast is built and scheduled, so there is a working example to send from and to model future campaigns on.
DataSegmentation
Core segments built against list health and behaviour — engaged, lapsed, new, high-value and purchase-stage audiences — so every flow and broadcast reaches the right person rather than the whole list. Built on a clean, validated Shopify integration.
LifecycleRetention logic
The lifecycle map that ties it together: which message a customer receives at each stage, how flows and broadcasts avoid colliding, and the suppression rules that keep the program considered rather than noisy. Documented in the handoff so it survives past the build.
Broadcasts, segments & lifecycle02
Klaviyo CRM Implementation · For LukeDelivery · 03
03 — Delivery
Two weeks to build. One to settle.

The build runs two weeks from Monday 15 June, with a review at the end of week one. First delivery — everything live — lands Monday 29 June, followed by a dedicated Q&A week to answer questions and steady the system.

1
Week 1 · Mon 15 → Fri 19 June
Audit & flow architecture
Kickoff and account audit: existing flows, list health, deliverability and segments. Confirm the Shopify ↔ Klaviyo integration is clean. Begin building the four foundational flows with copy in the brand voice. Week closes with the first review.
KickoffAccount auditIntegration checkFlow build begins
Deliverable: Klaviyo audit memo + flows in progress
✓
Review · Friday 19 June
Week-one review
A working review of the audit findings and flow progress with Paula. Confirms the integration is sound, the flow logic is right, and the voice is landing — so week two is build, not rework.
Audit sign-offFlow directionVoice check
2
Week 2 · Mon 22 → Fri 26 June
Build, broadcasts & segmentation
Complete and test all four flows. Implement the segmentation strategy. Define broadcast cadence and template structure, and build the first broadcast. Final QA with Paula across the full system ahead of go-live.
Flows testedSegments builtBroadcast templateFinal QA
Deliverable: full system built & QA'd
★
First delivery · Monday 29 June
Everything live
All four flows live. Segmentation in place. First broadcast scheduled. Email templates handed to Polina for ongoing visuals, and a handoff document delivered for ongoing operation.
Flows liveFirst broadcast scheduledHandoff docPolina handoff
Deliverable: live CRM engine + handoff
Q
Q&A week · Mon 29 June → Fri 3 July
Questions & settling
A dedicated week to answer questions, monitor the first live sends, fix anything that surfaces in the real world, and make sure Paula, Polina and Ani are confident operating the system. The week the engine proves itself.
Live monitoringQ&A supportEarly fixesConfidence check
The schedule03
Klaviyo CRM Implementation · For LukeDelivery · 04
04 — Delivery
Checkpoints, and what unlocks them.

Three fixed checkpoints keep the build aligned. Everything Luke needs to start should be in place by the end of day one.

Friday 19 June
Week-one review
Audit findings and flow progress reviewed with Paula. The gate between audit and full build.
Monday 29 June
First delivery
Full system live and handed off. The headline milestone — the deliverable date the schedule is built around.
Mon 29 Jun → Fri 3 Jul
Q&A week
Open support, live monitoring and any early fixes. Closes the engagement with the system steady.

From Paudelmar — day one

  • Paudelmar email: luke@paudelmar.com
  • Slack invite: paudelmar.slack.com
  • Google Drive — Yaksok project folder
  • The CRM Brief (authoritative scope) + brand voice reference

From Yaksok — requested via Ani

  • Klaviyo admin / full editor access
  • Shopify permissions for the Klaviyo integration
  • Yaksok Drive folders with brand assets
  • Current customer list export, if needed for segmentation

If anything is missing or blocking, flag it in Slack and tag Paula. We don't wait.

Reviews & access04
Klaviyo CRM Implementation · For LukeResources · 05
05 — Resources
Everything, in one place.

The source material for the build — the brand book that sets the voice, the flows deck, and the welcome-flow assets. All attached here; nothing to go hunting for.

PDF
Yaksok Brand Book
The complete brand foundation — identity, voice and visual system. The reference every line of copy answers to.
PDF · 3 MB · 30 pages
Download View
PPTX
Klaviyo Flows Deck
The Canva-ready flows deck — the email architecture and copy that the four foundational flows are built from.
PPTX · 5 MB
Download
ZIP
Welcome Flow Assets
The welcome-series build files — ready to drop into Klaviyo as the first flow goes live.
ZIP · 210 KB
Download
A note on the brand book: the attached copy is optimised for screen viewing (compressed from the 39 MB master so this single file stays light enough to email). For print-resolution assets, use the master in the Yaksok Drive.
Files & attachments05
Closing · iii
Yaksok is the Korean word
for promise.
In two weeks, the brand's relationship with every customer it has — and every one it's about to win — becomes a system that keeps that word automatically. Built once, in voice, and handed over to run.
Paudelmar × Yaksok · CRM Implementation · June 2026
i / 8