How this works Results

Company

About Ways to work FAQ

Insights

Blog Resources Find my biggest win
For Canadian manufacturers running Infor VISUAL

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

You run Infor VISUAL. It holds years of orders, every job, every invoice, and it still can't tell you which customers went quiet or which numbers moved this month. So every report is another export to Excel, rebuilt by hand. The canned reports you already pay for are hard to read. There's a cleaner way to get your data out, and it isn't a new ERP.

Find my biggest win Show me the VISUAL 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.

My engineers connect by API, read-only. Nothing in your ERP changes without your say-so. VISUAL keeps running exactly as it always has. No rip-and-replace, no migration, no re-training your people on a new system. I pull the answers out of the ERP you already run and build the dashboard, the lapsed-customer list, or the report you actually needed on top of it.

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.

Industrial manufacturer · 1st project

A third of their customers had quietly stopped buying.

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
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
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

Every figure here is from a real, paid engagement. Clients are de-identified at the client level: the names are gone, the numbers are not. See all the work

“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.

  1. 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.

    Find my biggest win
  2. $1,497 flat · one hour · credited

    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 full $1,497 comes off your build if we keep going.

    Get my AI roadmap
  3. $10K–$95K fixed, by scope

    The Build.

    A live dashboard on your VISUAL ERP, like the one above, or one painful workflow gone. Smaller builds start at $10K; the biggest system builds run to $95K. For scale: the dashboard build above ran about $55K. Either way it's one fixed number, quoted in writing before work starts, first proof in 14 days, and I don't leave until it's running without me.

    Price my build

Let's get your data out.

Proof in 14 days. Adoption for as long as it takes. The call is where it starts: one problem, one quick win, no prep needed.

  • A working session, not a sales pitch
  • One fix you can make this week
  • A straight answer on what's safe with your data
  • My engineers connect by API, read-only. Nothing in your ERP changes without your say-so

Want the numbers first? See the work.

Taking on 3 new engagements this quarter

Find my biggest win

Pick a time above, or email [email protected]. 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.

Find my biggest win