Mark Ajzenstadt

Mark Ajzenstadt

X

@mardehaym

Shared posts
3
Last activity
1 week ago
Media
2 media

Author posts

tgroenwals shared this post · Nov 8
Mark Ajzenstadt

Since July, our team has had more than 100 calls about AI implementation with CEOs, CFO...

1

Since July, our team has had more than 100 calls about AI implementation with CEOs, CFOs, CTOs and PE operating partners.

These 12 questions came up most often:

  1. “Where do we start?”

Where your customer would feel it first. Pick one workflow, run it for a month, then decide what comes next. Start with a long list of ideas and you’ll end up shipping none of them.

  1. “Can’t we just build this ourselves with Claude?”

For a lot of it, yes. Reports, research, content: get your people using agents every day. You don’t need a firm for that. You need one when the work touches a system of record, patient data or payment data, or when it has to run every day without somebody babysitting it.

  1. “How do we measure ROI?”

Name the number before you build: days to close, denial rate, hours per onboarding. If nobody can name it, you’re buying a demo.

  1. “How do we know the AI is right?”…
tgroenwals shared this post · Oct 18
Mark Ajzenstadt

the AI value creation problem

Private equity built its value creation playbook with financial engineers. AI is an engineering problem.
If you build value creation plans for a living, take a look at the AI section of your latest one. How much of it describes a better business, and how much describes the same business with fewer people?
Operating teams increasingly talk about an AI strategy for the portfolio. Too often, the plan underneath is a cost target with AI written next to it.
Peter Drucker put it bluntly:

"Marketing and innovation produce results; all the rest are costs."
It's a useful line to remember when an entire AI strategy begins and ends with the payroll.
The existing value creation playbook deserves its place. Pricing, procurement, sales effectiveness, working capital, add-on M&A: these are proven ways to improve a business. The cost work matters too. Shared services, fewer management layers and a more efficient back office can all create real value.

120 12 25 24.2K
tgroenwals shared this post · Oct 2
Mark Ajzenstadt

There are seven main steps for your company to go from tool adoption to agentic org.

1

There are seven main steps for your company to go from tool adoption to agentic org.

Most companies sit on step one, shopping for step seven technology. They need step four discipline.

Step one: tool adoption. AI tools exist across the org, humans run each one. Developer closes the lid, automations die. Somebody goes on vacation, the workflow goes with them.

Step two: context layer. Knowledge graphs per department, each behind its own API gateway. Sales queries engineering through an API. Separated domains keep agents from hallucinating across departmental boundaries.

Step three: harness engineering. Build evaluation criteria, routing logic, and quality gates before you pick a model. The LLM comes in last. Your harness is your IP and your capex. The model underneath is a commodity you swap when something better ships. If changing the LLM breaks your system, you built a dependency, not a platform.

7
MBall_Atlanta I respectfully disagree. I would suggest governance needs to move up somewhere around steps 2-3. Also, why most companies are not successfully elevating through this progression…because training and culture change mgmt is not even a mention here. “That’s implied” is a failure Aug 26
mardehaym Author Thanks, Matthew. In my other posts, I have outlined the culture change and mgmt before as main bottlenecks for becoming AI-native, it's true.

This post, however, is more focused on technical aspects of becoming an agentic organization, and the steps are numbered but some of them
Aug 26
MerbinJAnselm Thank you Mark. I’m someone who is working in SAP enterprise agent space (I help implement and realize) and finds your insights more relatable than anyone here. Aug 26