We are not selling you another tool to bolt onto the stack. We are selling the outcome. We replace the toolset with our toolset, wire server-side tracking, ship every flow and hand you back the savings. No SaaS fee, just setup and a small monthly retainer.
Replace stack
Klaviyo, AC, HubSpot — gone.
Code backend
Server-side, identity, consent.
Run with you
Flows, training, ROI in 3–6 mo.
You are wasting
per year on an ESP you barely open
Tracking coverage
38%
Active flows
3 / 27
Consent ledger
Missing
Seat cost
$3,860
Recoverable
$40,761 / yr
Recoverable spend
ROI in 3 to 6 months
The receipt
We audit these accounts every week. The rule builder is there. The flow canvas is there. The segmentation is there. Nobody wired any of it. You are renting shelves.
Average product usage inside a $5k/mo ESP account
Automated flows the average client actually runs
Sessions tracked, without server-side pixel
Yearly spend on features never wired up
Cidipi vs the ESP world
Guided tour
Every block below is a real screen you get on day one. Nothing is a roadmap slide, nothing is behind an enterprise SKU. Scroll it like a product manual, because that is what it is.
Web forms, warehouse imports and the shop pixel land in the same profile, deduplicated on e-mail and stitched by phone and user id. Consent stays per channel, so an opt-out on SMS is never silently overwritten by a later Excel sync.
Any field, any operator, nested AND and OR. The matching count updates before you save, so a segment is never a promise, it is a number. Rebuilds run nightly and on demand, and every segment has its own SQL you can read.
Drag blocks to reorder, what you see is what lands in the inbox. Each language can detach and hold its own copy, links and UTM tags. Brand tokens keep the palette consistent, and there is no template hostage crisis if you ever leave.
Point a segment at a template, schedule per market, throttle to protect your reputation. Delivery, opens and clicks land on the same profile, not in a separate silo. Suppression happens at send time, so opt-outs and hard bounces never enter the queue.
Enter on segment, wait, branch on behavior, send e-mail or SMS, suppress at send time. A grace period holds the first step so a correction right after signup never sends twice. Exit conditions cancel the remaining steps, not queue them.
Published forms collect fields and consent, and the answers land on the same profile with a proof trail: form, timestamp, source and exact wording. Change a field or a wording without a developer, and never lose the audit line.
Ask a question in your language. Cidipi shows the read-only query it would run, and the answer from live data. Never writes, always shows the query, always answers from the same rows the segments read. Your team stops waiting on analysts for a count.
Baskets, add-to-cart, checkout and orders in one live view, with a per-minute stream underneath. The storefront pixel feeds the same record as the newsletter form, so a basket and a consent belong to one person, never two.
Warehouse sync, enrichment, segment rebuild and SMS sync run on schedule and are visible. Every action is written down: who did what, when, and what came back. CSV, JSON, CRM sync and transactional e-mail all leave the same way they came in.
AI-ready by design
Pulse and Cidipi each ship their own MCP server. Connect Claude, ChatGPT, Cursor, Codex or any MCP client and let your agent query live events, segments, consent and campaign performance, with read-only guardrails where it matters.
Live event layer for your agent
Your AI can send and query server-side events in real time. Ask for a customer's timeline, replay a stream, or check consent before a campaign idea becomes a send.
Read-only access to the customer graph
Segments, campaigns, workflows and consent are exposed as tools. Your agent reads the same live data the platform uses, so it answers from fact, not a stale spreadsheet.
{
"mcpServers": {
"cidipi-pulse": {
"command": "npx",
"args": ["-y", "@cidipi/pulse-mcp"],
"env": { "PULSE_API_KEY": "<your-key>" }
},
"cidipi-cdp": {
"command": "npx",
"args": ["-y", "@cidipi/cdp-mcp"],
"env": { "CIDIPI_API_KEY": "<your-key>" }
}
}
}Use cases
Four common shapes we see every week. If yours is not here, the 20-minute audit still applies.
Pulse captures every checkout event server-side. Segment on last-purchased category, LTV, days since order. Post-purchase, replenishment and win-back flows that fire on the right cohort.
Ingest product events through Pulse, resolve to accounts, trigger lifecycle by plan, feature adoption or workspace health. Sales sees the same timeline marketing does.
Per-topic and per-brand consent, paywall event tracking, subscription state as a first-class segment dimension. Every send is enforceable against the ledger.
Subscription state, days-to-refill, cancellation reason and reactivation window as native segment fields. Workflows branch on the same logic the analytics dashboards show.
Savings configurator
Our monthly retainer is a fixed number, materially lower than Klaviyo, and it does not scale with your contact count. Setup is scoped with you at kick-off, based on how many systems we hook, how complex your stack is and what you want live. However much you pay Klaviyo, ActiveCampaign, Mailchimp or HubSpot today, Cidipi pays itself back inside a quarter or two.
Active identified customers in your database
Campaigns and flows combined
Transactional and marketing
Multi-step lifecycle you want to run
Setup is a one-time fee agreed on the audit call. It depends on how many systems we hook and how complex your backend is.
Connect your own account. You pay the provider directly for delivery, Cidipi only orchestrates sends and workflows.
Standard stack. Final quote after the 20-minute audit.
Flat monthly retainer, no per-contact tax. Setup is a one-time fee agreed at kick-off, based on your stack. Whatever you pay today, ROI lands inside 3 to 6 months.
Signal, not testimonials
“We were paying Klaviyo more than we were paying our lead developer. Cidipi took us off the meter in three weeks. The retainer is a rounding error next to what we spent last year on features we never opened.”
“The real value was not the price cut, it was finally having server-side events into one profile. Our attribution stopped being a religion.”
“The team coded three backend hooks with our engineers and stayed on the standup until we shipped. That is not a SaaS relationship, that is a partner.”
Migration guarantee
The reason teams stay on Klaviyo is not the platform. It is the fear of a bad cutover. So we removed the fear.
FAQ
If yours is not here, put it in the intake form. Real answer inside a week, from the person who would run your setup.
Book the 20-minute auditTwenty minutes
No demo theater. We open your account, read the workflows and the consent state, and give you a real number for setup and monthly retainer before you hang up.