Contacts, Campaigns, and Content in One Place: What the CRM Actually Tracks
An honest look at what Editor's CRM surface actually covers — contacts and campaigns, real and shipped — and a direct statement that no link to the kanban task board was found in the code.
CRM, content, and campaigns living in one product is exactly the pitch behind HubSpot's higher tiers, and comparison content in that category tends to get won or lost on one specific kind of honesty: is everything actually connected, or just co-located in the same navigation menu? That's a fair question to ask about Editor's CRM surface too, and the honest answer, checked directly against the code rather than assumed from the feature list, is a mix of both.
What's real and shipped
Editor has a genuine contacts and campaigns surface — frontend/apps/editor/src/app/(workspace)/contacts/page.tsx and campaigns/page.tsx render real admin components for managing contact records and campaign activity, backed by lib/crm/api.ts, which handles Go-backend-authenticated requests for CRM routes. This isn't a stub or a mock UI — it's a working contacts-and-campaigns management surface sitting inside the same workspace as the rest of Editor's tools, alongside the personalization and CSS-inlining infrastructure that campaigns actually send through.
What wasn't found, stated plainly
Here's the part worth being direct about: a natural-sounding claim for a platform like this would be that CRM contacts connect to the kanban task board — a lead comes in, a task gets created to follow up, that kind of pipeline. It's a reasonable thing to assume exists, and it's exactly the kind of integration a comparison piece would want to highlight. A direct grep across lib/crm/ and components/kanban/ for cross-references between the two found none. That doesn't prove with certainty that no connection exists anywhere in the codebase, but it means this piece isn't going to claim one, because the straightforward way to check for it came back empty.
Why stating the gap matters more than papering over it
The whole value of a comparison piece like this is specificity — telling you exactly what's connected and what's just sitting in adjacent parts of the same product. Claiming an integration that isn't there because it would make for a better pitch is the failure mode this kind of content is supposed to avoid. If you're evaluating Piskes specifically because you want contacts to flow into a task pipeline automatically, that's not a confirmed capability today, and it's better to know that going in than to discover it after building a workflow around an assumption.
What this actually adds up to
Contacts, campaigns, and content genuinely do live in one workspace, under one login, with real functioning tools behind each — that part of the "everything in one place" pitch holds up. What doesn't currently hold up, as far as this research could confirm, is a built-in pipeline connecting CRM activity to task management. Both things can be true at once, and describing them accurately — real surface, unconfirmed integration — is more useful than a pitch that blurs the two together.