Commercial Systems & Process Architect

Define the outcome. Understand the reality. Design the system.

I redesign processes and operating models, define the architecture behind them, and drive the change through execution.

Output-Driven.Second-Layer Thinking.

02 · How I work

Start from the outcome. Look beneath the request.

  1. Where I start

    Output-Driven

    The result that must become true.

  2. How deep I go

    Second-Layer Thinking

    Not the visible request—the whole system beneath it.

    The visible request

    Beneath it

    The work
    • Processes
    • People
    • Roles
    • Ownership
    • Decisions
    • Handoffs
    The structure
    • Systems
    • Data
    • Approvals
    • Constraints
    • Exceptions
    System effects
    • The existing operation
    • Dependencies
    • Side effects
    • Timing
    • Operational impact
    • Organizational impact
    • Execution impact
  3. What I configure

    Design

    • Processes
    • Operating model
    • Architecture
    • Ownership
    • Rules
  4. Where it lands

    Execution

    Change that runs, holds and evolves.

The method

Six stages. One loop.

Choose a stage to see the questions behind it.

  1. 01OutcomeWhat must become true?
    • Which result would make the work worth doing?
    • Who notices when it is true—and how?
    • What must not get worse along the way?
  2. 02RealityWhat is actually happening today?
  3. 03ConstraintsWhat cannot be ignored?
  4. 04DesignWhat system can produce the outcome?
  5. 05ExecutionHow does the change become real?
  6. 06MeasurementDid the intended result actually happen?

↺ Measurement feeds the next outcome.

Second-Layer Thinking, in one example
Visible request

“We need one global commercial process.”

Surface answer

Give every subsidiary the same stages and rules.

What actually changes

  1. Semantics“Qualified”, “won” and “customer” mean one thing: same stages, same exit criteria.
  2. Local variationLegal and fiscal constraints become registered variants; a preference needs a business case.
  3. Local systemsLocal ERP rules sit behind one customer and order contract, not inside the global process.
  4. Decision rightsA process board approves each variant; changing a global control needs Compliance.
  5. Minimum dataWhat must exist everywhere is defined once; local fields are declared, never redefined.
  6. RoutinesReviews run on common evidence; KPIs are calculated the same way in every entity.
  7. AdoptionThe rollout follows what each subsidiary can actually adopt—and when.
  8. EvolutionAfter go-live, every variant has a review date: renewed, merged into the template or retired.

The process is the visible layer. The operating model is the system underneath.

See it designed: Standardizing a global commercial operation before scaling the CRM

03 · What I design

Four layers of one system.

Business outcome

  1. Who owns, decides and governs?

    • Ownership
    • Decision rights
    • Governance
    • Global / local model
  2. How does the business really work?

    • Lifecycles
    • Handoffs
    • Exceptions
    • Decisions
  3. Which system is responsible for what?

    • Responsibilities
    • Identity & data
    • Integrations
    • Automation & AI
  4. Can it actually run—and keep improving?

    • Implementation
    • Adoption
    • Measurement
    • Evolution

Measurement feeds back

Architecture follows the business design—not the other way round.

These layers become real in the work below All eight disciplines on one map

04 · Selected work

Architecture, shown working.

Four flagships: operating model, architecture, execution and applied AI.

  1. Operating model

    Designing a global commercial operating model for fundamentally different sales motions

    Seven ways of selling. One frame to compare them.

  2. Architecture

    Designing a CRM–ERP customer lifecycle

    One customer relationship. Two system authorities.

  3. Execution & performance

    Designing account management as a performance, development and recovery system

    Every signal gets an owner. Every obligation, an outcome.

  4. Applied AI, governed

    Redesigning RFQ processing around AI without moving commercial authority to the agent

    AI prepares the evidence. People approve every commitment.

All cases

Contact

Have an outcome that is harder to reach than it looks?

If it crosses process, ownership, systems and execution, that is usually where the work gets interesting.

escasaincarlos@gmail.com Contact page