From Messy Handovers to Seamless Delivery: Ionyx Digital’s Notion AI Workflow🪄 E03
Notion in PracticeShow Notes
In this episode of Notion in Practice, Tim and Jerwin sit down with Matthew Shaw and Dave Merriweather from Ionix Digital to unpack how they rebuilt their entire sales-to-delivery process on Notion and Notion AI.
Ionix work with time-poor clients across construction, infrastructure, mining, rail and services – people who can close deals in a room but hate the admin it takes to get there. Traditionally, their sales team would run long discovery calls and pitches, then try to “re-say” everything in a handover meeting with copywriters, designers and developers.
Important context slipped through the cracks, projects dragged out, and rewrites piled up. Now, every discovery conversation is captured as a transcript, stored in Notion, and becomes a shared source of truth. Notion AI sits on top of those 70–80 page transcripts, letting the delivery team: Ask detailed questions and get instant, accurate answers Understand the client’s goals and language as if they’d been in the room Write content and design assets that hit the brief on the first pass
Matthew and Dave share: Why tools like Monday.com and Wrike weren’t the right fit for their workflow How they designed a single client page that connects sales, delivery, tasks and transcripts The real impact on quality: fewer complaints, fewer rewrites, and more consistent outputs How Notion AI helps them halve overall delivery timelines without cutting corners The internal AI tools they’ve built to critique client collateral and train the sales team What they learned about change management when rolling Notion out to two very different teams
If you run a services business, agency or consulting firm and struggle with handovers, inconsistent delivery or time-poor clients, this episode will give you a concrete example of how to: Turn conversations into assets Build a living knowledge base out of transcripts Use Notion AI as a partner for both sales and delivery
Three Actionable Takeaways Turn every client conversation into a searchable asset.Record discovery and pitch calls, store the transcripts in Notion, and let Notion AI answer detailed questions later instead of relying on one person’s notes and memory.
Design a single shared workspace for sales and delivery.Create a unified client page that links deals, transcripts, briefs, tasks and assets so delivery can start with full context instead of fresh questionnaires and repeat conversations.
Use AI to cut waiting time, not quality.Let AI reduce back-and-forth, rewrites and clarifications so the team can spend their time on higher-quality writing, design and strategy – which is where the real value is.
Guest Profiles Dave Merriweather: Matthew Shaw: Ionix Digital Host Profiles Tim Jeffries: Jerwin Parker:
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?
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?
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?