From Clicks to Conversions: Pay Only for Measured Outcomes

Episode Summary

Clicking on software was an accident, not a destiny. Matthew Swanson, founder and CEO of Motion Enterprises, traces it to BASIC: the first computer interface asked people to type commands, the technology was not ready, and everyone fell back on graphical interfaces. Thirty years on, he thinks the first principles are worth revisiting, and his answer is that the natural interface is not clicking but talking. His agents sit on top of Salesforce and the rest of the marketing stack, translating natural language into clicks on behalf of employees and customers, and moving people through the customer life cycle from top of funnel to conversion. The second half turns to money. He prices the way he designs: come up with a KPI for a campaign, then charge only for measurable increments in it, rather than by the hour or by the seat.

Key takeaways

  • He scopes the work narrowly and explains the technology plainly, in the same breath. At Motion Enterprises agents are applied through customer lifecycle management, and what the Transformer really does, in his account, is decide what is the next best thing to do

  • The move he makes with that definition is to claim the enterprise is doing the same thing. Deciding what to do next is, at the end of the day, all any enterprise is trying to figure out as well, from the macro question of which customers to go after down to the individual, which is why he designs agents to take customers through each stage of a life cycle to maximize revenue

  • His contrast between the two interfaces is concrete. Today it is an interface you click on where you have to figure out these boxes; with Motion it is a service you speak with the way you would another person

  • The history he tells is the argument’s foundation, and it is a claim about accident rather than design. When BASIC came out the technology was not ready, so nobody could type all the commands and get what they wanted done, and everyone fell back to graphical user interfaces. Thirty years later he wants the first principles revisited, and his conclusion is that it is not clicking, it is talking

  • He positions the product as a layer rather than a replacement, using the stack’s own history as the analogy. Just as Salesforce and the other SaaS tools are a layer on top of databases, he sees the opportunity to layer on top of the SaaS tools

  • The mechanism underneath the conversation is unglamorous and he says so. Instead of employees clicking around software or customers working through navigation flows, the agents do it on their behalf, translating natural language into clicks

  • He looks at the life cycle holistically, and names a starting point rather than the starting point. A starting point for most organizations, he says, is the top of the funnel: reaching new customers, moving them into awareness, engagement and consideration, and ultimately into the purchase stage

  • His picture of where software is going is built on a word he chooses deliberately. The way he likes to look at the future of software, in his words, is as an anthropomorphic version of employees, designed the way you would train an employee on your best practices, your tools and the business processes your company follows

  • Onboarding starts with the agents reading the systems. They can now comb through an existing MarTech stack and get a pretty good lay of the land, which he calls pretty incredible

  • The second half of onboarding is conversational, and he says why. A bunch of nuance is stuck in people’s heads, so an orientation process is where the conversation really starts, and from there a user can ask for things like a new LinkedIn ad campaign aimed at a segment

  • Asked whether customers value the strategic view or the tactical execution, he redirects to a third answer. The place he sees people most excited is outcomes, a very numeric-driven relationship built on outcomes teams know lead to revenue, with the pricing model aligned there

  • The pricing mechanism is stated precisely enough to act on. They come up with a KPI for a given campaign, and they will only charge for measurable increments in that KPI

  • The reasoning behind the model is a claim about company valuation, which he flags as a bigger subject than the episode. His North Star is how you measure the value of a company, which he believes can be better broken down into incremental outcomes everyone can align on as known numerical KPIs. That is what takes him away from charging by the hour and traditional seat-based models

  • What actually moves a deal, in his account, is not the model but a specific wound. When a team has that burning pain point, his example being that they cannot get their MQLs to hop on the phone, a no-risk pay-on-performance model becomes very attractive

  • His advice to listeners is about the starting point rather than the technology. The biggest challenge he sees in the marketplace is getting started, and a great place to get started, in his words, is a use case you know already has an ROI model built around it

  • The habit he wants built comes before the capability. Getting your organization into the habit of measuring outcomes is what he says will pave the way for taking advantage of these new capabilities. He also asks for an open mind, and reaches for the last time you met a genuinely new technology, which he says does not come around every day: the first time you picked up an iPhone, or first touched a computer

  • He closes on the size of the change rather than the tactics. A paradigm shift is happening right now, he says, and we all need to think differently about how we run our businesses if we want to take advantage of agents

About Matthew Swanson

Matthew Swanson is the founder and CEO of Motion Enterprises, which applies AI agents to customer lifecycle management, taking people from the top of the funnel through awareness, engagement and consideration to purchase. Motion Enterprises is the trading name of Silicon Valley Software Group, the technology firm he founded. His argument on this episode is that clicking on software was an accident of history rather than a destiny, and that the natural interface is conversation. His company prices on the same principle: it comes up with a KPI for a campaign and charges only for measurable increments in it, rather than by the hour or by the seat.

 

In this episode

00:42 Welcome, and who Matthew Swanson is
01:33 Customer lifecycle management, and the Transformer as deciding what to do next
01:56 What every enterprise is trying to figure out next
02:36 What would that look like
02:51 Clicking boxes, versus a service you speak with
03:03 A step back, and how interfaces came about
03:26 Why we click: BASIC, and the accident of the graphical interface
04:07 A layer on top of Salesforce and the SaaS tools
04:20 Translating natural language into clicks
04:51 Which parts of the customer life cycle this covers
05:06 Top of funnel through awareness, consideration and purchase
06:31 Sitting on top of the tools, and next to your employees
07:01 The future of software as an anthropomorphic version of employees
07:34 Do you train the agents, or do they learn by observing
07:47 Combing an existing MarTech stack during initialization
08:03 The nuance stuck in people’s heads, and the orientation conversation
08:25 What a former CMO would want to get out of it
08:59 Where people get most excited: outcomes
09:43 A KPI per campaign, and charging only for increments
10:22 Away from hourly and seat-based, toward incremental outcomes
11:04 What target customers say when the model is explained
11:56 The burning pain point, and MQLs who will not pick up
12:21 What listeners should take away
12:36 Where to start: a use case that already has an ROI model
12:57 Building the habit of measuring outcomes
13:25 The paradigm shift, and thinking differently about the business

In Matthew’s words

“It’s an interface that you click on and you have to figure out these boxes, and with Motion, it’s a service that you speak with like you would another person.”

Matthew Swanson   (02:51)

“We can revisit the first principles of what’s the best way to interact with software, and we think that it’s not clicking, it’s talking”

Matthew Swanson   (03:26)

“Rather than charging by the hour and traditional seat base models, we’re starting from this, this level of, of measurable outcomes”

Matthew Swanson   (10:22)

“The biggest challenge we’re seeing right now in the marketplace is getting started, finding that tangible use case”

Matthew Swanson   (12:36)

 

Resources

Matthew Swanson

Ideas and terms discussed

  • Customer lifecycle management: The scope he sets for his agents, and the reason the product is not a general assistant. Agents are designed to move a customer through each stage of a life cycle, from reaching someone new through awareness, engagement and consideration to purchase, with revenue as the measure

  • The Transformer as what to do next: His plain-language account of what the underlying technology does: it decides what is the next best thing to do. The move he makes with it is to say that this is also what an enterprise spends its time deciding, from which customers to pursue down to what an individual should do next

  • Not clicking, talking: The compression of his whole interface argument. Clicking became the way we use software because the first attempt failed, not because it was the right answer, and he thinks thirty years of progress is enough to revisit the question

  • The accident of the graphical interface: His history of how we got here. BASIC was the first interface for a computer, the technology was not ready for people to type commands and get what they wanted, so the industry fell back to graphical user interfaces. He presents this as contingent rather than inevitable

  • A layer on top of the SaaS tools: How he positions the product against the incumbents. SaaS tools are themselves a layer on top of databases, so he sees room for another layer above them. Underneath the conversation the work is mechanical: the agent translates natural language into clicks

  • An anthropomorphic version of employees: His design principle, and the phrase he uses for it. Agents are built the way an employee is trained, on the company’s best practices, its tools and the business processes it follows, and he describes them as sitting next to your employees rather than only on top of your tools

  • Initialization: The onboarding step, split into two halves. Agents comb an existing MarTech stack and get a pretty good lay of the land, which he calls pretty incredible, and then an orientation conversation captures the nuance that is stuck in people’s heads

  • Outcome-based pricing: The commercial half of the episode and the most unusual thing on this page. A KPI is set for a given campaign and the company charges only for measurable increments in it, replacing hourly billing and seat-based licensing. His reasoning runs through company valuation: if the value of a company can be broken into incremental outcomes, those are what everyone should align on

  • Paying only on performance: The form the pricing takes when a buyer meets it, and his account of when it lands. It is novel enough to need explaining, and what makes it attractive is a specific unmet need rather than the elegance of the model

Named on air

Related AI Realized episodes and events

 

Frequently Asked Questions

 
 
 
 
 
 
 
 
 
 
 
Previous
Previous

AI Agent Sprawl: Govern the Lifecycle Before You Backtrack

Next
Next

When Attackers Have AI, Verify the Person Each Time