Ryan Scott

A CRM migration, a weekly Sales workflow, and a financial analysis call for different solutions. In each, I work from the business question, trace the underlying data or behavior, and build and validate something people can keep using.

• SEMA · Migration & reconciliation

  CRM Migration & Reporting Rebuild

  A new CRM changed the structure behind familiar reports. I rebuilt recurring processes around Salesforce/Nimble AMS while tracing legacy logic and reconciling converted data.

  • SQL
  • SOQL
  • Salesforce
  • Nimble AMS
  • NetForum
  • Excel

  Read case study: CRM Migration & Reporting Rebuild

  Challenge

  Recurring reports carried business rules from NetForum that could not simply be copied into Salesforce/Nimble AMS. The same business questions had to be answered against different records, identifiers, and relationships.

  My contribution

  I rebuild recurring reporting processes, validate converted records, and investigate discrepancies as part of the broader CRM transition.

  Approach

  Start with what the legacy process was meant to do, then trace its logic and data relationships. Compare records across systems, investigate conversion discrepancies, and rebuild the reporting workflow against the new model. Validate the results and adapt the process as migration requirements change.

  Result

  Recurring reports have been rebuilt for the new environment, while reconciliation and validation continue as the migration evolves.

• SEMA · Recurring data processes

  Marketing Data Automation & Segmentation

  Audience rules were spread across data sources and recurring requests. I turned that work into reusable SQL processes for segmentation, exclusions, refreshes, and validation.

  • SQL
  • iPost
  • Salesforce
  • Excel
  • Power Query
  • Data Quality

  Read case study: Marketing Data Automation & Segmentation

  Challenge

  Marketing and operational requests draw on CRM, membership, exhibitor, and council/network information. Eligibility rules, suppression logic, and source data need to stay consistent across recurring refreshes.

  My contribution

  I build and maintain hundreds of SQL queries and recurring data processes supporting marketing segmentation, operational reporting, and data quality.

  Approach

  Translate each business requirement into explicit selection and exclusion logic. Trace how the source records relate, build reusable SQL processes, and validate audience eligibility and data quality. Maintain the refreshes and checks as business requirements change.

  Result

  Recurring audience and reporting work runs through reusable processes with consistent rules and validation, giving business teams a dependable basis for ongoing operations.

• SEMA / Sales · Weekly workflow automation

  Weekly Sales Lead Reporting Automation

  Weekly Sales lists began with manual exports, deduplication, and assembly. Scheduled FTP delivery now supplies the data, and I use a VBA macro to prepare the output before distributing it.

  • FTP
  • VBA
  • Excel
  • Reporting

  Read case study: Weekly Sales Lead Reporting Automation

  Challenge

  Weekly lead preparation started with manually exporting email opens and clicks, combining and deduplicating the engagement data, and assembling usable lists for Sales.

  My contribution

  I changed the preparation workflow to use scheduled FTP exports and VBA processing. I still prepare and distribute the weekly output.

  Approach

  Traced the path from email engagement data to the weekly Sales list to identify the manual preparation steps. Replaced manual source exports with scheduled FTP delivery and introduced a VBA macro to format and prepare the output. I run that preparation and distribute the results each week.

  Result

  Source data arrives automatically and the VBA-assisted workflow is used weekly. I handle final preparation and distribution.

• SEMA / Finance · Transactional analysis & validation

  Accounts Receivable Aging Reporting

  A positive order balance can hide a different picture at the line level. I work through bundles, payment rollups, and balance exceptions to develop and validate usable aging reports for Finance.

  • Salesforce
  • Nimble AMS
  • Reporting
  • Reconciliation
  • Validation

  Read case study: Accounts Receivable Aging Reporting

  Challenge

  Order-level balances do not tell the whole story of outstanding receivables. Bundled transactions, payment rollups, and positive overall balances with negative underlying lines complicate what should appear in an aging report.

  My contribution

  I develop and validate receivables reporting against Salesforce/Nimble AMS transactional data, translating Finance’s needs into reporting logic.

  Approach

  Work from the financial question back through Order Item and Order Item Line relationships. Reconcile order and line balances, examine bundle behavior and payment rollups, and validate how reporting exceptions affect the outstanding receivables shown.

  Result

  Finance’s requirements are being translated into explicit reporting logic grounded in the transactional relationships. Development and validation continue as balance and rollup exceptions are worked through.

• SEMA · Workflow design & documentation

  Event Operations Workflow Improvement

  A recurring booth-selection workflow kept bringing staff back for technical help. I simplified the reporting and data-handling steps and documented a process they could run more independently.

  • Reporting
  • Workflow Design
  • Documentation
  • Process Improvement

  Read case study: Event Operations Workflow Improvement

  Challenge

  Staff needed to complete recurring booth-selection tasks, but the reporting and data-handling workflow depended on repeated technical assistance.

  My contribution

  I redesigned booth-selection reporting and documented a repeatable workflow for the nontechnical staff using it.

  Approach

  Worked through the existing procedure from the staff’s perspective to understand what each step needed to achieve. Simplified the reporting and data flow, organized the recurring steps, and documented how to run the process.

  Result

  Nontechnical staff can complete recurring tasks with less technical assistance, using a more structured and documented workflow.

• SEMA · Analysis & decision support

  Membership & Financial Analysis

  National and chapter membership data needed to be read together to understand alignment and gain/loss. I reconciled those relationships and organized the financial and operational findings for stakeholders.

  • SQL
  • Excel
  • Power Query
  • Data Analysis
  • Financial Analysis
  • Reporting

  Read case study: Membership & Financial Analysis

  Challenge

  National and chapter membership relationships are complex. Alignment and gain/loss patterns need to be interpreted together with their financial implications before the data can support a useful discussion.

  My contribution

  I analyzed membership relationships, organizational alignment, and net gain/loss, then prepared reporting that stakeholders could interpret.

  Approach

  Start with the alignment question, reconcile membership relationships, and compare the gain/loss patterns. Connect those findings to the financial and operational analysis, then organize the detail into reporting that makes the relationships understandable.

  Result

  Stakeholders received an interpretable view of membership alignment, gain/loss patterns, and their financial implications to support discussion and decisions.