Enterprise platform delivery
MN.AI is a New Zealand practice covering ServiceNow, Salesforce, Appian and Power Platform, alongside bespoke Java engineering, platform data migration and systems integration. We work as a delivery partner to consultancies and system integrators, and directly with organisations who own the platform.
SNOWSFDCAPPNPWRPJAVAMIGRINTGEach of these is delivered by practitioners who have shipped the platform in production — not by generalists reading documentation for the first time.
SNOW
Scoped applications, workflow, portal
Scoped application build, Flow Designer workflow, Service Portal widgets, catalogue and record producers, ACLs and role design, and update-set packaging that imports cleanly the first time.
SFDC
Configuration, automation, Apex
Object and field design, record-triggered and screen Flows, approval processes, permission sets and sharing models, Lightning Web Components, and Apex where declarative tooling genuinely runs out.
APPN
Process, records, interfaces
Process models, record types and data stores, SAIL interfaces, expression rules and integration objects — packaged as deployable applications rather than hand-assembled environments.
PWRP
Dataverse, apps, automation
Dataverse table and relationship design, model-driven and canvas apps, Power Automate cloud flows, security roles, connection references and environment variables, delivered as managed solutions with a real ALM path.
JAVA
Services and applications
Custom services and applications where a platform is the wrong answer — or where a platform has reached its limit. Spring-based services, APIs, batch processing, and the test coverage to keep them maintainable after handover.
MIGR
Including Pega to Java, proven
Moving process, rules and data off a platform without losing the behaviour that mattered. Pega-to-Java migration delivered in production, with the rule logic reconstructed as tested Java rather than transliterated line by line.
INTG
Between platforms, and beyond them
Contract-first integration using OpenAPI as the portable layer, with platform-specific adapters either side. Built so the contract survives a platform being replaced — which, eventually, it will be.
Proof point
Platform exits are where most migration work quietly fails. Rules get translated instead of understood, edge cases surface after go-live, and the business discovers the new system does almost the same thing.
We have taken a Pega implementation to bespoke Java and into production. The approach was to treat the rule set as a specification to be reconstructed and tested, not a codebase to be ported — every behaviour re-expressed, covered by tests, and validated against the outgoing system before cutover.
The same method applies to exits from any rules-heavy platform, and to consolidation work where two platforms need to become one.
Most of our work reaches end clients through a delivery partner. We are comfortable being invisible in that arrangement, and equally comfortable in front of the client when that is what the engagement needs.
Named capacity for consultancies and system integrators who have won the work and need specialists who can deliver it. Under your brand, inside your governance.
One or more practitioners working inside an existing delivery team for a defined period, on your tooling and your ceremonies.
Discovery through to production for a defined scope, with the design documented well enough that someone else could maintain it.
Independent assessment of an implementation that has stalled, followed by the work to get it moving — including the parts nobody wants to write down.
Get in touch
Whether that is a platform you have won and need hands for, a migration nobody wants to own, or an implementation that has stopped moving — a short conversation will establish quickly whether we are the right people.
Or email us directly
directors@mnai.nz