Webinar | Impresoft GN Techonomy x Betty Blocks

Impresoft GN Techonomy x Betty Blocks

Discover how to use AI to build faster while keeping risks under control

Discover how to use AI to build faster while keeping risks under control

Discover how to use AI to build faster while keeping risks under control

Banner reading 'A Partner Webinar with Impresoft Gntechonomy'
Row of three headshots of webinar speakers

Presented by Fabio Marini (Senior Solution Architect at Impresoft GN Techonomy),

Dario Ambroggi (Director of Impresoft GN Techonomy), Chris Obdam (CEO of Betty Blocks)

15 July, 2026

Partner Webinar

JD Edwards

On 15 July, Fabio Marini (Senior Solution Architect, Impresoft GN Techonomy), Dario Ambroggi (Director, Impresoft GN Techonomy), and Chris Obdam (CEO, Betty Blocks) sat down to address a problem most JD Edwards organisations already have, whether they know it or not: business and IT users are wiring free, ungoverned AI tools directly into ERP and customer data, often without leadership ever seeing it happen. It works in the demo. It rarely survives contact with production.


The session walked through the alternative — building at AI speed while keeping governance, security, and the ERP core intact — and closed with a live build: a working portal on top of JD Edwards data, connected securely through GN's Gate.

Q&As

Questions from the webinar

How is this different from just using another AI tool to write code against our ERP?

The distinction raised was governance-by-design: rather than generating code that someone has to retroactively secure and document, the platform builds every application on a governed metadata model from the first prompt, so the audit trail and access controls exist before the app goes live, not after.

Does moving faster with AI mean giving up control over where our data goes?

The panel's answer: no — the live build showed the portal querying JD Edwards data directly through GN's Gate, with no data leaving the governed environment or passing through ungoverned third-party tools.

What happens to the application if we ever move off the platform?

Because the output is built on open standards and portable code, applications aren't locked to the vendor relationship — they can be deployed and run independently if that relationship ends.