Concept wireframe — provisional Verenward working brand. Not a representation of legal entity formation or trademark status.
About

The systems behind the growth.

Twenty years in and around operations. I started in sales, then ran service, and I've spent the last five keeping the systems behind a nearly trillion-dollar business in step with how fast it was growing.

The path here

I didn't start in technology. I started in sales, then I ran service. Some of those years were at large wealth management firms, some at small niche companies where the whole staff fit in one room. Both teach you things the other can't.

So I've carried a target that a system was supposed to help me hit, and I've run the operation that had to deliver after the sale closed. When a platform promises something the business can't actually do, I know what that costs. I've paid it.

What I do now

I lead CRM and Sales Enablement transformation at a global alternative asset manager. The job is keeping the infrastructure in step with the growth, and the growth has been steep.

$498B → $938B
Assets under management, nearly doubled
100 → 900+
CRM users over the same period

That has meant transformation work across several Salesforce environments and everything wired into them. Platform consolidation, data, workflows, integrations, process. Most of my week is spent between the business and the technology, working with senior stakeholders on what gets built, in what order, and whether the investment matches where the business is actually going.

Mergers and acquisitions

I've also led CRM and Sales Enablement integration for firms joining through acquisition. That work is where the theory stops.

Two companies almost never record a customer the same way. They don't agree on what counts as an account, and their systems rarely hand data to each other without a fight. Someone has to decide which record is right. Someone else has to make the data move. Treat those as one job and the integration stalls, usually for months.

Why Verenward

The problems I like are the ones no single team owns. They cross departments, they're messy, and they sit unsolved for years because everyone assumes someone else has it covered. Bringing order to that is the work I keep coming back to.

Verenward is where I'm putting it. Two products, because the integration work taught me they're two problems. VDX moves data between systems and keeps it moving. Verity decides what the data means and which record wins.

It's early days. If any of this sounds like your week, write to me.

Start with the operating problem.

Tell me what isn't working. I'll tell you honestly whether this is the right kind of help.

Start a conversation