Published 24 Sep 2026

Most finance teams I speak to describe the same week.
The reporting is quick now. Month-end numbers land faster than they did five years ago, and the variance is sitting on a dashboard before anyone asks for it. Then the real work starts.
Someone has to find out why. That means pulling data out of the ERP, the CRM and the spreadsheet that holds the adjustments, lining it all up, and writing commentary the CFO will trust. You spot the variance on Tuesday. By Friday you can say why it happened. The conversation about what to do comes after that, and sometimes the moment has already gone.
On Thursday, October 8, Paul Sutton and I are running a 45-minute educational session on what changes for finance when that gap closes.
Finance has spent twenty years getting the numbers right and getting them out on time. That work paid off. Close cycles are shorter, reports are more reliable, and most teams can tell you what happened with real confidence.
What happened was never the hard question, though. Reporting tells you where the problem is. It stops there. It won't tell you why revenue in one region came in under plan, and it won't tell you which of three possible responses is the right one.
The industry's answer for the last decade has been more dashboards. More views, more filters, more places to look. None of that made the explaining faster. It gave analysts more screens to check before they opened the spreadsheet anyway.
The Decision Gap is time. It's the stretch between seeing a problem and acting on it.
For most finance teams it runs to days, sometimes weeks. The cause is rarely bad data. Finance data is usually the best-governed data in the business. The delay comes from the work around it, which is stitching together several systems by hand, checking the joins, and turning the result into something a decision-maker can act on.
The goal is simple to state. Same-day. The variance appears, the reason is clear, and the team is discussing options before the afternoon is out.
Decision Intelligence answers three questions in order. What changed. Why it changed. What to do next.
BI and dashboards handle the first question well, and that's where they were designed to stop. Decision Intelligence works through the other two by reasoning across the data you already have, from several systems at once, and tracing a movement back to its drivers.
It doesn't replace the reports your team relies on. Those keep running. It adds the layer that finance has been building by hand in spreadsheets every month.
Paul and I will cover:
The last one matters most. It's easy to describe a faster answer. We'd rather show you one.
You'll leave able to explain Decision Intelligence to your CFO and your team in a couple of minutes, and with a clear view of which parts of your week it would change.
This session is for people who live with the gap between the number and the explanation. FP&A leads, controllers, finance directors and CFOs will get the most from it. Finance systems and IT people who get asked to "just build another report" will recognize a lot of it too.
If you've written variance commentary at nine o'clock at night because the numbers moved and nobody could say why, it's for you.
Can't make the live session? Register anyway and we'll send you the recording. If you want some background before the day, the replay of our earlier session, "What is Decision Intelligence?", is a good place to start.
New to the category? Learn what decision intelligence is and why it changes how teams act on data.

Vice President, Product Marketing
24 Sep 2026
Mark Hudson is VP of Product Marketing at eyko, where he leads positioning, content, and go-to-market execution for eyko Beats and the Decision Intelligence category. He founded and successfully exited two analytics companies, Antivia (acquired by insightsoftware) and Blue Edge Software (acquired by SAP BusinessObjects). His focus is helping decision-makers move past dashboards and reports to deliver action-based outcomes that drive better decisions.
Decision Intelligence for finance is software that answers three questions about the numbers finance already reports. What changed, why it changed, and what to do next. It reasons across data from the ERP and other business systems to explain a variance and recommend a response, work that finance teams usually do by hand in spreadsheets.
BI and dashboards show you what happened. They're built to display known metrics on a schedule. Decision Intelligence goes further by explaining why a number moved and suggesting what to do about it. BI points you to the problem. Decision Intelligence helps you understand it and act on it.
The Decision Gap is the time between spotting a problem and acting on it. In most finance teams it's measured in days or weeks, because explaining a variance means pulling and combining data from several systems by hand. Closing the Decision Gap means getting from the variance to a decision on the same day.
No. The reports your team relies on keep running. Decision Intelligence adds a layer on top of your existing data that handles the explaining and the recommending, which reporting tools were never designed to do.
The webinar is for FP&A leads, controllers, finance directors, CFOs, and the finance systems and IT people who support them. It's most useful for teams who can report a variance quickly but take days to explain it.
The webinar runs on Thursday, October 8, 2026, at 8:00am PDT, 11:00am EDT, and 4:00pm BST. It lasts 45 minutes and includes time for live questions.
Register anyway and we'll send you the recording after the session.
The latest industry news, interviews, technologies, and resources.

Three signs your JD Edwards reporting tool has been asked to do a job it was never built for, and where the line sits between reporting and deciding.
Read post

The case I would put in front of a board: five measurable components, five published benchmarks, and why decision intelligence and consulting solve different problems.
Read post

The AI data readiness pitch tells finance teams to rebuild before they can use AI. Jon Louvar, COO at eyko, on why the data your last audit ran on is the same data AI needs to reason over.
Read post