Salesforce Application & System Architect

Salesforce Architect connecting business operations, automation, integrations, and AI.

I help teams turn Salesforce into a platform they can depend on, from the first business conversation through design, build, testing, and release.

See selected work Get in touch
  • CPQ
  • Agentforce
  • Integrations
  • Flow & Apex
  • Access & security
  • Analytics
An illustrative Salesforce org. Hover a node to trace its connections.

Selected work

Four problems, and how I solved them

Agentforce · CPQ · Analytics

An AI workload advisor built on CPQ data

Counting opportunities said little about how busy an account manager really was. The real workload was in the complexity of each bid and quote.

I scored every bid from its CPQ quote, line groups, and lines, then captured history so leaders could watch workload change over time. On top of that data I built an Agentforce advisor that answers questions like “what if this rep took those two bids?” through governed Apex actions.

  • Complexity points instead of hours, so workload compares fairly across reps
  • Read-only by design: it models scenarios and never moves a record
  • Permission-aware services behind a React dashboard and Agent Script

Security · Access architecture

Untangling a legacy sales profile

One profile controlled both what salespeople could access and how Salesforce looked to them. Changing security meant risking the layouts, tabs, and record types people relied on.

I mapped effective access from every source: profile, direct assignment, and permission set group. Then I rebuilt it as a Minimum Access profile plus a group of 97 modular permission sets, 91 for specific objects and six shared. Layouts, record types, and tabs stayed on the profile, so the sales experience could stay exactly the same while security became modular and auditable.

  • Security separated from presentation, so each can change on its own
  • Layouts, record types, overrides, and tabs verified against the original
  • One permission set per object, so access can be reviewed object by object

Automation · Flow

Consolidating 143 overlapping Flows

Record-triggered Flows had piled up on the same objects. It was hard to predict what would fire on a save, so every process change carried risk.

I started with an Opportunity pilot, then mapped every active Flow to a consolidated replacement in a traceable source-to-target workbook. 143 Flows across 17 objects became 56, and Opportunity alone went from 64 to 9. Each replacement was checked against the behavior of its sources, and the originals were kept intact for a controlled cutover.

  • Every replacement traceable to the Flows it absorbs
  • Configuration errors caught in validation, not by users
  • Originals preserved, so the cutover can be staged and reversed

Agentforce · AI reliability

An AI sales agent that wouldn't take no for an answer

A prospect told an AI sales agent they had no current need. The agent replied politely, included a broken contact link, and kept following up.

I traced the exchange through the agent's topic routing, actions, Flows, and cadence state. The active topics skipped the intended seller lookup, calendar generation failed, and nothing saved the decline, so the cadence carried on. My redesign treats “no current need” as its own outcome, resolves the owner's real meeting link, validates the email before it sends, saves a closing decision on the record, and blocks automatic re-enrollment.

  • Every polite acknowledgment backed by a saved business decision
  • Actions bound to trusted record context instead of generated text
  • Regression tests for each failure path in the trace
Redline clouds mark where the trace broke down.

About

Business problems first, then the platform

My background combines Salesforce architecture, administration, consulting, and business operations. I've worked with sales, marketing, customer success, professional services, and leadership teams to turn business requirements into systems people can use and maintain.

Also certified

Agentforce Sales Consultant · Data 360 Consultant · OmniStudio Consultant · OmniStudio Developer · Platform Administrator · AI Associate

Education

BBA, Business Administration – Management, Towson University
ABA, Business Administration, College of Southern Maryland

How I work

  1. 1Frame the business questionAgree on what success means before any metadata changes.
  2. 2Trace the platformFollow the data through automation, integrations, permissions, and AI.
  3. 3Simplify the designLeave something the next admin can reason about.
  4. 4Build and verifyApex, LWC, and Flow, backed by tests and readback.
  5. 5Release with a clear scopeEveryone knows exactly what shipped.

Contact

Hiring a Salesforce architect? Let's talk.

LinkedIn

Résumé available on request.