4+ Years Salesforce Experience

Multiple Salesforce Certifications

Legal, Finance & Nonprofit

Admin • BA • Consulting Experience

Brandon Lindsey, founder and Salesforce consultant at Logos CRM Solutions

FOUNDER-LED SALESFORCE & LITIFY CONSULTING

Brandon Lindsey

Founder & Salesforce Consultant

LOGOS CRM SOLUTIONS

I’m Brandon Lindsey, a Salesforce consultant with 4+ years of experience across legal, finance, and nonprofit organizations, including hands-on Salesforce and Litify work for law firms.

I work directly with law-firm teams to understand intake, follow-up, and reporting gaps, then turn the agreed requirements into practical Salesforce and Litify improvements. Each engagement starts with a defined scope and a clear implementation plan.

Salesforce certifications: Administrator, Advanced Administrator, Associate

Platform Administrator
Platform Administrator II
Platform Foundations

Experience behind the work

Selected projects from Brandon’s prior professional experience—not Logos CRM Solutions client engagements.

Turning unreliable legal data into usable reporting.

Lead Salesforce Administrator · Law firm.

As the firm’s sole Salesforce administrator, I led the cleanup and standardization of 80,000+ records for its Salesforce implementation. Existing reports were outdated and the underlying data was inconsistent, limiting leadership’s visibility. I worked with the COO to define meaningful KPIs, then built 60+ reports and six dashboards to give leadership a clearer view of operations.

Redesigning revenue tracking for a $150M business.

Business requirements · Salesforce migration · Approximately 200 users.

At EMS, a business generating approximately $150 million in annual revenue, the existing revenue-tracking process wasn’t meeting business needs. I participated in initial discovery, documented stakeholder requirements, and translated those needs into Salesforce requirements. I then contributed to redesigning revenue tracking during a migration supporting approximately 200 users.

Salesforce experience in practice

Three projects from Brandon’s prior professional experience, showing the business challenge, implementation decisions, and measurable outcomes.

01 | Automated Legal Case Valuation Engine

01 | Automated Legal Case Valuation Engine

Estimates typically within approximately 10% of manual evaluations during validation

Challenge

A single subject-matter expert was responsible for manually estimating case values, creating a bottleneck and limiting the organization’s ability to forecast potential revenue.

Solution

I developed a record-triggered Salesforce Flow that calculated estimated case values using historical settlement data, injury-specific compensation averages, and weighted logic for cases involving multiple injuries.

Why I built it this way

I wanted the automation to reflect the organization’s existing valuation expertise rather than use arbitrary estimates. Historical outcomes provided the foundation, while weighted calculations allowed the solution to handle more complex cases.

Key considerations

Differences in injury severity, multiple injuries, historical settlement variability, and the need to validate automated estimates against expert judgment.

What I learned

Complex business decisions can be translated into maintainable Salesforce automation when the underlying rules are understood and validated with subject-matter experts.

Measurable results

Estimates typically within approximately 10% of manual evaluations during validation. Reduced reliance on one employee for initial case estimates. Enabled earlier revenue forecasting.

02 | Executive KPI & Performance Management System

02 | Executive KPI & Performance Management System

60+ reports · 6+ dashboards · Approximately 50 users

Challenge

Leadership lacked a reliable system for measuring organizational performance. Existing dashboards were outdated, data was inconsistent, and many important metrics had never been formally defined or tracked.

Solution

I worked with the COO and business stakeholders to define performance indicators, identify missing data, create new data-capture fields, and develop a comprehensive Salesforce reporting system.

Why I built it this way

Rebuilding the existing dashboards would not have solved the problem because the underlying metrics and data collection processes were incomplete. I started with leadership’s business questions, defined the required measurements, and then built the Salesforce configuration needed to support them.

Key considerations

Consistent KPI definitions, data availability, accurate stage probabilities, historical comparisons, reporting accessibility, and employee adoption.

What I learned

The most important part of business intelligence is deciding what should be measured and why. Effective reporting requires stakeholder alignment, trustworthy data, and metrics that support actual business decisions.

Measurable results

60+ reports developed and 6+ dashboards delivered. Performance metrics established across case lifecycles, revenue forecasting, attorney productivity, and task completion. Presented the reporting framework to the COO and supported rollout to approximately 50 users. Collected post-launch feedback to evaluate usability and adoption.

03 | Client Communications Integration & Historical Data Transformation

03 | Client Communications Integration & Historical Data Transformation

80,000+ historical records · Approximately 50 users

Challenge

A failing Salesforce communications integration prevented important client interactions from being captured reliably. The organization needed a chronological record of communications and documents to understand case progression and support legal preparation.

Solution

Following stakeholder and vendor evaluation, the organization selected a replacement communications solution. I implemented the Salesforce-side integration, standardized and transformed more than 80,000 historical records, configured API and webhook connections, addressed carrier permissions and compliance requirements, and coordinated testing and training.

Why I built it this way

The objective was not simply to restore messaging functionality. The organization needed complete, usable case histories. Standardizing historical records and ensuring new communications were captured correctly helped create a consistent chronological view of client interactions.

Key considerations

Historical data integrity, record associations, message chronology, integration reliability, carrier permissions, compliance, and user adoption.

What I learned

Integration success depends on more than establishing a technical connection. Data quality, business processes, compliance, and the usability of information all determine whether the implementation solves the original problem.

Measurable results

80,000+ historical records standardized and transformed. Integration deployed to approximately 50 users. Centralized texts, emails, documents, and files into chronological case histories. Completed user acceptance testing, documentation, and end-user training.