What Must Be Written on the Order Form (and SI SOW) Before We Fund FDE-Led Agentforce: Max Entitlements, Flex Multipliers, Outcomes Definition, and CSAT Ownership?

What must be written on the Order Form (and SI SOW) before we fund FDE-led Agentforce: Max entitlements, Flex multipliers, outcomes definition, and CSAT ownership?

Max, Flex, outcomes, and FDE fees can stack on one Agentforce buy. The risk is not that partners sound confused. The risk is your Order Form and SI SOW leave the stack unsigned. Diginomica (Katy Ring, Sep 25 2026) reports Salesforce naming Max, Flex-style consumption, and Service outcomes while SIs still struggle to price a three-to-five-year Agentforce commitment. Put the unknowns on paper before you fund the FDE motion.

What Diginomica and Salesforce say

Salesforce Max is the large predictability SKU. Nick Johnston, EVP Global Partnerships at Salesforce, told Diginomica that most customers still run seat-based pricing, that new bundles exist for high-consumption customers, and that Salesforce Max is the largest SKU for customers who want predictability with built-in consumption entitlements. Max also opens most of the Salesforce portfolio for broad adoption. Johnston also describes pure consumption options for predictability. This article does not invent a Max dollar amount, a Flex multiplier table, or a claim that Max is a published Flex Credits Rate Card line. Sibling Max editions context: Core / Advanced / Max editions

Outcomes pricing starts in Service, customer by customer. Johnston says Salesforce is introducing outcomes pricing, starting with customer service, so clients can pay per resolution. He calls outcomes "the most straightforward pricing approach" and says Salesforce is trying to do more of it, including via the Fin acquisition for similar Service options. Service outcomes pricing, per Johnston, is based on a customer contact resolution or a deflection (where the query is passed to the customer to solve themselves). There is typically an agreed approach to outcome data and KPIs. It is offered customer by customer, not as a universal list SKU in this interview.

Partners still need pricing clarity for multi-year Agentforce. Diginomica reports SIs concerned that it is hard to give clients certainty on Agentforce costs across a three-to-five-year contract. Johnston agrees partners need more clarity and says Salesforce is creating tools such as calculators and price sheets. Stephanie Sadowski (Accenture, Global Salesforce Business) told Dreamforce analysts that FDEs are scarce and that charge-out rate and pay-scale decisions are hard; what she needs from Salesforce is pricing clarity.

FDE Partner Network is real and growing. Nia Samady, Salesforce VP Global Partner Success, told Diginomica the FDE Partner Network now has 84 partners with 800+ verified practitioners and has run more than 65 workshops across GSI, RSI, and other partner sizes. Certification mixes knowledge assessment and FDE readiness in an account; practitioners attend a two-day workshop and become verified practitioners visible on AgentExchange. Samady says the FDE motion is intentional as a standalone motion that will expand beyond Agentforce. Diginomica source

CSAT ownership is still a handoff problem. Diginomica notes academic research that agents in customer service can hurt CSAT when agent-to-human handoff is full of friction. Khoa Le, Salesforce VP PM for Agentforce Service and AI, told Diginomica that human-to-human connection remains strategic end to end, that some customers will chase deflection and shorter handle time, and that professional services partners can help craft a better end-to-end experience. That is a CSAT and SOW ownership question, not a rate-card row.

Different line, same Proof Gap: Headless Platform Interaction (HPI) Flex Credits stay TBA on a separate Usage Type. See HPI TBA decoder

Decision rule for Director+ teams

1. Own the stack on the Order Form and SI SOW. Before funding FDE-led Agentforce, write Max entitlements (what is included), Flex multipliers or ceilings for any consumption lines you will use, the outcomes definition (resolution vs deflection, measurement window, dispute path), SI/FDE rates and change-order rules, and who owns CSAT when handoff fails. Do not treat partner confusion as the blocker; treat unsigned stack risk as the blocker.
2. Refuse unsigned outcomes. If outcomes pricing is on the table, require a written definition of resolution vs deflection, the KPI method, and who pays when the agent hands off mid-journey. Customer-by-customer means nothing binds until your paper says it.
3. Refuse open-ended Flex with no ceiling. If Flex Credits or related consumption sits beside Max or seats, demand written multipliers or a hard ceiling for the period you are funding. Sibling buy-model context: Flex Credits buying models and AELA vs Flex Credits
4. Refuse an FDE SOW without rate clarity. Scarcity of FDEs is the partner's problem to staff. Your problem is a signed rate card, role definition, and what happens when Salesforce pricing tools or Max/outcomes packaging move mid-term.
5. Name Max as predictability packaging, not as a Flex line you invent. Do not list Max as a published Flex Credits Rate Card usage type in this decoder. Ask what entitlements Max actually includes for your org on the Order Form.
6. Assign CSAT ownership before go-live. If deflection is the billed outcome, write who owns CSAT, rework, and escalation when the agent fails the handoff. Put it in the SI SOW, not in a slide.
7. Use a three-to-five-year lens. Diginomica's SI concern is multi-year certainty. If your SOW or Order Form cannot state how Max, Flex, and outcomes behave across that window, you are funding hope.

Eight-Seat Read (lite): who refuses what until the paper is signed

1. Procurement / Finance: refuses to fund Max + Flex + outcomes + SI/FDE fees until entitlements, multipliers or ceilings, outcomes definition, and FDE rates are on the Order Form and SOW.
2. CRO: refuses margin and capacity plans that assume Agentforce unit cost is "predictable" while outcomes stay customer-by-customer and Flex lines lack a written ceiling.
3. RevOps: refuses a hard Wallet / Flex forecast for the FDE-led build until consumption lines and any outcomes measurement window are written.
4. CS leader: refuses an outcomes or deflection KPI that bills the company while CSAT ownership on failed handoff is unassigned.
5. IT / Security: refuses production cutover for FDE-built agents until identity, data scope, and commercial change-notice paths sit beside the SOW.
6. Partner / SI owner: refuses an FDE SOW that lacks rate clarity, role definition, and a change-order path when Salesforce packaging or partner tools move.

Vendor claim score

/5: Johnston's claim that outcomes are the "most straightforward" approach and that Max delivers predictability with built-in consumption entitlements, versus Diginomica's record that outcomes are customer-by-customer and that SIs still cannot lock Agentforce certainty across three-to-five-year contracts. Predictability on the slide is not the same as predictability on your Order Form.

Confidence block (what is true from this source)

1. Max / outcomes detail here is interview framing, not a rate-card row. Johnston's Max and outcomes description comes via Diginomica partner/executive interview. Do not treat it as a Flex Credits Rate Card line item or a published list price.
2. FDE 84 partners / 800+ verified practitioners / 65+ workshops are Samady VP quotes via Diginomica, not an audited Salesforce rate sheet.
3. Diginomica premier-partner conflict: Diginomica discloses premier-partner relationships in its coverage ecosystem. Weight quotes as reported speech, then demand Order Form and SOW text from your own AE and SI.
4. No invented $/multipliers in this decoder. No Max list price, no Flex multiplier table, and Max is not listed here as a published Flex Credits usage type.
5. Outcomes scope in this piece: Service Cloud / customer service start, resolution or deflection, customer by customer.

Why we might be wrong

1. Salesforce calculators and price sheets land fast enough that SI three-to-five-year uncertainty shrinks before your next renewal.
2. Max entitlements on your Order Form actually cap the consumption pain you care about.
3. Outcomes stay Service-only long enough that Sales/other clouds are not in scope for your buy.
4. Your SI already prices FDE as value-based managed services with board-level cover, so rate clarity is less of a blocker than Diginomica's broader SI sample implies.

Quick compare

1. Salesforce Max: Large SKU framed for predictability with built-in consumption entitlements (Johnston via Diginomica). Ask what is included on your Order Form. Not treated here as a published Flex Credits Rate Card line.
2. Flex / consumption: Pure consumption options and Flex-style burn still need written multipliers or ceilings beside any Max or seat buy. Sibling: Flex Credits buying models
3. Outcomes (Service start): Pay per resolution; also deflection. Customer by customer. Write resolution vs deflection, KPIs, and dispute path before you fund.
4. SI / FDE fees: Separate from Salesforce packaging. Require rate clarity, role definition, and change orders. Network size (84 / 800+) does not replace your SOW.
5. HPI Flex Credits (TBA): Different Usage Type, same Proof Gap pattern. HPI TBA decoder

Sources

1. Diginomica, Salesforce and the SI - partners want pricing clarity as the FDE Partner Network becomes established (Katy Ring, Sep 25 2026): Diginomica
2. Sibling Max editions decoder: Core / Advanced / Max
3. Sibling Flex buy models: PayGo vs precommit vs prepurchase
4. Sibling AELA vs Flex: AELA vs Flex Credits
5. Sibling HPI TBA (different line, same Proof Gap): HPI TBA

Soft CTA

If you want the next Agentforce Order Form decoder and the weekly receipts before the AE and SI call, subscribe