December 22, 2025
7 min read
by Dimitris Kostoulas
Sales & Business Development Manager, Comsys
In my role, I connect with a broad spectrum of organizations – banks, insurers and financial institutions. The logos change, the company sizes change, but the conversations are surprisingly similar.
Nobody asks me to “do digital transformation”. They ask very specific, very pragmatic questions:
“How do we stop running core processes on Excel and email?”
“How do we respond to the regulator without breaking our legacy systems or overloading our teams?”
“How do we roll out a new product before the competition does and internal systems are ready to support it??”
“How do we make all of this secure and compliant when our data and processes are so fragmented?”
In those conversations, Jaggle is not a buzzword. It is a way to remove very real blockers from very real projects.
Jaggle is our enterprise-grade, AI-powered Low-code application generation platform, designed for business-critical applications in complex, regulated environments. Its role is simple: help organizations move from long backlogs and fragile workarounds to secure, maintainable applications delivered faster, with consistent governance and security controls, and more cost-effectively
Below are the pain points I hear most often in insurance, banking and finance – and how we address them with Jaggle in actual discussions and pilots.
People, not systems, run the claims journey
A typical picture in many insurers:
- First notice of loss comes via portal, email or call.
- Someone retypes data into the core policy system.
- Evidence lives in shared folders and personal drives
Handling times are measured in days, not minutes. One operations director summed it up: “We do not really have a claims system. We have a claims process that lives in people’s heads.”
Old systems slow down new products
Product teams want micro-insurance, embedded offers or new health packages. The core platform can support them “with a major release next year”. Until then, everything is custom development and slow change requests.
Agents and brokers work half inside, half outside the system
Partners use a mix of portals, email and static reports. Visibility on pipeline, documentation and commissions is limited. Any improvement usually means “one more portal” for information technology to maintain.
How Jaggle helps
Jaggle’s role is to put a real, secure application around these functions, without replacing the core policy system.
Guided claims workbenches around the core, with clear screens, tasks, rules, full audit trails and role-based access so sensitive claims data stays protected.
Product “shells” on Jaggle allow teams to design, test, and refine new products while the core catches up.
Agent and broker portals showing live production, document status and commissions, integrated with core systems but not exposing them directly, and secured with controlled, least-privilege access for each partner.
Low-code vendors talk a lot about customer onboarding and Know Your Customer (KYC). Those topics are real – but what leaders ask us goes deeper.
“Can we change KYC without rewriting everything?”
Financial institutions are under constant regulatory pressure. Anti-money laundering rules, documentation requirements and risk models keep shifting. The reality on the ground:
Multiple KYC tools and checklists.
Spreadsheets and email between front office, middle office and compliance.
Manual consolidation of evidence every time an audit arrives.
Credit and lending workflows are fragmented
Corporate loans, leasing, trade finance and even consumer credit often run on:
- Core banking for accounts and contracts.
- Another system for risk.
- Several small applications for approvals, collaterals and guarantees.
- Control of “who did what, when” depends heavily on people and email.
- Audits take more time than the business activity
Teams spend days assembling the history of a single case. Regulators want decisions, data and approvals in one place. What they get is a patchwork of screenshots and exported files.
How Jaggle helps
Jaggle acts as a configurable, secure layer on top of existing platforms, not a replacement
- Centralised onboarding and KYC orchestration in one generated application, with different flows per segment and channel, integrated with screening tools and public registries.
- Unified lending workbenches for end-to-end case management: applications, attachments, approvals, conditions and collaterals, with structured data captured once and reused across systems.
- Audit-ready evidence “by design” because every step, rule and data field is known to the platform, with auto-generated documentation and built-in audit logs instead of manual reconstruction.
The outcome we aim for is simple: fewer spreadsheets and emails in the core process, faster change cycles when regulation moves, and transparent journeys that hold up under regulatory scrutiny.
The Common Pattern: Same Constraints, Different Language
Across insurance, banking and finance, the themes repeat:
- Legacy is not going away. Core systems are staying. The realistic path is to wrap, extend and gradually modernise them with generated applications that speak the language of the business.
- Spreadsheets and email run business-critical processes. They are flexible and risky at the same time. Jaggle helps lift those processes into governed applications with access control, audit and consistent data.
- Change cycles are too slow for how markets move. Regulators, competitors and customers do not wait for annual releases. By combining low-code with AI-assisted modelling, code generation and documentation, Jaggle accelerates the entire application lifecycle, not just the user interface.
- Security and compliance expectations keep increasing. Regulators, auditors and internal risk teams expect clear controls over who accesses what, when and why, something that informal, spreadsheet-based and email-driven tools cannot provide.
Closing Thought from the Field
When I walk into a first meeting, I am not trying to “sell low-code”. I am trying to understand which business-critical process is currently held together by people improvising around systems that are too rigid or too slow.
Once that is clear, Jaggle gives us a focused way forward:
- Model the real-world process.
- Generate an application that reflects it, with governance, security, audit and integration built in.
- Iterate quickly, based on how teams actually work.
If this sounds close to what is happening in our organisation’s claims, onboarding or lending journeys, the most productive next step is usually a single, well-defined pilot: one process, one team, one measurable outcome.
That is where we see Jaggle move from a “platform description” on a slide to a fundamental tool on people’s screens – and where the conversation shifts from technology to what the business can finally execute.
About the Author
Dimitris Kostoulas is a highly experienced professional with more than 22 years of experience in the IT sales industry. As Sales and Business Development Manager at Comsys, he focuses on building strong relationships, managing high-performance teams, and driving measurable business growth.
Throughout his career, he has led multiple commercial teams to significant revenue expansion, combining strategic planning with a deep commitment to exceptional customer experience. His expertise spans people management, B2B partnerships, and strategic business development, always with a focus on creating long-term value for organizations and their clients.
by Dimitris Kostoulas
Sales & Business Development Manager, Comsys
In my role, I connect with a broad spectrum of organizations – banks, insurers and financial institutions. The logos change, the company sizes change, but the conversations are surprisingly similar.
Nobody asks me to “do digital transformation”. They ask very specific, very pragmatic questions:
“How do we stop running core processes on Excel and email?”
“How do we respond to the regulator without breaking our legacy systems or overloading our teams?”
“How do we roll out a new product before the competition does and internal systems are ready to support it??”
“How do we make all of this secure and compliant when our data and processes are so fragmented?”
In those conversations, Jaggle is not a buzzword. It is a way to remove very real blockers from very real projects.
Jaggle is our enterprise-grade, AI-powered Low-code application generation platform, designed for business-critical applications in complex, regulated environments. Its role is simple: help organizations move from long backlogs and fragile workarounds to secure, maintainable applications delivered faster, with consistent governance and security controls, and more cost-effectively
Below are the pain points I hear most often in insurance, banking and finance – and how we address them with Jaggle in actual discussions and pilots.
People, not systems, run the claims journey
A typical picture in many insurers:
– First notice of loss comes via portal, email or call.
– Someone retypes data into the core policy system.
– Evidence lives in shared folders and personal drives
Handling times are measured in days, not minutes. One operations director summed it up: “We do not really have a claims system. We have a claims process that lives in people’s heads.”
Old systems slow down new products
Product teams want micro-insurance, embedded offers or new health packages. The core platform can support them “with a major release next year”. Until then, everything is custom development and slow change requests.
Agents and brokers work half inside, half outside the system
Partners use a mix of portals, email and static reports. Visibility on pipeline, documentation and commissions is limited. Any improvement usually means “one more portal” for information technology to maintain.
How Jaggle helps
Jaggle’s role is to put a real, secure application around these functions, without replacing the core policy system.
Guided claims workbenches around the core, with clear screens, tasks, rules, full audit trails and role-based access so sensitive claims data stays protected.
Product “shells” on Jaggle allow teams to design, test, and refine new products while the core catches up.
Agent and broker portals showing live production, document status and commissions, integrated with core systems but not exposing them directly, and secured with controlled, least-privilege access for each partner.
Low-code vendors talk a lot about customer onboarding and Know Your Customer (KYC). Those topics are real – but what leaders ask us goes deeper.
“Can we change KYC without rewriting everything?”
Financial institutions are under constant regulatory pressure. Anti-money laundering rules, documentation requirements and risk models keep shifting. The reality on the ground:
Multiple KYC tools and checklists.
Spreadsheets and email between front office, middle office and compliance.
Manual consolidation of evidence every time an audit arrives.
Credit and lending workflows are fragmented
Corporate loans, leasing, trade finance and even consumer credit often run on:
– Core banking for accounts and contracts.
– Another system for risk.
– Several small applications for approvals, collaterals and guarantees.
– Control of “who did what, when” depends heavily on people and email.
– Audits take more time than the business activity
Teams spend days assembling the history of a single case. Regulators want decisions, data and approvals in one place. What they get is a patchwork of screenshots and exported files.
How Jaggle helps
Jaggle acts as a configurable, secure layer on top of existing platforms, not a replacement
– Centralised onboarding and KYC orchestration in one generated application, with different flows per segment and channel, integrated with screening tools and public registries.
– Unified lending workbenches for end-to-end case management: applications, attachments, approvals, conditions and collaterals, with structured data captured once and reused across systems.
– Audit-ready evidence “by design” because every step, rule and data field is known to the platform, with auto-generated documentation and built-in audit logs instead of manual reconstruction.
The outcome we aim for is simple: fewer spreadsheets and emails in the core process, faster change cycles when regulation moves, and transparent journeys that hold up under regulatory scrutiny.
The Common Pattern: Same Constraints, Different Language
Across insurance, banking and finance, the themes repeat:
– Legacy is not going away. Core systems are staying. The realistic path is to wrap, extend and gradually modernise them with generated applications that speak the language of the business.
– Spreadsheets and email run business-critical processes. They are flexible and risky at the same time. Jaggle helps lift those processes into governed applications with access control, audit and consistent data.
– Change cycles are too slow for how markets move. Regulators, competitors and customers do not wait for annual releases. By combining low-code with AI-assisted modelling, code generation and documentation, Jaggle accelerates the entire application lifecycle, not just the user interface.
– Security and compliance expectations keep increasing. Regulators, auditors and internal risk teams expect clear controls over who accesses what, when and why, something that informal, spreadsheet-based and email-driven tools cannot provide.
Closing Thought from the Field
When I walk into a first meeting, I am not trying to “sell low-code”. I am trying to understand which business-critical process is currently held together by people improvising around systems that are too rigid or too slow.
Once that is clear, Jaggle gives us a focused way forward:
– Model the real-world process.
– Generate an application that reflects it, with governance, security, audit and integration built in.
– Iterate quickly, based on how teams actually work.
If this sounds close to what is happening in our organisation’s claims, onboarding or lending journeys, the most productive next step is usually a single, well-defined pilot: one process, one team, one measurable outcome.
That is where we see Jaggle move from a “platform description” on a slide to a fundamental tool on people’s screens – and where the conversation shifts from technology to what the business can finally execute.
About the Author
Dimitris Kostoulas is a highly experienced professional with more than 22 years of experience in the IT sales industry. As Sales and Business Development Manager at Comsys, he focuses on building strong relationships, managing high-performance teams, and driving measurable business growth.
Throughout his career, he has led multiple commercial teams to significant revenue expansion, combining strategic planning with a deep commitment to exceptional customer experience. His expertise spans people management, B2B partnerships, and strategic business development, always with a focus on creating long-term value for organizations and their clients.
