ivorycomBook a demo

Blog

Writing about how revenue work actually gets done.

Category names move faster than the practices behind them. These pieces take one comparison at a time and work through what genuinely differs, what is marketing, and what it changes for a team on Monday morning.

Latest writing

  • Comparison

    Traditional CRM vs AI CRM: what actually changes

    Almost every CRM now claims AI. The claim is easy to make and hard to evaluate, because the interesting difference is not a feature list — it is which work the software will do when nobody is looking at it.

    6 min read

What we write about

Three threads, chosen because they are where teams most often buy the wrong thing: the difference between a CRM that stores and one that interprets, the difference between measuring traffic and reading intent, and the operational question of how much execution you are willing to delegate to software.

  • Comparisons that name what is actually different, not just which product wins.
  • The operational consequence — what changes in the daily work, not only in the feature list.
  • Explicit limits: where a signal stops being reliable and judgment has to take over.

Start from a topic instead

AI CRMWhat makes a CRM an AI CRM, and where the AI is allowed to actBuyer intentFirst-party and third-party signals, and how to score themVisitor intentReading website behaviour as revenue signal, privatelyRevenue operationsThe four handoffs where revenue actually leaks

See it on your own records.

The comparisons in these pieces are easiest to judge against data you already have opinions about.