AI CRM: what each sales step does and costs

An AI CRM add-on is worth paying for when the seat that includes it matches the step you want automated, and your records can feed it. As of October 2026, the Dynamics 365 Sales pricing page lists Sales Professional at USD 65 per user per month, paid yearly, and that card does not include Copilot. Enterprise at USD 105 adds Copilot summaries, email and meeting help, and access to prebuilt agents. Premium at USD 150 adds 1,000 Copilot Credits, Sales Insights, recommended actions, and enrichment. Prebuilt agents and custom agents built in Copilot Studio need Copilot Credits on Enterprise and Premium, and only Premium includes the 1,000-credit allotment.

The same month, Salesforce Sales Cloud lists Core at USD 195 per user per month and says AI can be added to Core and above. HubSpot's prospecting agent is priced at USD 1 for each lead it recommends outreach for, on top of HubSpot Credits. Odoo does not sell a separate CRM AI SKU: Agentic AI is a Custom-plan item, shown at US$ 61.00 and US$ 76.20 per user per month. The rest of this page walks capture, scoring, drafting, forecasting, and service, and names the license, the data, and the person who should accept the output.

What each seat includes before you add credits

Treat the seat price as the cover charge. Consumption pricing is the second bill, and it is easy to miss on a card that only shows the user fee.

• Dynamics 365 Sales Professional (US list, as of October 2026: USD 65 per user per month, paid yearly · What the public card ties to AI: Core sales force automation, Microsoft 365 interoperation, reporting, and dashboards. Copilot is absent from the card.)
• Dynamics 365 Sales Enterprise (US list, as of October 2026: USD 105 per user per month, paid yearly · What the public card ties to AI: Copilot in Dynamics 365, natural language insights, email and meeting assistance, opportunity summaries, and access to prebuilt agents such as Sales Close Agent. Agents still need Copilot Credits.)
• Dynamics 365 Sales Premium (US list, as of October 2026: USD 150 per user per month, paid yearly · What the public card ties to AI: Everything in Enterprise, plus 1,000 Copilot Credits, Sales Insights, recommended actions, and data enrichment.)
• Salesforce Sales Cloud Free, Starter, Pro (US list, as of October 2026: USD 0, USD 25, and USD 100 per user per month · What the public card ties to AI: These editions sit below the line where the page says AI can be added.)
• Salesforce Sales Cloud Core and above (US list, as of October 2026: Core USD 195, Advanced USD 395, Max USD 550 per user per month · What the public card ties to AI: AI can be added to Core and above. Check the live comparison table for which items are included and which are add-ons.)
• Odoo Standard (US list, as of October 2026: US$ 31.10 and US$ 38.90 per user per month · What the public card ties to AI: Agentic AI is not on this plan.)
• Odoo Custom (US list, as of October 2026: US$ 61.00 and US$ 76.20 per user per month · What the public card ties to AI: Agentic AI, Odoo Studio, multi-company, and external API.)

Prices: Microsoft, Salesforce, Odoo. Salesforce says its page is informational and subject to change. Odoo's footnote says the discount is valid for 12 months for the initial users ordered. The page shows two rates on each card and does not label which rate is yearly billing. These are US list figures. If you buy in Canada, ask the vendor for the CAD amount on the quote. Microsoft Relationship Sales, which bundles Sales Enterprise with LinkedIn Sales Navigator, is listed as variable with a 10-seat minimum and no public price.

Assume eight people need a CRM seat, all on the same plan, at the October 2026 yearly Dynamics rates. Professional is 8 times USD 65, or USD 520 per month. Enterprise is 8 times USD 105, or USD 840 per month. Premium is 8 times USD 150, or USD 1,200 per month. The step from Professional to Enterprise is USD 320 per month (USD 3,840 per year) and is the step that puts Copilot on the card. The step from Enterprise to Premium is USD 360 per month (USD 4,320 per year) and is the step that includes 1,000 Copilot Credits per user, so eight Premium licenses include 8,000 credits before anyone buys more. The Sales pricing page does not state how often that allotment refreshes.

The same eight seats on Salesforce Core are 8 times USD 195, or USD 1,560 per month, before any Agentforce consumption. On Odoo, eight Standard users land at 8 times US$ 31.10 (US$ 248.80) or 8 times US$ 38.90 (US$ 311.20). Eight Custom users, the plan that lists Agentic AI, land at 8 times US$ 61.00 (US$ 488.00) or 8 times US$ 76.20 (US$ 609.60). The gap between the lower pair is US$ 239.20 per month. The gap between the higher pair is US$ 298.40 per month. That gap buys the Custom bundle, which also includes Studio, multi-company, and the external API, so it is wider than an AI line item.

What capture features read, and what they send outside the CRM

Capture is the step where a feature fills a blank: a summary of an account, a news blurb, a sourced contact, or a field that was empty yesterday. Each product reads a different pile of data, and one of them sends a name off the CRM.

Copilot in Dynamics 365 Sales can only get information from records and files the signed-in user already has access to, per the Copilot overview. Included capabilities cover contextual insights and recommendations, lead and opportunity summaries, meeting preparation summaries, email summaries and reply drafts, and natural language chat. If a rep cannot open the opportunity, Copilot cannot summarize it for that rep. That is a useful limit for a 40-person firm with shared accounts: a junior coordinator does not suddenly see margin fields they were locked out of.

Microsoft's Sales Copilot FAQ says customer data is not used to train Azure OpenAI or other language models for this Copilot, and that data is not saved in a new data store. Account news is the exception to keep in a security review: the feature sends the account name to Bing. If your account names are themselves sensitive (a codename for an unannounced program, a government buyer), ask Microsoft whether account news can be turned off or limited to certain users before you enable it for the team.

Opportunity and account summaries come from a predefined field set. Admins can change which fields are summarized, capped at the top 15 fields, and that choice is organization-wide. You do not get a private summary layout per team. If finance wants margin in the summary and sales leadership wants it left out, one of those groups loses. Pick the 15 fields in a workshop, write them down, and review a summary against a live opportunity before you train the team to trust the paragraph.

HubSpot's prospecting agent researches accounts, monitors buying signals, sources contacts (including through ZoomInfo, Apollo, and Surfe), and drafts outreach. The price on that page is USD 1 for each lead the agent recommends outreach for. It is available on Starter, Professional, and Enterprise and runs on HubSpot Credits. A customer line on the HubSpot agent builder page says "It used to take 15 to 20 minutes to find the information we needed and copy it into HubSpot. Now it takes seconds with a custom agent in agent builder." That line describes a lookup-and-copy task. It does not say whether the copied fields were right. Judge that on ten accounts you already know.

Odoo 19's standard Ask AI agent can answer questions, open views, translate, summarize chatter, generate a follow-up, improve a draft, and suggest next steps. Odoo's AI documentation is explicit that this agent cannot make database changes: it cannot create leads or alter data. For capture, that means Ask AI can draft the note and cannot file the lead. A person still creates the record. AI fields are a separate path: they generate or suggest a value from the record, existing data, or external information after a user clicks the AI icon. A scheduled action that is on by default runs once a day and fills empty text and property AI fields. Adding an AI field through Studio may change the database's pricing plan, which is how a Standard database can get pulled toward Custom without a separate AI SKU on the quote.

What predictive scoring demands before the model is useful

Scoring is the feature most often sold as a time saver, and it is the one with a hard data floor. Microsoft's predictive lead scoring setup requires at least 40 qualified and 40 disqualified leads created and closed inside the training window. That window can be set from three months to two years. A Sales Enterprise license includes 1,500 scored records per month. The model can still be published if accuracy is below Microsoft's AUC threshold, and Microsoft says it will perform poorly.

Do the arithmetic on your own history before you buy the seat for scoring. You need 80 closed outcomes, split evenly between qualified and disqualified, inside the window you choose. A team that only marks leads qualified, and deletes the rest, will not meet the disqualified half. A team that has 30 closed leads in two years will not meet the count at all. Publishing anyway is allowed. The score will still appear on the form, and reps will treat a number on a form as guidance. That is the expensive failure mode: you paid for Enterprise or Premium, the model is weak, and the number still shows up in the morning meeting.

The 1,500-record monthly cap matters once volume is real. Assume a busy month with 2,000 leads that qualify for scoring. Enterprise covers 1,500 of them. A 2,000-lead month is 500 above the 1,500 Enterprise inclusion. Ask Microsoft which records are left out when you cross that cap. If your inbound is lumpy (a trade show week, a product launch), ask that question against a peak week, not an average one. Premium is the edition whose card lists Sales Insights and recommended actions. Enterprise is the edition whose scoring documentation states the 1,500 cap. Confirm on your tenant which cap applies to the license you are quoted, because the public scoring article states the Enterprise figure.

For Dynamics, the practical prep is the same work as ordinary CRM lead scoring: consistent qualified and disqualified reasons, a closed date that means the same thing on every lead, and enough of both outcomes to train. CRM data hygiene is the week you spend before you publish a model, so the 40 disqualified leads are real losses and are free of duplicate companies.

What a draft may send, and what stays a suggestion

Drafting is where the feature writes words a customer might read. The products differ on whether a person sees the text first.

HubSpot says every enrollment can be reviewed and edited before AI-drafted emails send, and that a team can later switch to a fully autonomous mode that sends without review. The prospecting agent page poses the buyer question "Can I review and edit outreach emails before they are sent?" The product answer is yes, until someone turns autonomous mode on. For a 20 to 100 person firm, leave the review step on for the first month and name who is allowed to flip the switch. Autonomous send plus a USD 1 fee per recommended lead means a bad segment spends money and reaches customers you did not intend to email. Put the sales manager who already approves outbound in that decision. When the list includes existing customers, include the COO.

Odoo keeps the edit step in the product. Send as Message and Log as Note open an editable pop-up before anything is sent or logged. Ask AI can improve a draft and generate a follow-up. It still cannot create the lead or change the record by itself. That split is the right default for a team moving off a shared inbox: the software proposes the sentence, the rep sends it, and the CRM does not grow a lead the rep never confirmed.

Microsoft splits the work across two Copilots, described in the Sales Copilot FAQ. The Sales agent in Microsoft 365 Copilot works with Dynamics 365 Sales and with Salesforce CRM. It can draft sales emails grounded in CRM data, capture meeting takeaways, and update relevant CRM fields from Microsoft 365 apps. The in-app Copilot summarizes records, prepares meetings, fetches account news, and answers questions, and it works with Dynamics 365 Sales only. If your CRM is Salesforce and you want the Microsoft 365 side, you are looking at the Sales agent, and you still need a Salesforce seat that can hold the fields it writes. If your CRM is Dynamics, decide which surface the reps live in. Reps who live in Outlook will meet the Sales agent. Reps who live in the Sales app will meet the in-app Copilot. Training both surfaces in the same week is how drafts get ignored.

Included Copilot email help on Dynamics is a draft, in the same family as reply drafts and email summaries. Pair it with a rule your team can follow: nothing leaves the company until the rep who owns the account has read it. The license does not enforce that rule. Your send process does.

What summaries and meeting prep can and cannot see

Forecasting in a small sales team is usually a weekly meeting, a stage, an amount, and a close date. The AI features in this set help that meeting by summarizing the record. They do not replace the stage definitions you already argue about.

On Dynamics, opportunity summaries and meeting preparation summaries are part of the included Copilot list on the pricing page for Enterprise and Premium. The summary is only as current as the fields in the top-15 set, and only as visible as the signed-in user's security role. A forecast call that depends on a custom delivery-risk field will ignore that risk if the field is outside the 15. Put delivery risk inside the set, or stop expecting it in the paragraph the manager reads on Sunday night.

Natural language chat lets a manager ask questions of records they can already open. A useful question depends on filled fields: stage, close month, and the date of the last activity. Empty next-step fields produce a paragraph with nothing behind it. Fill those fields before you coach managers to ask the chat in the forecast meeting.

Salesforce's pricing page shows included Flex Credits of 500K, 1M, and 2.75M per organization per year on the three highest columns of the Built-in AI table. Keep those three pools attached to the upper editions on that table, and confirm the column on the live page when a rep quotes a number. The line you can budget from today: AI can be added starting at Core, and Core lists at USD 195 per user per month. Pro Suite at USD 100 sits below that line on the same page.

Odoo summaries of chatter are an Ask AI action, read-only with respect to the database. A manager can ask for a recap of the thread. The recap does not move the stage. If your forecast depends on stage plus a probability field, keep those as manual fields with a definition your team wrote down. An AI field can suggest a value, and the daily job can fill an empty text field, which suits a last-touch summary and is a poor place for a commit amount. Keep the daily job off any figure your board reads.

What agents and credits cost after the seat is paid

The seat gets you in the door. Agents and enrichment draw from a second meter, and unused units expire.

Microsoft's Sales pricing FAQ says 1,000 Copilot Credits are included with each Dynamics 365 Sales Premium license. Extra credits are pay-as-you-go or prepaid Copilot Credit Commit Units. A footnote says Copilot Credits are required to run prebuilt agents and custom agents built in Copilot Studio. The Sales pricing page does not publish a dollar price per extra Copilot Credit. Before you sign Enterprise because the card mentions Sales Close Agent, ask the quote to show the credit estimate for that agent and the unit price. Eight Premium licenses include 8,000 credits. Eight Enterprise users include none of that allotment and can still run agents if you buy credits. For a team that wants summaries and email drafts and does not want an agent writing into opportunities, Enterprise is the card that matches the work. For a team that wants the agent, Premium's included credits are the number to test against a month of real use.

Salesforce lists Agentforce Flex Credits at USD 500 per 100,000 credits. An illustrative rate on the same page is 40 Flex Credits for USD 0.20. Unused Flex Credits do not roll over. There is no overage penalty: usage past the entitlement bills monthly in arrears at the contracted rate. The same page lists an Agentforce user license at USD 5 per user per month, conversations at USD 2 per conversation, flat-fee access at USD 125 per user per month, and help-agent resolutions at USD 2. Flex Credits and conversation pricing cannot be used in the same org. The USD 5 user license, the USD 125 flat fee, and help-agent resolutions at USD 2 are other prices on that page, listed separately. On the eight-user example, the USD 5 line is USD 40 per month and the USD 125 line is USD 1,000 per month. A quote should show each line you are being asked to buy, and it should use either Flex Credits or conversation pricing, not both.

HubSpot usage features such as Customer Agent, Prospecting Agent, and Data Agent consume HubSpot Credits, according to the credits article updated 16 September 2026. Unused credits expire each usage period and do not roll over. If only included credits are used up and no extra capacity pack was bought, usage-based features pause until reset or a purchase. Overage on the linked rate is USD 0.010 per credit, invoiced in increments of 10 credits, which is USD 0.10 per 10-credit block. A Marketing Hub Professional subscription comes with 3,000 included HubSpot Credits. The same article uses 5,000 included credits as the figure in an Enterprise example. Credits follow the highest subscription tier and are not added across hubs. Only paid seats and Partner Seats can spend credits.

Put a HubSpot month on paper before you enable the agent. Assume the prospecting agent recommends outreach for 40 leads a week. Over four weeks that is 160 recommendations, and the published per-lead fee is USD 160, before the credits those actions also consume. Ask HubSpot to price a week of your own enrollments in credits and in the USD 1 fee, on one quote. A Marketing Hub Professional subscription is the example HubSpot uses for 3,000 included credits. Credits follow the highest subscription tier and are not added across hubs. The prospecting agent consumes HubSpot Credits and pauses when the included credits on the subscription are used up and no capacity pack was bought. The sales manager should see that credit balance next to the list size.

HubSpot's agent-builder FAQ says agent builder (formerly Breeze Studio) is included in Starter, Professional, and Enterprise, that workflows do not consume credits, and that custom agents do consume credits measured in action units. The same page shows a buy button at USD 7 per month that grants access to additional marketing, sales, and service software. Treat USD 7 as the price of that extra software bundle on the button. Confirm the invoice line before you budget it as CRM AI.

Odoo Custom is the plan that lists Agentic AI, at the two US rates above. Standard users get the apps on that card and do not get Agentic AI. If an admin adds AI fields through Studio, ask whether the database's plan changes before the field goes live. Odoo.sh hosting is extra on top of the user price. The pricing page does not list a per-action dollar figure to set next to HubSpot's USD 1 or Salesforce's USD 500 per 100,000 credits.

What a service reply costs and who accepts the send

Service is the step after the sale: a reply on a case, a help resolution, or a prebuilt agent working a customer the rep already knows. The pages above price that work. They leave the accept step to you.

HubSpot groups Customer Agent with Prospecting Agent and Data Agent as usage features that consume HubSpot Credits. The same pause rule applies: when included credits are used up and no capacity pack was bought, the feature pauses until the period resets or you buy more. Have the person who owns the customer read a service reply before it sends. The credits article does not describe a required approval click for Customer Agent, so that read has to be your rule. Ask HubSpot to show, on one of your cases, which records the draft is grounded in.

Salesforce lists help-agent resolutions at USD 2 on the Agentforce pricing page, next to conversations at USD 2 per conversation. Those are separate lines. Flex Credits and conversation pricing still cannot be used in the same org, so the quote has to say which meter a help agent draws. A customer-facing resolution should wait for the service owner who already handles that account.

Dynamics prebuilt agents and agents built in Copilot Studio need Copilot Credits on Sales Enterprise and Sales Premium. Only Premium includes 1,000 credits with the license. Where the agent runs as Copilot in Dynamics 365 Sales, it can read records and files the signed-in user can already open. Name the account owner as the person who accepts anything the customer will see.

Who may accept a write back into the CRM

Separate a draft from a write. A draft sits in a window until a person sends it. A write changes a field other people will report on.

• Dynamics in-app Copilot summaries, meeting prep, email drafts, chat (What the product does: Reads records the user can access. Drafts replies and summaries. · Who should accept it: The rep who owns the account reads anything that will be sent. Summaries stay read-only unless someone copies them into a field.)
• Microsoft Sales agent field updates from Microsoft 365 (What the product does: Can update relevant CRM fields from Microsoft 365 apps, for Dynamics 365 Sales or Salesforce. · Who should accept it: Microsoft does not describe a required approval step for that update. Name an owner in your process: the rep on the meeting, with a manager spot-check of a sample each week.)
• HubSpot prospecting enrollments (What the product does: Review and edit before send, or a later switch to autonomous send. · Who should accept it: Keep review on until a named manager accepts autonomous mode for a named segment.)
• Odoo Ask AI send or log (What the product does: Opens an editable pop-up. Cannot create leads or alter data on its own. · Who should accept it: The user in the pop-up. Do not add a second automation that logs the note unattended.)
• Odoo AI fields (What the product does: A click fills a suggestion. A daily job fills empty text and property AI fields. · Who should accept it: A process owner reviews newly filled fields for a week, then decides whether the daily job stays on.)
• Dynamics predictive score (What the product does: A number on the lead after the model is published, including a weak model. · Who should accept it: The sales manager decides whether a below-threshold model is allowed to show. Default: do not publish it.)

The Sales agent line is the one to brief your security and sales leads together. It can update CRM fields from the apps reps already live in. That is convenient after a Teams call, and it is how a wrong close date lands in the forecast without a form save. For the first 30 days, export a sample of fields the agent touched and have the opportunity owner confirm them. If the sample is clean, widen it. If it is full of guessed next steps, turn the update off and keep the email draft.

Odoo's daily AI field job is easier to underestimate because it is on by default. It only fills empty text and property fields, so it will not overwrite a rep's note. It will fill a blank next-step field with a suggestion that then looks typed by a person in the pipeline review. Decide which fields are allowed to be empty, and which blanks should stay blank until a person types them. Amount, stage, and close date belong in the second group.

HubSpot's autonomous mode is a switch, which makes the rule easy to write down. Review stays on. Put the switch with a manager, and only for a list that manager built. The USD 1 fee is a reason to keep the list short, alongside the customer-facing risk.

How to decide which feature to pay for

Score each candidate feature on four tests: the step it serves, the license that turns it on, the data it must already have, and the person who accepts the output. If any test fails, leave the feature off and keep the cheaper seat.

1. Name the step. Capture and meeting prep are served by Dynamics Enterprise Copilot and by Odoo Ask AI. Scoring, on Dynamics, needs the closed-lead history and stays inside the Enterprise cap of 1,500 scored records per month. Outbound research is the HubSpot prospecting agent at USD 1 per recommended lead plus credits. Service replies are HubSpot's Customer Agent on credits, Salesforce help-agent resolutions at USD 2, and Dynamics prebuilt agents that need Copilot Credits on Enterprise and Premium.
2. Match the seat. Dynamics Professional at USD 65 does not put Copilot on the card. Enterprise at USD 105 does, without the 1,000 credits. Premium at USD 150 includes the credits. Salesforce AI starts, on the pricing page, at Core for USD 195. Odoo Agentic AI sits on Custom, at US$ 61.00 and US$ 76.20, and Studio can move a database onto a higher plan when you add AI fields.
3. Test the data on your tenant. For Dynamics scoring, count qualified and disqualified closes in the window you would set. If you are short of 40 and 40, do not publish. For summaries, list the 15 fields and check them on ten live opportunities. For HubSpot, run a small enrollment and read the drafts against the accounts you know.
4. Name the person who accepts the output. The account owner reads every email before it sends, and also confirms a weekly sample of field updates the Sales agent wrote. A process owner reviews newly filled Odoo AI fields for the first week. A manager, and only that manager, may turn on autonomous HubSpot send for one segment after the review month.

A CRM implementation that sequences those four tests will spend the first phase on fields, security roles, and closed-lead reasons, and only then enable the Copilot or agent that matches the phase. Teams already on Dynamics 365 Sales can scope the same choice as a Dynamics 365 Sales rollout: which roles need Enterprise, which need Premium, and which can stay on Professional because they never open a summary.

Two buying mistakes show up in the price pages themselves. The first is buying Premium for every user because one manager wants Sales Insights. Credits are included per Premium license, and Copilot reads only what that user can access, so a warehouse coordinator with a Premium seat does not make the forecast summary better. License the people who read and write opportunities. The second is treating a credit pool as a sunk cost you should burn. Flex Credits do not roll over. HubSpot credits expire and then pause the feature. Copilot Credits beyond the Premium allotment are a separate purchase with no unit price on the Sales card. Turn on one agent, read a month of consumption, and then decide whether the second agent earns its meter.

If your CRM also feeds inventory, billing, or a project plan, the sales summary is only half the picture. The operational question is which writes are allowed to cross into those records. Keep that decision with the same acceptor list above, and have the demo run on a copy of your data with security roles intact.

How Flectic can help

Flectic implements Dynamics 365 Sales for sales teams of 20 to 100 people that sell through long, considered cycles and fix the forecast in a spreadsheet before each board meeting. A fixed-price first phase delivers a working pipeline before you commit the full budget. Microsoft lists Sales Professional at $65 per user a month, a license cost separate from Flectic fees. Book a free discovery call with Flectic and compare the Dynamics 365 Sales implementation with your license total.

Sources

• Dynamics 365 Sales pricing, Microsoft, October 2026
• Copilot in Dynamics 365 Sales overview, Microsoft Learn, October 2026
• FAQ about Copilot in Dynamics 365 Sales, Microsoft Learn, October 2026
• Configure predictive lead scoring, Microsoft Learn, October 2026
• Salesforce Sales Pricing, Salesforce, October 2026
• Salesforce Agentforce Pricing, Salesforce, October 2026
• AI Prospecting Agent for Sales Teams, HubSpot, October 2026
• Manage HubSpot Credits, HubSpot, October 2026
• Easily Build Custom AI Agents | Agent Builder, HubSpot, October 2026
• Odoo Pricing, Odoo, October 2026
• AI, Odoo 19.0 documentation, Odoo, October 2026
• AI fields, Odoo 19.0 documentation, Odoo, October 2026