Salesforce design & implementation

Salesforceshould fit thebusiness.Not the other way round.

I help growing and mid-sized organisations design and deliver Salesforce around the work that needs to happen, the information people need and the outcomes the business is trying to achieve.

That starts before configuration. We understand the process, data, ownership and wider technology landscape first, then build the platform and delivery team around what the organisation can genuinely use and sustain.

Khyati Pal speaking on a panel about who should lead business transformationBusiness transformation first. Salesforce designed around it.
PeopleProcessDataSalesforceAdoption

Where implementations lose their way

A powerful platform cannot rescue an unclear operating model.

Salesforce programmes become expensive when the platform is asked to compensate for decisions the business has not made. The build gets moving, but the same gaps appear in a more polished interface.

  • Old workarounds recreated as new automation
  • Reporting built on data nobody owns
  • Integrations added without a clear system role
  • Users trained on screens, but not on the new process

A foundations-first implementation makes those decisions visible early, while there is still time to design the right answer.

What I lead

One line of sight from business problem to working system.

The person shaping the brief stays close to delivery, so business intent is not diluted between discovery, design and build.

01

Business analysis & discovery

Map the customer journey, current processes, workarounds, decisions and handoffs before turning them into system requirements.

02

Operating & solution design

Design how teams, roles, processes, controls and Salesforce should work together, including what belongs outside the platform.

03

Data, architecture & integration

Define the data model, ownership, migration, reporting and integrations needed for information to remain dependable across the customer lifecycle.

04

Implementation & quality

Lead the build through prioritisation, decision-making, testing and release, keeping the solution connected to the original business outcomes.

05

Adoption & continuous improvement

Prepare people for the new way of working, establish ownership and give the organisation a practical route for improving Salesforce after launch.

The Salesforce landscape

Use the capability the work needs. Leave the rest on the shelf.

Core CRM

Sales Cloud, Service Cloud, Revenue Cloud and Experience Cloud designed around a coherent customer journey.

Data 360

Salesforce's data platform, formerly Data Cloud, used where unifying and activating information supports a defined business outcome.

Agents & AI

Agentforce, AIforce and Claudeforce considered as part of the workflow, with dependable data, actions, permissions and human oversight beneath them.

Connected systems

Integrations and system boundaries designed deliberately, so Salesforce has a clear role rather than becoming the place every problem is pushed into.

Khyati Pal speaking about the business impact of fragmented technologyOne accountable lead.

A flexible implementation network

The right team for the work, not a fixed agency model.

I remain accountable for discovery, design and delivery decisions, then bring in trusted implementation specialists matched to the scope, pace and budget.

That can mean working alongside your internal Salesforce team, partnering with an existing supplier or assembling a focused delivery team from my wider network. You get continuity in the strategy without paying for capacity the programme does not need.

How the work moves

Decisions first. Configuration second.

Each stage creates what the next one needs, with business and technical decisions kept connected.

  1. DiscoverOutcomes, current work, friction, data and constraints.
  2. DesignOperating model, journeys, solution architecture and roadmap.
  3. BuildPrioritised implementation, migration, integrations and testing.
  4. Launch & improveEnablement, adoption, ownership and an improvement backlog.

Selected Salesforce work

Different industries. The same discipline underneath.

Operating design, data and adoption treated as part of the implementation, not as tasks to tidy up later.

Knovia

One lead-to-revenue model across four education and training brands.

Brand-aware routing, Dotdigital integration, shared reporting and a Salesforce model flexible enough to serve distinct businesses.

Keystream

From 20% CRM adoption to a connected commercial operation.

Commercial operating redesign, integrated Salesforce delivery and company-wide enablement resulting in full adoption.

Sumsub

A Salesforce-first strategy across three CRMs and 15+ tools.

End-to-end business analysis, future architecture, data readiness and a sequenced roadmap across the customer lifecycle.

Salesforce FAQs

Useful answers before we speak.

Do you deliver the Salesforce implementation as well as the design?

Yes. I can lead discovery, solution design, programme decisions and delivery governance through to launch and adoption. I bring implementation specialists from my partner network into the team where the scope requires configuration, development, integration or migration capacity.

Can you work with our existing Salesforce partner or internal team?

Yes. I can act as the business-facing transformation and solution lead alongside an existing partner or internal Salesforce team. This is particularly useful when the technical capacity exists but the programme needs stronger discovery, operating design, prioritisation or decision ownership.

Which Salesforce products do you work with?

The work commonly spans Sales Cloud, Service Cloud, Revenue Cloud, Experience Cloud, Data 360 and Salesforce's agent capabilities. The product mix is determined by the business process and information needs rather than by trying to use the broadest possible set of licences.

Can you help with Agentforce, AIforce and Claudeforce?

Yes. I help organisations identify where agents or AI-assisted workflows are genuinely useful, prepare the process and data beneath them and design the controls around their actions. The Salesforce AI landscape is moving quickly, so the exact capability is selected only after the use case, architecture and operating implications are clear.

What if our Salesforce implementation is already struggling?

A recovery engagement can assess the process, data, configuration, delivery model and adoption issues without assuming the answer is a complete rebuild. The result is a prioritised recovery plan and, where needed, hands-on leadership to stabilise and improve the programme.

Can you work with a smaller implementation budget?

Yes. I have a broad implementation partner network, which means the delivery team can be shaped around the complexity, pace and budget of the work. The aim is to protect the quality of the analysis and design while using specialist build capacity proportionately.

What size organisations are the best fit?

I work primarily with growing and mid-sized organisations, typically from around 50 people upwards. The strongest fit is a business where growth has made the customer journey, data, systems or ownership more complex than the current operating model can comfortably support.

A straightforward first conversation

Bring the vision. Bring the questions. Bring the messy bits.

Book a straightforward conversation about what you are trying to achieve, what may get in the way and whether I can help.

Book a conversation