I joined MuleSoft in 2018. This month marks four years.
I want to write honestly about what I've learned — not the LinkedIn version of what I've learned, but the version that's actually true.
1. The gap between platform capability and realized value is the real business problem
When I joined MuleSoft, I thought the primary challenge was helping customers understand the product. Get them trained, get them implemented, get them using the features — value would follow.
Four years in, I know that's wrong.
The challenge is not understanding. The challenge is organizational adoption. The gap between what a world-class integration platform can do and what an enterprise actually extracts from it is not a training problem or a feature awareness problem. It's an organizational change problem.
The enterprises that realize value are the ones that treat platform adoption as a change management initiative, not a technology project. They have executive sponsorship. They have internal champions. They have a roadmap that connects platform capability to business outcome. They measure consumption, not just utilization.
The enterprises that struggle have the same technical capability and far less organizational infrastructure around it.
2. Customer success is a commercial function — not a service function
I came into MuleSoft from a background in enterprise technology services, where "customer success" meant keeping the customer happy and resolving their issues.
MuleSoft taught me that real customer success is a commercial function. It is responsible for the renewal. It is responsible for expansion. It is accountable for the customer's measurable outcomes — because those outcomes are what drive commercial growth.
This isn't about being transactional with customers. It's about being honest. If you're accountable for a customer's outcomes, you have to be willing to have hard conversations about whether the outcomes are materializing — and to intervene when they're not.
The customer success professionals I've seen succeed at MuleSoft are the ones who hold themselves commercially accountable. Not just "is the customer happy?" but "is the customer realizing the value that justifies their investment? If not, what are we going to do about it?"
3. The frameworks matter — but the judgment to apply them is harder
I've built frameworks throughout my career. At MuleSoft, I've developed CARGO, TTC, and ICB — frameworks for thinking about platform adoption, customer interaction velocity, and expansion behavior.
The frameworks are useful. But four years in, I've learned that the harder challenge is judgment in application. When do you apply a framework rigorously and when do you let the specific customer situation override it? When is a customer's deviation from the ICB pattern a signal of risk versus a signal of a legitimate alternative adoption path?
Frameworks are thinking tools, not decision rules. The professionals who use them as decision rules eventually produce outputs that are technically consistent with the framework and wrong for the situation. The ones who use them as thinking tools — applying them as a starting point for analysis, not as a substitute for it — get the combination of structure and judgment right.
4. The company you work for shapes you more than you think
I've worked at large organizations throughout my career. MuleSoft — and Salesforce post-acquisition — operates at a level of commercial intensity and cultural clarity that I didn't fully appreciate when I joined.
Four years in, I've been shaped by it. The standards for what "good" looks like — in customer outcomes, in intellectual rigor, in commercial accountability — are higher than what I came in with. That's a gift, even when it's uncomfortable.
The people who complain that their environment isn't good enough to develop in are usually wrong. The environment you're in, with all its imperfections, is teaching you things you can only learn by operating in it.
Four more years from now, I'll know what I didn't understand today. That's the deal.
Views are personal.