Notion AI Custom Agents: What You Actually Pay For + The 3 Layer Guide (Agents, Skills, Guides) E09
Notion in PracticeShow Notes
In Episode 9 of Notion in Practice, Tim Jeffries and Jerwin Parker tackle the question on every Notion power user's mind: what will custom agents actually cost and is it worth it?
With usage-based pricing for Notion custom agents rolling out, Tim and Jerwin discuss what stays free (personal agent / Nosy, enterprise search, meeting notes) and what gets metered (custom agents). They walk through the three-layer model Smooth Ops uses to architect AI inside Notion: Agents, Skills, and Guides and why this structure keeps costs predictable while making your AI dramatically smarter.
In this episode: What you actually pay for in Notion AI (and what's free) The three-layer model: agents as orchestration, skills as SOPs, guides as reference material A real example: how Tim's calendar-sync custom agent costs ~$150 AUD/month and why it earns its keepHow picking the right LLM (Haiku vs Sonnet vs Opus) per agent changes your bill
Why clean databases are the non-negotiable foundation before any AI work When to reach for Claude + Notion MCP instead of staying inside Notion Meet Al, Tim's chief-of-staff personal agent, and how he handles every domain via dynamic skill-matching Why every skill needs an owner and a verification cadence: governance, not just authoring
Three actionable takeaways: Start with your data structure: clean, well-named databases are the foundation everything else relies on. Set up your personal agent (Nosy) with strong custom instructions before you build a single custom agent. Build skills as separate, reusable pages and keep custom agents lightweight: they should orchestrate, not contain logic.
Who this is for: New, Intermediate-to-advanced Notion users, consultants and operators who want to use Notion AI without burning through credits: especially anyone planning their custom agent strategy ahead of usage-based pricing.
🎁 Tim's special offer for listeners: If you're struggling to set up your personal agent instructions, reach out to Tim directly: he's giving away a free instructions starter kit to anyone who asks. (Mentioned around the takeaways at the end of the episode.)
📚 Further reading: Tim's Substack article Structure is the Strategy: open.substack.com/pub/smoothopsconsulting
👉 Subscribe wherever you get your podcasts and on YouTube @NotioninPractice for weekly real-world Notion + AI workflows.
More from Notion in Practice
Flight Centre Travel Group's Matt Upton explains how his automation team uses Notion, Notion Workers and Notion AI skills at enterprise scale, and why nothing gets automated until the process behind it is fixed. Matt is Head of Automation and Innovation for Flight Centre's Asia Pacific corporate brands, leading a team of around 30 across five brands from India and the Middle East to Japan, Australia and New Zealand. Inside a 12,500-person business, the work ranges from multi-step customer onboarding automations to five-minute tasks done 500 times a day. He joins Tim Jeffries and Jerwin Parker on Notion in Practice to walk through how his part of the business made Notion its single source of truth. Information used to be spread across Confluence, Azure DevOps, SharePoint, OneDrive and local files, and nothing joined up. Flight Centre's corporate technology teams now have roughly 1,000 Notion seats. "I tell people if it's not in Notion, it doesn't exist," Matt says, and that rule is what made the change stick. Who this is for Operations, automation and technology leaders fitting Notion, Workers and Notion AI into an existing enterprise stack, and smaller teams who want the same discipline without the headcount. Why can't you automate a bad process? Because automation speeds up whatever process it runs on. Matt's team won't automate anything until it has been through a continuous improvement pass. As Tim puts it, automating a bad process just makes the chaos go faster and the mess grow quicker. How did Notion take hold at Flight Centre? Microsoft Loop opened the door. Notion had been in the business for years with only a handful of real users, and once teams saw collaborative documents working in Loop, a few people pointed out that Notion already did this at scale. How does Matt's team sync Smartsheet and Azure DevOps with Notion? With Notion Workers, small pieces of code deployed to Notion. Matt has seven or eight Smartsheets plus Azure DevOps syncing into Notion databases this way, set up in a short conversation with a coding tool and left to run without babysitting. Most Workers do one plain job like this. How do you build a Notion Worker? Start with a brief. Tim gets clear on the problem with Notion AI, then hands the brief and the Worker docs to Claude Code. His Worker was deployed and working within an hour. Do you have to migrate everything into Notion? No. Smartsheet and Azure DevOps stay where they are as the data layer, Notion becomes the context and reporting layer on top, and Workers keep the two in sync. The episode also covers Notion as "the Switzerland of AI", connecting different models and tools. Three actionable takeaways Run a continuous improvement pass before you automate anything. Leave your system of record where it is and use Notion Workers to sync the data into Notion. Start every Worker with a brief from Notion AI, then point a coding tool at the brief and the Worker docs. Resources mentioned Tim's article "You already have a digital operating system": https://smoothopsconsulting.substack.com/p/you-already-have-a-digital-operating
AI doesn't run in a vacuum. It runs inside a world: the platforms your work lives on, the records that hold the truth, the rules about what happens next. Most AI disappointment isn't a model problem. It's that there was never a world built around it.
Tokens don't grow on trees. So what are you actually paying for when you pay for AI agents?
What happens when a former lawyer becomes Head of Operations at a scaling startup and decides to build an entire ops function using Notion agents?
In Episode 7 of Notion in Practice, Jerwin and Tim chat with Darja Nelson, Operating Partner at Bridgewest Ventures: New Zealand's leading deep tech venture capital firm that invests in early-stage deep tech companies.