Zero incidents in two years. Ten thousand statements processed. A small team. Fixed operating costs. The honest, unglamorous case for what an enterprise low-code platform actually buys you over time.
We talk a lot on this site about the moments where modern AI stacks earn their place — fast iteration, new product shapes, capability you couldn't build any other way. We talk less often about the other half of our practice, the platform work that just keeps doing its job, quarter after quarter, while the business gets on with growing. PayWise is one of those. Two years in, it's the strongest argument we have for OutSystems as a platform when the workload fits.
The recap, in a paragraph
PayWise is the supplier-payments platform we built for IGLU, the UK's largest cruise and ski agent. It ingests supplier statements, normalises them, matches lines to internal records, flags exceptions, and gives the finance team a live view of cash exposure. Built on OutSystems, run inside their estate, owned by their people.
What two years looks like, in numbers
- Zero production incidents in two years of continuous use across the finance function.
- 10,000+ statements processed end-to-end. Roughly double the year-one volume, no change to the architecture.
- Auto-match rates at industry standard, and rising. The matching logic has been refined every quarter against the patterns the team sees in production.
- Fully managed by a small team on the IGLU side. No DevOps headcount added to support it.
- Operating costs fixed. Platform licence, infrastructure and support sit on a known monthly line, not a consumption curve.
“The unglamorous version of success — nothing on fire, costs you can put on a slide, and a finance team that doesn't need to think about the tool they spend most of their day in.”
What we've actually been doing
Two years of zero incidents doesn't mean two years of nothing happening. The product has moved forward continuously, in a steady rhythm that suits how the business actually changes.
- Database evolution. Schema changes to support new supplier shapes and new payment categories, applied alongside the OutSystems data-model tooling so migrations stayed surgical, not big-bang.
- Matching rule refinement. Every quarter we look at the exceptions the team is resolving by hand, work out which patterns we can encode, and ship the rule. The curve has moved up steadily without ever needing a rewrite.
- Reporting updates. Finance reporting evolves as the business does. New supplier groupings, new exception categories, new period comparisons. Each one a small, contained change, each one delivered in days rather than weeks.
- Integration extensions. Additional supplier file shapes and a couple of new downstream feeds into the finance stack as IGLU's tooling moved.
- UX polish. Small ergonomic improvements based on what the team uses every day. Search behaviour, export options, audit-trail filters.
What this actually says about the platform
It's easy in 2026 to write OutSystems off as last year's idea, with so much of the industry's attention on AI-native stacks. The honest read, from inside a production system that nobody's touched as a hero project for two years, is more nuanced than that.
- Mature platforms compound. The runtime, the data layer, the deployment pipeline, the audit story — none of it has needed reinvention. Time that would have gone into plumbing has gone into making the matching better.
- The governance story holds up. SSO, RBAC, full audit, environment parity. Two years of audit reviews, no scramble.
- Costs are predictable. No consumption tail, no surprise bill in a busy month. Finance prefers this for obvious reasons.
- The platform stays current without forcing the team to. OutSystems' own platform updates land in our environments on a managed cadence. PayWise has moved through several without ever stopping.
The small-team angle
One of the most underrated things about a build like PayWise is what it doesn't need. IGLU runs it with a small team. No dedicated SRE rota for the platform itself. No specialist data engineer holding the schema together. The finance team owns the product roadmap and the platform team handles the runtime, and it works because the runtime doesn't demand attention.
For finance leaders evaluating where to put capability — in-house team, managed service, build-it-and-leave-it platform — that's the variable most pricing comparisons miss. The cost of operating a platform over a five-year horizon eclipses the cost of building it. Operating costs that sit on a flat line are easier to plan around than ones that scale with usage.
The honest verdict
Two years on, PayWise is the kind of product that doesn't get written up as a case study often, because the story is “it kept working, and quietly got better.” That story is harder to dramatise than a re-platform, but it's the one most finance teams actually want. A platform that absorbs growing volume without re-architecting, a maintenance rhythm a small team can sustain, a cost profile that's knowable up-front.
If you have a high-volume, rule-heavy, audit-sensitive workflow that's currently in spreadsheets — or in a brittle bespoke build that's been quietly costing you — the PayWise shape is one to look at seriously. Talk to us and we'll be honest about whether it's the right fit.
