The Fruition RevOps team went through the UNBOUND 26 agenda and found The Decision Engine session by BabelQuest. It’s a great session we just had to share with you. Read this first, though, because an engine is only as good as the number it fires on, and that part is on you, not the stage.
Hannah Fisher and Chris Grant, Principal Consultants at BabelQuest
All of it is a careful record of what already happened. The work of deciding what to do about it still sits with people, in a meeting, on a Thursday, looking at a dashboard and working out what it means. That gap is what the Decision Engine session at UNBOUND 2026 is built to close. Hannah Fisher and Chris Grant from BabelQuest run it Wednesday morning in Room 157, and their D3 Framework, Discover, Decode, Decide, is a way to move HubSpot from a system that records your work to one that helps you act on it.
It fits the theme of the whole event. This is the year HubSpot stops just holding your work and starts acting on it. Agents across the customer journey, workflows that fire on their own, a CRM built to decide and move. So this is worth understanding well before you walk into the room, because a CRM that drives action is a different machine from the one most people are running, and it asks for different things.
A decision engine is the attempt to close that jump inside the system itself. Instead of a person reading a dashboard and deciding, the CRM scores, forecasts, routes, and acts, using rules and, increasingly, AI agents. That’s the shift the D3 Framework is teaching, and it’s the shift the entire UNBOUND agenda is built around.
Walk the three steps and you can see what each one quietly depends on.
The difference between the CRM most people run and the one the UNBOUND session describes comes down to who makes the call, and how fast.
Routes, flags, and reaches out in seconds
Commits to whatever number it reads
So the real question the session is putting to you is whether the data underneath your agents is settled enough to trust what they do next.
Give the engine one source of truth.
So before a CRM can safely drive action, one rule has to be settled underneath it. Each number gets a single system that owns it. Finance owns the contract value. HubSpot owns the deal stage. Delivery owns fulfillment status. Once ownership is clear, a disagreement stops being a standoff, and the engine always has one answer to act on instead of three to guess between. Deciding who owns each number and enforcing it everywhere at once is a discipline with a name. Data governance. The agreed layer it produces is called a decision layer, and building it is the work we do at Fruition RevOps.
Room 157 is a good use of your Wednesday morning. The D3 Framework is a genuinely useful way to think about turning HubSpot from a system of record into a system that decides, and BabelQuest knows the platform. Bring one question with you: Before your CRM decides anything, do your systems agree on the number it’s deciding from? If they do, everything the session teaches compounds. If they don’t, the first thing to build isn’t a smarter workflow. It’s the layer that settles which number is real.
Meet us at UNBOUND 2026. We’ll talk through where systems usually stop agreeing on the same number, and how other teams have gotten everyone working from one version before the engine acts on it.
Provide you with a complete overview of the type of funnel and how to manage it.
Webinar Topic: Fix the Leak with Streamline Your Revenue Path with RevOps Funnels.
How to seamlessly guide prospects through your company’s journey,
Fill out the form below, and blogs, videos and content will come directly to your inbox.