Salesforce CRM & Field Service Transformation

The organisation was running sales, service, and field operations across disconnected spreadsheets and manual workflows with no shared system of record. I led the end-to-end pre-implementation of Salesforce Sales Cloud, Service Cloud, and Field Service as the operational backbone for the business, not just a CRM, but the foundation for growth, service delivery, and future ERP integration. The result was a clear approved build plan, executive alignment ahead of a Board review, and Salesforce positioned as the single source of truth before a single line of configuration was written.

​

The Business Challenge

The business had outgrown its tools. Without a shared system of record, leadership couldn't see the full pipeline, service teams couldn't track work efficiently, and field operations had no structured way to manage jobs and assets.
 

• Fragmented workflows across divisions and offices

• Manual coordination through emails and spreadsheets

• No centralized operational visibility for leadership

• Unreliable forecasting due to inconsistent operational data

• Disconnected systems and inconsistent reporting structures

• Poor data quality impacting workflow accuracy and reporting reliability
  
  Operational handoffs depended heavily on tribal knowledge instead of structured processes and system-driven execution.
   

The goal was to implement Salesforce as a long-term operational platform that could support the current business, accommodate future acquisitions, and connect with an ERP system. Critically, the aim was not just to deploy software,  but to design how the business would operate going forward.
 

My Role
I served as the operational anchor for the project. I wasn't building the system, but I was responsible for making sure it actually worked for the people who had to use it every day. My job was to translate between the field, the executives, and the Salesforce team and to make sure no one's priorities got lost in translation.

​

My responsibilities fell into four areas:

​

1. Requirements & Workflow Design
I mapped how work actually moved through the company (Sales, Service, Dispatch, Accounting) before Salesforce existed. We had spreadsheets, bid logs, and tribal knowledge—and my job was to figure out what needed to be standardized and what needed to be automated. I then translated those operational realities into structured Salesforce workflows, from Lead all the way through to Invoice.

​

2. Cross-Functional Alignment
This was less about system design and more about people. Sales wanted speed. Dispatch wanted scheduling flexibility. Accounting wanted billing accuracy. Leadership wanted visibility. I facilitated the tough conversations to get everyone on the same page, and made sure downstream teams weren't blindsided by upstream decisions.

​

3. Data Governance & Migration Readiness
Before we could flip the switch, we had to clean up years of inconsistent data. I led the effort to standardize legacy Accounts, Assets, and Opportunities, removing duplicates, fixing incomplete records, and structuring relationships so forecasting and dispatching would actually work post-launch. This was unglamorous work, but it prevented a lot of headaches after go-live.

​

4. Adoption, Training & Stabilization
I created the training guides, ran walkthroughs, and handled the day-one support when users got stuck. More importantly, I stayed involved after launch to catch the issues that only surface when people start using a system for real. When users pushed back on a workflow, I listened, documented the friction, and worked with the team to refine it, because the goal was to eliminate work, not create more.

​

Approach
The guiding principle was clarity before configuration. Past CRM implementations often fail because teams start building before business rules are understood. I established a structure-first approach: clarify roles and decision rights, run rigorous discovery, and validate the Object/Field Workbook before any build activity began. This phased, governance-led method reduced implementation risk and ensured the final system would reflect how the business actually operates, not what a default Salesforce instance looks like.

Collaboration

Executive leadership (CEO, COO): strategic direction and final sign-off

VP of Operations: process ownership for service and field operations

Sales leadership: pipeline and opportunity management requirements

Field managers: scheduling, work order, and asset management inputs

External Salesforce implementation partner: technical build and configuration
 

I served as the single internal coordination point across all groups, managing alignment and preventing scope drift throughout.
 

Tools
Salesforce • Excel • ERP • etc.
 

Project impact and outcomes
Quantifiable outcomes:

• Clear, approved Salesforce build plan delivered before configuration began, eliminating costly rework

• Executive alignment achieved ahead of Board review deadline

• 100% of Salesforce objects scoped, validated, and workbook-complete before build phase

• Install vs. Service opportunity framework defined, reducing future configuration complexity

Strategic outcomes:

• Salesforce positioned as the single source of truth across sales, service, and field operations

• Customization limited to where it drives real business decisions, keeping the build lean and maintainable

• Foundation established for future acquisitions, repeatable onboarding, and ERP integration
   

Most importantly, the project shifted the conversation from 'implementing Salesforce' to designing how the business will operate going forward.
 

What I Learned

The biggest risk in any CRM implementation isn't the technology, it's building the wrong system.

The most valuable work happens before anyone touches a configuration screen. Establish clarity on how the business actually works before designing how the system should work. Every assumption validated upstream prevents weeks of rework downstream.
 

Final Positioning Statement

This engagement demonstrated how operational transformation requires more than software implementation.
By aligning workflows, reporting structures, operational data, and cross-functional execution, the organization established a scalable operational foundation designed to support long-term growth and visibility.