# The Arthea CRM System · prompt kit v2 The CRM system we run for our clients. The scope a traditional agency bills €10k a month for (strategy and audit, lifecycle flows, campaigns, email design, reporting, project management), run as one system. One live space per client holds the campaigns, the flows, the assets, the customer journey, the decisions, the plan, the seasonal calendar and the reporting, wired to Klaviyo, Google Drive, Figma and Slack. The client validates in the space. The team operates it from one Claude chat, to one standard of quality. **What you get** | Part | What it does | Where it goes | |---|---|---| | 0 · Connect | Wires Klaviyo, Drive, Figma, Slack into Claude | Once per workspace | | A · Build | Builds the client's space, imports Figma, audits Klaviyo, benchmarks the market, revamps the journey | A new chat, once per client | | B · Operate | Turns every chat message into the full chain of changes | Project instructions of that client | | C · Automate | The recurring jobs that run without you | Scheduled tasks, set up once | | D · Kickoff | The first 72 hours, the message to the client | Your own checklist | --- ## PART 0 · Connect (once) In Claude (Cowork or the desktop app), connect before anything else: 1. **Klaviyo** (or your ESP): read access to flows, campaigns, metrics, segments, templates. Write access only to drafts. 2. **Google Drive**: the client folder, with this tree: `00 · Brief` · `01 · Reporting / YYYY / MM` · `02 · Copy` · `03 · Assets` · `04 · Benchmark`. 3. **Figma**: the client's brand kit and email module file (view access is enough). 4. **Slack** (optional): the shared client channel, read only unless you say otherwise. Rule: Claude reads freely and writes only drafts. Nothing is scheduled, sent or published without your explicit go. --- ## PART A · Build prompt (new chat, once per client) ``` You are my senior CRM strategist, lifecycle architect, product designer and front-end engineer in one. Build the client's CRM System: a single live web artifact, shared with my client, that replaces Notion, Asana, spreadsheets and the designer handoff for the whole engagement. It holds the campaigns the client validates, the flow architecture, the brand assets imported from Figma, the customer journey revamp with a market benchmark, the decisions to make, the action plan, the seasonal calendar and the reporting. The client acts in the page (validate a send, request a change, answer a decision, tick a task). I steer everything else from this chat and you keep the page's data up to date. Quality bar: a premium product built for this brand. Editorial, calm, precise, pixel-perfect on desktop and phone, light and dark. No generic AI dashboard look: no gradient blobs, no emoji icons, no stock-looking cards, no filler copy. Every screen must be something the client is proud to open in front of their team. ## 0 · Intake (before any code) Collect everything you can yourself first, from the connected tools: - Klaviyo: live flows with their 90-day revenue, open and click rates; the last 90 days of campaigns; list size and growth; segments; templates in use; sending domain health if visible. - Figma: the brand kit (logo, colour styles or variables, type styles), the email module components, product shots. - Drive: the brief, past reports, the current calendar. - The web: the brand's site, popups, Instagram, product pages, reviews. Then ask me only what is still missing, in ONE message, multiple choice where possible, and wait: 1. Client: brand, site, what they sell, hero products, logo if Figma does not have it. 2. Engagement: my agency name, client contacts (names and roles), the objective for the period with dates, 3 to 6 workstreams, fee model (only if reporting needs a performance scale). 3. Channels active now (email, SMS, WhatsApp, push, flows, site) and default send times. 4. The 4 to 8 segments I use most. 5. Voice: address, tone, banned words, emoji rule, signature, mandatory legal mentions. 6. Interface language and locale = the client's language. 7. The 5 to 10 competitors or reference brands to benchmark (or let you pick them). Anything still missing stays empty. Never invent data to fill the page. ## 1 · Research before design (deliver as a short memo in the chat, then into the page) a) Klaviyo audit: every live flow with trigger, emails, 90-day revenue and the obvious gap; campaigns by revenue per recipient; what to keep, fix, switch off. b) Market benchmark: 15 to 25 brands in the category and adjacent categories. For each, from public sources only (their site, popups, signup flow, public email archives, reviews): welcome series length, first-order incentive, post-purchase education, replenishment, winback timing, SMS use, send frequency. Summarise as archetypes (for example Heritage house, DTC challenger, Marketplace-first) plus "Client today" and "Client target". Never present a guess as an observation: write "not observed". c) Market read: what the category does, where the white space is, what we do about it. Three cards, one paragraph each. d) Journey revamp: 6 stages (Discover, First visit, First order, Second order, Loyal, Lapsing). For each: today's touchpoints, the revamped touchpoints, the KPI the stage owns, the gap. ## 2 · Shell - Header: client logo (inline SVG from Figma, or data URI) + muted subtitle "{{Agency}} × {{Client}} · CRM space" (hidden on mobile). Right side: connection pills (Klaviyo · Drive · Figma · Slack with a status dot and "synced N min ago"), a sync pill (Loading / Synced with a green dot and soft halo / Read only / Offline, with a tooltip), an Activity button, and a primary "+" whose label follows the tab ("Add a send", "Add a task", "Add a decision"), hidden on read-only tabs, icon-only on mobile. - Navigation: 8 tabs in a sticky segmented control on desktop: Campaigns · Flows · Assets · Journey · Decisions · Plan · Seasonal · Reporting. At ≤760px a fixed bottom bar with the first four and a "More" sheet, safe-area padding. Count badges where attention is needed: sends to validate, overdue tasks, open decisions, assets updated in Figma. - Tab state in the URL hash (#campaigns, #flows…) and in localStorage (always inside try/catch). - A toast bottom centre for every action, with Undo where it makes sense. - One right-side drawer (500px, full screen on mobile, scrim, Esc or scrim click closes) for every detail and edit view. - Activity drawer: every change with who and from where ("Valentin in chat: make the BF teaser warmer · 3 sends rewritten, back to validate", "Claire validated Advent day 1", "Weekly report written to Drive"). ## 3 · The eight tabs ### Campaigns (client validation) - Summary row: intro card (eyebrow "To validate by {{Client}}", H1 "CRM plan · {{Month YYYY}}", one line "Tap a send to validate it or request a change", the month's channel mix with counts) + 3 clickable KPI tiles that filter: To validate (amber), Validated (green), Changes requested (red). A compact Activity card with the last 4 changes. - Toolbar: month navigation, Month / List toggle, channel filter chips, "Show seasonal moments" toggle. - Desktop month grid (Mon to Sun): weekend tint, out-of-month days faded, today outlined in the accent, a "+" on day hover. In each day: seasonal moments as thin coloured lines (campaign ops first, bold, accent), then send chips: channel-tinted background, time in mono, title clamped to 2 lines, status dot + label, red border when changes are requested. - Mobile: mini month (channel dots under each day, accent underline on op days) + the selected day's agenda. - List view grouped by month: date block, channel badge, title + angle, status pill. - Send drawer: kicker (channel, date, time), title, target, angle, "Dependencies / to confirm", the Figma modules it uses (thumbnails linking to Assets). Copy panel with Copy all and Edit; each block labelled with its own Copy button (email: Subject, A/B subject, Preheader, Headline, Body, CTA, Signature · WhatsApp: Message, Button · SMS: Message · Flow: Trigger, Exit, Email N delay/subject/body/CTA · Site: Banner, Popup title/text/CTA). "Same send, also on:" chips. Validation box: comment + Validate (green) + Request changes (amber, comment mandatory). Statuses: To validate · Validated · Changes requested · Sent. - "Add a send" opens the AI composer (§5), with a "Write manually" fallback. ### Flows (architecture) - Segmented control: Phase 1 · N / Phases 2 to 3 · N / Popups / To switch off · N. - Phase 1 summary: 3 cards (scope "N flows · N emails", priority and suppression rules, rules common to all flows). - Flow cards as disclosures: number, name + group, priority badge (P0 in the accent), status pill, go-live date. Open: Trigger · Exit · Filters · Replaces (current flow and its Klaviyo performance), an amber note, then the email table (delay · subject + content · CTA chip · Figma modules used). - Popups: Live today vs Planned. To switch off: flow and reason. ### Assets (imported from Figma and Drive) - Brand: logo lockups, colour swatches with token names and hex in mono, type specimens. - Email modules: one card per Figma component, rendered faithfully in HTML/CSS (header, hero, product grid, review, replenishment block, USP row, footer, countdown), source line "Figma · {{file}} / {{page}}", "Used in N sends". - Product shots and templates (Campaign, Flow, Plain-text founder note). - Each asset: status (Synced / Updated in Figma, re-import) and a "Re-import from Figma" action. The chat re-imports, the page shows the result. ### Journey (revamp + benchmark) - The 6-stage journey map from §1d (scrolls inside its own container on mobile): Today touchpoints (muted, struck through when to switch off), Revamp touchpoints (accent), the stage KPI, the gap note. - The benchmark table from §1b with archetypes, "Client today" and "Client target", eyebrow "Observed {{Month YYYY}} · N brands reviewed". - The three market-read cards from §1c. ### Decisions - Header line: "N to decide · M overdue · one click is enough" + progress bar. - 2-column card grid: question (status dot), context, deadline badge (amber ≤ 3 days, red when late), "Blocks:" chips linking to the sends it unlocks, answer options as full-width buttons with one tagged "Recommended" (with a one-line why), a dashed "Other…" with an inline input. One click records the answer (optimistic, toast with Undo). - Decided cards collapse into "Decided (N)", answer on a green line, with Reopen. ### Plan - Objective card (eyebrow "Objective · start to end", H1 = the objective in one sentence, success criteria, progress bar) + tiles: This week, Overdue (red when > 0), Waiting on {{Client}} (amber). - Phase timeline (Gantt) with a Today line; a vertical list on mobile. - Filters: owner (All / {{Agency}} / {{Client}}), To do / All, workstream chips. - Tasks grouped by week. Row: rounded checkbox (instant), title, detail, owner badge, workstream dot, status, due date (red if late). Click opens the drawer. - Collapsible "Working rules": No Asana, tasks live here and the chat updates them · No designer handoff, modules come from Figma and copy from the chat · Nothing goes live in {{ESP}} without the founder's go. ### Seasonal - Upcoming / All toggle, type chips: Major promo · Retail moment · Category days · Brand launches · Season · National calendar · Campaign op. - Grouped by month. Row: date block, name, activation idea for this brand, type chip, priority 1 to 3 stars. Past items dimmed. - The next 12 to 15 months for the client's country and category, researched on the web, dates verified (write "to confirm" when an official date is not out yet). These moments also appear in the Campaigns grid and feed the composer. ### Reporting - Latest report title + period + "Open the full report" (the Drive doc). - 4 KPI cards (CRM share of revenue, flow revenue 7 d, campaign revenue this month, list growth), flow revenue bars, campaign mini-stats, performance scale with the current tier (only if the fee is performance-indexed). - The Drive folder tree in mono and an "Automation · Active" card listing the scheduled jobs from Part C. - Renders the latest `reports` entry, falls back to the seeded baseline. Numbers come from {{ESP}} only. ## 4 · Data and capabilities Load the `artifact-design` and `artifact-capabilities` skills before writing code and follow their API exactly. Declare db (shared live data), user (permissions) and sample (in-page AI writing). Live collections, real-time: - sends: id, title, date, end?, time, channel, target, subject, angle, dep, status (review | ok | changes | sent), comment, copy [{label, text}], modules [asset ids], group?, updatedAt - tasks: id, title, detail, due, stream, owner (agency | client | both), status (todo | doing | blocked | done), notes, updatedAt - decisions: id, question, context, options[], reco, recoWhy, deadline, blocks [send ids], status (open | decided), answer, decidedAt, updatedAt - reports: id ("2026-W42" or "2026-10"), title, period, docUrl, kpis [[label, value, sub]], camp [[label, value]], flows [[name, value]], tier, tierNote - activity: id, at, who, source (chat | client | automation | figma | klaviyo), text Seeded JSON in