← Olivista

Point of
View.

What's actually happening at the intersection of partner ecosystems, systems infrastructure, and AI — from someone who's built it from the inside.

March 2026 Scale
The Systems Work Has to Come Before the AI Work
Everyone is buying AI tools. The companies getting returns aren't the ones who bought the most — they're the ones who fixed the manual handoffs first.
↓ Read

There's a pattern I keep seeing. A company decides it's time to invest in AI — automation, agents, intelligent workflows. They buy the tools. Three months later, they're not getting the returns they expected, and they blame the technology.

The technology is usually fine. What's broken is underneath it.

I recently worked with an organization running a large-scale technology partnership program — hundreds of integrations, five or six cross-functional teams involved in every partner onboarding, meaningful recurring revenue at stake. They wanted to explore AI-assisted partner scoring and renewal intelligence. Smart idea. But when we mapped the actual process, contract terms lived in one place, billing configurations in another, security approvals in a third, and partner performance data nowhere in particular. Every handoff between systems was a human manually copying something into a spreadsheet.

You can't train an AI on a spreadsheet that lives in someone's email drafts folder.

The work that had to happen first was systems work: define the operating model, clarify ownership, clean up the handoffs, decide which data mattered, and make sure the systems could actually produce it. Only after that did AI become useful.

This is why I keep telling companies the systems work has to come before the AI work. AI is not a substitute for operational clarity. It is a multiplier of whatever is already true.

August 2025 Scale
The Partner Program Isn't the Strategy. The Data Layer Is.
Partnerships look like distribution on the surface, but the real advantage comes from the data model underneath the motion.
↓ Read

A lot of companies talk about building a partner program as though the program itself is the strategy. Recruit some partners, create a few tiers, define incentives, launch a portal, and expect the ecosystem to start producing growth.

But most partner motions do not fail because the partner deck was weak. They fail because the operating system underneath the motion was never built.

If you cannot see sourced pipeline, influenced revenue, onboarding velocity, activation quality, renewal performance, and the handoffs between internal teams, then what you have is not a strategy. You have activity.

The data layer is what turns a partner program into a scale asset. It tells you which relationships deserve more investment, where the operating friction is, which partner types actually convert, and whether the economics make sense as the motion matures.

January 2026 Vertical SaaS
Why Vertical SaaS Companies Are the First Movers in the AI Ecosystem Transition
The most durable AI advantages are showing up first in vertical software, where workflow depth and ecosystem context already exist.
↓ Read

Vertical SaaS companies have a head start in the AI transition because they already sit inside specific operating workflows. They understand the data objects, the user behavior, the compliance constraints, and the points where decisions actually get made.

That context matters because AI is not just a feature race. It is an ecosystem race. The winners will be the companies that know where intelligence can create leverage across software, service, partner, and operating layers.

Horizontal tools can generate broad utility, but vertical platforms often have the better foundation for applied intelligence. They can embed AI inside domain-specific moments where the value is obvious and the data is already close to the workflow.

September 2024 Sales Leadership
The First Sales Hire Almost Always Goes Wrong
The problem usually isn't the candidate. It's that the company hires for a title before it has defined the actual job to be done.
↓ Read

When founder-led sales starts to strain, the instinct is often to hire a head of sales and expect relief. But the first sales leadership hire often fails for a simpler reason: the company has not clarified what kind of leader it actually needs.

Some businesses need a builder. Others need a coach. Others need a player-manager who can architect the role while still carrying part of the load. Those are different jobs, and hiring as if they are interchangeable creates predictable disappointment.

The role has to be defined from the ground up: what stage the company is in, what motion already works, what is broken, what must be built, and what success should look like in the first ninety days.

April 2026 Scale & Exit Readiness
Scale Readiness: How IT Services Owners Build a Business PE Actually Wants to Buy
Most owners think they need to optimize for EBITDA. In reality, buyers pay for an operating model that can scale without the founder acting as the system.
↓ Read

Most IT services owners do not wake up thinking about multiple expansion. They wake up thinking about client escalations, staffing pressure, delivery bottlenecks, and whether the business can keep growing without becoming harder to run.

But if you look at what private equity firms actually reward in this category, the theme underneath the numbers is scale — not just bigger revenue, but a company that can add complexity without depending on the founder to hold every important decision together.

That distinction matters because buyers reward businesses that behave like platforms. They want consistency in reporting, disciplined delivery, repeatable commercial motion, and management infrastructure that can support another stage of growth.

Scale readiness is not about sounding sophisticated in a CIM. It is about building a business that is easier to operate, easier to measure, and easier to believe in.