# Growth or Advanced? Reading the Marketing Cloud Next edition boundary before you buy > One edition has a published price and the other does not. That asymmetry tells you more about how to run the decision than any feature grid will. - Source: https://synconai.com/insights/marketing-cloud-growth-vs-advanced - Publisher: SynconAI (https://synconai.com) - Desk: Marketing & Engagement - Author: SynconAI Delivery Team, Consulting & implementation - Published: 2 March 2026 - Updated: 29 August 2026 - Reading time: 8 minutes - Topics: Marketing Cloud, Editions, Pricing, Buying, Marketing Cloud Next ## Key points - Growth Edition is published at US$1,500 per org per month, billed annually. Per org, not per user, so adding marketers does not change the licence line. - The Advanced Edition price is not published. At buying time you are comparing capability against a quoted number you hold and nobody else does. - A feature grid is unusable when you are buying, because it asks you to predict which capabilities the work will need before the work is designed. - What forces the upgrade is operational complexity: separation, approval, data reach and orchestration. Test those against your own operation, not against a list. --- The Salesforce marketing [pricing page](https://www.salesforce.com/marketing/pricing/) publishes one number and withholds the other. Marketing Cloud Next Growth Edition is listed at US$1,500 per org per month, billed annually. Marketing Cloud Next Advanced Edition carries no published figure at all. That asymmetry is not an oversight, and it shapes the whole decision. One side of the comparison is a fact you can read this afternoon. The other is a number you will only hold after a commercial conversation. Any advice that pretends otherwise, including any blog that quotes you an Advanced price, is guessing. ::: warn Prices and packaging change. The US$1,500 figure is what Salesforce publishes for Growth Edition, per org per month, billed annually. Take the current numbers from the Salesforce pricing page itself, not from a consulting summary, this one included. ::: ## The price line that does not behave like Salesforce pricing Almost everything else you buy from Salesforce is priced per user per month. That single convention drives how organisations run the decision: count the seats, multiply, argue about who really needs one, and revisit the count every time the team changes shape. Growth Edition breaks that habit. It is published per org. A marketing team of two pays the licence line that a marketing team of twenty pays. Bringing an agency into the platform, or handing a second person the ability to build journeys, does not move the number. Two things follow, and they point in different directions. The first is who can afford to start. A per seat price puts a small marketing function off the platform entirely, because the tool costs what the team costs. A flat org price does the opposite: it sets a floor that a lean team clears as easily as a large one. The barrier moves from headcount to commitment. The second is that the usual sizing exercise produces nothing. There is no seat count to model, no ramp to negotiate, no per user discount curve to chase. The lever you are used to pulling is not attached to anything. What is left to decide is capability, which is the harder question, and the one most buying processes are worst at. ## Why the feature grid fails you at buying time The comparison table is the first thing everyone opens, and it is close to useless in the moment you actually need it. It asks you to predict which capabilities your operation will need, expressed in the vendor's vocabulary, about work you have not designed yet. Nobody can do that honestly. The grid answers the question *what is in each edition*. Your question is *will the thing my team does every Tuesday still work*, and no row in the table is written to answer it. It also ages. Edition contents move between releases; the shape of your marketing operation moves far more slowly. Anchoring a multi-year commitment to a table that will be rewritten twice before your first renewal is the wrong way round. The stable input is your own operation. ::: note Read the current comparison on the Salesforce [Agentforce Marketing](https://www.salesforce.com/marketing/) pages last, not first. It is the right document for confirming a decision and the wrong one for making it. ::: ## The threshold is complexity, not size What pushes a marketing operation past an entry level edition is rarely volume. It is how many things have to run in parallel without colliding. A team sending a great deal of mail to one audience, from one brand, on one approval path, is a simple operation running at scale. A team sending far less across four markets, with two legal entities, a compliance sign off and a segment that depends on service history, is a complex operation running small. The second one meets the edition boundary long before the first does. That is the reframe worth carrying into the meeting. Ask how complicated the work is, not how much of it there is. Four properties account for most of it. **Separation**, meaning how much has to stay apart: brands, markets, entities, sender identities, consent records, audiences that must never see each other's messages. **Governance**, meaning what has to be approved, by whom, with what evidence afterwards. **Data reach**, meaning how far outside the marketing tool a segment has to see. **Orchestration**, meaning whether journeys react to behaviour across channels or run to a schedule. ## The table: if this is true of your operation Not a feature list. A list of conditions that press on the edition boundary, and the question that tells you whether the condition is real. | If this is true of your operation | What it presses on | The question that confirms it | | --- | --- | --- | | More than one brand, market or legal entity sends from the same org | Separation of audiences, sender identity, consent and reporting | Who would see the wrong branding if two teams built a campaign on the same day? | | A send cannot go out without a documented approval | Governance, roles and an audit trail somebody outside marketing will ask for | Who can stop a send, and what happens when that person is on leave? | | Segments depend on data that does not live in the marketing tool | Reach into service history, entitlement, product usage or a unified profile | Where does the list come from today, and who exports it? | | Journeys react to behaviour rather than running to a calendar | Orchestration across channels and decisioning while the customer is present | What happens when two campaigns reach the same person on the same morning? | | Marketing operations has its own release process and test environments | Change control and the ability to fail somewhere that is not production | Where would you test a change to a live journey this week? | | Regulatory or contractual separation is imposed on you | Isolation that has to be demonstrable, not merely configured | Could you show an auditor which team could reach which contacts? | How to use it. None of these true, and Growth Edition is very likely the right starting point; the published price is the whole story and you can move on. One true, and it is worth probing before you sign, because a single hard requirement can carry the decision on its own. Two or more true, and you are having the Advanced conversation whether or not you wanted to, so start it early enough to get a quote you can actually evaluate. ## Questions that reveal the answer faster than a demo The table is the artefact. These are the questions we ask in the room, because the answers are usually already known and rarely written down. **Where does the segment come from?** If the honest answer is a spreadsheet somebody exports on a Monday, the data reach question is settled and the platform is not the only thing that needs work. Segments assembled outside the tool are a symptom of a data model problem that survives an edition upgrade untouched. That work deserves separating from the licence decision entirely, and the general shape of it is set out in the Salesforce [marketing automation guide](https://www.salesforce.com/marketing/automation/guide/). **What broke last time?** Every marketing operation has an incident it still talks about: the send that went to the wrong region, the offer that reached customers with an open complaint, the campaign nobody could stop. Whichever of the four properties failed in that story is the one to test hardest against the edition boundary, because it will fail again. **Who is accountable for a send after it has gone?** If the answer is a named person with a sign off they can produce, governance is a real requirement rather than a preference, and it deserves weight in the comparison. **What are you planning that you are not doing yet?** The edition has to fit the operation you will be running in twelve months. That is a forecast rather than an observation, so hold it lightly, but do not buy strictly for today either. ## The number nobody publishes Because the Advanced Edition price is not on the pricing page, the comparison at buying time is genuinely lopsided: a published figure on one side, a quote on the other, and no way for you or for us to model the gap in advance. That makes the conversation with your account executive the load-bearing part, so treat it as one. Take the conditions you marked in the table and ask what specifically changes at the boundary for each one, rather than asking for a feature list. Ask whether the Advanced line is priced per org as Growth is, or on a different basis, because that changes how the cost behaves as the team grows. And ask what it costs to move up later, in money and in rework, because that answer decides whether starting on Growth is a low risk beginning or an expensive detour. If you are still on the previous generation of the platform, the edition question is the second one. The first is the migration, which we covered in [Marketing Cloud Next against Engagement](/insights/marketing-cloud-next-vs-engagement). ::: tip Ask for the answers in writing. Editions and packaging change, and the record of what was described to you at signing is worth having at renewal. ::: ## What to do before you take the quote Four steps, in this order. Write down your operation against the four properties: separation, governance, data reach, orchestration. One page, produced by the people who run the sends rather than the people who sign the contract. Mark the conditions in the table that are true today, and separately those that will be true within a year. Keep the two lists apart, because a forecast should not be priced as a fact. Only then open the current edition comparison, and check it against what you wrote. You are confirming a decision at that point rather than making one. Then get the Advanced quote, and budget the implementation separately. The licence line is not the cost of the programme, which is the same trap we described for [Agentforce pricing](/insights/agentforce-pricing-and-implementation-cost): the published rate is the predictable part, and the data and process work underneath it is what decides your first year. The edition decision looks like a features question and is not. Per org pricing has already removed headcount from the argument. What is left is whether your operation is complicated enough to need the larger machine, and that is something you can answer about yourself, today, before anyone quotes you anything.