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.
Where I start
Output-Driven
The result that must become true.
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
What I configure
Design
- Processes
- Operating model
- Architecture
- Ownership
- Rules
Where it lands
Execution
Change that runs, holds and evolves.
Six stages. One loop.
Choose a stage to see the questions behind it.
- Which result would make the work worth doing?
- Who notices when it is true—and how?
- What must not get worse along the way?
- Who works in the process—and who decides?
- Where are the handoffs and the workarounds?
- What happens outside the happy path?
- What is fixed—by law, contract, budget or time?
- Which dependencies sit outside the team’s control?
- What scale must the design survive?
- Which part is process, ownership or data—and which is technology?
- Who owns each decision and each record?
- What is automated, and what stays with people?
- In which order can it land without breaking the operation?
- Who has to work differently—and what do they get back?
- How, and when, is the old way retired?
- Which signal shows the outcome is true?
- Who owns that signal—and acts when it moves?
- Did the design, not luck, produce it?
↺ Measurement feeds the next outcome.
“We need one global commercial process.”
Give every subsidiary the same stages and rules.
- Semantics“Qualified”, “won” and “customer” mean one thing: same stages, same exit criteria.
- Local variationLegal and fiscal constraints become registered variants; a preference needs a business case.
- Local systemsLocal ERP rules sit behind one customer and order contract, not inside the global process.
- Decision rightsA process board approves each variant; changing a global control needs Compliance.
- Minimum dataWhat must exist everywhere is defined once; local fields are declared, never redefined.
- RoutinesReviews run on common evidence; KPIs are calculated the same way in every entity.
- AdoptionThe rollout follows what each subsidiary can actually adopt—and when.
- 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 CRM03 · What I design
Four layers of one system.
Business outcome
- 01
Operating models
Who owns, decides and governs?
- Ownership
- Decision rights
- Governance
- Global / local model
- 02
Processes
How does the business really work?
- Lifecycles
- Handoffs
- Exceptions
- Decisions
- 03
Architectures
Which system is responsible for what?
- Responsibilities
- Identity & data
- Integrations
- Automation & AI
- 04
Execution systems
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.
Designing a global commercial operating model for fundamentally different sales motions
Seven ways of selling. One frame to compare them.
Designing a CRM–ERP customer lifecycle
One customer relationship. Two system authorities.
Designing account management as a performance, development and recovery system
Every signal gets an owner. Every obligation, an outcome.
Redesigning RFQ processing around AI without moving commercial authority to the agent
AI prepares the evidence. People approve every commitment.
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