Field service management software pricing for 30 technicians

For a US shop with 30 Dynamics 365 Field Service users, Microsoft’s US list price as of October 2026 is USD 105 per user per month, paid yearly. That is USD 37,800 a year, and USD 113,400 over three years, before tax, for those 30 licenses alone. Resource Scheduling Optimization, office users, Business Central, Copilot credits, and implementation sit outside that total. The same 30 users are listed at CAD 142.50 per user per month in Canada, or CAD 51,300 a year before tax. Odoo’s Field Service app is EUR 0 until a second app is installed, and ServiceTitan does not publish a 30-technician price.

The rest of this page prices one crew three ways: Dynamics 365 Field Service, Odoo, and a trades product such as ServiceTitan or Jobber. Each column keeps the technician license, the scheduling add-on, the back office, payments, and implementation on separate lines. A single per-technician sticker is the wrong number to take to a budget meeting.

What a 30-technician list price includes and leaves out

Use a fixed crew so the columns stay comparable. The base case is 30 W-2 technicians who each need a full product login. Dispatchers, CSRs, and finance staff are extra people until you count them. External technicians are a different license, and only when the vendor’s description matches how you pay them.

Three published patterns show up on the vendor pricing pages:

1. Microsoft posts a US dollar list and a Canadian dollar list, both paid yearly, and tells you the page is informational.
2. Odoo posts euros, with Field Service free while it is the only app, then a per-user fee once you install another app.
3. ServiceTitan, FieldPulse, and Jobber (past 15 users) ask you to request a price. Jobber is the exception through 15 included users, where a full USD grid is public.

Microsoft’s own warning belongs next to every total below. The US Field Service page says prices are informational and may not match checkout because of currency, country, and regional variant factors. Treat the arithmetic as list math you can audit, then replace it with the checkout quote before you sign.

Per technician, the US Field Service list is USD 1,260 a year (USD 105 times 12). Canada is CAD 1,710 a year (CAD 142.50 times 12). Those two unit costs are the floor for a full user. The rest of the bill sits in the sections that follow.

Dynamics 365 Field Service list price for 30 users

As of October 2026, the US Field Service pricing page lists three paid items that matter for this crew. Field Service is USD 105 per user per month, paid yearly. Field Service Contractor is USD 50 per user per month, paid yearly, described as a way to assign and manage external frontline technicians. Resource Scheduling Optimization is USD 30 per resource per month, paid yearly. Footnote 1 on that page says the RSO price assumes a single tenant.

The Canadian Field Service pricing page lists the same three items in Canadian dollars, each plus applicable tax: CAD 142.50, CAD 67.80, and CAD 40.70.

• Field Service user, per month, paid yearly (United States: USD 105 · Canada: CAD 142.50)
• Contractor user, per month, paid yearly (United States: USD 50 · Canada: CAD 67.80)
• Resource Scheduling Optimization, per resource per month, paid yearly (United States: USD 30 · Canada: CAD 40.70)
• 30 full users, one year, no RSO (United States: USD 37,800 · Canada: CAD 51,300)
• RSO on all 30 resources, one year (United States: USD 10,800 · Canada: CAD 14,652)
• Three years, 30 users, no RSO (United States: USD 113,400 · Canada: CAD 153,900)
• Three years, 30 users plus RSO on all 30 (United States: USD 145,800 · Canada: CAD 197,856)

The yearly figures are 30 times the monthly list times 12. The three-year figures multiply those yearly totals by three. They assume the list does not change, every one of the 30 is a full Field Service user, nobody in the office is licensed, Copilot credits are excluded, tax is excluded in the US column, and Canadian tax is extra. This is list arithmetic from those monthly rates. Microsoft’s checkout price can still differ, which the pricing page says in its own informational note. A shorter product-only breakdown sits on our Dynamics 365 Field Service pricing page. This article keeps going into the office, the books, and the other products.

Price every named user who is not an external technician at the full Field Service rate. The Contractor price is for external frontline technicians. If six of the 30 are external and Microsoft accepts them on Contractor, the US mix is 24 times USD 105 plus 6 times USD 50, which is USD 2,820 per month, or USD 33,840 per year. That is USD 3,960 a year under the all-full-user figure of USD 37,800. Ask Microsoft, in writing, whether each of those six people qualifies before you book the saving. A W-2 technician stays at USD 105 in the budget until that confirmation exists.

Dispatchers and CSRs who work inside Field Service are full users in this budget, at USD 105 or CAD 142.50, on the same basis. A cheaper back-office SKU is not published on the Field Service price page.

What scheduling, mobile, and Copilot add

Manual scheduling is already in the Field Service license. Microsoft’s product overview describes the schedule board and the schedule assistant as part of the product. The mobile app for iOS, Android, and Windows is also part of that description, including offline download, photos, video, and a digital signature. The pricing page does not list a separate mobile fee per technician. Footnote 3 on the pricing page limits one mobile note to the Contractor plan, so read that footnote against any Contractor quote before you assume the external crew has the same mobile terms as a full user.

Resource Scheduling Optimization is the add-on that changes the yearly number. The RSO overview describes it as a separate paid add-in, priced on the number of resources whose schedules are optimized. It can run overnight, during the day, for a single resource, and for emergency work. You do not have to put all 30 technicians on it. Ten optimized resources at the US list are USD 300 per month, or USD 3,600 per year. All 30 are USD 10,800 per year on top of the USD 37,800 user total, and USD 32,400 over three years on top of the USD 113,400 user total.

A practical split for many HVAC and electrical shops is to optimize the maintenance crew and leave the install crew on the schedule board. Assume 18 of 30 technicians are on RSO. US cost is 18 times USD 30 times 12, which is USD 6,480 per year, or USD 19,440 over three years. Canada is 18 times CAD 40.70 times 12, which is CAD 8,791.20 per year. The single-tenant footnote still applies.

Copilot credits are a third Microsoft line, and the dollar amount is not on the Field Service pricing page. Microsoft says credits are required to run prebuilt and custom agents, sold as prepaid Copilot Credit Commit Units or pay-as-you-go, and that an Azure subscription is required to use agents. Ask for a credit estimate in the same quote as the user licenses. Leaving the line off the spreadsheet makes the USD 37,800 look more complete than it is.

Business Central if the books stay in Microsoft

Dynamics 365 Field Service does not publish a finance or general-ledger user on its pricing page. If the office needs a Microsoft ledger, inventory, and payables, that is Dynamics 365 Business Central, priced separately as of October 2026. Business Central Essentials is USD 80 per user per month, paid yearly. Premium is USD 110. Team Members is USD 8 for limited access. Premium is described as Essentials plus service management and manufacturing. That service-management module is not the Field Service application. Buying Premium does not remove the USD 105 Field Service user.

Canadian Business Central list prices are not part of this comparison. A Canadian firm that wants both products should ask Microsoft for the Canadian Business Central figure and keep it on its own line, plus tax, beside the CAD 142.50 Field Service user.

Worked US mix. Assume 30 W-2 technicians, 2 dispatchers, and 3 CSRs who all work in Field Service, plus 4 finance users who only post in Business Central Essentials. Field Service seats are 35. RSO covers the 30 technicians and not the office.

• 35 Field Service users at USD 105 (Monthly list: USD 3,675 · Yearly list: USD 44,100 · Three-year list: USD 132,300)
• RSO for 30 resources at USD 30 (Monthly list: USD 900 · Yearly list: USD 10,800 · Three-year list: USD 32,400)
• 4 Business Central Essentials users at USD 80 (Monthly list: USD 320 · Yearly list: USD 3,840 · Three-year list: USD 11,520)
• License total (Monthly list: USD 4,895 · Yearly list: USD 58,740 · Three-year list: USD 176,220)

Each yearly cell is the monthly cell times 12, and each three-year cell is the yearly cell times three. The license total is the sum of the three lines. It excludes tax, Copilot credits, Contractor substitutions, Team Members, and implementation. Team Members at USD 8 is a Business Central limited-access license. It does not stand in for any of the 35 Field Service users.

The same 35 Field Service users in Canada are CAD 59,850 per year (35 times CAD 142.50 times 12). RSO on 30 resources adds CAD 14,652. Together that is CAD 74,502 per year, or CAD 223,506 over three years, plus applicable tax, before any finance users and before implementation.

Odoo is the opposite subscription shape, covered below: one user fee covers the apps on the plan you bought, once you have left the free single-app plan. Microsoft is two products stacked. Firms that also live in the pipeline, with agreements and repeat customers, usually need the office system designed with the board. That is a CRM implementation for the people who book and invoice the work, scoped beside the technician licenses.

Odoo when Field Service is the only app

Odoo’s Field Service app page says the app is free forever with unlimited users, and that you pay only if you install more applications. The pricing page’s One App Free plan is EUR 0 for one app and unlimited users on Odoo Online. For a crew that can live inside Field Service alone, the subscription for 30 technicians is EUR 0. Hosting on Odoo Online, support, and upgrades come with the subscription. Implementation does not.

The free plan ends the day invoicing, inventory, or accounting is installed. Every paying user then sits on Standard or Custom. A paying user, on Odoo’s pricing page, is someone with backend access to create, view, or edit documents, or an employee record in the HR app with no linked user. Portal users such as customers are not paying users. An employee who reports expenses or a timesheet is given as a paying user. Technicians who complete jobs in the back office, and office staff who edit invoices, both count once a second app is in place.

As of October 2026 the pricing page shows euros only. There is no USD or CAD list on that page. Keep these Odoo figures in euros until you have a quote in your currency. On the yearly control, Standard is shown as EUR 19.90 and EUR 24.90 per user per month. The monthly figures rendered with that card show EUR 24.90 and EUR 31.10. Custom is shown as EUR 35.90 and EUR 44.90 on the yearly control, and EUR 44.90 and EUR 56.90 on the monthly figures. The footnote says the discount is valid for 12 months for the initial users ordered. Odoo.sh hosting is not included in the subscription. Standard cannot use custom modules. Custom is required for Odoo Studio, multi-company, an external API, and Odoo.sh or on-premise.

A Light User is listed at EUR 7.90. The pricing FAQ says light-user capabilities include Field Services, My Planning, and Inventory Barcode Operator. Getting that license requires a meeting with an Odoo advisor and a custom quote, and the EUR 7.90 line does not say whether it is per month or per year. The three-year totals below do not use Light User. Put technicians on it only after the advisor names the people and the billing period.

Worked Standard total, with the assumptions written out. Assume Field Service plus invoicing, so One App Free no longer applies. Assume 30 technicians and 6 office staff are all paying users, 36 in total. Assume the yearly control is the contract you buy: the discounted EUR 19.90 applies to those initial users for the first 12 months, and EUR 24.90 applies for each of the next two years. All 36 people sit on Standard, none on Light User or Custom, and every figure stays in euros.

• Year 1 (Rate used: EUR 19.90 per user per month · Users: 36 · Subscription: EUR 8,596.80)
• Year 2 (Rate used: EUR 24.90 per user per month · Users: 36 · Subscription: EUR 10,756.80)
• Year 3 (Rate used: EUR 24.90 per user per month · Users: 36 · Subscription: EUR 10,756.80)
• Three-year subscription (Subscription: EUR 30,110.40)

Year 1 is 36 times EUR 19.90 times 12. Years 2 and 3 are 36 times EUR 24.90 times 12. The three-year cell is the sum. It excludes implementation, in-app credits, and any Odoo.sh fee. In-app credits called out as excluded are SMS, contact autocomplete, lead generation, and document scan. If you add users after the initial order, confirm whether they receive the 12-month discount. The footnote ties that discount to the initial users ordered.

If the same 36 people need Custom because you want Studio, a second company, an external API, or Odoo.sh, the yearly-control pair is EUR 35.90 for the discounted first year and EUR 44.90 after that. Year 1 is 36 times EUR 35.90 times 12, which is EUR 15,508.80. Each later year is 36 times EUR 44.90 times 12, which is EUR 19,396.80. Three years of subscription is EUR 54,302.40, still before hosting beyond Odoo Online and before implementation. Our Odoo Field Service pricing page stays on the Odoo card alone. The gap that matters at 30 technicians is the jump from EUR 0 to a per-paying-user plan the moment the second app is installed.

Implementation that Odoo prices and Microsoft does not

Odoo’s pricing page puts the buyer’s question in plain language: "Where can I get implementation services, and how much does it cost?". The Success Packs page answers with hours for companies that buy packs directly. Odoo says companies under 50 employees usually buy Success Packs directly, and companies over 50 employees usually use a partner. A shop with 30 technicians can fall on either side of that line. Thirty technicians plus 15 office and warehouse staff is 45 employees. Thirty technicians plus 25 office, warehouse, and admin staff is 55. Count employees, not trucks, before you assume a pack is how you will buy the work.

New-customer pack prices as of October 2026:

• Starter (Price for a new customer: EUR 499 · Consultant hours: 4)
• Basic (Price for a new customer: EUR 2,635 · Consultant hours: 25)
• Standard (Price for a new customer: EUR 4,675 · Consultant hours: 50)
• Custom (Price for a new customer: EUR 8,415 · Consultant hours: 100)
• Pro (Price for a new customer: EUR 16,830 · Consultant hours: 200)

The 15 percent new-customer discount applies to the first pack only. Returning-customer prices on the same page are EUR 587.06, EUR 3,100, EUR 5,500, EUR 9,900, and EUR 19,800 for those five packs. Onsite travel time and expenses are extra. Extra monthly charges apply for maintenance of extra modules. The subscription already excludes maintenance of custom code.

A 4-hour Starter pack cannot cover a 30-technician cutover with parts, pricebook, and invoicing. A 50-hour Standard pack is a defined block of consulting. Your pricebook and dispatch rules may need a larger pack or a second one. A 200-hour Pro pack is the largest published new-customer block, at EUR 16,830. Add that Pro pack to the Standard subscription example above and the three-year cash outlay is EUR 30,110.40 plus EUR 16,830, which is EUR 46,940.40, before travel, credits, and any later packs. Add it to the Custom subscription example and the sum is EUR 54,302.40 plus EUR 16,830, which is EUR 71,132.40, on the same exclusions. Those sums are list arithmetic on published pack prices. They are not a configured project for your pricebook.

Microsoft does not publish a Dynamics 365 Field Service implementation fee or a week count for 30 technicians. The license totals earlier in this article stay silent on purpose. Ask each bidder to price data migration, the schedule board, mobile, integrations, training, and the period after go-live as its own line. A single monthly fee labeled per technician hides which of those lines you can drop.

For a crew this size, the first phase that holds up in production is usually the board, the mobile job, and invoicing the completed work. Memberships, a deep pricebook, and a second trade can follow once dispatch is stable. We scope that sequence on our field service implementation work: who is licensed, which jobs move first, and what the office still does in the old system during the overlap.

ServiceTitan, Jobber, and FieldPulse when the grid stops

ServiceTitan’s pricing page says the company sells per technician and names three packages: Starter, Essentials, and The Works. The page calls out dispatch, scheduling, call booking, invoicing, and pricebook. Every package button is Request Pricing. No dollar amount, minimum technician count, or implementation fee is published there. The page says "Our per-technician pricing is designed to fit your business and goals, at any size." The demo form asks you to "Select Number of Techs" and asks "Do you have at least one full-time office employee?" Answer both with your real counts. Scheduling Pro, Dispatch Pro, and Field Pro are separate products, so a package name alone does not tell you the scheduling stack you will pay for.

ServiceTitan also says it is trusted by over 100,000 contractors and claims a 15 percent average yearly increase in revenue. Those are the company’s statements. They are not a substitute for a quote at 30 technicians. A useful budget request lists 30 technicians, the office headcount, whether memberships and a flat-rate book are in year one, which Pro products you are being sold, contract length, and implementation as its own figure. If the quote comes back as one monthly number, ask for the split before you compare it with USD 37,800 or with Odoo’s euro subscription.

Jobber is the trades tool with a public USD grid, and that grid ends before this crew. The Jobber pricing page states that all prices are in USD and exclude sales tax. For the Plus plan that includes 15 users, the page shows USD 699 per month with no commitment, USD 599 per month on a 1-year commitment, and USD 529 per month billed annually. Plus is described as "For teams who want to scale complex operations with greater control across jobs, crews, and revenue." Fifteen users at the annual prepaid rate is USD 6,348 per year (USD 529 times 12), or USD 19,044 over three years if that rate held. That figure is the published 15-user plan.

The team-size control for 16 or more people says Contact Sales. Jobber’s user cards also say: "A user is anyone who accesses your account at the office or in the field to view or manage the team’s schedule. Add users for $29/mo each." That USD 29 line is what the included-user cards say. It was not confirmed as the rate on a 30-user contract. Do not multiply 15 included users plus 15 extra users and call the result Jobber’s price. A dispatcher who only views the schedule is still a user under that sentence, so the Contact Sales count is everyone in the office and the field who opens the account, not the number of trucks.

Jobber add-ons on the same page, as of October 2026: Marketing Suite USD 99 per month, AI Receptionist USD 29 per month, and Pipeline USD 49 per month. Card processing is 2.9 percent plus USD 0.30. Tap to Pay is 2.7 percent plus USD 0.30. US bank (ACH) payments are 1 percent. Two-way texting is listed for the United States, Canada, and the United Kingdom. ACH is listed as available in the US. On a USD 500 card payment, 2.9 percent is USD 14.50, plus USD 0.30, which is USD 14.80. The same invoice on Tap to Pay is USD 13.80. On ACH at 1 percent it is USD 5.00, where ACH is available. On USD 500,000 a year of card volume, 2.9 percent is USD 14,500 before the per-payment USD 0.30, against USD 6,348 a year for the published 15-user Plus plan. Put an estimated annual card volume next to any Jobber quote so the processing line is visible.

The annual prepaid plan is billed up front, and the initial payment is non-refundable if you cancel during the year. A monthly 1-year commitment keeps billing through the 12-month term if you cancel early. Plus includes dedicated onboarding described as a USD 599 value. Lower plans list limited onboarding sessions and a data-import line valued at USD 499. The free trial is 14 days of Grow features with no credit card. None of those onboarding values is a published implementation fee for 30 users.

FieldPulse says pricing is seat-based and customized, including a 21 to 30 employee band on the quote form. Its page states: "FieldPulse is seat-based. You purchase a set number of seats upfront for your contract term." No seat price is published. Treat it as a written quote, with seats, term, and services separated, in the same way you treat ServiceTitan.

Salesforce is the priced enterprise list buyers meet on the same search. The Salesforce field service pricing page lists Dispatcher at USD 175 per user per month and Technician at USD 175 per user per month. Contractor Plus is USD 80, Field Service Plus is USD 230, and Agentforce 1 Field Service is USD 650. Prices are described as informational and subject to change. The Salesforce pricing page does not state an annual commitment, and CAD is not among the currencies it lists. Thirty technicians at the USD 175 per-user monthly list come to USD 63,000 over twelve months (30 times USD 175 times 12) before any dispatcher. The page does not say whether an annual commitment applies. For a 30-technician HVAC or electrical firm, price Field Service, Odoo, or a trades suite when one of those matches the work. The Salesforce list is here so a USD 175 quote has a source.

Three-year picture for a budget meeting

Keep the rows in the same order when a vendor sends a proposal back. Where the table says quote, the vendor page has not published a dollar amount.

• 30 full users, one year (Dynamics 365 Field Service: USD 37,800 US list, or CAD 51,300, paid yearly, before tax · Odoo: EUR 0 on One App Free while Field Service is the only app · Jobber or ServiceTitan: Jobber’s published Plus annual rate is USD 529 per month for 15 users. 16 or more is Contact Sales. ServiceTitan is Request Pricing.)
• Scheduling add-on (Dynamics 365 Field Service: Schedule board included. RSO is USD 10,800 per year if all 30 resources are optimized, or less if fewer resources are on it. · Odoo: No separate optimization price is published on the Odoo pricing page. · Jobber or ServiceTitan: ServiceTitan’s Scheduling Pro, Dispatch Pro, and Field Pro are separate products. Jobber does not publish a 30-user scheduling surcharge.)
• People in the office (Dynamics 365 Field Service: Full Field Service price if they use that app. Finance users are extra Business Central seats, USD 80 Essentials on the US list. · Odoo: A second app puts every paying user on Standard or Custom. The 36-user Standard example is EUR 30,110.40 over three years on the rates assumed above. · Jobber or ServiceTitan: Jobber counts office and field as users. ServiceTitan asks whether you have at least one full-time office employee.)
• Payments and credits (Dynamics 365 Field Service: Copilot credit unit price is not on the Field Service page. An Azure subscription is required for agents. · Odoo: In-app credits are excluded from the subscription. · Jobber or ServiceTitan: Jobber card rate 2.9 percent plus USD 0.30. ServiceTitan processing is not on the pricing page.)
• Implementation (Dynamics 365 Field Service: No published Field Service implementation fee. · Odoo: New-customer packs from EUR 499 for 4 hours to EUR 16,830 for 200 hours. Companies over 50 employees usually use a partner. · Jobber or ServiceTitan: ServiceTitan publishes no implementation fee. Jobber Plus describes onboarding as a USD 599 value, not a 30-user project price.)
• Three-year license floor you can compute (Dynamics 365 Field Service: USD 113,400 for 30 US users with no RSO and no office. USD 145,800 with RSO on all 30. The worked 35-user mix with RSO and 4 Essentials users is USD 176,220. · Odoo: EUR 0 if you stay on one app. EUR 30,110.40 on the Standard example. EUR 54,302.40 on the Custom example. Packs are additional. · Jobber or ServiceTitan: Not computable from the public pages at 30 technicians.)

Read the Dynamics column as US list arithmetic unless the row says CAD. Read the Odoo column as euros. A US or Canadian Odoo budget needs Odoo’s checkout or a written quote in your currency. The Jobber 15-user annual figure of USD 19,044 over three years is not a 30-technician price. Putting it in the same cell as USD 113,400 would invent a discount Jobber has not published.

How to choose for an HVAC or electrical crew

The choice follows the system you need in year one, which is something you can settle before the demos start.

Choose Dynamics 365 Field Service when the board, the mobile job, and agreements have to sit in Microsoft, and you accept a second product for the ledger. For a single-entity shop, Essentials at USD 80 is the finance seat to price first. Premium at USD 110 is the seat when you also need Business Central’s manufacturing scope. It still does not replace Field Service. Budget the US three-year license floor at USD 113,400 before you add RSO, office people, Business Central, credits, and implementation. In Canada, start at CAD 153,900 for the 30 users before RSO and tax.

Choose Odoo when you want the work order, the invoice, and the stock move on one per-user subscription, and you can live with euros until a local-currency quote arrives. Stay on One App Free only if you are sure a second app is not required. The moment accounting or inventory is installed, price every paying user. Standard is the plan while you do not need custom modules, multi-company, an external API, or Odoo.sh. Custom is the plan when you do. Implementation for a firm under 50 employees can start from a published pack. Odoo says companies over 50 employees usually use a partner. Still require the same line-item split, and bring the scope sheet here if you want that project scoped.

Choose a trades suite when the pricebook, memberships, and call booking are the point of the purchase and you are willing to run a quote process. ServiceTitan does not publish a 30-technician total. Jobber’s public grid stops at 15 users. FieldPulse does not publish a seat price. Use the quote when it splits technician licenses, office users, Pro or add-on products, payment rates, contract terms, and implementation. A single monthly fee with a technician count in the label cannot sit next to the tables above.

Quotes and a flat-rate book are commercial design of their own. If the office sells agreements from a structured price list, include that work in the phase plan, the way a sales implementation for quoted work would, so the technician’s invoice matches what the CSR sold.

Use the same scope sheet for every finalist:

1. List every person who will open the system, with role: technician, external technician, dispatcher, CSR, purchaser, accountant.
2. Mark which of the 30 technician schedules must be optimized in year one.
3. Say whether the ledger and inventory are in this project or stay where they are.
4. State US only, Canada only, or both, and which currency the contract must use.
5. Ask for mobile, payments, texting, and credit packs as their own lines.
6. Ask for implementation hours, travel, and the post-go-live window as their own lines.
7. Ask what happens to the price at renewal, and what you forfeit if you cancel in the first year.

Bring the completed sheet to a vendor, or to us. A 30-technician firm is large enough that the add-on and the implementation decide the three-year number, and small enough that a phased first release is still the sensible way to start.

How Flectic can help

Flectic implements Field Service on Dynamics 365, and for 30 technicians the license line is only part of the bill. Flectic sends a written proposal with a fixed price for each phase before work starts. See Microsoft Dynamics 365 implementation for how Flectic scopes that first phase. Book a free discovery call with Flectic to scope the technician count.

Sources

• Dynamics 365 Field Service pricing (United States), Microsoft, October 2026
• Dynamics 365 Field Service pricing (Canada), Microsoft, October 2026
• Overview of Dynamics 365 Field Service, Microsoft Learn, October 2026
• Overview of Resource Scheduling Optimization, Microsoft Learn, October 2026
• Dynamics 365 Business Central pricing, Microsoft, October 2026
• Odoo Pricing, Odoo, October 2026
• Odoo Field Service, Odoo, October 2026
• Odoo Success Packs, Odoo, October 2026
• ServiceTitan Pricing and Plans, ServiceTitan, October 2026
• Jobber Pricing, Jobber, October 2026
• FieldPulse Pricing, FieldPulse, October 2026
• Salesforce Field Service and Operations Pricing, Salesforce, October 2026