Accellum
Closed beta — opening in Q3

ABM platform for the solo
B2B marketer

Segment your account base across three axes — RFM, lifecycle and engagement. Connect your CRM, get 5–7 working segments with ready playbooks in a week.

Нажимая кнопку, вы соглашаетесь с Политикой обработки ПДн. Адрес используется только для приглашений в beta, без рекламной рассылки.

amoCRM · Bitrix24 · Yandex.Metrika · 152-FZ — data in Russia · YooKassa

A solo marketer in B2B already juggles everything. We take half the routine off your plate.

Three-axis segmentation in one place. 5–7 working segments, each with its own playbook, applied to your data a week after CRM connection.

RFM

1 — 5

Recency · Frequency · Monetary

  • 555Champions
  • 455Loyal
  • 344Promising
  • 211At-risk
  • 111Dormant

Lifecycle

6 stages

Markov chain of states

  • NewJust arrived
  • TrialPilot / demo
  • ActiveRegular usage
  • At-RiskDeclining activity
  • DormantGone quiet
  • ChampionExpansion

Engagement Score

0 — 200+

Weighted sum of events

  • open+ 1
  • click+ 3
  • lesson+ 5
  • webinar+ 10
  • demo+ 20
  • consult_request+ 30

What's inside

Every feature is built for one marketer running ABM solo — no agency, no separate analytics team.

Before

Importing your base — a full day's work

After

CSV or OAuth for amoCRM / Bitrix24

Field mapping is remembered; incremental syncs via webhook. Deduplication by email hash so one contact doesn't split across two accounts.

Before

Analytics — an Excel sheet

After

Ready-made segments and playbooks

RFM + lifecycle + engagement = 5–7 named segments (Champions, At-Risk, Pricing Visitors). Each ships with a 3–4 step playbook.

Before

Drafting a hypothesis — an hour per email

After

AI generation via YandexGPT

Get 3 email/campaign drafts based on the segment and touch history. PII is never sent to the prompt — we swap it for tokens on our side.

Before

A/B testing — needs a second list

After

Built-in multi-armed bandit

Run 2 variants of one playbook step — the system reweights traffic to the winner automatically. Segment metrics and significance in one view.

Before

Attribution — nothing makes sense

After

Yandex.Metrika + behavioural signals

Connect Yandex.Metrika to pull intent data: pricing visits, downloads, > 3 visits in a row. Each event boosts the engagement score on the spot.

Before

Marketing consent — a separate ordeal

After

152-FZ out of the box

Consents, processing log, RTBF within 30 days, audit log with an HMAC chain. Ready-to-sign DPA for every customer of yours.

Out-of-the-box connectors — only services that operate in Russia
amoCRMCRMBitrix24CRMYandex.Metrikaweb analyticsYandex.AudiencesadsVK AdsadsYooKassapaymentsDaDataenrichmentUniSender GoemailTelegram Bot APInotificationsYandexGPTAIGigaChatAI fallback

Data hosted in Russia. By law, not by claim.

  • · Hosting: Yandex Cloud, ru-central1 region, AES-256-GCM encryption with keys in Yandex KMS.
  • · Contact emails and phones stored as HMAC hashes with per-tenant salt.
  • · 152-FZ: registered with Roskomnadzor; processing policy published in advance.
  • · Audit log with a tamper-evident HMAC chain — every PII operation is logged irreversibly.
  • · DPA for every corporate customer; bespoke DPA available on the Pro plan.
PII processing policy →

Frequently asked

We're running a closed design-partner phase right now (5 companies, free of charge, direct line to the engineers). After that — invite-only beta for 50 customers. Public beta is targeted for Q3. Exact dates land in the email after you join the waitlist.

Ready to try? Join the waitlist.

Invites roll out in waves of 50. The earlier you sign up, the sooner you get access.

Нажимая кнопку, вы соглашаетесь с Политикой обработки ПДн. Адрес используется только для приглашений в beta, без рекламной рассылки.