For Canadian manufacturers running Infor VISUAL

Infor VISUAL dashboards and reporting, without exporting to Excel and rebuilding it by hand.

I use the order and operational data you already hold in Infor VISUAL to answer specific questions: which customers went quiet, what changed in sales, and which reports your team keeps rebuilding. One manufacturer used a read-only connection for customer intelligence and a live KPI dashboard. The first step for your business is checking the data, access and question that matter most.

Talk to Steve Show me the VISUAL work

For quoting, order patterns and reporting beyond one ERP, see my manufacturing AI consulting work.

The data's all in there.
VISUAL just won't hand it over.

If you run Infor VISUAL, you know the routine. Six years of orders, every work order, every labour ticket, every invoice, all sitting in there, and you still can't ask it a simple question: which customers went quiet, which jobs actually made money. The answers are in VISUAL's SQL tables, but they live behind Crystal reports only one person knows how to change. So getting a report out means the same drill every time. Export to Excel, rebuild it by hand, fight the dates and the dropped leading zeros, and hope the numbers tie out. The reports that came with VISUAL are hard to read, and the good ones cost extra. None of that is your team's fault. VISUAL was built to run the operation and hold the record, not to answer questions on demand. The data is all there. It just needs a way out.

The fix isn't a new ERP

I read what's already in VISUAL, and build on top of it.

For the manufacturer below, my team used a read-only API to work with VISUAL data while the ERP kept running. That access method is a project fact, not a promise about every installation. I check your version, permissions and source data before proposing a connection or a dashboard. Any build, training and handover are scoped in a written quote.

One VISUAL manufacturer · three projects

What I built on top of their VISUAL.

Every build below sits on the same industrial manufacturer's Infor VISUAL, in order. My engineers work read-only, by API, and nothing in their ERP ever changed. I found the problem, shipped it, and they brought me back. Then brought me back again. That's the part no case-study number can fake.

account trajectory · 6 yrs of ordersrefreshes quarterly

264 / 804accounts flagged lapsedtop account $67K → $0

Industrial manufacturer · 1st project

A third of their customers had stopped buying, and nobody noticed.

Six years of orders sat in their Infor VISUAL ERP, and it couldn't answer a single question about who was slipping away. Their top account, worth $67K a year, had already gone to zero. Nobody had noticed.

My engineers built the first read-only API into their VISUAL here, and I built an AI system that classifies all 804 accounts by buying trajectory. It flags the accounts whose ordering rhythm breaks, a steady customer that suddenly goes quiet, surfaces the cross-sell openings, and refreshes itself every quarter. The ERP finally talks.

264lapsed accounts found (33%)
$67Ktop account, gone to zero
199cross-sell openings surfaced

segment map · 804 accounts6 segments

152net-new prospects, SKU-matched

Same manufacturer · 2nd project

One pitch for every buyer became six playbooks.

More than 800 accounts were all treated the same way, so every new rep spent months just learning the base before they could sell to it.

I classified all 804 accounts into six clear segments, matched 152 net-new prospects to the exact products they'd buy, and wrote a sales playbook for each segment. A new rep now knows who to call and what to say on day one.

804 → 6accounts into clear segments
152net-new prospects, SKU-matched
6sales playbooks built

erp → live dashboard · Infor VISUALlive via API

3 hrs/wkback · manual exports gone

Same manufacturer · 3rd project · Infor VISUAL

Every report meant exporting the ERP into Excel and rebuilding it by hand.

By the third project they trusted me inside their data, so they handed me the reporting that was still eating their month-end. Their VISUAL ERP held every number they cared about but couldn't show them, so month-end meant dumping data into a spreadsheet and rebuilding the same report by hand, every single time.

My engineers extended the same read-only VISUAL connection into a live feed, and I built a dashboard tuned to the exact numbers they actually watch. It refreshes itself. The manual export is gone, and they have at least three hours a week back. VISUAL kept running exactly as it always has. Nothing in their ERP changed without their say-so.

3 hrs/wkback from manual export reports
Liverefreshes by API, not by month-end export
3rdproject with this client

These are three projects for one manufacturer, not three separate clients. Clients are de-identified; the work is described in more detail in the lapsed-account case study and the VISUAL KPI case study.

Before a build

The useful questions come first.

The output should be a report your team trusts and uses. That starts with a small, testable question and the right access.

What data can I read?

I check your VISUAL setup, approved permissions and the fields needed for the question. I do not assume the same API or tables are available at every site.

How do we trust the answer?

We compare a small sample against known orders and existing reports, agree on definitions, then decide how often the result needs to refresh.

Who runs it after launch?

The quote sets out the dashboard or report, review steps, training, handover and any ongoing help. Your team keeps the decision on customer and operational action.

For a closer look at options on existing VISUAL data, read how to get more value from VISUAL. For work beyond ERP reporting, see all services.

“They've become a huge resource for us in AI and data intelligence. What stands out is their practical, business-focused approach. They don't just provide theory, they build real tools on our own data.”

Senior ExecutiveIndustrial Equipment Manufacturer, Canada

References available on request. Ask on the call and I'll connect you with a current client.

After it ships

Then I don't leave.

Most tools die because nobody stays past the install. Most consultants vanish after the invoice. I stay at your side, training your people, until it sticks. When your team runs the dashboard without me, my job's done, and not before.

How this works

Getting your VISUAL data out, in three steps.

You don't pick a service today. You book a call. Each step earns the next one.

Free

The 15-minute call.

One call, one problem. Tell me what you keep exporting out of VISUAL by hand, and you leave with one fix you can make this week, whether or not we ever talk again. No prep needed.

Talk to Steve
One-hour assessment · quoted by scope

The Assessment.

I go through your operation and hand you three to five moves, ranked by dollar impact and how easy they are to ship. Small enough to say yes without a board meeting. The scope and fee are agreed in writing before work starts.
Request an assessment quote
Fixed scope · written quote

The Build.

A live dashboard on your VISUAL ERP, like the one above, or one painful workflow gone. Deliverables, fees, timeline, training, handover and support are agreed in writing before work starts.
Request a build quote

Let's get your data out.

Bring one report you keep rebuilding or one customer question VISUAL cannot easily answer. I will help identify the next sensible test.

A working session, not a sales pitch
One fix you can make this week
A straight answer on what's safe with your data
We check approved data access before choosing a connection method

Want the numbers first? See the work.

Not on VISUAL? See AI for manufacturers and distributors.

Taking on 3 new engagements this quarter

Talk to Steve

Pick a time above, or email steve@wallai.ca. I reply personally, usually within a business day. No spam, no drip sequence. Same calendar for everything: if it's about the Assessment or a build, say so in the booking notes.