
Hi, I'm Heinricht.
I'm a software & systems builder — operator-tested, ERP/WMS focused. I built the OpsUI platform — a modular ERP, WMS & CRM for Australian and New Zealand operations — and I'm the author behind this knowledge platform.
Based in Wainui, north of Auckland. 6+ years building software — game systems at Hytech Studios that reached 20+ million player visits, then product, marketing and growth for ValoTracker, a Discord platform that scaled to 40,000+ servers. Three-plus years on the warehouse floor too — Arrowhead Alarms and Mighty Ape — picking, packing, dispatch, RMAs, peak Christmas stock control, including 2+ years operating NetSuite (Oracle ERP) daily. Built products at scale, learned operations on the floor, then built the software for it.
Heinricht Smith is a software & systems builder — ERP/WMS & NetSuite focused — who built OpsUI, and the author behind the ERP knowledge platform at community.opsui.co.nz. He writes about enterprise resource planning architecture, financial modelling, implementation risk, and ANZ compliance — drawing on 6+ years building software across games, SaaS and ERP (game systems at Hytech Studios, ValoTracker at 40,000+ Discord servers), 2+ years operating NetSuite (Oracle ERP), and operator experience at Arrowhead Alarm Products and Mighty Ape.
ERP buyers don't have anywhere to turn for honest analysis.
When I was on the floor at Arrowhead and Mighty Ape, I kept seeing the same gap: how the systems were designed, and how the work actually happened. Vendors sold the design. Consultants billed the gap. The buyer was on their own.
That gap is why ERP implementations fail at the same 50–75% rate they've failed at for two decades. It's not a technology problem. It's a knowledge problem.
This knowledge platform is the long-form version of every conversation I'd have with a buyer trying to navigate ERP selection on their own. It covers the 17 clusters that matter most — vendor landscape, architecture, cost modelling, failures, compliance, industry-specific considerations, and module deep-dives.
Vendor-neutral by design. I run a product (OpsUI) but the analysis covers SAP, Oracle, Microsoft, NetSuite, MYOB, Workday, Sage, Infor, Xero, and Odoo the same way.
Where to start.
Four pillar clusters covering the questions every ERP buyer needs answered before signing anything.
Architecture & System Design
ERP architecture fundamentals, modular design patterns, and system integration approaches.
Cost & Financial Modeling
True cost of ownership analysis, ROI frameworks, and financial modeling for ERP decisions.
Failures & Risk Analysis
Why ERP implementations fail, risk assessment frameworks, and recovery strategies.
Compliance & Governance
ERP governance, internal controls, audit requirements, and NZ/AU regulatory compliance.
Quick facts about Heinricht Smith
- Role
- Software & Systems Builder
- Based
- Wainui, Auckland
- Founded OpsUI
- January 2026
- Background
- Ops + Engineering
OpsUI ERP Platform.
Complete guide to OpsUI modular ERP platform - transparent pricing, pay-for-what-you-need philosophy for NZ/AU businesses.
The knowledge platform is vendor-neutral, but it would be dishonest not to tell you what I actually build. OpsUI is a modular ERP — buy the modules you need, public per-module pricing, five users included on every plan, in-region data hosting in NZ and AU. The OpsUI vendor cluster on this site covers the platform the same way the rest of the site covers SAP and Oracle.
I read every message.
Question about an article? Want a second opinion on an ERP evaluation you're running? Drop me a line on LinkedIn — the fastest reply path is a DM, and I'm usually under a day.
For OpsUI-specific questions (pricing, demos, integrations) the product site is the better path.