01
Platforms
What each of these platforms is actually good at
Seven tools I work in or get asked about, with the parts that get oversold named out loud. I take no vendor commission and have no licence to sell you.
02
Short answer
The platform is rarely the constraint. In most consumer businesses the messaging tool is capable of more than the team is asking of it, and what holds the program back is the data model underneath and the absence of anyone deciding what each customer should receive next. The tools are still genuinely different, though, and choosing wrong costs a year — so here is where each of them earns its licence fee.
Seven stances, and the reasoning
Years at Adobe on the vendor side of the martech table sit behind all of this — useful when I am negotiating on yours. What a platform genuinely does, what it is sold as doing, and how far apart those two things usually are is a lesson best learned from inside a vendor.
None of what follows is a scorecard. There is no commercial reason for me to prefer any of them, and where my view is shallower the entry says so.
Braze
The one I know best, and excellent at what it is for: real-time, event-triggered messaging across app, push, in-app, email and SMS. Canvas is the most workable orchestration surface in the category for a team that wants to build without an engineer in the room every time, and the latency is real.
Oversold as a customer data platform. Braze holds a profile, not a history, and the first time segmentation needs a question answered about behaviour over two years you are back in the warehouse, which is where the question belonged. Its predictive features are a convenience, not a substitute for a model fitted on your own data. And the commercial model rewards sending more, which is the opposite of the contact budget I would have you build.
Salesforce Marketing Cloud, and Data 360
Two things sold as one. Marketing Cloud Engagement — the old ExactTarget lineage — is deep and unglamorous, and inside a large regulated enterprise that depth is the point: it will do the awkward thing compliance needs, and there is somebody in every market who knows how. The newer Growth and Advanced editions on the Salesforce core platform are a different product with a different ceiling. Ask which one the demo was built in.
Data 360 is where the customer data and the segmentation now live, and it is the right answer when the rest of the business already runs on Salesforce — one shared data model earns its cost the moment service and sales read the same customer. Oversold as a substitute for having a data model: buying it does not settle the argument about what a customer is, it moves the argument into a new tool and attaches a licence fee to it.
Klaviyo
The best tool here for what it was built for: ecommerce lifecycle on a commerce platform it integrates with natively. Time from signing to a first revenue-producing flow is shorter than anything else on this page, and a small team can run a serious program in it unaided.
Oversold upward. A subscription business with contracts, entitlements and a warehouse buys it because the demo was quick, then spends two years discovering that the model underneath is an order and a product rather than a relationship over time. If your customer is a subscription rather than a basket, look hard before signing.
Voyado
The Nordic retail answer, and for a retailer a strong one. Tiers, points, member pricing and bonus cheques are there on day one; in a general-purpose platform each is a build, and a longer one than anyone scoped. The data model is retail-shaped from the start — customer, receipt, article — so a whole modelling project never happens. Engage and Elevate arrive as one suite, so on-site behaviour reaches the lifecycle programme without an integration project between them. The Nordic fit is in the plumbing: point-of-sale integrations that already exist, a GDPR posture built for this market, support in the team’s own language.
Built for retail, and the boundary is hard. Beyond retail — subscription, energy, media, marketplaces, which is most of the list I say I work with — the receipt-shaped view stops fitting and the data model starts working against you. Event-driven orchestration is weaker than Braze, custom modelling more constrained than a CDP with best-of-breed messaging on top, and outside the Nordics the partner ecosystem and hiring pool thin quickly. Score the agentic framing the way the audit scores any AI claim: the workflow, not the label. A Nordic retailer with a loyalty programme should usually look here first; if churn is a subscription problem rather than a repeat-purchase one, it is the wrong shape however good it is.
Iterable
The sensible middle: strong cross-channel journey building, a data model that tolerates more complexity than the ecommerce tools, and commercials that are easier to defend to a finance director than the top of the market. For a lot of mid-size consumer businesses it is simply the right answer.
Oversold as the decisioning layer. It builds journeys well. It is not where the logic that arbitrates between five teams competing for the same customer should end up living.
Customer.io
The one to want when engineering is already in the room. Event-driven by design, priced sanely, and pleasant to work in when the triggers come from your own product rather than a campaign calendar. Product-led businesses often get more out of it than out of tools costing twice as much.
Oversold as something a marketing team can own alone. It expects good events, and if nobody owns the event schema the program degrades quietly and nobody can say when it started. Brand and creative operations are thinner than in the enterprise tools.
Bloomreach
Strongest when the commerce side is bought with it. If search, merchandising and the customer data platform arrive as one purchase and the business is retail commerce, the joined-up version beats assembling the same thing yourself, and the analytics layer is more capable than its reputation.
Oversold outside retail commerce. The parts fit each other; they do not automatically fit a subscription business. This is the entry where my view is the shallowest of the seven, and I would say so in the room too.
- Deepest
- Braze
- Also daily
- Salesforce Marketing Cloud & Data 360
- Comfortable
- Klaviyo · Iterable · Customer.io · Bloomreach
- Nordic retail
- Voyado
- Data side
- Databricks · SQL · Python
- Commission
- None, from any of them
- Vendor side
- Years at Adobe, on the other side of the same table
03
How I would choose one
Four steps, in this order. Most selection processes run them backwards.
01
Write down the three hardest things
Not a feature list — the three journeys that are genuinely hard in your business. Every platform here does the easy eighty per cent more or less identically, so the easy eighty per cent tells you nothing.
02
Settle where the data will live
That answer decides more than the vendor shortlist does. A modest messaging tool on a warehouse everyone trusts beats a suite on a data model nobody agrees with.
03
Price the migration honestly
Two quarters of a team’s attention, plus everything that quietly stops working while it happens. That cost is real and it is almost never in the business case.
04
Then demo against your own worst case
Bring the awkward journey, not the one in the script. Vendors are all good at the script; the difference between them shows up in the awkward one.
04
Questions about tooling
Which one do you recommend?
Most of the time, the one you already own. Replacing a platform buys you two quarters of migration and a team that has lost track of its own program. When the tool genuinely is the constraint that shows up in the audit, or in the first two weeks of a program, with reasons attached.
Do you take commission from any of these vendors?
No vendor commission and no licence to sell you, which is the reason a page like this can exist. If that ever changes it will be written at the top of this page before it is written anywhere else.
We are mid-migration and it is going badly. Is that something you do?
Sometimes. The first thing worth establishing is whether the migration is the problem or the thing that exposed it, because most painful migrations are a data-model argument that was never had, arriving late. Project-managing the implementation itself is better done by the people already inside it.
Will you tell us to buy something?
Rarely, and never with a preference of my own attached. More often the answer is that what you already own does this and nobody has been shown how, or that the gap is a decision layer rather than a licence.
05
Related services
S1
Fractional Lifecycle Leadership
The retention seat, held from inside your organisation — including the person who writes the queries.
Ongoing, sized to the role
S2
Lifecycle & Retention Programs
Contact strategy, LTV tiering, churn prediction and orchestration — designed and built with your team, in your stack.
A quarter and up
S3
The AI Marketing Audit
Every team and workflow reviewed and scored for where AI creates leverage — and where it’s theatre.
Three weeks, fixed price
Down to two of these? Say which two — the answer takes an email, not a demo.hello@andersson.consulting
06
Available for new engagements
Start a conversation
If the timing fits, email me directly. There is no funnel behind it, and the reply comes from me.