I Built Hubble for JD Edwards Reporting. Then I Started Over.

I have spent most of my career thinking about JD Edwards reporting.

I created Hubble Reporting (originally known as Insight Reporting) to help people get better reporting out of JD Edwards. Over 1,000 customers used it to pull live JDE data into reports they could actually work with, without waiting on IT or wrestling with batch jobs. We sold insightsoftware.com to TA Associates, where Hubble Reports lives on today.

Most people would call that a finished story. I didn't. I still had an itch to scratch.

What customers kept telling me

Two things came up in almost every customer conversation, and neither of them was really about reporting.

The first was that no business runs on a single system anymore. JD Edwards holds the financial and operational truth, but the rest of the story lives in CRM, HR, supply chain, and a dozen other places. A reporting tool that only sees JDE only sees part of the business.

The second was more uncomfortable. Even with great reporting, customers were still stuck on the questions that actually matter. A report can tell you DSO went up or margin went down. It cannot tell you why, and it certainly cannot tell you what to do about it.

The tools are good. That's not the problem.

Let me be clear about something, because I have skin in this game. The JD Edwards reporting tools available today are good. Hubble by insightsoftware, ReportsNow, QuickLaunch Analytics. These are strong products built by people who understand JDE deeply. I built one of them.

But they all share the same ceiling. They are built to show you what happened. Faster than native JDE reporting, more flexibly than One View, without dumping everything to Excel. All real improvements.

Understanding what happened is still the first thing business users want to know. And in most businesses, it's the easiest question to answer, as most have already solved their reporting requirements.

The Decision Gap

Here is the pattern I saw over and over. A finance leader spots a number that looks wrong in a report. Then the real work starts.

An analyst pulls extracts. Someone cross-references the CRM. There are meetings. There are follow-up questions, then follow-up extracts, then more meetings. Two or three weeks later, the team has a theory about why the number moved and a proposal for what to do.

By then the number has moved again.

This is the Decision Gap. Business intelligence made the "What" fast and cheap, and left us understanding the "Why" and the "What Next" as slow, manual, expensive work. The gap between seeing a problem and deciding what to do about it never really closed. BI just moved it downstream and called it self-service.

Why I started eyko

Insight Reporting, and later Hubble, was a market-leading product in its own right. That made the conclusion harder to accept, not easier. The market had moved. Customers needed analysis across all their business systems, not reporting on one. And as AI emerged, we could see how much of that multi-source problem it could take on.

The way I think about it: reporting gets you to where the problem is. It doesn't tell you what the problem is.

eyko exists to close that gap. Not by replacing your JD Edwards reporting tool, but by adding the layer that reporting tools were never designed to provide.

Three capabilities do the work.

Playbooks are structured, evidence-based briefings generated from your live data. Each one works through a real business question in three layers: what happened, why it happened, and what to do next. You get a narrative, root cause analysis, supporting evidence, and prioritized recommended actions. Not a chart to interpret. A briefing to act on.

Conversations let you interrogate the analysis in plain language. Ask a follow-up question, get a structured answer grounded in your actual numbers, with tables and charts inline. No SQL, no ticket to IT, no waiting for the next reporting cycle.

Pulses give you live, interactive access to your business data. Cards, tables, and charts you can explore and drill into using natural language, with no analyst configuration required. And each card includes Discover, which surfaces signals from the data: insights, trends, anomalies, risks, and opportunities, along with the recommended next action. You don't have to spot the problem yourself. The Pulse points at it.

Together, they compress the Decision Gap from weeks to hours. The investigation that used to take a cross-functional team most of a month happens in an afternoon, with the evidence attached.

And because eyko connects to your other business systems alongside JD Edwards, the analysis sees the whole business, not just the part that lives in JDE. That was the other half of the itch.

What this means if you run JD Edwards

Oracle has committed to JD Edwards Premier Support into the late 2030s. You are not migrating next quarter, and you shouldn't have to bolt on a data warehouse project just to get better answers out of a system you already trust.

Keep your reporting tool if it's working for you. It answers What, and it does it well. And if it isn't working for you, or you never invested in one, eyko handles the What too. It just doesn't stop there.

Then ask yourself how long your team currently spends getting from What to Why to a decision. If the honest answer is weeks, that's not a reporting problem. It's a Decision Gap. And it's now a solvable one.