Using Low Code / No Code Approaches#

Today I’ve been working on a low code / no code solution for a client.

They needed to automate a number of tasks, but without the overhead of maintaining their own IT infrastructure or investing in a fully custom-built system — something they neither had the desire nor the in-house capability to support.

In this case, I used Microsoft Power Automate as part of Microsoft 365. The specific tool isn’t the important part — what matters is that it provides a way to automate business processes without writing code, and without introducing additional infrastructure.

As a simple example, when a form is submitted, a record is automatically created in SharePoint and the relevant people are notified.

Previously, this wasn’t automated. The assumption was that this kind of process required a bespoke solution and would be expensive to implement, but in many cases that simply isn’t true. This change removes a manual step and ensures submissions are no longer missed.

A low code approach can handle a surprising amount of day-to-day operational work — particularly where processes are repeatable and well-defined. It allows organisations to move quickly, reduce manual effort, and avoid the long-term burden of maintaining custom software.

That said, it’s important to understand where the limits are. Low code solutions work best within the boundaries of the platforms they integrate with. Once requirements move beyond that — whether through complexity, scale, or performance — a bespoke solution may become the better option.

Understanding where each approach fits is key. Low code isn’t a replacement for software engineering, but it is a very effective tool when used in the right context.

Typical use cases for low code solutions (using Microsoft Power Automate as an example) include:

  • Automating form submissions and approvals
  • Notifications and alerts (email, Teams, etc.)
  • Data synchronisation between systems (e.g. SharePoint, Excel, CRM)
  • Simple workflows with clear, repeatable steps
  • Internal tools where speed is more important than customisation

Where things start to break down is when workflows become highly complex, require strict performance guarantees, or depend on integrations outside of supported platforms.

It’s important that low code solutions aren’t oversold. They’re not a silver bullet, and they won’t replace well-designed software where it’s genuinely needed.

That said, when used in the right context, they offer a very practical way to automate processes and deliver real value without the cost and complexity of a bespoke build.

As with most things, it comes down to using the right tool for the right job.

If you’re unsure whether a low code approach is suitable for your organisation, it’s often worth assessing the problem before committing to a full custom build.

Looking to automate business workflows, self-host applications, or build bespoke web tools? Find out about my software development services at Protoworks (NI).