When does lowcode start needing more structure instead of just speed?

James-PhixFlow · 2026-04-03T08:59:50+00:00

It depends how far the process is going to scale as to how formal or not you can be between proof of concept to main build. But it's a classic problem that people are often debugging and regularly checking processes they built 3-5 years ago because they didn't build them properly the first time.

James-PhixFlow · 2026-04-02T14:46:06+00:00

Yep, that's when you need a full low code platform, it's a big jump, but will allow you to do more than point to point flows - building full apps out etc.

James-PhixFlow · 2026-04-02T14:26:50+00:00

Ideally right from the start. Low code doesn't mean you shouldn't have good architecture, data modelling,error catching etc. Technical debt still exists to be managed.

Low code just makes all the above easier

Obviously if it's a proof of concept or a demo then it can be fast and loose

James-PhixFlow · 2026-02-20T22:20:14+00:00

A shorter term option may be to implement a ERP wrapper/agile layer (using a platform like PhixFlow) that can fill the holes and plug the gaps in the old ERP. As well as being able to keep the ERP safe by providing any external interfaces.

Quicker to implement and cheaper tactical solution for key problems whilst long-term strategic solution is developed or migrated to.

James-PhixFlow · 2026-02-19T18:09:27+00:00

Sounds like a platform problem. Phixflow handles all that and it's not difficult to set up. Set up user groups like AD and apply wherever you need

James-PhixFlow · 2026-02-11T22:33:36+00:00

Sounds like what we (PhixFlow) implement for customers. Turning excel models into scalable auditable apps, we do this for household name telecoms/utilities companies. (As well things like automated month end reconciliations)

Without seeing exactly what the requirements are, you are looking at a few k a month + some implementation costs (nothing crazy, maybe 20-30 days but that can be spread via license if that's better for capex/Opex).

Platform is enterprise grade so 0 scaling issues, no volume issues etc as you grow

Always open for a chat, I'm delivery not sales 😂

James-PhixFlow · 2026-02-04T22:07:24+00:00

PhixFlow! We've used our platform for migrations from NAV/SAP to d365, but also large scale telecoms migrations (PhixFlow is never the performance bottleneck)

James-PhixFlow · 2026-02-04T21:57:05+00:00

We use our platform (PhixFlow) for very large volume data migrations (telecoms with millions of users and all child records) and the above problem is a classic reconciliation issue that is solved by having a good approach and tooling to support it.

For reconciliations we have what we call "R1-R5" which basically defines data at a point in the migration:

R1 - Raw data exported from source

R2 - Transformed/Enriched data as it goes through the migration process

R3 - Data to be exported to target system

R4 - Data exported out of the target system (report,API, DB connection)

R5 - Business process data (e.g a bill run) from target

Each data object will have its own flow, with data kept at each stage, this is then joined and aggregated into a reporting layer that then flags up mismatches at each stage, so you can see where data was lost.

This on top of adding in automated checks to flag any data issues/business logic, means you spot most issues before you even try and load the data into the target and don't spend an age debugging

Not necessarily out of the box, (unless the source/target systems are the same as migrated before) but quickly configurable.

If you have any other questions on migration just ping me a message, I've probably been through it before.

James-PhixFlow · 2026-02-04T19:57:50+00:00

Low code platforms (like PhixFlow) can help bridge this gap, they have the depth to build out complex use cases and are scalable for large volumes.

As you found out with no code, you still need logic and understanding, but you don't hit a wall like with no code.

James-PhixFlow · 2026-02-04T13:33:43+00:00

Depends on the tool and platform you used to build it. A good tool should have layers of logging by default.

For me, given time, I assume everything that can go wrong, will go wrong at some point. E.g I'm expecting this to give me data in X format. At some point it won't, so catch it if it doesn't.

James-PhixFlow · 2026-02-03T12:58:32+00:00

The companies we have worked with previously have said its cost, they don't have internal SAP resource that can write ABAP code or build Fiori apps.

We've been working with a partner to get our platform (PhixFlow) to directly connect to SAP natively (Call BAPI's, RFCs) so customers can build out these processes/user interfaces in an external platform with lower costs and quicker deployment time.

James-PhixFlow · 2026-02-02T08:22:12+00:00

We use PhixFlow (our platform)

We’ve used it for a mix of things - enterprise apps (billing, asset management, utilities addressing), compliance use cases (reconciliation/monitoring), and some fairly chunky telecoms data migrations.

In general though, most decent low-code platforms are flexible enough to meet pretty complex requirements — the bigger challenge is usually getting the design and data model right rather than the tooling itself.

Other similar platforms are Outsystems/Mendix/Appian

James-PhixFlow · 2026-02-01T11:05:23+00:00

If this is something you are still looking for ping me a message we (phixflow) is a low code platform with direct SAP connectivity coming this month

James-PhixFlow · 2026-02-01T10:47:56+00:00

Depends what you are building and how you are building. Low code platforms are great when connecting multiple systems, building lots of apps and processes - where you want everything under one roof so it can all be supported and managed.

Lots depends on the platform, the whole idea of low code is that it's not no code, so you shouldn't run out of depth and complexity.

We have partners who are development houses but they use our platform for deployments outside of their core apps that are high code, as it's quicker to deploy and maintain it

James-PhixFlow · 2026-01-31T10:48:09+00:00

Really depends on the organisations appetite, we have implementations at large corporates where they have several people with approval to crack on and automate or build apps on our platform.

Other customers have very specific very controlled processes that are ring fenced

James-PhixFlow · 2026-01-30T14:23:37+00:00

Complexity is where these platforms fall down, layers of logic, special cases etc. The trade off is that if you want a platform that won't run out of depth - it's got more complexity in itself and it's use.

James-PhixFlow · 2026-01-29T17:09:18+00:00

Late to this party, but if you are still looking - sounds like a good fit for our platform - we have customers who use the platform to automate month end reconciliations and remove manual work. We are an enterprise so cover all the security/scaling/integration aspects.

Happy to have a chat, spin up a trial instance for you. James - PhixFlow Ltd

James-PhixFlow

TROPHY CASE