Salesforce for energy services companies: from tender to renewal

21 September 2026
Arcsen

Energy services and engineering companies in the Gulf and Egypt sell to a short list of large buyers: utilities, government entities, industrial groups and developers. Work arrives as a tender, becomes a contract for years of operation and maintenance, and earns its margin at renewal. Yet the tender calendar often lives in a spreadsheet, the contract terms in a shared drive, the asset register in the ERP and the crews’ work on paper, so the account manager walks into a renewal meeting without knowing which of the client’s chillers are overdue for service.

Salesforce can carry the whole cycle, provided you decide early which system owns each record. This guide covers what Energy & Utilities Cloud adds for utilities and energy retailers, how tender to renewal maps to the core clouds, and what to settle with the ERP and asset systems.

Energy & Utilities Cloud, or the core clouds?

Energy & Utilities Cloud is one of Salesforce’s industry clouds, used by electric, gas and water utilities, retail energy suppliers and renewable energy companies, in Salesforce’s words. It adds self-service enrolment that checks service availability and activates contracts, multi-site quoting that splits a bulk configuration into individual orders, tariff comparison against time-of-use plans, industry CPQ for homes and businesses, order management including switching, work and asset management, incident management, clean energy programmes and contractor portals, plus Agentforce agents that answer complex customer questions and automate approvals. Its MuleSoft integration asset has templates to create customers, contracts, premises and service points, request meter readings, rebills and billing adjustments, and retrieve bills, payments and balances.

So the choice is fairly clear. If you sell or distribute energy and bill customers at premises and meters, the industry data model saves you building one. An energy services company, engineering contractor or equipment maker selling projects and maintenance contracts to businesses will do most of its work in Sales Cloud, Revenue Cloud, Service Cloud and Field Service, and needs the industry cloud only where premises, service points or meter data enter the process.

From tender to renewal, stage by stage

We model each tender as an opportunity with its own record type, stages and deadlines, and each award as a contract the delivery team works from:

Stage	On Salesforce	Decide early
Account plan	An account plan per major buyer in Sales Cloud: objectives with metrics, a SWOT analysis, priorities and competitors	Which accounts get one, and who owns it
Tender	An opportunity per tender: portal reference, clarification and closing dates, bid bond, and a bid or no-bid approval	Who can commit the company to a bid
Proposal	Quotes for equipment, projects and multi-year maintenance, with discount approvals	Which system holds costs and price lists
Award	A contract and a service contract with entitlements for the service levels, sites and assets in scope	Which terms become data, and which stay in the signed document
Mobilization	Assets registered by customer and site, with maintenance plans that generate work orders	Where the master asset register lives
Delivery	Work orders and service appointments for technicians and crews, completed on the mobile app	Territories, skills and what each visit must record
Service levels	Cases linked to the entitlement, with milestones counting down to first response and resolution	Who is alerted before a breach
Renewal	A renewal quote from the contracted asset in Revenue Cloud, or a renewal opportunity opened well before the end date	How early renewals start, and who owns them

The award row decides whether the rest works. A contract that exists only as a PDF cannot drive maintenance plans, service levels or a renewal date, so capture the service terms as data on the day it is signed.

Assets, service contracts and crews

In a maintenance business the asset sits at the centre of the record. Register each chiller, transformer, generator or inverter against the customer and site, and attach the service contract that covers it. A Field Service maintenance plan sets the visit schedule for one or more assets and creates work orders for future visits. Its rules can follow the calendar, react to readings such as a temperature or efficiency threshold, or follow usage, and a schedule can be fixed or float from the last completed visit. Service levels sit on the same contract: its entitlements carry an SLA policy, and a case linked to one starts milestones such as first response and resolution time.

Crews often work where the signal is poor, in plant rooms, substations and remote sites. Salesforce describes its Field Service mobile app as built to be offline first, and its App Store listing includes Arabic. Salesforce classes Arabic as an end-user language: standard objects and pages are translated, admin pages, Setup and Help stay in English, and admins should review the right-to-left limitations first. Whatever you build, from checklists to the service report, needs its own Arabic version and a test on your crews’ phones. See how we deliver Field Service.

Regulators and major accounts

Two relationships carry more risk than any single deal. The first is the major account, the utility, government entity or industrial group behind a large share of your tenders. Give each an account plan, an account team and one record holding every tender, contract, case and visit, so the relationship survives a change of account manager.

The second is the regulator. Treat each authority as an account, and track licences, permits, inspections and submissions as records with an owner, a due date and an expiry, linked to the sites they cover. A licence renewal should never depend on one person’s calendar.

ERP and asset systems: settle ownership first

Most of these companies already run an ERP for orders, costs and invoices, and many run an asset management system for the engineering register. Agree one owner for each record before anyone builds an interface:

Record	System of record	In Salesforce
Customers and contacts	Salesforce, holding the ERP customer number	Full record, sent to the ERP for invoicing
Costs, price lists and invoices	ERP	Prices for quoting, and invoice status on the account
Contracted service terms	Salesforce	Service contract, entitlements and the assets in scope
Asset register	The asset system, where you have one	Assets under contract, with the asset system’s ID
Work orders and visits	Field Service	Full record, with time and materials posted to the ERP

For SAP, the MuleSoft Accelerator for SAP provides pre-built system APIs for accounts, products, sales orders, billing documents, pricing and sales contracts, and a quote-to-cash flow between Salesforce and SAP S/4HANA. Salesforce’s integration guidance for utilities adds other patterns: Salesforce Connect shows external data without storing it, which suits maintenance history, and platform events tell Salesforce when something changes elsewhere. See how we approach MuleSoft integration.

Rule of thumb: the ERP owns costs and invoices, the asset system owns the engineering register, and Salesforce owns the customer, the contracted service terms and the work your crews do.

Our work in energy and utilities

Arcsen is a Salesforce Summit partner with offices in Dubai, Riyadh, Jeddah, Doha and Cairo. Our energy and utilities work includes:

Dalkia: Sales Cloud runs B2B sales automation for Dalkia, the EDF Group’s energy services company, in Saudi Arabia.
Dubai Supreme Council of Energy: LPG licensing. One digital workflow for licensing LPG cylinder distributors in Dubai, with 16 steps across eight authorities, from legal entity registration to the DSCE permit.

Clients on our energy and utilities page also include alfanar and Gas Arabian Services.

Where to start

List what is open: every live tender with its closing date, and every contract with its end date and owner.
Sign the ownership map with finance, operations and IT.
Model one contract type end to end, such as planned maintenance: service contract, entitlements, assets, maintenance plan and crews.
Pilot Field Service with one crew, offline and in Arabic, on the phones they already carry.
Decide on Energy & Utilities Cloud once you know whether premises, service points or meter data are part of your process.

Running sales, contracts or field crews on Salesforce? Start with our free Salesforce Health Check: ten working days and a scored report on your whole org, yours to keep. See our energy and utilities work, talk to our energy team or send us your RFP.

Frequently asked questions

Does an energy services company need Energy & Utilities Cloud?

Not always. Salesforce built it for electric, gas and water utilities, retail energy suppliers and renewable energy companies. Companies selling projects and maintenance contracts to businesses usually start with Sales Cloud, Service Cloud and Field Service, and add it where premises, service points or meter data matter.

Can Salesforce track maintenance contracts and service levels?

Yes. Service contracts hold entitlements with an SLA policy, cases linked to them run milestones such as first response and resolution time, and maintenance plans generate work orders for the assets under contract.

Does the Field Service mobile app work offline and in Arabic?

Salesforce describes it as built to be offline first, and its App Store listing includes Arabic. Arabic is an end-user language in Salesforce, so admin pages, Setup and Help stay in English.

How does Salesforce connect to SAP and asset systems?

Usually through MuleSoft. The MuleSoft Accelerator for SAP has pre-built APIs for accounts, products, sales orders, billing documents, pricing and sales contracts, and Salesforce Connect can show asset system data without storing it.