Enterprise & ERP integration
Software that sits on top of large ERP deployments and gives business users control of their own processes, without waiting on IT or a vendor change request.
- 01Every output change needing a ticket, a vendor and a six-week wait
- 02Business logic buried in configuration files only two people understand
- 03Documents and data that have to survive audit, archive and retention rules
- 04Integrations across Dynamics, AX, Navision and SAP that all behave differently
- 05Migrations that cannot take the system offline
Visual process design
Drag-and-drop designers that let business users build their own output and rules, replacing config files nobody wants to own.
ERP integration
Microsoft Dynamics, AX, Navision and SAP, including the data extraction and formatting layers between them.
Document output at volume
Conversion, layout, distribution and archiving, built multithreaded because enterprise volumes are unforgiving.
Rules engines
Business logic expressed where the business can see and change it, with an audit trail.
Careful migration
Replacing a core system incrementally, with both paths live until the new one has earned the traffic.
The bottleneck is never the software
In most enterprises the system can already do what the business wants. The problem is that changing it requires a ticket, an internal queue, a vendor, and a release window, so a request that takes twenty minutes of work takes two months of calendar.
Software that closes that gap is worth more than software that adds features. Give the person who needs the change the ability to make it safely, and the whole organisation speeds up.
What we have built
Advanced-Forms is enterprise Document Output Management: business users visually design how ERP data becomes documents, including layout, business rules, distribution and archiving, on top of large Microsoft Dynamics, AX and SAP deployments. We rebuilt its conversion core, turned its configuration files into a drag-and-drop designer, and led the product as technical manager and product owner over a team of twelve.
It displaced Microsoft, SAP and Oracle incumbents at customer sites, which happened because it removed the vendor from the loop rather than because it had a longer feature list.
Working in enterprise constraints
We expect the things that come with this sector: procurement, security review, on-premise or private cloud deployment, data residency, and a change process that exists for good reasons. Those are constraints to design around rather than obstacles to complain about.
What we will push back on is a specification that encodes the current process without asking whether it should exist. That question is usually where the value is.
Tell us the one thing it has to do.
If it's sharp enough to prove in a week, we'll say so and give you a date. If it isn't, we'll tell you that too, along with what we'd build first instead.