Provincial privacy law and what it means for a CRM
Alberta has its own privacy statute for the private sector, which governs how organizations collect, use, and disclose personal information in the province. The practical effect for a CRM resembles other jurisdictions: clear purposes, appropriate consent, reasonable security, and a process to respond to access requests. Federal anti-spam rules also apply to commercial email and text messages. Confirm specifics with your counsel and design consent and access controls accordingly.
Selling to industrial and resource customers
Industrial accounts have many stakeholders: operations, procurement, engineering, and safety, often at multiple sites. A good account plan maps these roles and the projects each is responsible for. Opportunities may be tied to turnarounds, drilling programs, or capital budgets with predictable timing, so tracking the customer's calendar helps you prepare early.
- Model customer sites and the contacts at each.
- Track vendor qualification and safety documentation requirements per customer.
- Log the planned maintenance or project windows that drive demand.
Field service for remote and asset-heavy work
Service companies dispatch crews to well sites, plants, and farms where connectivity can be poor and safety is paramount. Field Service supports scheduling by skill and certification, mobile work orders that work with limited connectivity, and capturing safety checks, photos, and signatures. Asset records for the customer's equipment give technicians the history they need before they arrive.
Salesforce Field Service →Equipment dealers, agriculture and trades
Dealers sell new and used equipment, parts, and service, and farmers and contractors expect fast answers on all three. A CRM for dealers combines customer and machine records, quotes, trade-ins, parts orders, and service appointments. Seasonal demand means tailoring campaigns to planting, harvest, and shutdown schedules, and tracking each customer's equipment age supports replacement conversations.
Forecasting for cyclical demand
Resource-linked demand moves with commodity prices and customer budgets, which makes ordinary pipeline arithmetic unreliable. Complement rep judgment with external signals: the customer's announced capital programs, scheduled shutdowns, and the status of regulatory approvals. Record these on the account so forecasts rest on observable events. Reviewing forecasts against what actually closed, quarter after quarter, teaches the team where its optimism usually runs ahead of reality.
Scenario-based forecasts help leadership plan crews and inventory: what happens to field service demand if a major customer defers its maintenance program by a quarter?
Partners, joint ventures and projects
Resource businesses often work through joint ventures and project teams that combine several companies. Contacts and accounts may belong to more than one relationship. Define how partner organizations, project structures, and shared contacts are represented, and who may see which information, so collaboration does not expose commercially sensitive details.
Our Salesforce practice →Decisions to settle before configuration starts
- Account structure. Decide how parent companies, operating units, and sites are represented.
- Safety and compliance records. Define where certifications and site requirements live and who maintains them.
- Offline needs. List the field tasks that must work without connectivity and test them on the real network.
- Confidential relationships. Agree how sensitive deals and partner information are restricted.
A realistic first 90 days
- Days 1 to 30. Clean account and site data, define the account hierarchy, and design consent and access rules.
- Days 31 to 60. Launch the sales process for one segment, and pilot field work orders with a single crew.
- Days 61 to 90. Add service agreements and customer portals, and review pipeline timing against customer project calendars.
Pitfalls in Alberta projects
- Flat account models. Treating a major operator as one account with fifty contacts hides where the work actually is. Model sites and units.
- Field screens built in the office. Test mobile forms in gloves, in weather, and with poor signal.
- Ignoring cyclicality. Forecasts should reflect commodity cycles and customer budgets, not just rep optimism.
- Open visibility across partners. Sharing too much in joint projects creates commercial and legal risk.
