From Systems Thinking to Salesforce
From Systems Thinking to Salesforce
From Systems Thinking to Salesforce
My background in Mathematical Engineering shaped the way I approach complex systems: by looking for patterns, dependencies, and the decisions that hold everything together.
My background in Mathematical Engineering shaped the way I approach complex systems: by looking for patterns, dependencies, and the decisions that hold everything together.
Working across Salesforce clouds taught me that technical correctness is only one part of a successful solution. Systems also need to be understandable, maintainable, and practical for the teams using them.
Working across Salesforce clouds taught me that technical correctness is only one part of a successful solution. Systems also need to be understandable, maintainable, and practical for the teams using them.
Today, I focus on connecting marketing, data, personalization, AI, and Salesforce architecture with real business needs and meaningful customer experiences.
Today, I focus on connecting marketing, data, personalization, AI, and Salesforce architecture with real business needs and meaningful customer experiences.

What I Value
What I Value
These principles guide how I work, make decisions, and collaborate with teams.
These principles guide how I work, make decisions, and collaborate with teams.
Clarity over complexity
Clarity over complexity
Clarity over complexity
I prefer systems people can understand and operate.
I prefer systems people can understand and operate.
I prefer systems people can understand and operate.
Architecture with a human purpose
Architecture with a human purpose
Architecture with a human purpose
Scalability matters, but so does the experience of a customer, marketer, service agent and delivery team.
Scalability matters, but so does the experience of a customer, marketer, service agent and delivery team.
Scalability matters, but so does the experience of a customer, marketer, service agent and delivery team.
Honest collaboration
Honest collaboration
Honest collaboration
I ask questions, challenge assumptions and communicate risks early rather than decorating problems.
I ask questions, challenge assumptions and communicate risks early rather than decorating problems.
I ask questions, challenge assumptions and communicate risks early rather than decorating problems.
Sustainable delivery
Sustainable delivery
Sustainable delivery
Good work should reduce dependency and chaos, not create more of it.
Good work should reduce dependency and chaos, not create more of it.
Good work should reduce dependency and chaos, not create more of it.
How I Work
How I Work
How I Work
I am naturally analytical, curious and direct. I like understanding the full system before making decisions, while keeping the outcome practical and actionable.
I am naturally analytical, curious and direct. I like understanding the full system before making decisions, while keeping the outcome practical and actionable.
I am naturally analytical, curious and direct. I like understanding the full system before making decisions, while keeping the outcome practical and actionable.
I work best in collaborative environments where people can challenge ideas openly, decisions are documented, and ownership is clear. I tend to notice gaps between teams, tools and processes, so I often contribute beyond implementation into architecture, product thinking and coordination.
I work best in collaborative environments where people can challenge ideas openly, decisions are documented, and ownership is clear. I tend to notice gaps between teams, tools and processes, so I often contribute beyond implementation into architecture, product thinking and coordination.
I work best in collaborative environments where people can challenge ideas openly, decisions are documented, and ownership is clear. I tend to notice gaps between teams, tools and processes, so I often contribute beyond implementation into architecture, product thinking and coordination.
Analytical & curious
Analytical & curious
Collaborative & direct
Collaborative & direct
Systems thinker
Systems thinker
Outcome-focused
Outcome-focused
Analytical & curious
Collaborative & direct
Systems thinker
Outcome-focused
Beyond Client Delivery
Beyond Client Delivery
I also build small products and experiments that explore better ways of working with technology. Salesforce Navigator began as a way to reduce the friction of finding the right source across Salesforce documentation. My other projects explore calm interfaces, intelligent systems, and technology that feels useful without demanding attention.
I also build small products and experiments that explore better ways of working with technology.
Salesforce Navigator began as a way to reduce the friction of finding the right source across Salesforce documentation.
My other projects explore calm interfaces, intelligent systems, and technology that feels useful without demanding attention.
Beyond Client Delivery
I also build small products and experiments that explore better ways of working with technology. Salesforce Navigator began as a way to reduce the friction of finding the right source across Salesforce documentation. My other projects explore calm interfaces, intelligent systems, and technology that feels useful without demanding attention.
I care about doing work that is useful, thoughtful and built to last.
I care about doing work that is useful, thoughtful and built to last.
I am especially interested in projects involving Salesforce architecture, personalization, AI-enabled customer experiences, and teams navigating complex multi-cloud ecosystems.
I am especially interested in projects involving Salesforce architecture, personalization, AI-enabled customer experiences, and teams navigating complex multi-cloud ecosystems.
© 2026 Merve Ayan. All Rights Reserved