Low-Code / No-Code Platform Development

When the workflow shape is well-understood, the user count is in the hundreds to low thousands, the integration surface is finite, and the platform's data model can absorb the domain without contortion. Low-code is excellent for workflow apps, inspection systems, permit platforms, and internal admin tooling. It is a poor fit for high-throughput consumer experiences, deep domain modelling, or platforms that need to evolve faster than the vendor's release cadence.

OutSystems for the regulated, integration-heavy work we do most of — government regulators, energy authorities, large internal platforms. The lifecycle tooling and integration story is, in our experience, more enterprise-ready. Mendix is the right call for data-intensive applications inside Siemens-aligned estates or where domain modelling is the dominant complexity. Both can be delivered well; both can accumulate technical debt fast if the governance is weak.

Only if the governance is weak. The same drag-and-drop interface that accelerates delivery also makes it easy to ship something that does not survive contact with the next requirement. We deliver low-code with the same discipline as custom development: architecture standards, code-review gates, naming conventions, reusable component library, ALM, and a Centre of Excellence model. Low-code without that discipline is a liability waiting to surface.

Real, and worth pricing into the decision. OutSystems, Mendix, and Salesforce all create platform lock-in by design — that is the trade for the acceleration. We design integration boundaries so the business logic that has to outlive the platform decision is in services we control, not in the platform's proprietary primitives. That does not eliminate lock-in; it bounds it.

Yes — this is a standard engagement shape. Platform selection, governance framework, code-review standards, citizen-developer programme design, reusable-component library, and capability transfer to the internal CoE team. We have built CoEs that operated for years after we left.

Both. Salesforce is custom Apex, Lightning Web Components, Experience Cloud, and MuleSoft-Salesforce integration — not declarative-only delivery. Microsoft Power Platform (Power Apps, Power Automate, Power BI) is the cost-effective choice for internal tooling and process automation inside Microsoft-aligned estates. Different platforms, different fit.