01 · About

From designing solutions to defining the system behind the outcome.

From CRM consulting to business-unit leadership and in-house transformation, each stage expanded the system, domain and decisions I was responsible for. That widening boundary is where today’s way of working comes from.

02The threadAn expanding boundary

The boundary kept moving outwards.

Each stage expanded the system, domain and decisions I was responsible for.

System
what I was responsible for making work
Domain
what I had to understand to do it
Decisions
what I had to make or influence
  1. FirstThe solutionRequirements, processes, data model, configuration
  2. ThenThe client engagement and its deliveryDiscovery, expectations, commitments, delivery
  3. ThenThe business around the solutionPipeline, proposals, roadmap, budget, people, partners
  4. NowThe operating system behind the strategyBusiness Plan, operating model, initiatives, architecture, execution
03Career evolutionPerspective, not chronology

Three stages, three different questions.

  1. 01 The solution

    CRM consulting

    CRM Consultant

    Primary question

    How should the requirement become a working solution?

    I started across the table from the client: discovery with sales and service teams, business and process analysis to find the problem behind the requirement, solution architecture, and delivery the client held me accountable for. My consulting work covered multiple CRM clouds, products and solution contexts, later developing a stronger Salesforce specialization. Across more than 20 consulting projects—for organizations of different sizes, sectors and levels of digital maturity, from consumer goods and retail to industrial and non-profit organizations, among others—similar problems kept appearing in very different settings. That taught me to separate what is fundamental from what is context-specific, and that the requirement is rarely the whole problem.

    Responsible for
    A working solution, from the requirement to go-live.
    What entered the picture
    The client’s processes, across sectors, sizes and maturity levels.
    Decisions in the role
    Solution design and delivery—and when to challenge the requirement.
  2. 02 The business around the solution

    Area leadership

    Salesforce Area Manager

    Primary question

    How do solution, commercial, people and delivery decisions become one viable business?

    Running a Salesforce area moved the boundary from delivering a solution to running the business around it. Business development, commercial planning and pipeline, presales and proposal strategy meant shaping solutions before they were sold. As Product & Technology Lead I also owned the technology roadmap, how the service portfolio evolved and the architecture decisions behind it. Delivery management, budget and capacity sat in the same role, together with leading and developing the team, the client relationships, and the partners, Salesforce ecosystem and technology vendors the area depended on. None of it could be decided in isolation: a proposal committed capacity, capacity depended on people, and the roadmap decided what the team could sell next.

    Responsible for
    The area as a business: offer, pipeline, delivery and team.
    What entered the picture
    Commercial strategy, economics, people, partners and the Salesforce ecosystem.
    Decisions in the role
    What to sell and how, roadmap and portfolio, architecture, budget and capacity.
  3. 03 The operating system behind the strategy

    RevOps, AI & CRM leadership

    RevOps, AI & CRM Lead · multinational industrial B2B

    Primary question

    How should the operating model evolve to turn the Business Plan and long-term strategy into execution?

    Inside the business, the work starts from the Business Plan and the long-term strategy—where the business needs to be in a few years. I lead, design and drive the transversal initiatives that turn those priorities into operating capability: commercial processes, ownership and decision rights, global standards and local governance; how CRM, the boundaries with ERP, data, integrations, automation and applied AI should support them; and the adoption, measurement and long-term evolution that make the change hold. Working with stakeholders from operational teams to C-⁠level leadership, the job is to align priorities, decisions and execution. Architecture is still part of it—as one layer of making strategy, operating model, technology and execution move in the same direction.

    Responsible for
    The operating model that turns strategy into execution.
    What entered the picture
    Business Plan, commercial processes, global and local governance, CRM, ERP boundaries, data, integrations, automation and applied AI.
    Decisions in the role
    Which initiatives and in what order, ownership and decision rights, architecture, adoption and measurement.

Professional foundation, across all threeCertified Business Analyst & Architect

04Both sides of the tableOutside-in · inside-out

Consulting taught me how to frame, design and deliver change. Working inside the business taught me what happens when the project team leaves.

Outside-in

As a consultant

  • Client expectations
  • Advisory
  • Solution proposals
  • Project delivery
  • Commercial commitments

Inside-out

Inside the business

  • Ownership after go-live
  • Adoption
  • Governance
  • Operational consequences
  • Dependencies between initiatives
  • Long-term evolution

I still work both ways: outside-in when framing a problem with stakeholders, inside-out when judging whether the answer will survive its second year.

05How I work todayLead · design · execute

Most of the problems I work on no longer belong to one department or one platform.

Lead
Align stakeholders, decisions, priorities, dependencies and teams.
Design
Define the operating model, process, ownership, architecture and governance.
Execute
Drive implementation, rollout, adoption, measurement and evolution.

The environment is multinational, multicultural and industrial B2B: long customer lifecycles, complex products, several sales motions, subsidiaries at different levels of digital maturity, global standards meeting local constraints, and transactional systems connected to the commercial work.

So the responsibility reads better as a chain from strategy to execution than as a list of technologies.

From strategy to execution

  1. Strategic directionWhich capabilities does the business need over the next few years?
  2. Operating modelHow must processes, ownership and decision rights change?
  3. Transversal initiativesWhich initiatives are needed, in what order, and what depends on what?
  4. Digital architectureHow should CRM, ERP, data, integration, automation and AI support the model?
  5. AlignmentHow do leadership, business teams, IT, data, subsidiaries and partners move in the same direction?
  6. Execution & evolutionHow does the change become real, adopted and measured—and keep improving?
06What those stages taught meThree lessons

Each stage left one lesson behind.

  1. Consulting taught me

    The requirement is rarely the whole problem.

    A request usually arrives as a proposed solution. The work is finding the outcome it was meant to produce.

  2. Area leadership taught me

    A technically correct solution can still be commercially or operationally wrong.

    If the economics, the team, the capacity or the client relationship cannot carry it, it is not the right solution.

  3. Working inside the business taught me

    The real test begins after go-live.

    Ownership, adoption, governance and the next initiative decide whether a design survives its second year.

Those experiences are why I now start from the outcome and design the system around it.

How I work

If the outcome is clear but the system around it is not, that is usually where I am most useful.

The problems I find most interesting sit between disciplines, teams and systems.

escasaincarlos@gmail.com