---
title: Recommendation engine vs. next-best action
url: https://markin.ai/compare/recommendation-engine-vs-next-best-action
kind: category
description: A recommendation engine surfaces the right content. Next-best action chooses the right commercial treatment. Why relevance is not revenue.
updated: 2026-09-03
---

# Recommendation engine vs. next-best action

> A recommendation engine predicts which item or content a user will engage with and ranks by relevance. Next-best action selects the commercial treatment,  an offer, a save, a channel, a hold, that maximises expected incremental revenue for a sized opportunity. A rec engine answers 'what should we show'; an NBA answers 'what is worth doing, and what is it worth'. The two are complementary, not substitutes.

## In short

- Recommendation engine: What should we surface to this user next? Output: A ranked list of items by predicted engagement or relevance.
- Next-best action: Which action is worth taking for this customer, and what is it worth? Output: One chosen action per customer, including a deliberate hold.
- A rec engine ranks items by predicted engagement; it attaches no revenue value, margin or cost to the action behind the recommendation.
- The intelligence layer sizes the revenue opportunity behind it, the action layer chooses whether to recommend, to offer, to save or to hold, and the whole loop is measured against control.

## What each layer is

**Recommendation engine**, A system that predicts and ranks the items, content or products a user is most likely to engage with, using collaborative filtering, content models or embeddings.

Answers: What should we surface to this user next?

**Next-best action**, A layer that sizes the commercial opportunity for a customer and selects the treatment,  message, offer, channel, timing or hold, that maximises expected incremental revenue.

Answers: Which action is worth taking for this customer, and what is it worth?

## Side by side

|  | Recommendation engine | Next-best action |
| --- | --- | --- |
| Question it answers | What should we surface to this user next? | Which action is worth taking for this customer, and what is it worth? |
| Primary input | Item features, interaction history, user embeddings, catalogue metadata. | Opportunities, uplift models, margins, costs, contact history, constraints. |
| Primary output | A ranked list of items by predicted engagement or relevance. | One chosen action per customer, including a deliberate hold. |
| Usual owner | Product, data science. | Growth, data science, revenue leadership. |
| How it's measured | Click-through rate, take rate, watch time, relevance. | Incremental revenue and ARPU against a holdout. |

## Why a great recommendation can leave revenue on the table

Recommendation engines optimise engagement within a fixed catalogue. Relevance is not value: the most relevant next item is rarely the highest-value commercial action, and a rec engine has no concept of margin, cost or when not to act.

- A rec engine ranks items by predicted engagement; it attaches no revenue value, margin or cost to the action behind the recommendation.
- It cannot surface a commercial opportunity nobody modelled,  an upgrade, a save, a reactivation, because its output space is the catalogue.
- It cannot decide to hold: there is always a next-best item, even when no item has positive expected value.
- Its impact is measured on take rate and engagement, not on incremental revenue against a control group.

## Where Markin fits

Markin treats the recommendation as one candidate action among many. The intelligence layer sizes the revenue opportunity behind it, the action layer chooses whether to recommend, to offer, to save or to hold, and the whole loop is measured against control.

- **Recommendations become a candidate, not the answer.** A rec engine's output is one input to the decision; the action layer compares it against a save, an upgrade or a hold and picks the highest expected incremental value.
- **Ranked by revenue, not relevance.** Actions are selected on expected incremental revenue net of margin and cost, so the highest-value move wins the customer's attention even when it is not the most relevant item.
- **Hold is a first-class output.** When no action has positive expected value, the decision is to do nothing, something a rec engine, which always returns a next item, cannot express.

Next: [Next-Best Action](https://markin.ai/solutions/next-best-action)

## When Markin is not the right answer

- Your only commercial lever is surfacing content, and engagement is the business model: there is no treatment selection problem to solve.
- Your catalogue has no commercial action behind it, so there is nothing to size in revenue terms.
- You cannot connect a recommendation to an outcome, so the loop cannot be validated against control.

## FAQ

**Is a next-best action system just a recommendation engine?**

No. A recommendation engine predicts the next item a user will engage with. A next-best action system sizes the commercial opportunity for a customer and chooses the treatment,  offer, save, channel, hold, that maximises expected incremental revenue. The rec engine answers 'what to show'; the NBA answers 'what to do, and what is it worth'.

**Can a recommendation engine do retention?**

It can recommend content that keeps a user engaged, which indirectly helps retention. It cannot decide who is worth saving, with which treatment, at what cost, or who to leave alone, those are commercial decisions that need uplift, margin and cost, not relevance.

**Do the two compete?**

No. They are complementary. A recommendation engine is a strong candidate-action source; the next-best action layer decides whether to recommend, to offer something commercial, or to hold, and proves the choice against a holdout.

**How is Markin different from the decisioning or AI already inside recommendation engine?**

A decisioning engine ranks actions a human already defined, inside the campaign surface it was given. Markin forms the hypotheses itself,  marketing, product, pricing or a technical anomaly holding growth back, sizes them, executes them inside recommendation engine and your product surfaces, and reads each one against a randomised holdout. It behaves like a data science and growth team, not like an optimiser.

**Does Markin only test messages and offers?**

No. Anything a human growth scientist would investigate is in scope: onboarding friction, feature adoption, pricing and packaging, dunning, and technical health issues such as a checkout error rate or a broken deeplink quietly killing conversion. Marketing is one of four hypothesis domains, not the boundary.

**What is the business case for adding Markin on top of recommendation engine?**

On the assumptions preloaded above, 5.0M customers at 14 a month, a small move in ARPU is a large number in absolute terms, because it applies to the whole installed base every month rather than to a campaign. Across Markin deployments the verified range on treated cohorts is +17% to +35% ARPU against a randomised holdout. The point is not more messages: it is finding the highest-value action per customer, launching it, and proving it against control before it scales.

**How long before it pays for itself?**

First sized opportunities are in test within six weeks and the first holdout-verified result lands inside 90 days. Payback depends on your base, margin and programme cost, the calculator on this page computes it from your own numbers, after applying the 20% to 40% haircut BCG finds when next-best-action programmes are incrementality-tested.

Source: https://markin.ai/compare/recommendation-engine-vs-next-best-action