Job ticket 777488 · smb · signals desk · no subscription
Contact 251 is where the meter starts. The words were never metered.
Klaviyo's Free plan holds 250 profiles and 500 emails a month, email support expiring on day 60; real segmentation and A/B testing start at an estimated US$20 a month and climb with your list. This job ticket hands the pre-send work — which the platform hosts but does not do — to prompts you own: paste the offer and the desk drafts control plus one-disciplined-variant; paste the campaign and the frame wires the single testable question with a pre-committed decision rule, or refuses a test too small to resolve.
Klaviyo is a trademark of its owner. This is an independent, unaffiliated comparison built on Klaviyo's own published pricing material, linked below and re-read every thirty days.
Paste the offer, press pull the lever, and two columns rise side by side — control and variant, one dimension apart, every figure traced to your paste. — rendered in this browser
Sample data is illustrative, not a claim about Klaviyo. Every Klaviyo figure on this page comes from the linked pricing page, read 2026-09-27.
The prompt pack
Two prompts, each mapped one-to-one onto a Klaviyo feature you are currently rationed on. Run them from this page with a free key, or copy them into any free chat model — the text is identical either way, and it is printed in full at the bottom of this section so it survives this site.
Loading the pack from tools.json… If this fails, the full prompt text is still readable below.
One-time unlocks only, never a subscription. If a price ever appears here it was read from Stripe in that request, not typed by hand. An unlock is client-side gating, not secure payment verification: it is stored in this browser and cannot prove payment to anyone else.
What Klaviyo's own pricing page says
Read from klaviyo.com/pricing on 2026-09-27. Fields we could not read are marked unconfirmed rather than filled in with a plausible number.
| The job | Klaviyo Free | This page | This page + a free-tier model |
|---|---|---|---|
| Profiles / monthly sends | 250 / 500 | Not a product — send on rails you own | undefined |
| Campaign copy | You write it inside the editor | Two drafted columns traced to your offer, US$0 | undefined |
| A/B testing | Gated feature from est. US$20/mo | The test framed as a document — variable, metric, rule | undefined |
| Segmentation · flows · analytics | The paid platform | Not displaced — honestly out of scope here | undefined |
What this replaces, and what it does not
A displacement claim you cannot substantiate is a lie with good typography. This is the whole scope, including the parts where Klaviyo wins.
A drafted campaign pair
Control and single-dimension variant with traced claims and figures
A wired test frame
One variable, one metric, pre-committed decision rule — or refusal with arithmetic
Documents you keep
Markdown downloads ready for any sender
No contact storage
Lists live in your sender; nothing is uploaded here
No sending
The desk produces copy, not broadcasts
No deliverability or automation
Flows, warm-up and bounce handling stay with the platform you pay or self-run
The prompts, in full, as text
Copy these into any model. They are the product; the page around them is convenience. Each block is the exact system prompt the interactive runner sends, plus the user-message template.
Prompt 01 — 1. Pull the campaign lever · klaviyo-campaign-lever v1.0.0 · best ally: Google Gemini API — Free usage tier · gemini-2.5-flash
Replaces: The campaign copy the platform hosts but does not write: your pasted offer turned into one send-ready email — subject, preview, body, single CTA — plus one disciplined variant.
Why this model: Marketing copy with a stated offer, audience and one CTA is constrained composition with hard line budgets; a free Flash at mid temperature stays concrete and inside the brand notes you paste. Fallback ally: OpenRouter — :free model variants.
System prompt (1320 chars):
You work the signals desk: the reader pastes their offer, their audience and one action they want. You pull one email — subject, preview line, body under 120 words, single CTA — plus exactly one VARIANT that changes the stated dimension only (angle, not facts). Every claim traces to the pasted offer; prices and deadlines travel verbatim.
Return ONLY one JSON object. No markdown fences, no commentary, no preamble.
{
"kicker": string (max 8 words),
"title": string (the table's caption, max 8 words),
"columns": [ { "label": "Slot" }, { "label": "Control" }, { "label": "Variant" } ],
"rows": [ [ value, value, value — one array per row, same order as the columns, every cell a short string ] ],
"notes": [ string (one short footnote each) ]
}
Hard rules:
1. Rows: Subject / Preview / Opening / Body / CTA line — five rows, both columns filled.
2. The VARIANT changes only the named dimension (benefit-led vs urgency-led) and the change is stated in the header.
3. Body stays under 120 words per column; CTA is one imperative sentence, identical link placeholder in both.
4. No fabricated scarcity, no invented reviews, no unquoted statistics.
5. Opening line addresses the pasted audience's situation, never 'Dear valued customer'.
6. Write in the brand voice the reader pasted, or clean-neutral if none.
User message template:
Variables:
{{offer}}— Your offer details (max 600 chars) sample data shipped with the tool{{audience}}— Audience + desired action (max 300 chars) sample data shipped with the tool
Output schema (the answer must match this exactly):
Decoding: temperature 0.6 · max 1600 output tokens · responseMimeType application/json · budget ~500 in / ~900 out · cost per run: 1 request against Gemini's free daily messages; the relay floor needs no key at all.
Prompt 02 — 2. Wire the test frame · klaviyo-test-frame v1.0.0 · best ally: OpenRouter — :free model variants · qwen/qwen3-32b
Replaces: The A/B discipline the meter guards: your pasted campaign read for its single testable question — hypothesis, metric, decision rule — so the send settles something.
Why this model: Test design is methodological reasoning with crisp artifact requirements (one variable, one metric, a pre-committed rule); a free 32B at low temperature frames clean tests and refuses mushy multi-variable ones. Fallback ally: Google Gemini API — Free usage tier.
System prompt (1340 chars):
You wire the signals frame: the reader pastes a campaign email (or two variants) and their list size. You wire one honest A/B test — the single variable, the hypothesis in one sentence, the metric, the sample split, and the pre-committed decision rule. Tests that cannot resolve get refused with the reason.
Return ONLY one JSON object. No markdown fences, no commentary, no preamble.
{
"kicker": string (max 8 words),
"title": string (the table's caption, max 8 words),
"columns": [ { "label": "Element" }, { "label": "Setting" }, { "label": "Why" } ],
"rows": [ [ value, value, value — one array per row, same order as the columns, every cell a short string ] ],
"notes": [ string (one short footnote each) ]
}
Hard rules:
1. Rows: Variable / Hypothesis / Metric / Split / Decision rule / Refusal (if any).
2. Exactly one variable for the test; other differences between variants are named as contamination in a WARNING row.
3. Hypothesis predicts direction and mechanism in one sentence.
4. Metric is one number with its window (open rate within 72h, click-through on the CTA).
5. Decision rule commits before send: margins and what 'inconclusive' means, sized honestly to the pasted list size.
6. Lists under roughly 1,000 get a REFUSAL on small effects with the arithmetic shown, plus the larger effect that could resolve.
User message template:
Variables:
{{campaign}}— Pasted campaign/variants (max 2500 chars) sample data shipped with the tool{{list}}— List size + send cadence (max 160 chars) sample data shipped with the tool
Output schema (the answer must match this exactly):
Decoding: temperature 0.2 · max 1400 output tokens · responseMimeType application/json · budget ~900 in / ~700 out · cost per run: 1 request against the free OpenRouter daily pool; the relay floor needs no key at all.
Questions worth asking before you cancel
If you don't send, what's the point?
The point is that the two things Klaviyo does not do for you at any tier — writing the campaign and designing a resolvable test — are the two things that determine whether the send works. The rails are commodity; the levers are the craft.
Why would a test frame ever refuse to test?
Because a 900-person list cannot resolve a 2-point open-rate lift, and pretending otherwise trains teams to read noise as signal. The frame prints the refusal arithmetic and the effect size that could resolve — then you choose the bolder variant honestly.
Are Klaviyo's prices really 'estimates'?
That is the pricing page's own word: 'Estimated price per month' at the slider's default, read 2026-09-27. The artifact records US$20 on the Email plan, the US$1 first-month promo, and the US$59–78 spread the shared-marketing view printed.
Where does my offer text go?
Into one request to your free ally and nowhere else — no lists uploaded, no sends fired, nothing stored. Levers download as Markdown; the desk forgets the offer when the tab closes.
Send this to someone still paying for it
Nothing is loaded from X or LinkedIn until you click, and no share is counted, logged or reported back to us — the buttons are plain links to each network's own share page.