At SaaStr AI 2026, Kyle Norton, CRO of vertical AI leader for restaurants Owner.com, walked through how his team is generating outcomes that look almost impossible on paper for traditional B2B. Owner sells vertical AI to independent mom-and-pop restaurants (think HubSpot plus Shopify for the corner takeout spot) and they’re at ~$100M ARR growing triple digits. Kyle joined when they were at $2M.
The headline numbers from the talk:
- 20x close-won to OTE. A $150K rep brings in $2M+ in ARR per year. That’s the average, not the top performer.
- 4x the ARR per rep of their direct SMB competitors.
- $100K+ in closed-won ARR per outbound BDR per month. Not pipeline. Closed revenue. Per BDR. Average.
And no, they’re not selling tokens or running a usage meter. It’s traditional B2B subscription revenue with AI baked into the GTM motion.
Here are the five decisions Kyle says every B2B company needs to be making right now, and where Owner has landed on each.
First, A Quick Frame: Where Are You On The Sophistication Ladder?
Kyle borrowed a sophistication ladder from Brendan Short, who writes The Signal:
- Level 0: Reps using ChatGPT as a smarter search bar.
- Level 1: Individual reps and RevOps building custom GPTs and skills, Slacking each other markdown files. Most companies are stuck here.
- Level 2: A GTM engineering or applied AI team automating end-to-end workflows like pre-call research and lead scoring.
- Level 3: Centralized infrastructure, shared skills, a context library. Real compounding leverage. The gap starts to widen fast here.
- Level 4: A recursively self-improving system that builds new tools for itself. Kyle hasn’t found a single B2B company actually there yet. Including Owner.
The thesis: the gap between Level 3 and everyone else is becoming exponentially wider, not linearly wider. This is not a 10-15% productivity lift. It’s per-rep output doubling, or work happening with no humans touching it at all. Which is why every B2B company should be racing to Level 3 now.
Decision 1: Centralized vs. Decentralized AI
The “let a thousand flowers bloom” approach feels empowering. Everyone builds. Everyone vibes. AI literacy goes up across the org.
Kyle’s take: it also stalls companies at Level 1.
Decentralized models trap good ideas inside small pockets of early adopters and never scale. Worse, they pull reps away from their actual job. Stewart Butterfield calls it “hyperrealistic work-like activities.” Adrien Rosencrantz at Webflow calls it “AI performance theater.” When a director shows up with a cool app, the right question is: did this put you on more customer calls, or did it just feel like work because it was fun?
Owner’s position: a small, central team of experts owns AI for GTM. Ideas can bubble up from anywhere. But production-grade builds happen centrally.
The reason is simple. What Owner’s applied AI lead builds is not 30-50% better than what a rep builds on a weekend. It’s 5-10x better. So why have 20 people build 20 mediocre tools when you can have one team build one tool that actually moves a number?
One caveat. If you sell AI for a living (Replit, Cursor, Claude wrappers, etc.), every rep has to be AI-native because the product demands it. Centralization still applies, you just need decentralization bolted on top.
Decision 2: Build vs. Buy
Kyle’s framework, and one of the cleanest mental models in the talk: buy your infrastructure, build your intelligence.
The five questions to run any decision through:
- How critical is uptime? If it breaks for an afternoon, does the team grind to a halt?
- How customized does it need to be? Is off-the-shelf already 90% of the way there?
- What’s the engineering ROI?
- Is this core proprietary intelligence?
- Does it give us a real competitive advantage?
Run a dialer through this and you obviously buy. Twilio has spent more on uptime than your entire engineering org will ever spend on anything. AI sims platforms like Avoma? Buy. Latency problems aren’t your problem.
Run Owner’s AI Pre-Call Research tool through it and the answer flips. Uptime doesn’t matter (leads are batch-enriched overnight). The customization required for independent restaurant marketing is extreme. The engineering cost was modest. The intelligence is uniquely Owner’s. The competitive advantage is enormous, because when their reps make a cold call, the level of personalization is on another planet from competitors.
That AI PCR build is a huge chunk of how the BDR team gets to $100K+ closed-won per BDR per month. Two weeks of one engineer’s time. 15 BDRs now booking 85% more ops.
This framework is also why Kyle is bullish on Salesforce surviving the disruption narrative. Run Momentum, Data Lane, Avoma through the five questions and they all clearly land in “buy.” Most of the AI surface area Salesforce competes for is infrastructure work.
Decision 3: Where To Start
The advice nobody wants to hear because it’s not sexy: start with the data.
Two things matter.
Third-party data: your full market map. Who are your accounts? Are they scored? Who are the right contacts inside them? What’s your hypothesis for why they need your product? You cannot point AI agents at mediocre data and expect anything other than mediocre output. Garbage in, slop out.
First-party data: your customer journey, properly instrumented. Owner uses Momentum to ingest every call transcript and fill out as many Salesforce fields as Kyle wants. Pricing changes, positioning evolution, competitor mentions, all of it gets captured automatically. You can’t ask a rep to fill out 25 fields. They won’t. Momentum will.
Once data is in place, Kyle uses what he calls the 5P framework for picking what to build first:
- Possibilities. What are the real opportunities in your business?
- Payoff. If you solve it, how big is the win?
- Probability. What are the odds this actually works?
- Perspiration. What’s the total effort, including adoption and change management?
- Priority = (Payoff × Probability) / Perspiration
You don’t need to actually do the math. The mental model alone surfaces the right starting points.
One more thing on starting: change management is the number one challenge, not the tech. If you’re early on this, prioritize builds that are obviously net-positive for the rep. Make their job easier. Help them make more money. Build trust before you start asking them to invert workflows 180 degrees. The market has done a great job scaring reps that they’re about to be replaced. Get them on your side first.
Decision 4: The People Stack
Who actually does this work?
A centralized team of legitimate technical talent. Not RevOps doing AI on the side (though great RevOps people can convert into this role). Engineering and data backgrounds tend to work best.
Where it reports matters less than who owns it. Kyle originally had the role in his org, then moved it under his VP of Data because the problem-solving cadence was better. It can sit under the CRO, the CEO, RevOps, data, etc. What matters is that whoever owns it is genuinely AI-pilled and willing to push hard. They will need to fight for budget. They will need to force behavior changes. They will need to push through “this isn’t good enough yet, run it again.” That requires a believer at the helm.
The other big people stack question: AI should make you rethink the job function itself. Jordan Crawford’s frame: a job is just a bundle of tasks. AI gives you license to unbundle every task and ask where each one should actually live. Machines or humans?
The BDR job is the obvious example. Most BDR job descriptions still include prospect list building and research, and at most companies that’s 60% of BDR hours. That is a terrible use of a sales rep. Owner unbundled it. A central data team handles list-building. The BDR sells.
Expect to see CS and onboarding collapse, AM and CS collapse, traditional sales functions get reshuffled. Companies that unbundle the work first get the productivity gain first.
Decision 5: Assistive vs. Agentic
The spectrum:
- Assistive (co-pilots): Reps invoke tools themselves. Humans make every decision.
- Hybrid: Deterministic workflows with generative steps and human checkpoints.
- Fully agentic: Autonomous loops with no human in the loop.
The key concept Kyle wants every operator to learn: lossiness.
Every generative step in a chain introduces error. If you ask an AI to crawl your site, infer your value prop, infer your ICP, infer your positioning, identify competitors, and then write an email based on all of that, you’ve stacked five generative steps. The output is AI slop. We all get it in our inboxes every day.
Be deliberate about how many generative steps you chain before a human or a deterministic rule intercepts. For Owner’s enterprise reps, AI surfaces a scored, reasoned account list. A human then decides which accounts go into the prospecting engine. That single human checkpoint kills the lossiness compounding effect.
The other underappreciated piece: you are the eval. Most “AI doesn’t work” stories are really “I built an MVP, tried it twice, and gave up” stories. The build is the easy part now. The grinding iteration on prompts, context, and workflow chains until output quality is actually good is the work. Most people quit at hour three. The breakthroughs are usually at hour six or eight.
The Personal Stack: Lead From The Front
Kyle closed with what might be the most important point for B2B leaders, and the one we keep coming back to on 20VC: you cannot delegate AI fluency. You have to build your own stack.
Garry Tan’s frame: stop thinking productivity. Start thinking compounding systems. Your skills, your context files, your meeting note ingestion, your personal knowledge graph. All of it compounds the more you use it.
Kyle’s podcast workflow is a good template. Guest says yes. An agent fires off a pre-written intake email with a Tally form. The webhook triggers Open Claude. A research skill ingests everything about the guest, scrapes their LinkedIn, drafts five candidate topics, Kyle picks one, the agent one-shots the docket. Six to ten hours to build. Saves hours every week now. Every episode he records gets broken into atomic ideas and stored in his knowledge graph for future reference.
He didn’t get there in one shot. He got there by grinding. The first dockets were bad. The LinkedIn scrape kept failing. The carousel generator was annoying to nail. But each iteration compounded into the next, and now the system runs itself.
If you want to keep your job, automate your job and do a new job on top of it (h/t Jeff Charles at Ramp). The leaders who are still asking their team to do all the AI work are going to lose to the ones who lead from the front.
The Takeaways
- Centralized beats decentralized. Get ideas from everywhere. Ship from one team.
- Buy infrastructure. Build intelligence. The five-question framework will tell you which is which.
- Start with data, then prioritize on (Payoff × Probability) / Perspiration. And go after rep-positive wins first to build momentum.
- The people stack has to be technical and AI-pilled. Put it under someone who cares.
- Be deliberate about generative chain length. Lossiness is real, and you are the eval.
- Don’t let reps run agents. Run agents centrally and deliver the output into the surfaces reps already live in (Salesforce, Salesloft, wherever). Reps running and managing agents is just another distraction from being on customer calls.
- 60% of BDR hours at most companies goes to list-building. That is a terrible use of a sales rep. Centralize it and let the BDR sell.
- Test every AI initiative against one question. Did this put us on more customer calls and move a real number, or is this AI performance theater?
- The hour-3 quitter loses to the hour-8 grinder. The build is easy. The iteration is where the value lives. Most “AI doesn’t work” stories are really “I gave up too early” stories.
The companies sitting at Level 1 watching this race from the sidelines are going to find out the hard way that the gap doesn’t close. It widens. Every month.
(note: Jason Lemkin led the seed round for Owner for SaaStr Fund)
