Carlos EscasainCommercial Systems & Process Architect
ENES

About / professional approach

I work where business process becomes system behavior.

Commercial Systems & Process Architect working across global CRM environments, Revenue Operations, CRM–ERP boundaries, integration, data, automation and governed AI—starting from how the organization actually operates.

I am most useful when a requirement sounds simple, crosses several organizational boundaries and contains more assumptions than decisions.

I analyse how work actually flows, find the broken assumptions and merged decisions, redesign the process, define ownership and boundaries—and then design the technology architecture that supports it.

My approach is platform-aware but not platform-defined. Salesforce is an important part of my experience; the wider system—process, identity, data authority, ERP, integration, analytics, governance and adoption—is the actual field of work.

01How I approach the work05 connected capabilities
  1. 01

    Process architecture

    Analysing how work actually flows, then redesigning stages, decisions, handoffs, approvals and exceptions before anything is automated.

    Current state · target state · governance
  2. 02

    Operating model design

    Defining ownership, decision rights, escalation and measurement so the process can be run—and changed—by the organization.

    Decision rights · KPIs · variation
  3. 03

    CRM & Revenue Operations

    Encoding an agreed commercial lifecycle in CRM, with pipeline, handoffs and management signals designed as one system.

    CRM · RevOps · commercial execution
  4. 04

    Integration & data

    Defining identity, system authority, contracts and recovery across CRM, ERP and the data platform.

    ERP · APIs · events · analytics
  5. 05

    AI & automation

    Placing automation where work is deterministic and reversible, and designing human review where it is not.

    Workflow · agents · guardrails
02The order I work inProcess first
  1. 01Process

    Which stages, decisions and exceptions does the outcome require?

  2. 02Operating model

    Who owns each stage, decision and handoff?

  3. 03Systems

    Which system acts at each step—and which one is authoritative?

  4. 04Data

    Which information is required, and who may create or change it?

  5. 05Automation

    Which work is deterministic enough to automate, and where must a person decide?

  6. 06Measurement

    How do we know the operation works—and who acts on the signal?

03TrajectoryNot a CV

From platform delivery to systems judgement.

Foundation
Hands-on CRM delivery built fluency in the consequences of data models, automation, governance and user experience.
Expansion
Global commercial environments brought process redesign, ERP integration, Revenue Operations, data ownership and organizational change into the same frame.
Current focus
Process and commercial systems architecture across CRM, integration, decision intelligence and human-controlled AI workflows.

Have a process or architecture problem worth thinking through?

Start a conversation