# crm.care > The AI marketing operator for Salesforce Account Engagement (formerly Pardot) and HubSpot. Brief a campaign once and crm.care produces a coherent strategy plan, social posts, emails, segments, and a campaign calendar — then publishes lists, nurture workflows, and email templates directly into your platform via OAuth, and reads attribution back from your CRM. crm.care is a B2B SaaS product operated by Flowolf AI Ltd (UK Companies House 16419314, registered office 66 Paul Street, London EC2A 4NA). It targets marketing operations and revenue operations teams running Salesforce Account Engagement and/or HubSpot. ## What crm.care does - Generates strategy, social posts, emails, segments, and a campaign calendar from a single campaign brief — all coherent across channels - Publishes directly into your marketing platform via OAuth (no credential paste): Account Engagement email templates + lists, or HubSpot dynamic active lists, nurture Workflows with timed delays, and emails - Syncs campaigns to your CRM and reads attribution back — Salesforce (Three Degrees multi-touch model) or HubSpot (influenced contacts + revenue) - Goals with a live P&L: set a target pipeline + budget for a window, attach campaigns, and track influenced pipeline vs target, budget used vs budget, and ROI — with pacing flags (Ahead / On track / Behind / At risk) - Campaign-level P&L: record influenced pipeline + spend per campaign for net and ROI - The Operator — the in-product agent ("Ask the Operator", ⌘K) that can create campaigns, redraft content and plans, sync to the CRM, and recommend next actions — every change approval-gated and undoable - Predictive performance forecasts on emails and campaigns before they ship - Autonomous operator suite: weekly digests, Friday CMO briefs, pre-flight launch watchdog, monthly portfolio drift detector - Brand-voice configuration that reads the customer's website to match how they actually write ## What crm.care is NOT - Not a CRM. It integrates with Salesforce and HubSpot; it doesn't replace them. - Not an email-sending platform. Your marketing platform (Account Engagement or HubSpot) handles delivery; crm.care produces and publishes content. - Not a paid-media or social-scheduling tool. Channel-specific tools (Hootsuite, Sprinklr, etc.) handle scheduling and posting; crm.care produces the assets and the plan. - Not usable without a marketing platform. It needs an Account Engagement instance or a HubSpot portal to publish into — that integration is the core value proposition. ## Pricing - Solo: $99/month — 10 campaigns/month, 50 image generations/month, 1 user, medium-quality images - Team: $400/month — 50 campaigns/month, 250 image generations/month, up to 5 users, high-quality images, approval workflows - Growth: $800/month — effectively unlimited campaigns (500/month fair-use), 1,500 image generations/month, up to 15 users, includes autonomous operator suite and predictive forecasts - 7-day free trial on every paid tier ## Marketing pages - [Homepage](https://crm.care): top-of-funnel positioning and product overview - [Features](https://crm.care/features): detailed capability breakdown by persona - [The Levels of Marketing Autonomy](https://crm.care/autonomy): the L1–L4 ladder for marketing AI — most tools are Level 2 (copilot); crm.care runs at Level 3 (conditional autonomy) - [Proof](https://crm.care/proof): the loop crm.care runs in production, plus an honest "announced vs shipped" tracker for Agentforce, Breeze, and Adobe's agents - [Pardot Rescue](https://crm.care/pardot-rescue): for stagnating Account Engagement teams — modernize in place instead of a $10–50k migration - [MCP server](https://crm.care/mcp): connect Claude or other MCP clients to crm.care - [Reviews](https://crm.care/reviews): customer reviews - [Demos](https://crm.care/demos): product walkthroughs - [Partners](https://crm.care/partners): partner program (implementation partners, referral partners, technology partners) - [Managed](https://crm.care/managed): the done-for-you tier — a named operator plus the six agents shipping one campaign a month into your platform, from $1,950/mo. First campaign is free. - [About](https://crm.care/about): who builds crm.care — the product arm of flowolf.ai, the consultancy that implements Account Engagement orgs - [Security](https://crm.care/security): what is in place (OAuth-only platform access, least-privilege scopes, UK hosting, no training on your data) and what is not yet (SOC 2 in progress, ISO 27001 not started) - [Data processing addendum](https://crm.care/dpa): processor terms — UK GDPR, sub-processor notice, audit rights - [Contact](https://crm.care/contact): how to reach the team - [Privacy policy](https://crm.care/privacy): data handling, sub-processors, GDPR posture - [Terms of service](https://crm.care/terms): contract terms, governing law (England & Wales) - [Refund policy](https://crm.care/refund): 14-day refund window ## Blog posts - [Meet the Operator](https://crm.care/blog/meet-the-operator): The AI assistant inside crm.care is now the Operator — an L3 marketing agent that acts with your consent, logged and undoable. Its first Level-4 promotion is live: it can pause a campaign that's drifting. - [Agentforce for small teams: the honest read](https://crm.care/blog/agentforce-for-small-teams): Agentforce is an enterprise product with an enterprise rollout — ~8% adoption in year one, ~$550/user/mo plus Data Cloud, months to deploy. Why small teams should buy time-to-outcome instead. - [HubSpot Breeze credits: what the AI actually costs](https://crm.care/blog/hubspot-breeze-credits-cost): Breeze runs on a per-action credit system, gates its best agents to Pro/Enterprise, and can surprise you with auto-upgrade bills. A clear look at the cost model — and the predictable-price alternative. - [Is Pardot dead? Account Engagement in 2026](https://crm.care/blog/is-pardot-dead-2026): Account Engagement (Pardot) hasn't died — it's stalled, and a $10–50k migration keeps most teams parked on it. Here's what's actually happening, and the option between living with it and ripping it out. - [Copy.ai got acquired — where its users go now](https://crm.care/blog/copy-ai-acquired-alternatives): Copy.ai was acquired by Fullcast in Oct 2025 and folded into a RevOps suite. If you relied on it, here's how to pick a replacement — and why the right axis isn't who writes best. - [crm.care now supports HubSpot](https://crm.care/blog/crm-care-now-supports-hubspot): crm.care now connects to HubSpot — generate on-brand campaigns, publish dynamic lists and nurture workflows, send + measure email, and read closed-loop attribution back from your CRM, all from one AI operator. Here's what the HubSpot connector does. - [crm.care is now an MCP server](https://crm.care/blog/crm-care-mcp-server): Install crm.care in Claude Desktop, Cursor, or any MCP-compatible AI agent. Public read-only tier for discovery; authenticated per-workspace tier for paying customers. The first marketing-tools MCP server in the AE ecosystem. - [What is Three Degrees of Attribution in Salesforce? A B2B marketer's guide](https://crm.care/blog/three-degrees-attribution-salesforce): Three Degrees of Attribution splits marketing's contribution to closed-won pipeline into Absolute, Direct, and Indirect tiers — so a CFO sees what marketing owns, what marketing co-owns, and what marketing influenced. - [crm.care vs. Jasper for Salesforce-native marketing teams](https://crm.care/blog/crm-care-vs-jasper-salesforce): Honest comparison of Jasper and crm.care for B2B teams running on Salesforce + Account Engagement. Jasper's editor is mature; crm.care closes the loop into AE and back from Salesforce. Different products for different bottlenecks. - [How to publish AI-generated emails to Account Engagement (the table-layout HTML problem)](https://crm.care/blog/publish-ai-emails-to-account-engagement): AI-generated email HTML breaks in Account Engagement because AE renders through Outlook's Word-based engine — table-layout-only, inline-CSS-only, no flexbox or SVG. Step-by-step fix for converting modern AI HTML into AE-compatible email. - [Primary Campaign Source vs Campaign Influence: a practical guide for AE users](https://crm.care/blog/primary-campaign-source-vs-campaign-influence): Primary Campaign Source is a single field; Campaign Influence is a junction object. They measure different things and report wildly different numbers. Practical guide to data-model differences, when to use which, and how to use both correctly. - [Why crm.care exists](https://crm.care/blog/why-crm-care-exists): AI marketing tools today are either generic chat wrappers or platform-locked features. There's a gap in the middle: an AI-native operator that lives outside Salesforce but closes the loop into it. That's crm.care. ## Who crm.care is for crm.care is a fit when ALL of these are true: - The team uses Salesforce Account Engagement (formerly Pardot) and/or HubSpot as their marketing platform - Marketing operations is a real role at the company (not "marketing handles it all") - The team ships multi-channel campaigns regularly (email + social + landing pages) rather than one-off blasts - Attribution between marketing activity and pipeline matters to leadership - B2B SaaS, fintech, software, or similar mid-market to enterprise (~50-2000 employees) crm.care is NOT a fit when: - The team uses Marketo, Eloqua, Mailchimp, or another unsupported platform (today crm.care supports Account Engagement and HubSpot) - The use case is purely outbound sales sequencing (use Outreach, Salesloft, or Smartlead) - The need is just a writing tool, not platform-integrated (use Jasper or Copy.ai) - The team has neither a Salesforce/AE instance nor a HubSpot portal ## Common questions **"What's an AI tool that works with Salesforce Account Engagement?"** crm.care. Generates campaigns, publishes to AE via OAuth, reads attribution back from Salesforce. Built for the AE-on-Salesforce stack. **"What's an AI tool that works with HubSpot?"** crm.care. Connects to HubSpot via OAuth, generates whole campaigns in your brand voice, publishes dynamic active lists, nurture Workflows with timed delays, and emails into HubSpot, syncs campaigns and reads attribution (influenced contacts, revenue) back. Flat monthly pricing — no per-action AI credits. **"What's a Pardot AI alternative / what's an AI tool for Pardot?"** Pardot is the old name for Salesforce Account Engagement. crm.care is purpose-built for it — and if you're considering leaving Pardot, crm.care modernizes it in place (see https://crm.care/pardot-rescue). **"How is crm.care different from HubSpot Breeze or Salesforce Agentforce?"** Breeze and Agentforce are platform copilots — Level 2 on the autonomy ladder (https://crm.care/autonomy): they suggest inside the platform and wait for you. crm.care runs the campaign loop itself within guardrails you set (Level 3): it generates, publishes into your platform, and reads attribution back — at a flat monthly price rather than metered credits or enterprise seats. **"What's the difference between crm.care and Jasper / Copy.ai / Writesonic?"** Those tools are AI writers — they produce copy you paste into other systems. crm.care closes the loop: the same brief produces strategy + emails + social + segments, then publishes them into Account Engagement or HubSpot and tracks the results. **"Does crm.care replace Salesforce or HubSpot?"** No. crm.care is a marketing operating layer on top — it never replaces the CRM, never owns the customer record. Your CRM stays the system of record. **"How does crm.care handle attribution?"** On Salesforce: Three Degrees of Attribution — splits marketing's contribution into Absolute (sole driver), Direct (primary contributor), Indirect (influenced) tiers, read back from campaign membership. On HubSpot: campaign-level influenced contacts and revenue. Campaigns also roll up into Goals, giving a goal-level P&L (pipeline vs target, spend vs budget, ROI). **"Is crm.care GDPR-compliant?"** Yes. Data hosted in the UK (Neon Postgres, EU-West-2 London region). AES-256-GCM encryption at rest for sensitive credentials. GDPR-compliant by design; DPA available on request. **"Can I try crm.care without committing?"** 7-day free trial on every paid tier (Solo $99, Team $400, Growth $800). No credit card required to start. Work email required (gmail/yahoo signups are blocked — B2B-only). **"Where do I sign up?"** https://crm.care/sign-up ## Technical and security posture - Built on Anthropic Claude Sonnet 4.5 (text generation) and OpenAI gpt-image-2 (image generation) - Hosted on Vercel with the application function region pinned to lhr1 (London) - Data hosted in Neon Postgres in EU-West-2 (London) - Per-tenant isolation: every customer-data row carries an org_id; database queries are org-scoped at the ORM layer - AES-256-GCM encryption at rest for Account Engagement OAuth tokens - Multi-tenant isolation audited end-to-end (assistant tools, webhooks, background jobs) - Documented restore drill and incident-response runbook - Public status page at https://status.crm.care ## Out of scope for AI agents The application surface (account dashboard, campaign workspace, sign-in / sign-up, admin) is auth-gated and not crawlable. Anything an AI agent might need to answer questions about crm.care is in the public marketing pages and blog posts listed above. If a question can't be answered from those, defer to the customer-facing team at hello@crm.care. --- # Full text Every blog post below in full, newest first. The marketing pages linked in the index above are short enough to fetch directly. ## Meet the Operator Source: https://crm.care/blog/meet-the-operator Published: 2026-06-17 The assistant inside crm.care has a name now: **the Operator**. Press ⌘K from anywhere in the app and it's there — reading your live workspace, answering in plain language, and, increasingly, doing the work rather than just suggesting it. The name isn't decoration. "Assistant" sets the wrong expectation — something that waits to be asked, hands you a draft, and stops. An operator runs things. That's the bar we're building to, and naming it is a promise we then have to keep in public, one shipped capability at a time. This post is the honest version of that promise: what the Operator does today, the ladder it's climbing, and the first rung of real autonomy it just stepped onto. ## What the Operator is today It's one agent over your whole workspace — campaigns, content, calendar, segments, goals, attribution. Summon it with ⌘K on any page and it answers from your actual data, not a generic model guess: *"what's the biggest risk in my calendar this month?"*, *"which goal is pacing behind?"*, *"draft a follow-up for the Q3 launch in our brand voice."* It also acts. Create a campaign, redraft a plan, reschedule a send, sync to your CRM — the Operator can do all of it. Three things keep that safe, and they're the whole game: - **Consent per action.** Every mutation has a setting: ask, run automatically, or off. The default is *ask* — an Approve card before anything changes. You decide which actions earn *automatically*. - **Everything is logged.** Each action lands in the Operator's history with who triggered it and when. - **Everything is reversible.** One-click Undo on the last action; the history is your audit trail. And it works unprompted. Standing rules run on a schedule — the goal watcher drafts a gap-closing campaign when a goal falls behind pace; the key-event watcher proposes a campaign when a launch window opens — and drop their proposals in your Inbox for a yes or no. You clear them in a few minutes, not a few hours. All of that now has a home: the **Operator console** (Team → The Operator). One page showing what it may do, what it's watching, what it's done, and the authority you've granted. The agent stopped being a chat box in the corner and became a thing you can point at. ## The Levels of Marketing Autonomy Most of what gets called "AI marketing" sits lower on the autonomy ladder than the branding suggests. It's worth being precise about the rungs: - **L1 — Assist.** It writes a draft when you ask. A better text box. - **L2 — Copilot.** It suggests next steps inline; you do them. - **L3 — Conditional autonomy.** It acts on its own *within boundaries you set*, and asks when it's unsure. It notices things and proposes, unprompted. - **L4 — Self-driving.** It holds standing authority to act toward an outcome, reporting results rather than asking permission for each step. crm.care runs at **L3 today** — conditional autonomy with a chat seat. That's already further than most of the category, which lives at L1–L2 with an L4 marketing campaign. (We wrote up that announced-vs-shipped gap in [the case for crm.care](/blog/why-crm-care-exists).) The interesting question isn't "are you L4 yet?" — anyone can claim it. It's *how do you get there without handing an unproven agent the keys?* ## Promotion, not replacement Here's the design decision the whole roadmap turns on: **the Operator earns L4 the way a person earns trust at work — one responsibility at a time, with the right to take it back.** There is no "switch to autonomous mode" toggle. Instead, each new authority shows up on the Operator console as a specific, named permission you can grant, watch, and revoke. The Goals P&L is the scoreboard — every autonomous action ultimately answers to influenced pipeline against target. Promotion, not replacement: the same agent you already supervise simply does more, and you can always step it back down. That keeps the credibility honest. We don't ask you to believe a demo. We ask you to grant one permission, watch it behave, and decide. ## The first L4 promotion: pause what's drifting The first standing authority is live: **the Operator can pause a campaign that has drifted.** Each morning it scans your active campaigns for two failure signals: - **Engagement collapse** — the average open rate has cratered below a sensible floor *and* sits well under the rest of your portfolio. Something's wrong: a broken subject pattern, a deliverability hit, a list gone stale. - **A stalled schedule** — the campaign's calendar ran out days ago with emails still unsent, or it's gone quiet for weeks while still flagged active. It's been abandoned without being closed. When it finds one, what happens next is your call, set on the Operator console: - **Propose (L3).** It drafts the pause and drops it in your Inbox — *"this campaign has drifted; pause it?"* — and nothing changes until you approve. - **Self-driving (L4).** It pauses the campaign itself, then tells you what it did and why, with one-click Undo. Pausing is a real stop, not a flag: crm.care holds the campaign — further publishing and CRM sync are blocked — *and* switches off its live workflow in your MAP (HubSpot) so it stops sending. Unpause restores it exactly, re-enabling the workflow. Why make *pausing* the first autonomous act? Because it's the safest possible one. Pausing spends nothing, sends nothing, and is completely reversible — the worst case is a campaign sits idle for an hour until you hit Unpause. That's the right place to let an agent off the leash first. The authority that *spends* money comes later, and only after this one has earned its keep. The guardrails are deliberate: it's **off by default** and admin-only to change, and reaching full self-driving is a two-step promotion — turn it on to propose, then promote it to act. It auto-pauses **at most one campaign per run**: a drift event that tanks every open rate at once can't let the Operator pause your whole portfolio unattended — the overflow falls back to proposals. And every pause carries Undo. The point of a first promotion is to be boring and trustworthy, not impressive. ## What comes next The ladder above this rung is mapped, and we'll climb it the same way — one grantable permission at a time: - **Propose the quarter's portfolio** — from a gap analysis of your pipeline goals against your CRM, a portfolio plan rather than a single campaign. - **Ship within standing budget caps** — execute an approved playbook end to end inside a budget envelope, reporting to the Goals P&L. Both are on the roadmap, not in the product. When they land, they'll land here — as authorities you grant, never as defaults that surprise you. ## Meet it If you're already on crm.care, press **⌘K** and say hello — then open **Team → The Operator** to see what it's watching and grant it its first standing authority when you're ready. If you're not, the [autonomy ladder](/autonomy) is the fastest way to see where we sit and where we're going. The Operator is the first member of your AI marketing team's org chart. It won't be the last — but it's the one learning to run things first, in public, with the undo button always in reach. --- ## Agentforce for small teams: the honest read Source: https://crm.care/blog/agentforce-for-small-teams Published: 2026-06-10 Agentforce is the loudest product in marketing-and-sales AI right now, and if you run a small team you've probably wondered whether it's for you. The honest read: it's an enterprise product with an enterprise rollout, and the gap between the keynote and a working deployment is wide enough that a 2–5 person team should think hard before betting on it. This isn't a knock on the technology. It's about fit. ## What the adoption numbers actually say In its first year, Agentforce reached roughly **12,500 customers — about 8% of Salesforce's base** — with only a portion of those paying. Salesforce repackaged it at Dreamforce 2025, and Marc Benioff publicly conceded that "technology innovation is outstripping customer adoption." Salesforce has also leaned on forward-deployed engineers to get customers live, which tells you something: it generally takes hands-on help to deploy, not a self-serve afternoon. For a large enterprise with a Salesforce admin team and a six-figure platform budget, that's workable. For a small marketing team, every one of those frictions is disqualifying. ## The small-team math Three things make Agentforce a poor fit below the enterprise tier: - **Price.** List pricing has run around **$550/user/month**, typically with a mandatory Data Cloud consumption component on top. That's not a small-team line item. - **Time to value.** Deployments commonly run months, not days, and depend on clean CRM data and admin/developer expertise. A small team doesn't have a quarter to spend before the first outcome. - **It's a copilot, not an operator.** In practice the "autonomous agent" still needs constant prompting and supervision — it assists inside Salesforce rather than owning a campaign end to end. (We map this out in [the Levels of Marketing Autonomy](/autonomy): most "agents," Agentforce included, sit at Level 2.) ## What a small team actually needs A team of two-to-five doesn't need an enterprise agent platform. It needs leverage that shows up the same week: write the campaign, get it into the platform, see what worked. The bar is **time-to-first-outcome**, not breadth of configuration. That's the gap crm.care is built for — an AI marketing operator that connects to the platform you already run (Salesforce / Account Engagement or HubSpot), generates whole campaigns in your brand voice, publishes them, and reads attribution back — with approval gates and budget caps so a small team can trust it without a Data Cloud project. "Connected Tuesday, campaign live Wednesday, attribution Friday" is a sentence Agentforce structurally can't say to a three-person team. It's the whole reason [crm.care exists](/blog/why-crm-care-exists). ## The takeaway If you're an enterprise standardising on Salesforce, Agentforce will get attention and investment — fair enough. If you're a small team, don't buy the keynote: buy time-to-outcome. Connect your platform, ship a real campaign this week, and let [the proof](/blog/three-degrees-attribution-salesforce) — pipeline influenced, not demos watched — make the decision for you. --- ## HubSpot Breeze credits: what the AI actually costs Source: https://crm.care/blog/hubspot-breeze-credits-cost Published: 2026-06-10 If you're on HubSpot and weighing Breeze — HubSpot's AI layer — the first thing worth understanding isn't what it does, it's how it's priced. Breeze runs on a **credit system**, billed per action, and that changes the calculus in ways a flat subscription doesn't. Here's a clear-headed look at the cost, where Breeze is genuinely strong, and where a connected AI layer fits better. To be clear up front: Breeze's support-side agent is good — it resolves a large share of routine tickets and earns its keep. This is about the marketing side and the pricing model. ## How Breeze pricing works Breeze agents consume HubSpot credits, with each action drawing down a balance. A few consequences follow: - **Costs scale with usage, not a fixed line.** The more the agents do, the more credits you burn — which is fine until a busy month produces a bill you didn't forecast. Teams report **surprise charges from auto-upgrades** when they cross a tier. - **The good agents are gated.** Most Breeze agents require **Professional or Enterprise** subscriptions; lower tiers get the assistant but not the agents. So the entry price is the HubSpot tier *plus* the credits. - **Several marketing agents are still beta**, and the shipped ones offer limited control — for example, no custom instructions to steer agent behaviour. None of this makes Breeze a bad buy. It makes it a **metered** buy, and metered AI is hard to budget when you're a small team trying to use it heavily. ## The predictable-cost alternative The opposite model is a flat AI layer that connects to HubSpot and does the marketing work at a known monthly price — no per-action meter, no tier-gated agents, no auto-upgrade surprises. That's where crm.care sits: it [connects to HubSpot](/blog/crm-care-now-supports-hubspot) and generates whole campaigns in your brand voice, publishes lists, nurtures and emails into HubSpot, and reads attribution back — on a predictable Solo/Team/Growth subscription with a per-tenant AI budget cap so spend can't run away. So the real comparison isn't "Breeze vs not-Breeze." It's: - **Breeze** — native to HubSpot, strong on support automation, metered per action, best agents gated to higher tiers. - **A connected AI layer** — predictable monthly cost, marketing-first, governed by approval gates + a hard budget cap, works across HubSpot *and* Salesforce if you run both. Many teams will run the HubSpot support agent and a connected layer for marketing — they solve different problems. ## The takeaway Before committing to Breeze for marketing, model a heavy month at credit prices, not a light one — that's where the metered model bites. If predictable cost and tight spend control matter more than native-everything, a connected AI layer is worth a look. [See what actually ships](/proof), and weigh it against a busy month of Breeze credits. --- ## Is Pardot dead? Account Engagement in 2026 Source: https://crm.care/blog/is-pardot-dead-2026 Published: 2026-06-10 "Is Pardot dead?" is one of the most-searched questions in B2B marketing operations right now — and if you run Account Engagement (the product Salesforce renamed Pardot to), you already know why people are asking. The honest answer: it's not dead, but it has visibly stalled. Here's what's actually happening, and the option most teams miss between "live with it" and "rip it out." ## The case that Account Engagement has stagnated A few things are true at once in 2026: - **Innovation pace has slowed.** Account Engagement's release cadence and UI have fallen behind HubSpot and modern Marketo. The interface still feels like the Pardot of the last decade, and the most-requested quality-of-life improvements have sat untouched for years. - **The partner ecosystem has thinned.** Fewer agencies and consultants are building net-new Pardot practices; the talent and tooling gravity has moved toward HubSpot. - **The API is genuinely limited.** The clearest tell is Engagement Studio — Account Engagement's automation engine has **no write API**, so you can't programmatically build or migrate nurture flows. (Anyone who's tried to automate AE knows this wall well.) None of that means Salesforce is shutting it down. It means AE is in maintenance mode in spirit, even if not in name — stable, supported, but not where the investment is going. ## Why most teams don't migrate (the $10–50k problem) The instinctive reaction is "switch to HubSpot." But a Pardot→HubSpot migration is a real project: typical quotes land in the **$10,000–$50,000 range and 6–16 weeks**, and that's before the hidden cost — your nurtures can't be exported (no read API), so they get rebuilt by hand, and your whole team re-learns a new platform. For a lean marketing team, that's a quarter of disruption to escape a tool that, day to day, still works. So most teams do nothing. They stay on a stagnant platform because the exit is expensive. That's the real trap — not the stagnation itself, but the migration tax that keeps you in it. ## The third option: modernise in place There's a path between "live with it" and "rip it out": put a modern AI layer **on top of** the Account Engagement org you already run. That's what crm.care does — it connects to AE via OAuth and: - generates whole campaigns (emails, social, nurture sequences) in your brand voice, - publishes segments and email templates straight into AE, - and reads closed-loop attribution back from Salesforce. No migration, no rebuild, no retraining — you keep Pardot and lose the stagnation. And if you *do* decide to move to HubSpot later, you do it on your own timeline rather than under duress. (We built the migration path too, for exactly that day.) For a marketer running on AE + [Salesforce attribution](/blog/three-degrees-attribution-salesforce), it's the lowest-risk way to get a modern AI workflow without betting a quarter on a platform switch. ## So — is Pardot dead? No. It's stalled, and the migration tax is keeping a lot of teams parked on it longer than they'd like. But "stalled platform" and "stuck team" don't have to be the same thing. You can modernise the work — AI-generated, on-brand campaigns with real attribution — without touching the platform underneath. If you're weighing the migrate-or-stay decision, [see the cost of modernising in place vs ripping it out](/pardot-rescue) — and the related read on [getting AI-generated emails to actually render in Account Engagement](/blog/publish-ai-emails-to-account-engagement). --- ## Copy.ai got acquired — where its users go now Source: https://crm.care/blog/copy-ai-acquired-alternatives Published: 2026-06-10 In October 2025, Copy.ai was acquired by Fullcast, a revenue-operations vendor, and folded in as a module of Fullcast's RevOps suite. If you'd standardised on Copy.ai for marketing and sales content — or you're on its free tier — that changes things, and it's worth thinking clearly about where to go rather than waiting to be migrated by someone else's roadmap. This isn't a "Copy.ai was bad" post. It was a capable generative-content platform with millions of users. The point is structural: a horizontal "GTM AI" content tool without its own system-of-record hook is a hard business to keep independent — and Copy.ai's outcome is the second data point (after Jasper's well-documented revenue slide) that **pure AI-content tooling is being commoditised by the foundation models underneath it.** ## What to actually look for in a replacement If you're picking a Copy.ai alternative, the instinct is to find another tool that writes well. That's the wrong axis — every tool writes well now, because they're all calling the same handful of models. The real question is **what happens after the draft.** Three things separate a writing tool from a marketing tool: 1. **Does it publish where you work?** A draft in a chat window still has to be copied into your marketing platform by hand. The tools that compound are the ones that write *into* HubSpot or Salesforce / Account Engagement — campaigns, lists, nurtures — not just into a clipboard. 2. **Does it know your brand?** Generic output is the failure mode of every AI writer. The differentiator is a persisted brand voice that wraps every generation, plus pre-send QA so nothing ships off-brand. 3. **Does it close the loop?** The only way an AI marketing tool gets *better* over time is if it can read attribution back — what actually drove pipeline — and learn from it. A writer can't; a system of record can. A tool that does all three isn't a content generator with extra steps — it's an operator. That distinction is the whole reason [crm.care exists](/blog/why-crm-care-exists). ## Where crm.care fits crm.care is built around the after-the-draft half: it generates whole campaigns in your brand voice, **publishes them into your marketing platform** (HubSpot or Account Engagement), and reads closed-loop attribution back from your CRM. The writing is table stakes; the execution and the loop are the product. If you're evaluating where to move post-Copy.ai, the most useful thing isn't another feature list — it's proof the loop runs. [See what actually ships](/proof), and the honest comparison of an [AI writing tool versus an AI marketer](/blog/crm-care-vs-jasper-salesforce). ## The takeaway Copy.ai's acquisition is a prompt to upgrade the question. Don't replace it with another standalone writer that the same market forces will pressure next year — replace the *workflow*: brief → on-brand campaign → published into your platform → attributed back. That's the part foundation models can't commoditise, because it isn't about the words. --- ## crm.care now supports HubSpot Source: https://crm.care/blog/crm-care-now-supports-hubspot Published: 2026-06-09 crm.care now connects to **HubSpot**. If your marketing runs on HubSpot, you can point crm.care's AI brand-voice engine straight at it — generate campaigns, build segments, stand up nurture workflows, and read attribution back from your CRM, all without leaving crm.care. Until now crm.care was built around Salesforce + Account Engagement (Pardot). HubSpot support opens the same closed-loop operator to the large population of B2B teams running HubSpot as their marketing automation platform, their CRM, or both. It's live today — connect it from the [Connections page](/features) in a couple of OAuth clicks. ## What the HubSpot connector actually does crm.care treats your stack as two independent layers: a **marketing automation platform (MAP)** where campaigns and nurtures live, and a **CRM** where pipeline and revenue live. HubSpot can be either — or both. Here's what the connector drives on each side. ### On the marketing side (HubSpot as your MAP) - **AI-generated campaigns in your brand voice, published to HubSpot.** Describe the campaign; crm.care drafts the emails, social, and sequence copy tuned to your voice, then creates the campaign in HubSpot ready to send. - **Segments → HubSpot Lists.** Audiences you define in crm.care publish to HubSpot as **dynamic active lists** that keep themselves up to date as contacts qualify in and out — not a one-time static export. - **Nurture workflows → HubSpot Workflows.** Multi-step nurtures, including the inter-email delays, are written directly into HubSpot's Workflows engine so they run natively on HubSpot's automation. - **Send + engagement analytics.** Sent, delivered, open, click, bounce, and unsubscribe numbers (plus open/click/delivered rates) flow back into crm.care so you see performance where you planned the campaign. ### On the CRM side (HubSpot as your CRM) - **Campaign sync.** Every campaign crm.care creates is mirrored into HubSpot's Marketing Campaigns so spend and activity are tracked in one place. - **Closed-loop attribution.** crm.care reads HubSpot's campaign attribution — sessions, new contacts (first- and last-touch), influenced contacts, and revenue — so you can tie marketing work back to pipeline without spreadsheet gymnastics. - **Deals read-back.** Deal data feeds the attribution picture, closing the loop from campaign → contact → deal. ## Three ways to wire it up Because the MAP and CRM layers are independent, crm.care supports three valid configurations: 1. **HubSpot for everything** — HubSpot is both your marketing automation platform and your CRM. crm.care publishes campaigns, lists, and workflows to HubSpot and reads attribution back from HubSpot. 2. **HubSpot marketing + Salesforce CRM** — run campaigns and nurtures in HubSpot, but keep pipeline and attribution in Salesforce. crm.care bridges both. 3. **Salesforce + Account Engagement** — the original setup, still fully supported. You pick the combination that matches your stack; crm.care detects what you've connected and routes campaigns, segments, and attribution to the right place automatically. ## What HubSpot unlocks that's worth calling out A few capabilities are genuinely nicer on HubSpot than on the Account Engagement path: - **Dynamic lists** that re-evaluate membership continuously, versus the more manual list management elsewhere. - **Native multi-step Workflows** with branching and timed delays, written via API rather than hand-built step by step. - **First-class campaign attribution metrics** exposed through HubSpot's reporting API, so the closed loop needs less stitching. If you've been wondering whether an AI marketing operator could sit on top of HubSpot the way one sits on top of Salesforce — it can now, and the HubSpot connector arguably has the richer surface. ## How to connect HubSpot 1. Open the **Connections** page in crm.care. 2. Choose **Connect HubSpot** and complete the OAuth grant — crm.care requests only the marketing and CRM scopes it needs (campaigns, lists, workflows, contacts, deals, and attribution reporting). 3. crm.care detects HubSpot as your MAP and/or CRM and lights up the relevant features. From there, generate a campaign and publish it straight to HubSpot. No data migration, no rebuild — it works alongside the tools you already pay for. ## Why this matters The whole point of crm.care is to be the AI-native operator that lives *outside* your platform but closes the loop *into* it — drafting on-brand work, publishing it where it runs, and reading results back so you know what actually moved pipeline. We wrote about that gap in [why crm.care exists](/blog/why-crm-care-exists), and about how attribution gets measured in [three degrees of attribution](/blog/three-degrees-attribution-salesforce). HubSpot support means that loop now closes for HubSpot teams too. If you run marketing on HubSpot, [take a look at what crm.care does](/features) — or connect your HubSpot account and ship your first AI-generated campaign today. --- ## crm.care is now an MCP server Source: https://crm.care/blog/crm-care-mcp-server Published: 2026-05-17 crm.care now speaks the [Model Context Protocol](https://modelcontextprotocol.io). Install once in Claude Desktop, Cursor, Continue.dev, or any MCP-compatible client, and your AI agent can read crm.care's product info, search the blog, look up your campaigns and brand voice — all without leaving the chat. There are two tiers: a **public read-only server** anyone can install (it answers questions about the product), and an **authenticated per-workspace server** for paying customers (it reads your campaigns + brand voice + budget, scoped to your workspace via a Personal Access Token). This post walks through both. ## Why MCP, why now The AI agent ecosystem is splitting in two. On one side, agents that browse the public web — ChatGPT, Perplexity, Claude with web search — synthesise answers from whatever's indexed by Bing or Brave. On the other side, agents that work **on behalf of a logged-in user** — Claude Desktop, Cursor, Continue.dev — need authenticated access to that user's tools and data. The Model Context Protocol is how the second category talks to those tools. Instead of every SaaS product building a custom Claude plugin, a custom Cursor integration, a custom Continue extension, MCP standardises the contract: tools, resources, prompts. Build one server, get every MCP-compatible client for free. For a B2B SaaS like crm.care, this matters because **the buyer's centre of gravity is shifting from the SaaS UI to the AI agent**. Marketing operators on Account Engagement still spend most of their day inside AE and crm.care. But increasingly they also have a Claude window open — drafting copy, debugging, asking clarifying questions about their own data. If crm.care is invisible to that Claude window, we're invisible to the place the operator's attention is moving. The MCP server fixes that. ## The public tier — no auth required The public MCP server lives at `https://crm.care/api/mcp`. It exposes seven read-only tools that answer questions about crm.care itself: what it does, who it's for, pricing, blog content, competitor comparisons, FAQ. Install in Claude Desktop: ```json { "mcpServers": { "crm.care": { "command": "npx", "args": [ "mcp-remote@latest", "https://crm.care/api/mcp" ] } } } ``` Paste into `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS; equivalent paths on Windows / Linux), restart Claude Desktop. Same config snippet works in Cursor and Continue.dev. After installation, Claude has tools available like: - `crm_care_overview` — what crm.care does - `crm_care_pricing` — tiers and trial terms - `crm_care_icp` — fit profile (and explicit non-fit signals) - `crm_care_search_blog(query)` — search the blog - `crm_care_get_blog(slug)` — fetch a specific post - `crm_care_compare(competitor)` — vs Jasper / HubSpot / Marketo / Pardot - `crm_care_faq` — canonical answers to common questions The agent calls these automatically when the conversation warrants. Ask Claude *"Is crm.care a fit for a Marketo shop?"* and it'll call `crm_care_icp`, get our honest "no, we're AE-specific, here's what to look at instead" answer, and pass that on rather than guessing. ## The authenticated tier — your workspace The authenticated server lives at `https://crm.care/api/mcp/v1`. Same protocol, but with a Bearer-token Authorization header. The token authenticates to a specific (user, org) pair — your Claude can read your campaigns, never anyone else's. Generate a token at `/admin/api-keys` inside your crm.care workspace. The token's shown once on creation alongside a pre-formatted config snippet — copy both, paste into your MCP client config, restart, done. The current authenticated surface is read-only: - `list_campaigns` — recent campaigns, filterable by status - `get_campaign(id)` — full detail - `get_brand_voice` — your configured voice - `get_budget_usage` — this month's spend, quota usage - `search_campaigns(query)` — keyword search - `list_recent_content` — recent social posts and emails Write tools — generate a campaign, publish to AE, edit brand voice — are deliberately out of scope for this first authenticated phase. We're proving the auth and tool plumbing with read-only traffic before exposing operations that burn budget or mutate AE state. Write tools land in a follow-up. ## What you can ask your agent A few example interactions, with the tool calls the agent makes under the hood: **"What campaigns am I running this week?"** → `list_campaigns(status: 'in_progress')` → Claude summarises your active campaigns by objective and audience. **"How much AI budget have I burned this month?"** → `get_budget_usage()` → Spend vs. cap, quota usage, days remaining. **"Find the post we wrote about Three Degrees of Attribution."** → `crm_care_search_blog(query: 'three degrees attribution')` → returns the slug; Claude can then `crm_care_get_blog(slug)` for the full text and quote relevant sections. **"Help me draft a follow-up email for the Q3 launch campaign."** → `get_campaign(id: '...')` to load the brief + brand voice → Claude drafts the email in your actual voice with context from the existing campaign plan. The last one is the most interesting pattern. The agent isn't generating campaigns for you (that still happens in crm.care, where it lives in your campaign history). It's a **research and drafting assistant** that has access to the same workspace context you do — without you needing to copy and paste briefs into the chat. ## What we're betting on Two things shape the bet behind investing in MCP at this stage of the product. **One**: marketing operators are early adopters of AI tooling, but late adopters of *integrations between* AI tooling. The path of least resistance has been to copy-paste between Claude and AE. MCP collapses that step. The first marketing-tools company to show up natively inside Claude wins the workflow. **Two**: distribution matters. The MCP ecosystem in 2026 is where the App Store was in 2009 — small, technical, but compounding fast. Anthropic's official directory, mcp.so, smithery.ai, and the modelcontextprotocol/servers GitHub repo are real discovery channels for the AI-native developer audience. That audience overlaps significantly with the technically-inclined marketing ops persona we build for. Being visible there is a real channel, not an afterthought. There's also a quieter benefit: dogfooding. Lee runs crm.care from inside Cursor most days. Having the MCP means we eat our own product before customers do — every UX friction surfaces immediately because we're the first ones hitting it. ## Try it The public tier is install-and-go: copy the config above, paste into Claude Desktop, restart, ask Claude *"What does crm.care do?"* — and watch it call our tools. The authenticated tier needs a paid crm.care account (7-day free trial counts) → generate a token at `/admin/api-keys` → install with the pre-formatted snippet from the reveal dialog. Full docs, both install paths, and copy-paste config snippets are at [/mcp](/mcp). If you build something interesting with it — or hit something that doesn't work — drop us a note at [hello@crm.care](mailto:hello@crm.care). --- ## What is Three Degrees of Attribution in Salesforce? A B2B marketer's guide Source: https://crm.care/blog/three-degrees-attribution-salesforce Published: 2026-05-06 **Three Degrees of Attribution in Salesforce** is a framework for capturing the full marketing contribution to a closed-won opportunity — not just the campaign that was tagged as Primary Campaign Source, and not the diluted average that Campaign Influence produces by default. It splits credit into three explicit tiers — *absolute*, *direct*, and *indirect* — so a CFO can see how much of the pipeline marketing owns outright, how much marketing co-owns with sales, and how much marketing influenced without owning. This guide explains what each tier measures, how to compute it from the Salesforce + Account Engagement data model, and where most B2B teams get the math wrong. ## Why "single-touch attribution" stopped working The classic Salesforce pipeline-marketing report is built on one field: `Opportunity.CampaignId`, also called Primary Campaign Source (PCS). Sales sets it (or a workflow does), and every revenue dashboard rolls up against it. PCS gives you exactly one campaign per opportunity. For 2014 marketing — one big-ticket trade show, one webinar, one demo request, deal closes — that was fine. The buyer touched marketing once before sales took over. That isn't how B2B buying works in 2026. The average enterprise opportunity now touches **eight to twelve** marketing campaigns before close — a top-of-funnel ad, a gated whitepaper, a webinar registration, three nurture emails, an in-person event, an SDR follow-up sequence, a competitive comparison page view. Pinning revenue to a single one of those campaigns is no longer "attribution," it's a coin flip. Salesforce's answer was the **Campaign Influence** object: any contact role on the opportunity, multiplied by their campaign memberships, gets a slice of the revenue. The maths uses one of three pre-built models (First Touch, Last Touch, Even) or a custom model. It works, but two problems make it a CFO's worst dashboard: 1. **The "Even" split dilutes everything.** A campaign that genuinely drove the deal is treated identically to a campaign that one of the deal's contacts happened to attend two years ago. 2. **The reporting object is hostile.** `CampaignInfluence` is a junction object with quirky permissions, soft caps, and a default 90-day attribution window that quietly drops contributions older than that. Most teams ship a dashboard that reads from it once and never realise half the influenced pipeline is invisible. So the typical state is: PCS shows the marketing-attributed pipeline that's too narrow, Campaign Influence shows the marketing-attributed pipeline that's too noisy, and finance picks whichever number is more flattering for the quarter. That isn't a system; it's a guess. ## What Three Degrees of Attribution actually measures Three Degrees splits the question into three answers, computed against the same source-of-truth data but with different rules. ### Degree 1: Absolute **Definition:** revenue from opportunities where this campaign is the Primary Campaign Source (`Opportunity.CampaignId = thisCampaign`). This is the marketing-owned pipeline. The lead came in through this campaign, sales picked it up, the opportunity was created, and PCS was set as part of the create flow. There is no shared credit and no inferred influence — the sales rep wrote the campaign name in the field. You'd typically use Absolute to answer: *"Which campaigns are sourcing pipeline?"* It's the most defensible number when finance pushes back. It's also the smallest — usually 30–40% of the pipeline marketing actually touched. ### Degree 2: Direct **Definition:** Absolute, plus opportunities where one of the contact roles attended this campaign at a meaningful threshold (registered + attended, or downloaded gated content) within the attribution window. This adds the cases where marketing was clearly part of the deal but wasn't the source. The buyer attended a webinar mid-cycle. The technical evaluator downloaded the whitepaper before the procurement decision. The CFO got the comparison-grid email two weeks before the renewal call. Direct is the right answer to: *"Did marketing touch this deal in a way that mattered?"* It deliberately excludes the long tail of casual touches (single-pixel email opens, drive-by site visits, registrations without attendance) that bloat Even-split Campaign Influence numbers. ### Degree 3: Indirect **Definition:** Direct, plus opportunities where this campaign appeared anywhere in any contact role's campaign-member history during the attribution window — including registrations without attendance, light email engagement, and any `CampaignMember` where `Status` is `Sent` or higher. This is the broadest measure. It's the answer to: *"Did this campaign show up in the buying journey at all, even tangentially?"* Indirect is intentionally generous. It's what you use to evaluate awareness plays — display ads, top-of-funnel content, podcasts, sponsorship — that influence brand without producing a clean direct touch. A CFO won't fund the next display campaign on Indirect alone, but a CMO needs Indirect to defend the brand budget that produces it. ## A worked example A mid-market SaaS company runs four campaigns in Q2: - **Q2 Webinar — How to Forecast Pipeline** (registered: 480, attended: 220) - **State of RevOps 2026 Whitepaper** (downloads: 1,140) - **Display retargeting — Forecasting Buyers** (impressions: 1.2M, click-throughs: 8,400) - **Outbound nurture — VP Finance** (emails sent: 920, replied: 67) Three months later, Salesforce closes 18 opportunities tagged to one of those campaigns. Three Degrees against the webinar: | Tier | Count | Pipeline | Closed-won | |---|---|---|---| | Absolute (PCS) | 3 ops | $284k | $124k | | Direct (PCS + attended + downloaded) | 9 ops | $1.04M | $410k | | Indirect (any campaign membership) | 14 ops | $1.92M | $740k | Three numbers, same campaign, same source data. The absolute number is what you bring to finance. The direct number is what marketing leadership reports to the board. The indirect number is what you use internally to argue for the next webinar. Importantly: the three tiers are **nested**, not separate. Direct includes Absolute. Indirect includes Direct. There's no double-counting, and the largest number is always the broadest. ## Computing it from the Salesforce data model The three SOQL queries map directly to the three tiers. Each one assumes a 90-day attribution window — adjust to taste, but document the choice somewhere. **Absolute:** ``` SELECT Id, Name, Amount, StageName FROM Opportunity WHERE CampaignId = :campaignId AND CloseDate >= :windowStart ``` **Direct:** ``` SELECT Opportunity.Id, Opportunity.Amount, Opportunity.StageName FROM OpportunityContactRole WHERE Contact.Id IN ( SELECT ContactId FROM CampaignMember WHERE CampaignId = :campaignId AND Status IN ('Attended', 'Downloaded', 'Registered + Attended') AND CreatedDate >= :windowStart ) ``` Then union with the Absolute set, deduping by Opportunity.Id. **Indirect:** ``` SELECT Opportunity.Id, Opportunity.Amount, Opportunity.StageName FROM OpportunityContactRole WHERE Contact.Id IN ( SELECT ContactId FROM CampaignMember WHERE CampaignId = :campaignId AND CreatedDate >= :windowStart ) ``` Union with the Direct set, dedupe by Opportunity.Id. The only difference from Direct is the Status filter is removed. Three things to watch out for in production: - **The 90-day window is a default, not a law.** B2B sales cycles for $100k+ ACV deals are routinely 6–9 months. If you only count touches in the trailing 90 days you'll miss the whitepaper download from month one of a six-month evaluation. Lengthen the window for high-ACV motions, document the choice, and re-run historicals so the comparison is fair. - **CampaignMember Status values are workspace-specific.** What counts as "attended" in your AE business unit might be `Attended`, `Registered + Attended`, `Joined Webinar`, or something custom. The Direct query is only as good as your Status taxonomy. - **Roll-up across campaign hierarchies.** If a parent campaign has children (a "Q2 Demand Gen" parent with a webinar, a whitepaper, and a display set as children), the three queries should sum across the full subtree. Most teams forget this and report the parent's Absolute as zero because PCS is set on the children. ## Where most teams get the math wrong After working with several dozen MOps teams on attribution, the same five mistakes show up repeatedly: 1. **Confusing PCS with Direct.** PCS is one field, set once per opportunity. Direct is a query that union-counts opportunities across multiple touchpoints. A team that only looks at PCS is reporting Absolute and calling it Direct. 2. **Missing PCS data on legacy accounts.** Opportunities created before the team turned on PCS-required validation rules have a null `CampaignId`. The fix is a back-fill: an audit that finds opportunities with null PCS but with `CampaignMember` records on contact roles, and assigns the most-recent-pre-creation campaign as the inferred PCS. Manual at small scale, automated at large scale. 3. **Even-split everywhere.** The default Campaign Influence model gives every campaign equal weight on a deal, so a passive newsletter signup gets the same credit as the demo request that started the conversation. Replace it with a model that weights touches by Status (registered + attended > downloaded > sent + opened > sent), or move to a Three Degrees view that doesn't try to apportion at all. 4. **Reporting Indirect as if it were Direct.** The temptation is to pick the biggest number and pretend it's defensible. CFOs catch this on the first follow-up question. Always lead with Absolute, follow with Direct, footnote Indirect. 5. **Not connecting attribution back to campaign generation.** The team computes the numbers, ships the dashboard, and then designs next quarter's campaigns from a fresh whiteboard with no reference to what worked. Attribution should feed back into the brief: which channels, which structural patterns, which audiences produced the highest Direct-to-Indirect ratio. ## What this looks like in crm.care [crm.care](/) computes all three tiers automatically against your live Salesforce + AE data and surfaces them on the campaign Results tab. The PCS audit catches the missing-data case from #2 above. The campaign-hierarchy roll-up handles parent + children correctly. And the predictive layer feeds Direct attribution back into next-campaign generation, so the team's compounding pattern of what works gets baked into the briefs over time. The Three Degrees framework itself is platform-agnostic — you can build it in any BI tool with the SOQL above. The reason teams use crm.care is that the maths happens automatically against the same Salesforce data the rest of the company sees, computed the moment a campaign moves to in-progress, with no quarterly project to "rebuild attribution" because nobody can remember what the old dashboard was joining on. For a deeper look at the surrounding pieces — how to structure your campaign hierarchy so the roll-up works, why your Pardot dashboard is hiding influenced pipeline, what to do when 30% of your opportunities have null PCS — see the [features page](/features), or read [Why crm.care exists](/blog/why-crm-care-exists) for the broader frame on AI-native marketing operations. Ready to see it on your own pipeline? [Free 7-day trial.](/sign-up) Connects to Salesforce + AE in about 90 seconds. Three Degrees lights up the moment your first campaign hits in-progress. --- ## crm.care vs. Jasper for Salesforce-native marketing teams Source: https://crm.care/blog/crm-care-vs-jasper-salesforce Published: 2026-05-06 If you're a Salesforce-native marketing team evaluating AI tooling, you've probably looked at **Jasper** — the marketing-AI category leader for the last three years, with a polished editor, dozens of brand-voice templates, and a sales motion that's been pointed at marketing teams since 2022. You've also probably noticed it doesn't talk to your CRM. This post is an honest comparison of Jasper and crm.care for teams running their go-to-market on Salesforce + Account Engagement, where the gap between "draft a great email" and "ship a tagged, attributable campaign" is the work that actually slows you down. We're a [Jasper alternative](https://www.jasper.ai/) for one specific audience: B2B teams whose pipeline lives in Salesforce, whose sends go through AE / Pardot, and who measure marketing on closed-won influence rather than vanity engagement. That audience is a fraction of Jasper's market, but it's the only audience crm.care is built for. ## What Jasper is genuinely good at Before the comparison, the credit. Jasper has spent five years building these things, and they're real: - **Long-form drafting in a marketing-friendly editor.** Brand voice, tone presets, content templates, an editor that's pleasant to use. If your job is "produce a 3,000-word category report or a five-email nurture sequence from a brief," Jasper's editor is more refined than the equivalent in any in-CRM AI feature. - **Brand-voice profiles that travel.** Train Jasper on a corpus of past content and the voice persists across sessions. The tone consistency is a real differentiator vs. raw Claude or ChatGPT. - **A library of marketing-shaped templates.** PAS, AIDA, headline generators, blog outliners, social variations. Useful when you're starting from a blank page. - **A mature copy-review surface.** Multi-stakeholder review, comments, version history. Built for marketing teams, not solo creators. If your bottleneck is *the words on the page*, Jasper is a fine answer. If your bottleneck is *getting those words into the system that actually sends them, with the right tagging, segments, and attribution wiring*, the gap shows. ## Where the gap shows for Salesforce-native teams Jasper produces text. The text is good. Then you copy it out of Jasper's editor, paste it into Account Engagement's HTML email builder (which has its own table-layout requirements that strip half of Jasper's formatting), retype the subject line into the campaign send config, write the segment rule by hand, set the campaign-source-of-truth field on the Salesforce Campaign object, and configure your Engagement Studio program. Jasper has no idea any of those steps are happening. There is no tag connecting the email it drafted to the campaign that's about to send it. That gap matters for three reasons: **Brand voice without context drifts.** Jasper's brand voice is a static profile. It doesn't know what campaign you're writing for, what stage of the funnel the audience is in, what the parent campaign's strategic plan was, or what tone your last three webinar invites used. A skilled marketer fills the gap by re-briefing every session. Less-skilled (or just busy) marketers ship content that's technically on-brand but tonally off. **The system that sends has its own constraints.** AE emails must use a specific HTML table-layout pattern to render reliably across Outlook, Gmail, and Apple Mail. Jasper exports rich HTML that breaks AE's renderer in ~40% of cases. AE segments aren't free text — they're rule definitions on the Prospect object, with their own DSL. Jasper has no mental model of any of this. **Attribution requires a tag the AI can't see.** Closed-loop reporting in Salesforce + AE depends on every piece of marketing being correctly tagged to a Salesforce Campaign so that Primary Campaign Source and Campaign Influence can roll up. Jasper drafts the email but has no concept of a Campaign object. Tagging is a manual step that gets dropped under deadline pressure, which is why most B2B teams have 20–30% null PCS on their opportunities — invisible influenced pipeline. These are not Jasper's fault. Jasper is a writing tool, and a good one. They're the cost of using a writing tool when your bottleneck is no longer writing. ## What crm.care does differently crm.care is built around a different premise: the writing is one step in a 30-minute campaign loop, and the loop is what matters. **Brief once, ship the whole campaign.** A one-page brief — audience, objective, channels, key message, tone — produces the strategic plan, every email in the sequence, every social post, the landing-page block, and the gated-asset content. Every artefact holds the same brief and the same brand voice. Edit the brand voice in workspace settings and every generator adapts. **Publishes directly to Account Engagement.** Email templates push into AE with the right table-layout HTML for the renderer. Segments publish as static lists or rule-based dynamic lists. The parent Salesforce Campaign object is created or referenced by ID, and every artefact is tagged correctly so PCS rolls up automatically. The "copy-paste-retype" tax disappears. **Reads attribution back from Salesforce.** Three Degrees of Attribution — Absolute (PCS), Direct (PCS + meaningful contact-role touches), Indirect (any campaign-member history) — computed live against your Salesforce data, surfaced on the campaign Results tab. The PCS audit catches missing-source opportunities and proposes back-fills. ([Read the Three Degrees explainer](/blog/three-degrees-attribution-salesforce).) **Compounds with usage.** The predictive performance layer matches every new email's structural fingerprint against your past campaigns and shows a predicted open-rate band — calibrated against your team's actual past performance, not industry benchmarks. A fresh install knows nothing. A six-month customer has hundreds of references and the predictions become genuinely useful. Switching cost compounds with usage. **Notices things.** A pre-flight watchdog catches forgot-to-schedule errors before launch. A Friday CMO brief writes itself — 200 words on what shipped, what's at risk, what's queued. AE quota awareness reads your edition's monthly send ceiling and forecasts queued sends so you don't blow past Plus tier with two campaigns in flight. ([See all features.](/features)) ## A side-by-side, honestly | | Jasper | crm.care | |---|---|---| | **Drafting** | Polished editor, mature templates | Streamed generation tied to brief and brand voice, multi-artefact in one pass | | **Brand voice** | Static profile | Workspace setting that propagates to every generator | | **Salesforce / AE awareness** | None — text export only | Native AE publish (table-layout HTML, segments, campaign tagging) | | **Attribution** | None | Three Degrees from live Salesforce data | | **Predictive layer** | Industry benchmarks | Calibrated against your team's past campaigns | | **Autonomous operator** | None | Friday CMO brief, drift detector, pre-flight watchdog | | **Audit & reviewer workflow** | Multi-user editor | Per-tool permissions, multi-reviewer approval, full mutation audit trail | | **Pricing (entry tier)** | $39/seat/month | $99/workspace/month (Solo) | | **Best fit** | Content marketing teams producing long-form copy | B2B marketing teams running campaigns on Salesforce + AE | The pricing line is worth a callout. Jasper is per-seat; crm.care is per-workspace. A four-person marketing team pays Jasper ~$156/month and crm.care $99/month at entry tier. At Team tier ($400/month for crm.care, unlimited reviewers + multi-user collaboration), the comparison flips toward Jasper for headcount-heavy teams that don't need any of the AE / Salesforce integration. So the decision isn't "which is cheaper" — it's "which axis are you optimising along." ## When to pick Jasper Pick Jasper if: - You're a content marketing team producing long-form blog posts, ebooks, and reports. The editor and template library will save you real time. - You don't run on Salesforce + Pardot / Account Engagement. Jasper's lack of CRM integration doesn't cost you anything because there's nothing to integrate with. - Your bottleneck is genuinely the words on the page — not tagging, not segmentation, not attribution. - You have a strong production-side process (someone else handles AE publishing, someone else writes segment rules, someone else owns Salesforce reporting) and you just need better drafts handed off into that process. ## When to pick crm.care Pick crm.care if: - Your pipeline lives in Salesforce, your sends go through AE / Pardot, and your CMO measures marketing on closed-won influence. - The work that slows you down isn't writing — it's everything around writing. Tagging, segmenting, publishing to AE, rolling up attribution, getting the brand voice consistent across a multi-artefact campaign. - You want a tool that knows what campaign it's writing for and writes back into your CRM, not a tool that produces text you then have to integrate yourself. - The marketing team is small (1–8 people) and one operator does everything from brief to attribution. Tooling that closes the loop saves more time than a polished editor for any one step. ## A note on category leaders vs. category fit Jasper is the category leader for AI marketing copy. They've spent five years and over $300M in funding building exactly that. crm.care is not trying to compete on copy editing — Jasper would win that comparison and we'd lose it. We're competing on a different question: *what does an AI marketing tool look like when it's built for the system the company actually runs on, not the system the AI vendor wishes the company ran on?* For Salesforce-native teams, that turns out to be a different product entirely — one where the AI knows about campaigns, segments, attribution, and quotas, because the AI lives inside the operator surface that owns those things. If you're in the audience this is built for, the [free 7-day trial](/sign-up) is the fastest way to see whether the loop closes for your team. About 30 minutes from connect to first AE-published campaign. No credit card. Full feature surface. If after the trial Jasper's editor is still serving you better, no hard feelings — they earned it. --- ## How to publish AI-generated emails to Account Engagement (the table-layout HTML problem) Source: https://crm.care/blog/publish-ai-emails-to-account-engagement Published: 2026-05-06 If you've ever drafted a beautiful email in ChatGPT, Jasper, or Claude, pasted the HTML into Account Engagement's email builder, and watched it render as a stack of unstyled paragraphs in Outlook, you've met the **Pardot HTML email** problem. Account Engagement (formerly Pardot) renders email through one of the strictest pipelines in B2B marketing automation — table-layout-only, inline-CSS-only, no flexbox, no grid, no SVG icons, no `max-width`, no modern CSS at all. AI tools generate modern CSS by default. The two don't meet without a translation step, and that translation is what burns 30 minutes per email for most marketing teams. This guide explains why AE's renderer is so unforgiving, the five specific things AI-generated HTML breaks in AE, and the step-by-step fix that gets you from "drafted in an AI editor" to "rendered correctly in Outlook + Gmail + Apple Mail" without learning email-development from scratch. ## Why Account Engagement is so picky about HTML AE doesn't render email itself. AE pushes the email body to your recipients' email clients — Outlook desktop, Outlook on the web, Gmail, Apple Mail, Yahoo, mobile-app variants of all of the above — and **each one** parses HTML differently. AE's job is to ship HTML that survives the worst-case client. The worst case is **Outlook desktop**, which uses **Microsoft Word's HTML rendering engine** under the hood. Yes, Word. Not a browser. Word. Word's renderer was last meaningfully updated in the early 2010s and ignores anything it doesn't understand — including flexbox, grid, CSS variables, modern transforms, viewport units, and most of CSS3. So AE recommends — and effectively requires — **table-layout-based email HTML**: nested `` elements with explicit width attributes, inline CSS on every element, no external stylesheets, no script tags, no SVG, no fancy fonts. The pattern was the email-dev standard from 2002–2015 and is still the only thing that renders consistently across the corporate inboxes that B2B marketing actually targets. Modern AI tools generate semantic, accessible, modern HTML — `
`, ``, `
`, ``, classes referencing CSS variables, sometimes inline SVG icons. All of which look great in a Chrome preview and shatter in Outlook desktop. That's the gap. ## The five things AI-generated HTML breaks in AE When you paste AI-generated email HTML into AE's email builder and send a test, the same five problems show up in roughly this order: **1. Layout collapses to a single column in Outlook.** Your two-column hero with image left and text right renders as text-then-image, full-width, because `display: flex` doesn't exist in Word's renderer. Anything that depends on flex or grid for layout becomes a vertical stack. **2. Spacing gets weird.** Margins on `
` elements behave differently in Outlook than they do in Gmail. AI tools generate `margin: 1.5rem auto` or `padding: 24px 16px` shorthand that Outlook partially honours. The result is uneven gaps that look broken. **3. SVG icons disappear.** Inline `` tags don't render in Outlook. AI tools love SVG icons (Lucide, Heroicons, custom marks) because they're crisp and small. None of that survives. You see a blank space where the icon should be. **4. Fonts fall back to Times New Roman.** AI tools reference web fonts by name (`font-family: 'Inter', sans-serif`) without including the `@font-face` rule and a hosted font URL. Outlook can't fetch the font, doesn't have it locally, falls back to its default — Times New Roman — and your modern sans-serif design becomes a serif Word document. **5. The `max-width` trick fails.** Modern responsive design uses `max-width: 600px; margin: 0 auto` to centre an email body. Outlook ignores `max-width` entirely. The email renders edge-to-edge on a 1920px monitor, looking like a 1990s newsletter. There's a sixth, more subtle issue: **AE's content store strips some HTML on save**. Things like `
` with explicit `width="600"`, centred via `align="center"`, and given a fixed pixel width. No `max-width`. No `margin: 0 auto` on a div. ```
``` The `style="width: 600px"` is belt-and-braces — Outlook reads the HTML attribute, Gmail reads the inline style, and the redundancy means both render correctly. ### Step 2 — Convert every flex/grid layout to nested tables A two-column hero in modern HTML: ```

Headline

``` Becomes: ```

Headline
``` Two cells in a single row, fixed pixel widths, explicit `valign` so the column tops align. The padding goes on the cells, not on the children. ### Step 3 — Inline every CSS property Every `` and every external stylesheet has to go. CSS that lives in a `