Someone built your OutSystems estate.
The apps still run. The reasoning behind them left.
We work on New Zealand's largest OutSystems platform, powering companies like McDonald's NZ. 10,000+ daily users.
Field notes
What we check,
and why it matters.
Free to read, nothing gated.
Latest
What still earns ODC
The deadline is gone. What is left is a business case per application, and most estates will pass fewer of them than they expected.
Read it →Earlier
Reading a factory before you quote it
What we look at before putting a number on someone else's estate, and the four things that actually blow up an estimate.
Read it →Earlier
Inheriting an OutSystems estate you did not build
What to check, in what order, and what each answer tells you. Eight sections.
Read it →What We Do
Most of our work starts
with an estate that exists.
Greenfield builds are last on this list for a reason.
01, Audit
Fixed scope
Platform audit and second opinion
The person who designed your platform is no longer the person running it. We tell you what you are holding, and what would hurt most if it broke next week.
Your platform vendor will not tell you the estate belongs somewhere else. The partner who built it will not tell you they are the problem. That is what an outside read is for.
- Architecture review
- Codebase health audit
- ODC migration feasibility
- Roadmap and recommendations
02, Migration
Fixed scope
O11 to ODC
Sequencing, data model continuity, integration cutover. The one-time project in-house teams should not have to learn on their own estate.
ODC is a different runtime, not an upgrade. The C# extensions usually set the timeline.
03, Capacity
Retainer
Senior capacity
Senior engineers embedded alongside your team, architecture depth included. Clean handover whenever your hiring catches up.
- Platform upgrades and patching
- Enhancement and bug tickets
- SLA-backed response
- Monthly health reports
04, Build
Scoped
OutSystems development
Enterprise applications on OutSystems, built without cutting corners on architecture or security.
- Architecture and domain design
- API and system integrations
- QA, UAT and deployment
- Knowledge transfer
Senior-only, no junior blend.
Most people start with 01. It commits you to nothing after it.
Featured Engagement
New Zealand's largest
OutSystems platform.
Stock control, delivery management, automated data exports and KPI reporting, across a live multi-restaurant estate.
The relevant part is not that we built it. It is that it is still running, still being changed, and has been for years.
Stock Control
Theoretical vs actual variance, with period-close reconciliation.
Delivery Management
State transitions, audit trails, rollback-safe stock movement.
Datahub XML Exports
Daily exports to a standardised global format, gap-filled.
KPI & Sales Reporting
Day-part sales, role-based access, country-specific defaults.