I design, automate, and improve Salesforce solutions that work.

Salesforce Administrator, Consultant, and Business Systems Analyst with 6+ years of experience translating business requirements into scalable CRM solutions. I work across Salesforce configuration, Flow automation, integrations, data quality, user enablement, and end-to-end delivery.

Selected work

Digital lending and mortgage platform on Salesforce

Financial institution

Experience CloudLoan servicingPayment gatewayMarketing campaigns
The problem
The lender wanted to digitally transform its operations, moving loan and mortgage applications, underwriting, and servicing off manual processes and onto a single platform.
What I did
Implemented a Salesforce solution where borrowers apply online through an Experience Cloud site and go through a credit scoring process. Automated application management, servicing, underwriting, and investor management, added document management, integrated payment gateways, and set up campaigns to promote loan and mortgage products.
Outcome
A borrower-facing application journey and an internal servicing process running end to end on one platform, with payments and marketing connected rather than bolted on.

Sales Cloud and Service Cloud for an international e-commerce company

E-commerce, multi-region

Sales CloudService CloudCustomer engagement
The problem
Sales and service processes were disconnected, which slowed the sales team down and left customer engagement inconsistent across regions.
What I did
Implemented Sales Cloud and Service Cloud together, streamlining the sales pipeline and service processes and giving teams a shared view of each customer.
Outcome
Customer engagement up 35% and sales productivity up 20% after go-live.

Job application portal for a start-up

Start-up, recruitment

Experience CloudIdentity verificationDocument management
The problem
Applications were arriving with no structure, no verified identity, and documents that could not be reliably tied to the person who sent them.
What I did
Built a portal where applicants register, activate their account by email, verify their identity, and only then upload documents, so every file is associated with a confirmed registration record.
Outcome
A simpler experience for job seekers and an organised, verifiable intake for the start-up's hiring team.

Telesales quoting and enrolment on Sales Cloud

Retail energy, Texas market

Sales CloudLightning Web ComponentsRetentionBusiness analysis
The problem
A retail energy provider's telesales agents were working through a guided sales flow that quoted from legacy pricing logic, hard-coded plan rules, and product bundles that no longer matched the catalogue. The company was replacing its pricing engine and expanding into a new market, so call handling, plan selection, checkout, transfer of service, and renewals all had to be rebuilt while agents kept selling on the old flow.
What I did
Worked as the business analyst and consultant across five epics, running discovery with sales, operations, and engineering and turning it into epics, user stories, acceptance criteria, and dev-ready task breakdowns. For plan selection, designed the new Lightning Web Component and controller that call the modern pricing engine as the sole source of truth: inputs such as brand, jurisdiction, meter identifier, and customer segment mapped through configuration, results persisted config-first, a visible pricing source indicator, and legacy pricebook and bundle logic removed with no silent fallback. Specified the call initialization and checkout parity stories, the existing-customer path that creates an opportunity from a lead without native conversion and closes the lead with a terminal status, and the contact dedupe match selection flow. Covered transfer of service end to end (move-in and move-out, switch hold automation, paperless billing enrolment, utility reject notifications) and the retention and renewal workflows (plan change, contract cancellation, renewal order registration, order approval logic), including a gap analysis of the legacy bundling feature. Configured the retention pilot's permission set and record type visibility so pilot agents saw the new market's records and everyone else did not.
Outcome
Agents quote from one pricing source with no hidden fallbacks, can leave and re-enter a quote without losing state, and follow a consistent path whether the caller is new or existing. Developers built from a specified backlog without a second round of discovery, and the pilot rolled out to a controlled agent group before wider release.

Fundraising and events migration to Nonprofit Cloud

Environmental nonprofit, British Columbia

Nonprofit Success PackExperience CloudStripeData migration
The problem
The organisation was running fundraising on a legacy platform that was being retired. Donor history, recurring gifts, and payment records sat in that system, online giving came through a separate tool, and events were handled outside the CRM entirely. Staff had no single view of a supporter, could not reconcile donations against constituent records without manual work, and had no way to sell event tickets that landed back in the database.
What I did
Delivered the engagement end to end across four workstreams under a signed service agreement. Migration: mapped the legacy data model to the Nonprofit Success Pack, migrated donors, donations, recurring giving, and opportunity and payment history, aligned the contact and account model including a contact to person account conversion that handled records already present in the org, and reconciled every record before sign-off. Online giving: configured and integrated Fundraise Up with NPSP so donors, one-time gifts, and recurring giving flow into the correct objects, with field mapping and end-to-end transaction testing. Event management: designed a custom data model of seven objects covering events, venues, ticket types, registrations, leads, and payment transactions, then built a public Screen Flow on an Experience Cloud site for guest users that lists events, captures attendee details, and hands off to Stripe Checkout through an Apex callout. Built the webhook handlers that record completed sessions and failed payment intents against the registration, along with two custom Lightning Web Components for the public pages. Documentation: produced build documentation with plain-English and technical sections, flow specifications, a risk and gap register reviewed item by item with the client, an event setup user guide for the platform chosen for day-to-day events, and administrator handover materials.
Outcome
One record per supporter with donation history intact, online gifts arriving in NPSP without manual entry, public event registration with payment status recorded automatically, and a documented system the team runs without depending on the consultant. Delivered on schedule with a formal project completion notice.

Member referral program application

Credit union, Manitoba

Financial Services CloudWeb-to-LeadFlow automationDevelopment lead
The problem
The credit union wanted to grow deposits through member referrals, with a promised incentive for the referring member. There was no way to capture a referral from the web, track it through registration and enrolment, confirm the referred member had actually met the deposit condition, or tell the finance team who was owed the incentive. Doing it by hand would have meant reconciling spreadsheets against account balances after the fact.
What I did
Led development of a member referral application inside Salesforce covering referral capture, registration, and enrolment end to end. Extended the standard Web-to-Lead HTML form so referrals submitted from the public website land directly in the application, carrying the referrer's identity from first capture through to the referred member's conversion so attribution is never lost. Designed and built the eligibility engine underneath: each referral is validated against the institution's deposit thresholds once the new member's account is funded, and when a referral qualifies the system automatically flags the referrer as eligible for payout of the promised amount, giving finance a clean, auditable list rather than a manual reconciliation. Configured the supporting objects, record types, and permission model so branch staff, marketing, and finance each saw the parts of the process relevant to them.
Outcome
Approximately CAD 805,000 in attributed member deposits within the first five working days after launch, with every payout traceable to a verified referral.

Person account conversion and Shield rollout on Financial Services Cloud

Credit union, Manitoba

Financial Services CloudService CloudSalesforce Shield
The problem
Member records migrated from a legacy contact system as plain contacts, which blocked the FSC data model, and the organisation needed stronger controls over sensitive member data.
What I did
Planned and executed the contact to person account conversion, including the constraint that business accounts could not be converted, and implemented Shield with Event Monitoring, Data Detect, and Platform Encryption.
Outcome
A clean member model that unlocked FSC features, plus audit visibility and encryption in place before the compliance review rather than after.

ServiceNow to Salesforce incident-to-case integration

Portfolio and lab work

ServiceNowIntegrationHubn8nRunbooks
The problem
IT and customer support teams often run on different platforms, and incidents that affect customers rarely make it into the CRM in a usable form.
What I did
Designed and built a two-way incident-to-case integration, compared native IntegrationHub against an n8n orchestration layer, and wrote runbooks covering setup, failure modes, and recovery. Part of a five-project ServiceNow administration portfolio built on a developer instance.
Outcome
A working reference implementation and a clear recommendation on when each approach is the right fit.

Recent integration and automation projects

Salesforce · HubSpot · REST APIs

Salesforce–HubSpot contact synchronization

Built and tested contact retrieval and synchronization workflows using Salesforce Flow, HTTP callouts, Named Credentials, and HubSpot APIs. Worked through authentication, data mapping, execution context, and scheduled-run troubleshooting.

n8n · Middleware · Automation

Cross-system workflow orchestration

Designed middleware automation for recurring data synchronization and operational notifications, using n8n to coordinate processes between applications.

Salesforce Service Cloud · Integration

IT ticketing to Salesforce Case integration

Integrated an external IT ticketing application with Salesforce so new tickets initiate Case creation, connecting service intake to Salesforce case management.

Integration work

Selected integration engagements, with the business need, technical implementation, and resulting workflow improvement.

Salesforce org-to-org integration

Business need

Two Salesforce environments needed to exchange business information without forcing teams to work in disconnected systems.

What I implemented

Led the integration effort between the two Salesforce organizations, aligning the information that needed to move between environments and the business processes that depended on it. The work focused on keeping records synchronized and making shared information usable across teams.

Outcome

A more connected operating model, reducing the need to reconcile information manually between the two organizations.

Salesforce and NetSuite ERP

Business need

Sales and finance teams needed consistent CRM, financial, and operational information across Salesforce and NetSuite.

What I implemented

Integrated Salesforce with NetSuite ERP to support the exchange of financial and operational data between the systems. Connected CRM activity with downstream ERP information so teams could reference a consistent view of the relevant transactions and business records.

Outcome

Improved visibility between sales and finance workflows, with less reliance on disconnected data and manual handoffs.

Email validation API

Business need

Incorrect or invalid email addresses entered into Salesforce were affecting contact-data reliability and downstream communication.

What I implemented

Connected Salesforce to an external email validation service using HTTP callouts. The integration checked email information at the point of entry, allowing validation feedback to support cleaner records before the data was used by other processes.

Outcome

Stronger email data quality and fewer avoidable delivery issues caused by invalid addresses.

Real-time currency conversion

Business need

A financial services team needed current exchange-rate information when handling customer cash-conversion requests.

What I implemented

Implemented a currency-conversion capability within Salesforce that retrieved live exchange-rate information for use in the teller workflow. This made conversion information available where staff were already processing customer requests rather than requiring a separate manual lookup.

Outcome

More consistent currency calculations and a smoother teller experience when processing exchange requests.

Salesforce and Stripe payments

Business need

Invoice payment activity needed to connect with Salesforce order and customer processes instead of remaining a separate step.

What I implemented

Integrated Salesforce with Stripe to support invoice payment processing and connect payment activity with the broader order-to-cash workflow. The implementation brought payment processing closer to the CRM process used to manage customer and order information.

Outcome

A more streamlined payment workflow with fewer disconnected steps between invoicing and payment handling.

Secure lead capture and referral lookup

Business need

External lead sources and internal agents needed secure ways to create leads and retrieve referral information through Salesforce.

What I implemented

Built a Node.js OAuth proxy hosted on Azure to act as an intermediary for lead creation from external channels. Separately, implemented a referral lookup service using AWS Lambda and API Gateway and surfaced that capability to Salesforce agents through a Screen Flow. These components connected external services with Salesforce-facing workflows while keeping the integrations behind dedicated service endpoints.

Outcome

External lead intake and agent referral lookups became accessible through integrated workflows rather than separate manual processes.

What I do

Business analysis

Discovery workshops, process mapping, epics and user stories, and acceptance criteria written so developers and testers read the same thing.

Implementation

Sales Cloud, Service Cloud, Experience Cloud, Nonprofit Cloud, and Financial Services Cloud builds, from data model and flows to permissions and release.

Integration

ERP, payment, pricing, validation, and IT service platforms connected to Salesforce through APIs, middleware, and custom services.

Migration and data

Moving from legacy CRMs and fundraising tools, org consolidation, deduplication, and person account conversions that survive contact with real data.

Administration at scale

Large user bases, Shield, permission design, release management, and the operational hygiene that keeps an org trustworthy over time.

Documentation and handover

Build guides, runbooks, and completion notices that let a client run what was built without depending on the person who built it.

Platforms and certifications

Salesforce

  • Sales Cloud
  • Service Cloud
  • Experience Cloud
  • Nonprofit Cloud and NPSP
  • Financial Services Cloud
  • Flow, LWC, Apex (reading and specifying)
  • Salesforce Shield

Around Salesforce

  • ServiceNow administration
  • NetSuite ERP
  • Stripe, Fundraise Up, Zeffy
  • Node.js, AWS Lambda, Azure
  • n8n and IntegrationHub
  • Jira and Agile delivery
  • HubSpot CRM and REST API integrations
  • Salesforce Named Credentials and HTTP callouts

Certifications

  • Salesforce Certified Administrator
  • Salesforce Sales Cloud Consultant
  • Salesforce Service Cloud Consultant
  • Salesforce AI Associate
  • Certified ScrumMaster

How I work

  1. Understand the process before the platform

    Every engagement starts with the people doing the work today. The org design follows from what they need to do, not from what the platform makes easy.

  2. Write it down so it can be built

    Stories and acceptance criteria are specific enough to test against. If a developer has to guess, the analysis is not finished.

  3. Build in small, shippable pieces

    Working software early, reviewed with stakeholders, adjusted before the next piece. No big reveal at the end.

  4. Leave the client independent

    Documentation, runbooks, and handover are part of the deliverable, not an afterthought once the invoice is paid.

Contact

Available for contract and project work: senior administration, business analysis, and implementation consulting. Based in Canada and working remotely with teams across North America.