Every IT leader knows the pattern. One team builds a report in a spreadsheet. Another spins up a workflow with slightly different logic to answer the same question. A dashboard is shared across three departments, and within a week, nobody can say for certain where the underlying numbers came from. 

Instead of freeing up capacity, self-service has quietly become another form of manual work: chasing down mystery logic, reconciling duplicated effort, and answering questions nobody wants to own. 

Self-service was never the risk 

It is tempting to read that scenario as an argument for tighter control — fewer people building, more requests routed through a central team, more approvals before anything ships. That reaction is understandable, but it solves the wrong problem. 

Self-service fails when there are no shared rules for access, quality, documentation, and ownership. Without those guardrails, speed doesn’t produce faster decisions, just more confusion distributed across spreadsheets and more shared drives. 

The real tension is that most organizations have been offered only two options. Either lock everything down, or let everyone build whatever they want and hope it holds together. Neither one scales. 

IT as the paved road, not the checkpoint 

Centralizing data was never the hard part. The real challenge is the last mile: turning that data into decisions and actions the business can actually trust. Closing that gap does not mean IT owns every rule, calculation, and exception that determines how work gets done. 

It means IT builds the paved road — trusted access, approved workflows, reusable templates, and visibility into what is being built — while the people closest to the work own and adapt the business logic that runs through it. 

That division of labor changes what “governance” means in practice. Instead of a gate every request has to pass through one at a time, governance becomes the infrastructure that keeps logic visible, understandable, repeatable, and auditable by design. When the fastest way to answer a question is also the most trusted way, analysts do not need to be talked into compliance, and IT does not need to inspect every workflow to know it will hold up. It is simply how the work gets done. 

Freedom and guardrails, together 

Governed self-service isn’t about choosing between speed and control, it’s about giving each side of the equation what it actually needs to trust the other. 

Governed self-service gives analysts: 

• Access to trusted data 

• Reusable templates and workflow patterns 

• Clear rules for sharing and automation 

• A way to document logic 

• Support when a workflow needs to scale 

And it gives IT: 

• Visibility into who is building what 

• Better governance over access and data use 

• Fewer one-off requests 

• Less mystery logic floating around the business 

• A cleaner path from individual workflow to team-wide process 

What this looks like in practice 

Papa Johns’ finance team offers a useful example of governed self-service in action. The team handles risk-sensitive, high-volume work — franchise billing, royalty calculations, aggregator commissions, and SOX-compliant period close — across a global, multi-currency franchise business. 

Historically, much of that logic lived in spreadsheets and disconnected tools, separate from the systems of record and hard to audit when workflows changed. 

Using Alteryx, Papa Johns rebuilt franchise billing and reconciliation as a governed workflow that runs directly against its Google BigQuery environment, so calculations execute where the data already lives rather than being copied out to another location. 

With Alteryx, complex calculations are visible, repeatable, and auditable. Finance users can ask natural language questions, such as comparing month-over-month figures, and receive immediate answers while also seeing how logic is applied. IT can support governance without becoming a bottleneck. 

The partnership between the business and IT was key to scaling success. Michael Wyant, VP of Enterprise Data and Corporate Solutions, and his team are responsible for governance and data pipelines. The finance team owns the business logic and can adapt it as requirements change. 

Each side owns the part of the problem it understands best. 

The result is a workflow that finance trusts, that IT can stand behind, and that scales as a template for other high-stakes processes across the business. That’s the kind of outcome that governed self-service is meant to produce. 

Fewer surprises, more trust 

None of this requires IT to slow analysts down or analysts to work around IT. When self-service is built on shared standards, analysts stop waiting on tickets, IT stops chasing down mystery logic, and the business gets answers that hold up the moment someone asks, “Where did this number come from?” 

Alteryx supports that model by giving business teams a governed way to build and adapt workflows themselves, while giving IT the visibility, controls, and security required to support it all at enterprise scale. 

The goal was never more control for control’s sake. It is fewer surprises, less rework, and more answers the business can actually trust. 

Ready to see what governed self-service could look like for your team? Explore the AI-Ready Starter Kits to get started. 

 To learn more, visit us here. 

There’s a scenario that plays out every day across the enterprise. A salesperson is about to close a major deal. They want to know what their commission will be. They type the question into ChatGPT or their favorite AI assistant. What comes back is a thoughtful, well-written explanation of how software companies typically structure sales compensation. 

The one thing it won’t tell them is what their commission will actually be if they close this specific deal. That gap between what AI can reason over and what it knows about your business is the defining challenge of enterprise AI adoption right now. 

I call it the logic layer. And without it, AI gives you impressive sounding outputs that are often disconnected from how your business runs. 

Why business logic lives with the analyst 

One of the more persistent myths in AI is that analysts are on the verge of becoming unnecessary. 

The reality is the opposite, and the logic layer is exactly why. 

In an AI-enabled enterprise, analysts become more essential because they are closest to the logic and context that governs the business. They know which definition of pipeline matters and which edge cases matter in audit, merchandising, finance, or marketing. 

I believe enterprises that succeed in the AI era will not be defined by how much AI they deploy but whether the people who understand the business own and control the intelligence that runs it. 

If that ownership defaults entirely to IT or to a vendor’s black box, companies risk scaling systems they cannot fully adapt or audit. Giving business teams the tools and mandate to own their logic is what makes the AI system trustworthy and responsive to how your business runs. 

That is why I see analysts as the architects of this next phase. 

What the logic layer looks like in practice 

Let me return to the commissions example, because it illustrates the concept precisely. Right now, when a salesperson needs to know their commission on a deal, they send a message to the commissions analyst. That analyst has their own spreadsheet — because comp plans change every quarter, with spiffs and special programs layered on top. They run the math manually and send back an answer. 

What if that same analyst built a simple, well-defined calculator that encoded their commission logic — the actual rules for your company, your plans, your programs — and connected it to the AI systems your salespeople are already using? Now when a rep asks what their commission will be on a specific deal, they get the right answer. Not a generic explanation of how commissions work. 

And here’s the compounding value: that same logic can then be used by the annual planning agent to model the operational cost implications of different comp plans. It can feed the scenario planning model that runs hundreds of simulations for financial planning. The analyst who built it enables an entire network of AI systems to act on accurate, business-specific logic. 

That’s the logic layer in practice: curated, purpose-built data assets and calculators that encapsulate how your business works, maintained by the people who understand it, deployable to every AI system that needs it. 

What the logic layer requires 

This is where I think most companies are still stuck. They’ve made the infrastructure investments. They have cloud data platforms and approved LLMs. But they’re asking those systems to do things they were never designed to do on their own. 

The logic layer requires three things: 

• Purpose-built data assets. A narrow, clean, well-defined data set that reflects how you actually measure a specific business process. 

• Encoded business logic. This is the part that lives in people’s heads right now — the policies, the edge cases, the context that makes data mean something. 

• The ability to update it. Nobody runs a business to keep it the same. The logic layer has to be something that domain experts can update when the business changes. 

A pragmatic path forward 

The good news is that you don’t have to wait for a perfect architecture before you start building a logic layer. 

Start with your highest-value, most-repeated business processes — the ones where an analyst is currently fielding the same questions week after week. These are the processes where encoding logic into a curated, AI-ready data asset delivers immediate, measurable value. 

Then, empower your analysts to own that encoding — not IT. Give them low-code tools to do the work, and the mandate to treat that encoded logic as a strategic asset they own and evolve as the business changes. 

This is also where leadership posture matters. 

I have said for a while that this should not be framed as a choice between business and IT. It is both. IT should set standards, manage infrastructure, establish security boundaries, and make approved AI capabilities available across the organization. But IT should not become the bottleneck for every piece of business logic the company needs to operationalize. 

If this feels familiar, it should. We have seen this pattern before in enterprise technology. Infrastructure and platforms matter. But the last mile, the part that turns capability into business value, always depends on the people closest to the work. 

AI is no different. 

The companies that get the most from AI will be the ones that treat it like an operating model. They will automate core workflows, curate the right data, and empower analysts and domain experts to define the logic that makes AI useful and generate answers the business can use. 

I recently had a chance to go deeper on these ideas on the Talking AI podcast. If you want to hear more of my thinking on the analyst’s evolving role, how the logic layer connects to agentic workflows, and why I think the next 18 months will be pivotal for getting this right, it’s worth a listen. 

 To learn more, visit us here. 

Every new frontier model release seems to spur a fresh round of doomsday articles. Just Google “the end of white-collar jobs,” and you’ll be bombarded with discourse on the end of modern work, the unraveling of the social contract between employees and organizations. 

What I don’t see anyone talking about, however, and what I believe is a far more productive conversation, is the opportunity for knowledge workers. 

Nobody understands critical business processes better than your line-of-business (LOB) employees. Not executives. Not IT. Not even the most advanced LLMs. These are your business analysts and RevOps professionals, your supply chain managers and finance leaders, and the employees whose expertise has been forged over decades. 

For an enterprise to become truly intelligent, these workers must be involved in how AI workflows are built and deployed. Their guiding hand is the only way AI can learn and truly understand your business. 

But what does this transition look like, and how can organizations start operationalizing AI in a meaningful way alongside knowledge workers? Let’s take a look. 

What enterprise intelligence requires 

Imagine walking your board through a set of financials and recommending specific actions. Then, in your next meeting, you walk everything back because your AI layer got the numbers wrong. 

There is no faster way to kill an AI initiative than by delivering wrong outputs. Without trust, the whole system falls apart. 

In our recent survey of 1,400 business and IT leaders, we found that while over 90% of organizations are using AI, only 28% trust it to support decision-making. As for how many organizations scaled their AI pilots into production, the number was just under 25%, suggesting a very strong correlation between trust and operationalization. 

An intelligent enterprise, then, is an organization that has trustworthy AI embedded across the business. 

At Alteryx, we say the results of any AI system must follow our VURA framework: an AI system and its outputs must be visible, understandable, repeatable, and auditable. In other words, two people need to be able to go to AI with a question and arrive at the same answer; anyone who uses AI in their workflows must be able to explain how their AI system arrived at that answer. 

Who’s responsible for operationalizing AI? 

Enterprise intelligence is about trustworthy AI deployed throughout key business processes, but who’s ultimately responsible for these AI systems and processes: IT teams or knowledge workers? 

Let’s say you want to use AI in your Sarbanes-Oxley process, e.g., your journal entries, revenue recognition, access controls, etc. Before IT can help you build a new AI workflow, IT must first understand your Sarbanes-Oxley process in great detail. Then, they have to code a tool your finance team can trust. 

It’s possible, sure. But creating this solution would take an inordinate amount of time. Then, when a new regulation comes along or you have an acquisition, the whole thing falls apart. You have to get back in line with IT to retune everything. 

Moreover, if your books don’t balance out or if you fall out of compliance, IT does not want to have that responsibility fall on them. You can see why ownership of AI systems and workflows must sit with LOB workers. They are the only ones with the expertise to ensure the veracity of AI’s outputs. They are the only ones who can successfully shape and define its logic and oversee its ongoing execution. 

Data is the fuel. Business logic is what keeps AI on course. 

Finally, there’s the question of data. We’ve all heard “bad inputs, bad outputs.” Seeing as I’m the CEO of a data analytics company, you might expect me to say that reliable data is the end-all, be-all when it comes to trustworthy AI outputs. 

And while it’s absolutely essential, it’s only the first step. 

Aggregating your enterprise data into a cloud data platform is immensely useful. All of that data becomes readily accessible. You gain a single source of truth across teams and workflows. But you can’t point your LLM at a cloud data platform and ask it to make sense of your data for a complex business process. 

Again, you need the people who understand these critical processes to guide your LLMs to interpret the right data in the right way. This is what will make your AI systems visible, understandable, repeatable, and auditable. Yes, you need clean, reliable data. But more than that, you need business logic around that data, and that can only come from your knowledge workers. 

The five pillars of enterprise intelligence 

At the highest level, enterprise intelligence rests on five core pillars: 

1. Trustworthy, transparent data 

2. Empowered business analysts 

3. Shared responsibility across the C-suite 

4. Cross-functional collaboration 

5. Leadership that evolves alongside AI 
    

Each pillar reinforces the same core idea: AI only becomes valuable when it’s grounded in reliable data, shaped by real business expertise, supported by executive ownership, and scaled across teams that can put it to work to improve their daily processes. 

Tap into the intelligence all around you 

As a business leader looking to build an intelligent enterprise, the most important questions you can ask are the ones around operationalizing AI in key business processes. What would it take for you to trust AI’s outputs? What would make AI-powered processes superior to your current ones? 

Once you have those answers, engage your LOB workers immediately. Give them ownership and autonomy. Rather than asking AI to replace them, lean into their intelligence. Let your knowledge workers use their expertise to amplify, shape, and govern AI. Their business mastery is what makes enterprise intelligence possible. 

 To learn more, visit us here. 

“You’re right,” the LLM says. “I was mistaken.” 

Have you ever read these words during an AI workflow? Nothing kills trust faster than incorrect outputs. It’s no wonder, then, that only a quarter of businesses today fully trust AI to support decision-making and forecasting. 

And yet, we know AI is business critical. Nine out of 10 businesses are using it; 64% say it’s powering innovation. 

So, how do you bridge the gap from experimentation to trustworthy deployment? How do you get verifiable, reproducible results from AI at scale? In this article, I’ll show you the framework that’s powering AI success for leading organizations. 

Why organizations still don’t trust AI 

We asked 1,400 IT and business leaders what their biggest barriers to success with AI workflows were. One in two (49%) said inaccurate or biased outputs; 38% said it was a reluctance to allow AI to make decisions without human oversight. 

Then, there was the data issue. Data readiness is an integral part of successful AI workflows. However, half of all organizations said they still faced poor quality or fragmented data. While you don’t need perfect data to start using LLMs, you absolutely need trustworthy data. 

VURA: The framework for trustworthy AI 

Closing this trust gap requires two things. First, organizations need a logic layer that connects AI systems to the people who understand the data and business best. Line-of-business teams and analysts cannot sit on the sidelines. They need to help build and validate AI workflows so the logic behind AI’s outputs reflects how the business actually operates. 

Second, AI workflows and processes should be visible, understandable, repeatable, and auditable. Together, these principles form VURA, a framework we developed to help organizations build and scale trustworthy AI systems. These guidelines will help build trust in your data and your AI’s outputs. You’ll need both if you want your business to build enterprise intelligence. What follows are the four pillars of VURA.  

• Visible 

Visibility is transparency. Your AI workflows shouldn’t be a black box regarding the data used and the logic applied. Every employee using AI tools should be able to answer two questions: “Where did this answer come from?” and “How did we draw that conclusion?” Otherwise, employees may be working from incorrect information. They could give your customers faulty intel or make important decisions with serious downstream effects. 

If those answers are still unclear, you may need to tighten your governance or reconsider whether your current AI and data solutions are working. Visibility becomes especially important when AI is used across teams. 

• Understandable 

It can almost feel like science fiction when tools like ChatGPT or Gemini take the most complicated or vague of prompts, parse through them, and give you an intelligent, thoughtful answer. 

However, this low threshold for asking and answering virtually any question in natural language isn’t an excuse for glossing over business fundamentals. Your AI systems must be able to explain the logic behind their outputs to even non-technical business users, and your business experts must be able to validate those outputs. 

• Repeatable 

Repeatable means that with the same AI tools, data, prompts, and business logic, AI will give you the same answer every time. Two people should be able to go to AI with the same question and arrive at the same answer. If an AI system or workflow gives you an excellent answer followed by one that’s clearly wrong, it’s not ready for operationalization. You can’t trust it. 

Repeatability also requires documentation. When teams identify prompts or processes that help produce reliable outcomes, those should be recorded and shared. 

• Auditable 

An auditable AI process means you can see what happened. There’s a trail. If there’s an answer or report that seems off, you should be able to identify who owns the workflow, what data and prompts were used, what logic the system followed, and where human judgment and oversight were involved. Auditability is a check and balance for both your AI systems and the human engineers working behind the scenes. 

Start building trustworthy AI systems today 

AI can only deliver scalable business value when it’s grounded in trustworthy data and business logic. To operationalize these systems, you’ll have to ensure your AI workflows are visible, understandable, repeatable, and auditable. 

Alteryx is the transformation and business logic layer that helps you move AI from experimental pilots to trustworthy production. It connects to data wherever it lives, helps business users apply their expertise to AI-powered workflows, and instills the guardrails needed for both your data and your AI systems. 

With Alteryx, the people closest to the business can shape how data is prepared and applied, while IT gains the governance and auditability required for enterprise use. That’s how AI outcomes become trustworthy. That’s how enterprise intelligence is built. 

 To learn more, visit us here. 

If you’re a senior analyst, you’ve probably faced a dataset that used to open in seconds but now takes minutes. Or maybe you’re up against a formula that worked fine last quarter, but now shows an error because someone renamed a tab in a file three layers upstream. Ever spent an afternoon figuring out whose numbers are right when colleagues send back a few different “final” versions of the same report? None of that is a personal failure, but it is a sign that the volume and complexity of your work has outgrown what a spreadsheet was built to handle. 

The cost is more than just your time and inconvenience. When reporting slows down, multiple versions of a number circulate before anyone catches it, or one person’s spreadsheet logic is the only process your team has for something that matters, that’s a risk to the business. 

Plenty of solid analysis still belongs in a spreadsheet, but as your data and stakeholders grow, the balance between preparing data and analyzing it changes. If prep now takes more of your week than analysis does, the tool has become the bottleneck — not you. 

Watch for concrete signs you’ve hit that ceiling, what a platform “built for scale” needs to do differently, and how to decide whether it’s time to move. 

When spreadsheets stop being enough for your data analysis 

Every spreadsheet has a hard ceiling, and it’s lower than people might expect. Microsoft’s own published specifications cap every worksheet at 1,048,576 rows by 16,384 columns, regardless of your computer’s memory or Excel version. Once a dataset crosses that line, rows don’t get flagged — they simply don’t load, and it’s easy to miss. 

The bigger risk is accuracy. A 2024 literature review published in Frontiers of Computer Science, covering more than 30 years of spreadsheet research, found that 94% of spreadsheets used in business decision-making contain errors that create real risk of financial losses and operational mistakes. Most analysts already understand that the more a spreadsheet grows past its original design, the harder it gets to trust every formula in it. 

Alteryx’s own research backs this up from the analyst’s side of the desk. The 2025 State of Data Analysts in the Age of AI report, a global survey of 1,400 data analysts, found that 76% still rely on spreadsheets for data preparation, even as AI tools reshape the rest of their workflow. Manual prep work isn’t a habit analysts choose, but it’s still the default because nothing else is in place yet. 

Spreadsheets are ultimately designed for individual calculation, not for shared, repeatable, large-scale analysis. Asking them to do that job is where the cracks start to form, and when you need to start thinking of an alternative. 

What “built for scale” means 

“Scale” gets used loosely in analytics marketing, so it’s worth being specific about what a platform needs to do differently than a spreadsheet. It comes down to four tasks: 

• Connect to data where it already lives 

A spreadsheet only knows what you paste into it, which means every report starts with an export, a download, or a copy-paste job that’s already slightly out of date by the time it’s finished. Platforms that support scale should be designed to connect, transform, and prepare AI-ready data by connecting natively to a broad range of enterprise applications, databases, and cloud platforms. This way data can be pulled in and refreshed rather than manually re-exported every reporting cycle. For an analyst, that means less time reconciling which export is current and more time on the analysis itself. 

• Prepare and blend without rebuilding from scratch 

Scalable platforms should also give analysts a drag-and-drop canvas for cleansing, blending, and reshaping data from multiple sources, with code-friendly options like Python and SQL available for analysts who want them. It should allow for logic to be built once and held to a standard we call VURA: visible, understandable, repeatable, and auditable. Analysts shouldn’t have to deal with a chain of formulas that only one person fully understands, and that visibility matters as much as the automation. When you build a workflow as a series of documented steps, colleagues can review, troubleshoot, or take over in a way a dense formula chain rarely allows. 

• Automate the workflow, not just the calculation 

The real definition of scale for an analyst is a process that runs without being rebuilt by hand. An essential component of that is workflow automation and orchestration so analysts can schedule and reuse any workflow they build. 

• Report without abandoning familiar formats 

Leaving spreadsheets behind for analysis doesn’t mean stakeholders lose the outputs they’re used to. Reporting tools can generate tables, charts, and formatted outputs in PDF, HTML, or Excel, closing the loop between analysis and the people who need to read the result. 

Spreadsheets vs. a scale-ready analytics platform 

The differences between spreadsheets and analytics platforms are less about features and more about the needs that develop as your data and your team grow. 

Matching the platform to where your team is right now 

“Scale” doesn’t mean the same thing for a 5-person team tracking budgets as it does for an enterprise running hundreds of scheduled workflows. It’s important to consider your team’s specific size and overall org structure before you shortlist any options. 

If your team is still primarily working out of Excel or CSV files and wants to reduce manual, repetitive spreadsheet work, there are several platforms built just for these types of applications. Alteryx One Starter Edition, as an example, is built specifically for that transition — code-free data prep accessible from a browser, aimed at teams getting started rather than running complex automation. 

You don’t need to know your exact tier or platform before you start a conversation with your team, but the conversation can go faster when you can describe your situation in terms of how many people touch the data, how often it needs to run, and who needs to see the output (rather than starting from a feature list). 

Governance doesn’t disappear with spreadsheets 

It’s tempting to think that moving off spreadsheets automatically solves governance, but that just changes what governance looks like. TechTarget’s coverage of data and analytics governance requirements notes that organizations should look for scalable, modular platforms that can adapt as needs change, rather than assuming governance is solved by the platform switch alone. 

It’s important to investigate whether or not a platform supports this with governance and administration capabilities such as role-based access controls, audit logs, and version history. They’re built to give IT the oversight it needs while giving analysts the flexibility to build and run their own workflows. 

A quick readiness check 

Before you bring a platform comparison to your team or your leadership, it helps to be specific about what’s driving the need. What follows are a few questions worth answering honestly: 

• Are you regularly working with datasets that approach or exceed Excel’s row limit, or that make Excel noticeably slow to open and calculate? Slow-loading files and truncated imports are usually the first visible sign, not the first real cause. 

• How much of your week goes to gathering and cleaning data by hand, instead of analyzing it? If prep consistently outweighs analysis, that ratio is the problem — not a single unwieldy file. 

• If you left tomorrow, could someone else pick up your spreadsheet-based process without you walking them through it? A process that exists only in one person’s head is a significant business continuity risk. 

• Do stakeholders currently receive conflicting versions of the same report because multiple people are editing copies independently? That’s a flag that the workflow needs a single source of truth. 

• Does your organization need an audit trail for how a number was calculated, not just what the number is? Regulated or audited environments tend to outgrow spreadsheet-based tracking quickly. 

If you answered yes to two or more of these, this is a reasonable signal that it’s worth having a conversation about moving beyond spreadsheets. 

For a deeper dive on how to build the internal case, check out this guide from Alteryx on evaluating workflow automation tools for analytics teams and another breakdown of evaluating business intelligence tools that scale without increasing complexity. 

See it on your own data 

The fastest way to know whether a platform fits your workflow is to run your own data through it rather than a demo dataset. You can start a free trial of Alteryx One to test connectivity, data prep, and workflow automation against the kind of analysis you do every week. 

[CTA]   

 To learn more, visit us here. 

The old way of creating reports is almost cliché, but only because it remains so pervasive. 

It’s a familiar scene: A teammate pings you at 4:57 pm asking for a last-minute report. The data and business logic you need live across 10 spreadsheets, in five Microsoft Teams threads, and in an email from two months ago that you can’t seem to find. 

But that was the old way. What happens when you use AI for the same situation? 

Let’s find out. 

What working with AI often looks like 

Your stakeholder pings you, asking for a report based on a massive tax reconciliation spreadsheet. 

This spreadsheet is a beast, chock-full of tabs, formulas, and data that’s been copied and pasted from several enterprise data sources. 

“Sorry for the last-minute ask,” they say, “but can you just throw AI at this?” 

You go to your LLM prompt library, select a robust prompt, and input it into Claude, along with the spreadsheet. 

Four seconds later, you get over 1,700 lines of Python code. Somewhere inside, there appear to be all the data transformations, calculations, and visualizations you need to build your report. 

But there’s a hiccup. 

Your stakeholder remembers that your tax jurisdictions change four times a year and wants to ensure that you can make any necessary changes. 

Sure, you think, that shouldn’t be a problem. I can probably find that line of code somewhere … 

Also, there are three subsidiaries. Someone else handles those taxes, so you’ll need to filter those out. 

Finally, your stakeholder remembers that your CFO will want to sign off on this and that your auditor is coming tomorrow. They’ll both want to see the logic behind your report. 

Suddenly, parsing through and validating hundreds of lines of AI-generated code seems far more difficult and time-consuming than you’d hoped. 

VURA: The missing piece 

While AI can bring incredible levels of automation and speed, those are only force multipliers when directed strategically. 

“I can get an infinite number of PowerPoints out of the AI systems if I want that,” Ethan Mollick recently told me during our executive exchange. “It may even be good content, but if it doesn’t serve the purpose you need it to, the productivity gains become a trap.” 

Ethan’s point is that more isn’t always better; bringing four hundred PowerPoints to a sales call won’t help you close a deal. Likewise, instantly generating hundreds of lines of Python is unlikely to help your CFO feel confident in your AI’s vibe-coded report. 

For an AI workflow to be trusted, it has to be Visible, Understandable, Repeatable, and Auditable, or VURA. You need to know what’s happening at every step of the process: where the inputs came from, how business logic was applied, and whether the outputs were correct. 

So, how can you accomplish this? 

The transformation and business logic layer 

Let’s try a different AI-powered workflow. Same situation and model. Only this time, we’re going to add a visual transformation and business logic layer. 

First, we go into Claude and type up a prompt, but instead of Python, we ask for an Alteryx workflow. 

We open our workflow in Alteryx, and instead of hundreds of lines of AI-generated code, we see a visual canvas showing the entire tax reconciliation process. 

It’s still an AI-generated workflow, but now, anyone in the organization can inspect it. They can see what data was used. Your analysts and domain experts can validate the logic. And you can add governance and repeat the process. 

Suddenly, AI-generated workflows become far more trustworthy and scalable, giving you a foundation for enterprise intelligence. 

The future of enterprise AI workflows 

AI tools that can’t adapt when the business changes have short shelf lives, and rebuilding from scratch constantly drains tokens, time, and energy. Endless iterations create endless chances for inconsistencies and errors. 

With a visual business logic layer, the people who know your business best — your business analysts, sales professionals, finance team, and more — can apply their expertise to your AI workflows and validate its outputs. They can see what’s happening at every step of your AI workflows so that every process is Visible, Understandable, Repeatable, and Auditable. 

Speed and reliability are no longer mutually exclusive. Now, you can bring AI’s power and your business experts together to create something fast and reliable, the intelligent solution you need to create scalable business value. 

Learn more: See how Alteryx One can help you build AI workflows your business can trust. Or, watch a live workflow demo to see Alteryx in Action. 

 To learn more, visit us here. 

There’s a version of this story you’ve probably lived. The close is approaching, someone pulls a number from a file that hasn’t been updated, and an hour later you’re untangling a discrepancy that shouldn’t exist. The fix takes 20 minutes. Finding the source took two days. 

This is the part where most articles would tell you to ‘ditch the spreadsheet.’ But that’s not the real problem, and honestly, it’s a little insulting to the work you’ve actually done. 

Your spreadsheet isn’t the issue. The process built around it is. 

The logic is real. The medium is the limitation. 

Think about what lives in the workbooks your team maintains. How revenue maps to each entity. What counts as a valid reconciling item. The variance threshold that triggers a review. The intercompany elimination logic that took a year to get right. None of that is just data — it’s institutional knowledge. It’s business logic, and it belongs to finance. 

The problem is that spreadsheets were never designed to share that logic, version it, or let anything else use it reliably. When a process lives in a file on someone’s desktop, it’s invisible to every system downstream. You can’t hand it off cleanly. You can’t audit it without opening every tab. And when the person who built it leaves, a piece of your operations leaves with them. 

Why this matters more now than it did two years ago 

A lot of finance teams are under pressure to adopt AI — for close acceleration, anomaly detection, forecast assistance, narrative reporting. The pitch is compelling. The results, so far, have been uneven. 

Here’s why, and this part is specific to finance: AI can process data at scale and surface patterns quickly, but it cannot enforce your cost allocation methodology, validate your intercompany eliminations, or know what your organization has decided counts as an exception. 

For a tax team, that means it can’t apply your jurisdiction mappings reliably. For an audit team, it can’t reproduce your evidence logic. For FP&A, it can’t honor the constraint assumptions built into your planning model. That requires logic that’s documented, governed, and repeatable — and if that logic is locked in spreadsheets AI can’t see, AI can’t apply it. So it guesses. In finance, a confident guess on a tax provision or a consolidation rule isn’t a minor error. It’s a liability. 

The teams getting real value from AI are the ones who built the foundation first and then let AI work on top of it. 

The question most teams haven’t answered yet 

The shift that helps isn’t about which tool you use but where your process logic lives and who can access it. When your reconciliation rules, transformation logic, and validation criteria exist in governed workflows rather than locked files, the close gets more consistent, errors surface earlier, and handoffs get simpler. 

But getting from here to there raises a real question most teams are still working through: what does that transition look like for a tax team, an audit function, or an FP&A group that has years of logic built up in Excel? What moves first, what stays, and what does a week of progress realistically look like? 

That’s where the specifics matter — and that’s what we’ll get into next. 

 To learn more, visit us here. 

Most finance leaders at large organizations have made the right investments. A modern ERP, cloud data platforms, planning tools, and more. And now, increasingly, AI — for forecasting support, anomaly detection, close acceleration, and reporting at scale. 

The technology stack looks right. But when the board starts asking about results, the returns are harder to point to than the investments were. 

What your ERP was built to do — and what it wasn’t 

Your ERP is excellent at what it was designed for: capturing transactions, enforcing accounting standards, managing the chart of accounts. It is the system of record, and it performs that job well. 

But it doesn’t encode how your organization has decided to handle intercompany eliminations across a complex entity structure. It doesn’t carry your FP&A team’s cost allocation methodology, refined over three budget cycles. It doesn’t know what variance threshold triggers a controller review versus a VP escalation, or how your tax team has mapped jurisdictions for Pillar Two. That logic — specific, documented, organization-defined — isn’t in your ERP. It’s not in your data warehouse either. 

For most finance organizations, it lives in spreadsheets. Sometimes in the heads of the people who built them. 

Where AI runs into trouble in finance 

There’s a finding that gets cited a lot in finance AI conversations: research from MIT found that 95% of organizations are seeing no measurable return on their gen AI investments. Bain & Company looked at the same picture and reached a different conclusion for finance specifically. The fastest payback from AI in finance comes from embedding it in workflows — not from running pilots. The distinction matters because it explains why so many finance AI efforts stall after the proof of concept. 

AI can process data at speed and surface patterns across large datasets. What it cannot do is infer your business logic from raw inputs. Without that context, AI outputs in finance look confident but aren’t defensible — and in a function where auditability is a baseline requirement, that gap is not a minor limitation. It validates that trustworthy AI is critical for scaling workflows and AI pilots. 

Our own survey of 1,400 IT and business leaders asked what their biggest barriers to success with AI workflows were. One in two (49%) said inaccurate or biased outputs. Further, 38% said it was a reluctance to allow AI to make decisions without human oversight. While you don’t need perfect data to start using LLMs, you absolutely need trustworthy data. 

The layer that’s actually missing 

The gap between your ERP and your AI ambitions isn’t a data gap. It’s a business logic gap — the layer where your organization’s specific rules, methodologies, and decision criteria live, and where AI needs to operate to produce outputs you can stand behind. 

When that layer is built correctly — logic documented, workflows repeatable, outputs traceable — AI has validated, structured inputs rather than raw data it has to interpret. Outputs can be explained to auditors and to the board. And the sequencing question resolves itself: getting the process right is how you adopt AI. 

What it takes to build that layer 

Closing the gap takes more than a mandate to “use AI responsibly.” It takes three specific things, built and owned inside finance rather than handed off to IT. 

• A purpose-built data asset for each process. Not another warehouse but a narrow, well-defined data set scoped to one process that reflects how your team measures it, not just what your ERP happens to store. 

• Encoded logic, not tribal knowledge. The allocation methodology or the variance threshold that triggers escalation — built into a repeatable workflow instead of a senior analyst’s spreadsheet. The shift is building it once; in a form AI can use. 

• A way to update it when the business changes. Comp plans get revised, tax jurisdictions shift, and the chart of accounts gets restructured after an acquisition. Logic that can only be changed by submitting a ticket to IT will be stale before it’s deployed — the people who own the process need to be the ones who can adjust the rule. 

None of this requires waiting for a perfect architecture. The highest-value starting point is whatever process has your analysts fielding the same question, the same way, every single cycle. Encode that one workflow first, connect it to the AI tools your team is already using, and the logic compounds from there: the same governed calculation that answers one controller’s question can feed the scenario model that runs your next planning cycle. 

 To learn more, visit us here. 

Every CFO I talk to right now is under some version of the same pressure: the board wants AI, the business wants faster answers, and the finance team is often still reconciling spreadsheets. The promise of AI in finance is real. But so is the gap between that promise and what most organizations are able to deliver. 

I believe finance leaders need to be asking not simply, “How do we use AI?” but “What would make our data trustworthy enough for AI?” 

That distinction matters. AI-ready finance data is intentionally shaped for a specific business outcome, so we can trust what AI produces from it. In finance terms, it’s the difference between having transactions and being able to defend the numbers. 

Finance data is uniquely messy, and important 

Finance data is messy for rational reasons. We pull from multiple systems — ERP, CRM, payroll, procurement, planning tools, banks, data warehouses, and yes, still spreadsheets. 

We live through reorgs, acquisitions, new products, and chart of accounts changes. And when the business cannot wait, we create manual workarounds to keep moving. 

That complexity is the context in which we’re now being asked to use AI. It’s no wonder that so many initiatives stall. 

The non-negotiables of AI-ready finance data 

When Alteryx talks about AI-ready data, I translate it into a few non-negotiables. For finance leaders, this is where the concept becomes practical. 

• Purpose-built, not “all the data” – AI-ready data should be scoped to the decision or workflow at hand. If I am building a cash forecast, I do not need every field from every ledger table. 

• Clean and standardized – AI does not politely ignore bad inputs; it often amplifies them. That means your data needs to be deduplicated, standardized across dates, currencies, and units, and mapped to consistent hierarchies. 

• Combined across sources, with business context – Finance work is inherently cross-source. AI-ready data is joined and enriched so the dataset reflects business reality, not just system silos. 

• Traceable and transparent – This is where finance leaders should push harder than anyone else. AI-ready data has lineage. It is auditable and explainable, not just at the output layer, but in the data shaping behind it. 

• Governed and controlled – AI readiness is about data risk management as much as data quality. AI-ready data should live inside a governed process, not a series of hero spreadsheets and copy-paste steps. 

• Maintainable as the business changes – This is one of the hidden killers of AI initiatives. A one-time cleaned dataset is not AI-ready if it breaks the minute a new subsidiary is added, a cost center structure changes, or a revenue stream appears. AI-ready data has to be built through workflows that can be updated and re-run reliably, not through one-off cleanups. 

Where AI-ready data creates value in finance 

This is where the concept becomes real. AI-ready data is the difference between value and noise in some of finance’s most important workflows, including: 

• Close acceleration: When trial balance data, mappings, intercompany logic, and exception rules are standardized, finance can generate more dependable variance flags and automate more of the financial close and reconciliation process. 

• Cash forecasting: Better-connected bank data, AR/AP, billing schedules, and seasonality drivers make forecasts less likely to be derailed by missing or misclassified transactions. 

• Anomaly and fraud detection: Clean, aligned vendor master data, payment runs, approval chains, and PO matching help teams reduce false positives and investigate issues faster. 

• Revenue quality and leakage: When contracts, invoices, usage, CRM data, and credit logic are brought together in a way that reflects the actual economics of the business, AI can help surface patterns that matter. 

• Narrative reporting: Grounding LLMs in curated, reconciled variance drivers and approved definitions allows teams to draft commentary responsibly within clear guardrails. 

Filling the AI data readiness gap 

I’ve found that in most organizations, there’s a constant friction point between data engineering and finance. Engineering understands the architecture, pipelines, and platforms. Finance understands the business context and logic — how revenue is recognized, how allocations work, where the exceptions hide. 

The handoff between those groups is often slow and messy. Analysts build fragile workarounds. Engineering teams inherit backlogs of finance requests that are actually business critical. 

What resonates with me about Alteryx is that it sits in that gap. It enables finance and business analysts to build repeatable data workflows for extracting, cleaning, joining, enriching, and shaping data for specific finance use cases. 

It emphasizes transparency and traceability, and it supports a model where IT can govern, and finance can execute. Just as importantly, it helps organizations turn their existing ERP, warehouse, and cloud investments into outputs that are actually usable for analytics, automation, and AI. 

How to get started 

If you want to make progress without boiling the ocean, my practical advice is simple: start small and start right. 

• Pick one workflow that is high pain and highly repeatable (recs, allocations, forecasting inputs, reporting packs). 

• Define what “trusted” means: the reconciliation rules, thresholds, approvals, and audit trail you need. 

• Build the AI-ready dataset first cleaned, joined, governed, and repeatable. 

• Then add AI where it makes sense (classification, summarization, exception explanation) inside the workflow, not as a free-floating tool. 

My bottom line is this: AI-ready data is an operating standard. It is how we scale AI without scaling risk. And for CFOs, that should be the real objective, not chasing the latest tool, but building the trusted data foundation that makes smarter automation, better decisions, and more resilient finance performance possible. 

To learn more, visit us here.  

Say your reconciliation tool flags a break between two ledgers, and now there’s a number that needs an explanation. The AI-generated summary says the mismatch is a timing difference, transaction posted late on one side. Reasonable. You move on. 

Then your controller asks which transaction, on which date, and why it posted late instead of on time. And now you’re not looking at an explanation anymore. You’re looking at a sentence that sounded like one. 

The four part test behind every AI answer 

That gap is the same thing the last piece here named: can you explain where the answer came from, and would the explanation survive someone pulling on it? Most practitioners have been running that check for years, on spreadsheets, on junior staff’s work, on their own numbers before a review meeting. AI just hands you answers that sound complete far more often now, and faster than the checking can keep pace with. 

The test itself breaks into a few plain questions, and it’s worth naming them because most people run all four without thinking about them separately: 

• Visible: Can you see where the number came from? 

• Understandable: Do you actually understand the logic that produced it, or just the sentence describing it? 

• Repeatable: Would the same input produce the same answer next time, or is this a one-off? 

• Auditable: Could someone other than you retrace it if they had to? 

Four different failure modes, and an AI-generated explanation can fail any one of them while still reading like a good answer. 

Why the gap is widening faster than the checking 

The reconciliation example holds up because it’s ordinary. Nobody’s arguing AI shouldn’t touch reconciliation work. Matching balances, drafting a first-pass explanation for a variance, flagging what needs a human look — that’s real time back. The problem isn’t the AI doing that work. It’s that the logic behind “this is a timing difference” has to already be defined somewhere the AI can point to. If it isn’t, the model is pattern-matching its way to something plausible, and plausible is not the same as traceable. 

Deloitte’s Finance Trends 2026 survey of over 1,300 finance leaders found 63% have fully deployed AI in their departments, with only 21% reporting clear, measurable ROI. That’s a broader adoption figure than an explanation-quality study, but the gap it points to lines up with the reconciliation example: plenty of AI running, not much of it yet standing up to scrutiny. 

Where the logic has to live 

Closing that gap starts with what the AI is drawing from in the first place, before it ever produces an answer. Every explanation an AI generates borrows its logic from somewhere: a threshold for what counts as material, a rule for what makes something a timing difference, an assumption about which system wins when two ledgers disagree. When that logic lives only as a pattern the model has inferred from past examples, the explanation is a guess dressed in confident language. When it’s defined, owned, and applied the same way every time, the AI has something real to summarize. 

Finance has kept this kind of logic for as long as the job has existed, often in a spreadsheet somebody built years ago that everybody trusts without fully remembering why it works. That logic hasn’t changed. Who can now touch it, and how fast, has, and that means the definitions underneath it need to hold up to more traffic than they ever have before. 

Get that part right, and the reconciliation example flips. The AI’s explanation becomes a summary of logic that was already defined, applied consistently, and traceable back to where it came from — the version that survives the follow-up question. 

See trusted AI workflows in action 

If you want to see what that looks like in a live workflow rather than in the abstract, Alteryx’s AI-Ready Starter Kits are pre-built Alteryx workflows and synthetic datasets designed to demonstrate how Alteryx can be applied to specific business use cases. They prepare and structure data to produce analysis-ready outputs, which can be extended using external AI tools. 

The Reconciliation Exception Resolution AI-Ready Starter Kit shows the pattern from this piece in practice: exceptions routed to an owner, prioritized by materiality, and documented consistently enough that the resolution holds up when someone asks how you got there. 

To learn more, visit us here.

There’s a specific moment every finance leader knows. A number is about to leave the building — headed for the board deck, the earnings call, or the audit committee — and right before it goes, you pause. You want to know where it came from, and you want to know it will still make sense if someone asks how you got it. That pause happens no matter what produced the number. 

That instinct shows up in the data too. In a Gartner survey of more than 200 CFOs, confidence across finance leaders’ top 2026 priorities averaged around 63%, while confidence in driving enterprise AI impact came in at just 36%. 

Leaders aren’t lacking confidence broadly. They’re confident about cost discipline and growth investment. The drop is specific to AI. It’s a broader measure than any single number leaving the building, but it points in the same direction: AI is the one place finance leaders can’t yet count on the confidence that usually comes easily. 

The four things every number has to pass 

That pause is a fast version of a test. Before you’d trust a number, you check four things: 

• Where it came from 

• Whether you could explain it simply 

• Whether it would come out the same way twice 

• Whether you could trace it back through the data if someone asked 

Most finance leaders have never written that test down. They’ve never had much reason to, because until now, the systems producing their numbers usually held up well enough that the check rarely turned into a real problem. 

AI doesn’t automatically pass that test. It can produce a plausible answer to almost anything, including things it has no real basis for knowing, and the answer looks the same whether the logic underneath is solid or made up. That’s the real source of the confidence gap. 

Leaders don’t doubt that AI can help. They doubt whether they could explain the answer if someone pushed back on it. The four things finance leaders already check for come down to four words: visible, understandable, repeatable, and auditable, or VURA. Those words succinctly describe what leaders were already checking for instinctually. 

Who owns the logic underneath 

Naming the test doesn’t resolve where it gets applied, though. That takes a harder answer about where the logic itself lives. Deterministic logic is defined by finance, not inferred by AI. A model can draft a variance commentary, summarize a forecast, or flag an anomaly worth a second look. 

It should never be the one deciding what counts as an exception, how revenue gets recognized, or which threshold triggers an escalation. Those are calls finance makes, and AI’s job is to work within them, explain them, and apply them consistently, not to invent them when it doesn’t have enough to go on. 

That distinction is where most AI disappointment in finance actually starts. The model usually isn’t failing at what it’s good at. The failure happens earlier: nobody defined the logic it needed, so it guessed, and it delivered that guess with exactly the same confidence it would use for a right answer. Looking at the output alone, you can’t tell the difference. 

That’s exactly what the four-question test catches. Ask where the number came from, whether you can explain it, whether it repeats, and whether you can trace it back to the data, and you’ll find out fast whether the AI applied logic finance defined or made something up that looks close enough. 

Building the standard into the workflow 

This is an architecture decision as much as a governance one. The four questions get easy answers when there’s a layer between raw enterprise data and the AI consuming it, one that prepares the data, holds the logic finance owns, and keeps every output traceable back to both. 

That’s the role Alteryx plays. It doesn’t compete with the model doing the reasoning, and it doesn’t replace the ERP or EPM system the data lives in. It’s the business logic layer that makes sure what reaches the model is something finance already stands behind, so the model’s output can be too. 

Build that in, and the pause before the number goes out changes what it’s doing. Instead of hoping the number will hold up, you can check that it does, every time, because the answers to those four questions are already built into how the workflow works, not something you have to reconstruct from memory. 

If you’re looking for a concrete way to see what that looks like on a real workflow, take a look at our AI-Ready Starter Kits: pre-built Alteryx workflows and synthetic datasets designed to demonstrate how Alteryx can be applied to specific business use cases. They prepare and structure data to produce analysis-ready outputs, which you can then extend using external AI tools such as large language models. 

Understanding why finance leaders hesitate to trust AI is only the first step. The next is building the governed foundation that gives AI reliable business logic to work from. 

Learn more in Building Finance AI You Can Trust, where you’ll explore the principles and practical steps behind AI-ready finance workflows. 

 To learn more, visit us here. 

If you work in finance, you’ve probably been handed an AI tool in the last year or so. Maybe a copilot in your spreadsheet, maybe something bolted onto the close, maybe a chatbot that promised to answer any question about the numbers. And maybe, if you’re being honest, it hasn’t changed your Tuesday very much. 

You’re not doing it wrong. The tool isn’t broken. What’s missing is the part nobody put on the slide: AI is only as good as the work it’s standing on, and most of the time, the work underneath it is a mess. 

Confident AI answers you can’t trust 

Here’s a familiar scene. Someone asks the AI assistant a reasonable question — “why did margin move in the East region last month?” — and it produces an answer that sounds great. Confident. Well-organized. Possibly even formatted with little bullet points. The only problem is that you have no idea whether it’s right, because you don’t know which data it pulled, whether it used the current cost allocation method, or whether it quietly grabbed last fiscal year’s calendar. 

So you do what any sensible finance person does. You check it by hand. Which means the AI didn’t save you the work. It added a step. 

This is the quiet truth about why so much finance AI stalls. It’s not that the models can’t reason. It’s that they’re reasoning over data that was never cleaned, rules that were never written down, and logic that lives in one analyst’s head and three tabs of a workbook nobody else can open. AI didn’t create that gap. It just made it impossible to ignore, because now something is making decisions on top of it. 

McKinsey looked at how finance teams are actually using gen AI and found a useful counterexample. Across the handful of finance functions where they saw AI adopted in earnest, professionals were spending 20 to 30% less time crunching data — and putting that time back into the analysis their job is supposed to be about. In one case, a global consumer goods company pointed a gen AI assistant at budget-variance work and saw roughly 30% of that manual effort disappear. That’s a real result. But notice what made it real: it was pointed at a specific, repeatable task, working from data the team had already organized around a shared definition of what “variance” even means. The AI didn’t figure that out on its own. The team handed it a problem that was ready to be automated. 

What separates the workflows that pay off 

The finance work where AI delivers tends to share a few traits. It’s bounded — a clear start and end, not “answer anything about the business.” It’s repeatable, the same shape every month. And it’s tied to something that matters: cash, margin, risk, a number someone downstream is going to act on. 

That’s the easy part to say. The harder part is what has to be true underneath. For AI to work on one of those tasks, the data feeding it has to be prepared and validated before the model ever sees it. The rules — what counts, what gets excluded, how things roll up — have to be defined by your team and applied consistently, not guessed at by a model that’s never read your policy manual. And when the output lands, you have to be able to trace it back: which numbers, which logic, who signed off. In finance, that traceability isn’t a nice-to-have. It’s the difference between an answer you can put in front of an auditor and one you can only put in front of people who won’t ask hard questions. 

Think about the difference between two versions of the same workflow. In one, the AI reaches into raw data, applies whatever it infers the rules to be, and gives you a number. In the other, the data gets cleaned and structured first, your team’s actual business logic gets applied to it, and only then does AI work on top of a foundation it can stand on. The first one feels faster right up until something’s wrong and you can’t tell why. The second one is the one you can defend in a meeting. 

That’s really the test worth applying to any AI effort on your desk: can you explain where the answer came from, and would the explanation survive someone pulling on it? If yes, you’ve got something worth scaling. If no, more AI won’t fix it — it’ll just produce wrong answers more quickly. 

Where this leaves you on Monday 

None of this means starting over. The business logic your team has built — the spreadsheets, the rules, the institutional memory of how things actually work here — is the valuable part. The goal isn’t to throw it out for an AI that doesn’t know any of it. It’s to get that logic into a form that’s governed and repeatable, so AI can finally do something useful with it. 

The most practical move is also the least dramatic. Pick one workflow. Not the whole close, not “AI across finance.” One bounded, repeatable, annoying task you’d happily never do by hand again — invoice matching, a recurring variance pull, a report you rebuild every month. Get the data right for that one thing, write the rules down, and put AI to work on top of it. When it works, you’ll have something real: a workflow you can trust, and a clear sense of what the second one should be. 

Two traps worth naming, because they’re the ones McKinsey watched teams fall into. One is waiting for perfect data before you do anything — you’ll be waiting forever, and the team next door will have shipped three workflows by the time your data is pristine. The other is the opposite mistake: automating a process that’s still a tangle of exceptions and one-offs. Drop AI on top of a fragmented workflow and it doesn’t simplify it, it just adds a confident-sounding layer to the mess. The move is in between: standardize the one thing first, then automate it. 

If you want a low-stakes way to see what that looks like before you commit, our AI-Ready Starter Kits are built for exactly this. AI-Ready Starter Kits are pre-built Alteryx workflows and synthetic datasets designed to demonstrate how Alteryx can be applied to specific business use cases. They prepare and structure data to produce analysis-ready outputs, which can be extended using external AI tools such as large language models (LLMs). They won’t run your finance function — that’s not what they’re for. But they make the shape of a workflow that actually pays off tangible enough to copy. 

The AI on your desk isn’t the problem. The work underneath it is. Fix that for one thing, and you’ll stop wondering why AI hasn’t paid off — because it finally will. 

Search our full AI-Ready Starter Kit library to find finance use cases fit for you and your team. 

To learn more, visit us here.

The intuitive way to help a coding agent is to give it more. More context in the prompt, more documents in the window, and the whole project history pasted in before the real request. The more the agent knows, the better it should do.

The catch is that an agent will use everything you give it and weigh details that have little to do with the task at hand. Without a way to judge what’s relevant to your teams, it’s the agent’s first day on the job every time, and the output gets less reliable and more costly as a result.

Why relevance beats volume

An agent given too much context doesn’t ignore the noise. A stale decision from a project that was abandoned, a requirement from a different part of the system, a comment thread that was later reversed — all of it becomes input, and the agent has no reliable way to know which parts still matter. This results in context drift: work that’s confidently built on the wrong basis and token inefficient.

This is why giving an agent access to everything tends to disappoint. The knowledge an agent needs for a given task is usually a small, specific slice: the requirements for this feature, the decisions that still hold, the constraints on this part of the system. The value is in delivering that slice and leaving the rest out, so the agent reasons over what’s relevant instead of everything the team has ever written down.

Ground agents in trusted knowledge

The raw inputs your agents need already exist: the requirements, the acceptance criteria, the decisions, and the reasons the work is shaped the way it is. What most teams lack is a knowledge graph that can make sense of it, distill the relevant slice, and feed only that to the agent. More specifically, it needs to:

Scope context to the work at hand. An agent picking up a piece of work should draw on the requirements, acceptance criteria, and decisions attached to that specific work — not a generic dump of everything. When the context is scoped to the task, the agent builds against the real target instead of reasoning over things that don’t apply.

Bring the history that still holds. Most work connects to work that came before it. An agent that can see the related decisions and the reasons behind them, filtered to what’s still current and relevant, avoids resolving old problems and contradicting choices the team already made. The filtering matters as much as the access.

Write results back so the record stays current. When an agent completes work, what it did and why should flow back into the system of record. That keeps the record an accurate account of the work, so the next task, and the next agent, inherits context that’s current rather than stale.

Make scoping automatic

Relying on developers to handpick the right context for every task doesn’t scale, and it makes the quality of an agent’s work reliant on what someone remembered to include. Connecting the knowledge graph to your agents lets the relevant context flow automatically, scoped to each task. Then an agent starts from what applies without anyone assembling it by hand.

Done this way, the system of record becomes the live source agents draw from, and it earns its keep twice: once when people plan and track work in it, and again when it feeds agents exactly what each task needs.

What this means for leaders

The instinct is to invest in more capable agents, but the higher return (namely, more accurate outputs and fewer tokens spent) is often in the context you feed the agents you already have. An agent working from the relevant slice of your system of record produces work that reflects what your team decided and can be traced back to a real requirement.

See how leading engineering organizations give agents clarity before they write a single line of code.

A sharp spec gets an agent building the right thing, but a deliberate review is what makes the result something you can stand behind. As agents generate more code, the challenge facing engineering leaders is remaining accountable for the output. Developers say it plainly: “The agent’s work has my name on it.”

This puts review at the center of engineering quality rather than at the end of it. Review is where a team decides what it’s willing to stand behind, what it trusts enough to ship, and what it needs to look at harder before anything reaches production.

Why the old review model can’t keep up

A pull request written by a person carries signals a reviewer reads without thinking about it: who wrote it, the shape of the change, the story the commits tell. Those signals are how a reviewer knows who to hold accountable and how hard to look. Agent output strips most of those signals away. The code is confident, well formatted, and plausible whether or not it’s correct — and it arrives faster and in greater volume than before. When review can’t keep up, work piles up waiting to merge, and the productivity gain the agent promised stalls at the pull request.

That leaves a gap right where accountability and security live. A change can look finished and still carry a subtle security flaw, mishandle sensitive data, or solve the wrong problem. When no one can say why an agent made a choice, no one can fully own the result. At the scale agents now operate, those small gaps compound into potential exposure.

What review has to establish now

Review stops being a single quality gate at the end of the work and becomes the step where trust, accountability, and safety are made explicit.

Establish accountability for every change. Agent authorship doesn’t remove human ownership; It makes naming that owner more important. Accountability starts with the developer who drove the change. They own the first pass: reviewing and accepting the agent’s output before it goes anywhere else. Peer review follows from there. A review process that records who accepted a change — and on what basis — keeps accountability clear as volume climbs.

Treat security and sensitive areas as their own tier. Not every change carries the same risk. A well-scoped change to a low-risk area can move quickly. A change touching authentication, data handling, permissions, or a core system earns deeper scrutiny. Making that calibration explicit means the highest risk work always gets a human’s full attention, no matter how much code an agent generates.

Make the agent’s reasoning reviewable. A reviewer who can see what the agent was told, what standards it worked against, and what tradeoffs it made can judge whether to trust the change. When that reasoning is missing, no one can verify the work, and trust becomes a guess.

Build the review layer on purpose

The organizations that get this right agree on what acceptance looks like before work starts, so review has a clear standard to test against. It means keeping the reasoning behind a change with the work itself, so it can be audited later instead of living in a chat history no one can find. And it means capturing what review surfaces, so a caught vulnerability or mistake protects the whole team rather than one reviewer.

The strongest organizations build these checks into the workflow itself. Automated review steps enforce the standards every change has to meet before it moves forward: Tests passed, security scans run, sensitive areas routed to a required approver, and nothing merged without a recorded owner. Automation handles the mechanical checks that are easiest to skip under pressure so that human review can go deep on the judgment calls that actually need it. Done this way, review scales with the volume of agent-generated code.

What this means for leaders

Speed from agents is easy to get. Trust in the code they generate is not, and it’s what your organization is accountable for. Review is where you build it. Invest there, and agent output becomes something you can scale with confidence.

See how leading engineering organizations are building review into their agentic workflows.