Salesforce Outcomes

Problem

The existing sales process relied on one opportunity per year, making multi-year forecasting and reporting complex and error-prone.

Approach

Redesigned the architecture to use a single opportunity across all years, restructured reporting metrics like ARR and TCV, and shifted key metrics to pull from Contracts instead of Opportunities.

Outcome

Enabled the CFO with accurate real-time metrics for decision-making and more accurate spiff payouts.

Problem

An organization needed a scalable quoting process with complex product structures and pricing logic.

Approach

Implemented a CPQ catalog with bundles, lookup-based pricing, and tiered discounting, and added custom development for rebate handling.

Outcome

Sales could quote complex products in CPQ instead of side workarounds in Excel.

Problem

I've helped many different orgs on small problems that weren't a full project. Whether it's an annoying red unknown error or a metric that is miscalculating, I'm happy to track it down and fix it.

Approach

Ask a lot of questions, dive into the backend, and find the root cause.

Outcome

Quoting works again and reps are back to selling instead of fighting with the system.

Problem

Many companies need senior Salesforce help as part of the team without hiring a full-time admin, analyst, or release manager for every slice of work.

Approach

This is daily work for me across many orgs. I join as one of the team, filling the roles of business analysis, finding system improvements, development, and release management.

Outcome

I assimilate like one of the team, they only paid for what they needed from me, and I generally accomplish in 15–20 hours a week what they would pay somebody 40 hours a week to do.

Problem

Across multiple orgs, legacy automation in Process Builder and Workflow had errors and could not scale.

Approach

On many of these migrations I analyzed the existing logic, documented what it actually did, and rebuilt it in Flow.

Outcome

Orgs moved onto Salesforce's supported automation, with fewer errors and a model that is easier to maintain.

Problem

A company that offered financial services needed tax tracking in Salesforce without Financial Services Cloud, and they were paying for Salesforce products they did not use.

Approach

I built tax tracking on the clouds they already had, reviewed their Salesforce contract, removed what they did not need, and wrote a letter to Salesforce so unused items could come off the agreement.

Outcome

There was a system and accountability to make sure tax payments weren't missed and that they were paid on time, with reminders scheduled before the payments were due. They got to reuse their Salesforce contract amount on features that were actually useful to them.

Problem

A new customer portal was needed to streamline support requests and case visibility.

Approach

Built in Experience Cloud using secure, role-based access and custom screen Flows for case creation and management.

Outcome

Customers had a self-service site to see the products they owned, related businesses if they were in a hierarchy, and guided case creation and visibility, reducing support workload.

Problem

Commission calculations were manually tracked when multiple users helped on a single deal.

Approach

Introduced Opportunity Splits and custom split types and logic so commission tracking stayed accurate across multiple roles and scenarios.

Outcome

Cleaner reporting and automated compensation tracking in place of the manual process.

Problem

With Strikedeck being decommissioned, core customer success workflows needed to be rebuilt natively in Salesforce.

Approach

Recreated essential functionality using a combination of custom and standard objects, Flow automation, and dynamic layouts.

Outcome

Preserved business continuity and improved long-term maintainability inside Salesforce.

Problem

Teams needed records moved into Salesforce from other systems—or from one Salesforce org to another—without bringing the mess with them.

Approach

I have helped on many of these migrations, including HubSpot, Practifi, and Salesforce-to-Salesforce. I made sure data was cleansed before import and meticulously mapped, and I supported the developers who scripted the changes by preparing the Salesforce org metadata so the data had a place to land.

Outcome

A sparkly Salesforce system with all of their data, so it now feels like home.

Problem

A nonprofit moving from Raiser's Edge needed years of volunteer data in Salesforce Nonprofit Cloud without losing their unique volunteer structure.

Approach

I led phase two as project manager and consultant, designing a data model with Person Accounts and light custom configuration and automation.

Outcome

Volunteer data landed in a model the organization could support going forward.

Problem

Mission-driven organizations needed Salesforce integrations with their donation systems for a clear customer understanding and reporting.

Approach

Just like I would with any other engagement, everything from discovery, business analysis, build, and deployments.

Outcome

Nonprofits get the support they need to continue their important missions without an additional cost burden.

Problem

Duplicate records kept showing up in reporting and outreach for both nonprofits and for-profit businesses, including on custom objects.

Approach

Across many orgs I built matching rules, validation, and duplicate processes for standard and custom objects, using scheduled emails of duplicate results if they existed, and custom screens to guide duplicate merging, along with selection of certain attachments from each record.

Outcome

Cleaner data people could trust, whether the records lived on Person Accounts or custom objects.

Problem

High team turnover led to knowledge gaps and inconsistencies in onboarding and daily support.

Approach

Built a centralized Salesforce documentation library in Quip and paired it with in-app guidance for key features.

Outcome

Faster ramp-up, easier support, and improved process adoption across teams.

Problem

Manual inventory tracking created delays and errors in stock reporting for a tourist business with a large amount of expendable and stable inventory.

Approach

Developed an automated system within Salesforce to monitor inventory levels, item movement, and storage locations, along with guided and mandatory logging.

Outcome

Real-time visibility into current stock, and when and how much to re-order once items were used.