Oct 03 2026 Phave and the Layer Rules Were Never Built For
Marketing automation has spent much of its history attempting to turn human decisions into increasingly sophisticated sets of rules. We built flows, scoring models, nurture logic, routing frameworks, and governance layers to answer a deceptively simple question: given everything we know about this person, what should happen next?
AI capabilities change the nature of that question. Once a system can intelligently choose among several acceptable actions rather than simply execute a predetermined path, marketing automation begins to move from orchestration toward decisioning. That is a meaningful shift, and it deserves a more interesting conversation than whether a new platform can reproduce the feature list of an established one.
Which is why I found the launch of Phave interesting, even if I am not entirely convinced by how it was positioned.
Phave came out saying it replaces Marketo, Eloqua, Pardot, and HubSpot. Those are not four versions of the same job.Marketo and Eloqua operate at the same altitude: long-cycle enterprise platforms whose staying power comes not only from the software, but from the admin practice around them, years of CRM scar tissue, and enforceable compliance and governance frameworks.
Pardot is a lighter version of that job for companies that already live in Salesforce and do not want to build a marketing operations center of excellence. HubSpot is simpler by design. It is thoughtfully built for leaner teams charged with a more straightforward goal: generating traffic, capturing demand, and supporting inbound. At that stage, a lighter, simpler tool is often exactly what’s needed.
In my opinion, a product that claims all four in one sentence has not yet chosen its buyer.
Set the Marketo and Eloqua noise aside, and it looks like a viable application for Phave becomes much clearer: a company graduating out of HubSpot or Pardot, one that has outgrown three basic nurture tracks but doesn’t have the budget, appetite, or organizational complexity to justify a full Marketo or Eloqua practice.
This is where Phave becomes considerably more interesting.
The rule still has its place. Consent, frequency, quiet hours, eligibility, and the other non-negotiable constraints were never the problem. The rule was simply never meant to be the right instrument for deciding which of two otherwise acceptable emails a person should receive next. That is a real gap, and it is a mid-market gap Phave may be well positioned to address.
The product underneath it is a more serious thing than the video suggested. The session spent the hour proving the wrong thing. I came for the conversation between Jon Miller and Scott Brinker about what this category becomes once the decision is no longer a flowchart.
We never quite got to the substance of that discussion.
Instead, we moved quickly into a sped-up product demo which made the company feel smaller than the argument it was making. A demo has its place. But room had already gathered for the harder question.
Arguably, the more interesting challenge sits one step earlier: how does a company decide which platform is actually right for what it is trying to achieve?
Who decides: Marketing, IT, RevOps, or a centralized technology function? What criteria matter? How much autonomy should the system have? Where does governance live? What happens when the technology becomes capable of making decisions faster than the organization is capable of approving them?
An RFP can count requirements. It cannot tell you whether a team can live with a system that reasons inside rules it still owns, or whether the vendor fits the way the organization actually makes decisions.
The legacy selection model belongs to a slower market.
The tools changed.
The way we choose them has not.