Marta Rutkowska Archives — Altkom Software

AI w underwritingu i likwidacji szkód — ile decyzji można oddać technologii

18/09/2026 |

12 min reading

AI in insurance generates plenty of interest, but the conversation often hits a wall as soon as decision automation comes up. Even though the technology can do much more, modernization efforts still tend to start with proven use cases such as document review, data extraction, and automated summaries. Insurers are far more cautious when it comes to using AI for more advanced tasks, including risk analysis, anomaly detection, building case context, and preparing recommendations. But perhaps we are spending too much time asking how many decisions we can hand over to AI, and not enough time asking how to design a process that uses the technology without giving up control, accountability, or auditability.

Magdalena Marczak

Obsługa polisy między kanałami cyfrowymi a infolinią

16/09/2026 |

8 min reading

Apps and self-service channels were expected to take over a significant share of policy servicing after purchase, yet the phone remains one of the most widely used ways to contact an insurer. That is not necessarily a problem, as some customers deliberately choose to speak with a person when dealing with more complex issues. The situation is different when calling becomes the only way to complete a process that could not be finished online. In this article, we look at where transitions between channels begin to generate costs that remain hidden when each channel is analyzed separately.

Magdalena Marczak

How to modernize loan origination without replacing the core banking system.

31/08/2026 |

10 min reading

You've just received another proposal for a low-code platform that promises to accelerate product launches and take pressure off IT. It sounds appealing, especially when the backlog keeps growing and Sales has been waiting three weeks for a new promotion. But in origination, configuration speed is only part of the equation. Maintaining control over case state, handling exceptions, and ensuring consistency across systems are just as important. So if you want greater control over the process as a whole, it may be better to put the technology decision aside for a moment and start with a different question: which parts of the process should remain a stable foundation, and which can safely be moved into fast business configuration?

Judyta Bartnicka

Automated credit decisioning without losing control — process diagram

26/08/2026 |

13 min reading

Working as an IT manager on projects for financial institutions, I have often heard some version of this statement: “We want to automate decisions, but we need to know what the system based them on.” In recent years, that tension has become even more pronounced. On the one hand, there is growing pressure to process applications faster and increase the share of automated decisions. On the other, institutions still need to be able to trace and reconstruct how each decision was made. And since, in financial services, “faster” cannot mean “we don’t know why,” how can institutions implement automated credit decisioning without creating a black box?

Kamil Kopeć

Audyt UX aplikacji bankowej — punktowe poprawki, audyt UX czy redesign aplikacji mobilnej banku

04/08/2026 |

10 min reading

Customers are increasingly abandoning processes in the banking app, and the number of contacts with the call center and customer service is rising. You are expected to present a plan for improvement, yet it is still unclear whether changing a few screens will be enough, a full UX audit is needed, or the problem really justifies a redesign budget. Before you involve more teams, you can start with a quick diagnosis of a selected journey. It is a simple way to organize your first observations, point to the most likely sources of the problem, and decide what the next step should be.

Marta Rutkowska

Ilustracja 3D: centralny niebieski sześcian z definicją produktu ubezpieczeniowego połączony liniami z sześcianami systemów sprzedaży, polis, szkód, danych, dokumentów i ryzyka — jedna definicja produktu dystrybuowana do wielu systemów.

22/07/2026 |

9 min reading

The sales director promises the executive team a new auto insurance offering by the beginning of the quarter. A week later, IT hears about the idea for the first time and immediately knows the change will not happen quickly: it affects five systems, two operations teams, and documentation that no one has updated in years. What looked like a straightforward product change from the business perspective starts stretching into several months. In this article, we explain what really determines the pace of product changes and how to design an architecture that makes them easier to implement.

Magdalena Marczak

Altkom Software's article about common UX problems in banking apps

18/06/2026 |

10 min reading

Even a mature banking app can become less effective at key moments in the process, when new features, regulatory requirements, business goals, and security start competing with the user’s need to complete a task simply and efficiently. Our UX audits for the financial sector show that some problems recur regardless of a bank’s operating model, organizational scale, or product team maturity. In this article, we discuss six problems that most often weaken users’ trust in a banking app.

Kornelia Marczewska

Altkom Software's article about reasons behind longer time-to-market in insurance

17/04/2026 |

8 min reading

Why do some insurers bring a new product to market in a matter of weeks, while others still take months? Market examples show that a change in system architecture alone can reduce time to market from over 28 weeks to around 10 weeks¹. A modular system can also shift offer management from IT to the business, reducing time to market by up to 80%². In this article, we explain why even a minor product change can trigger an IT project, and what needs to be structured to shorten the path from a business decision to implementation.

Magdalena Marczak

Article about the role of UX in internal systems

01/04/2026 |

10 min reading

Many organizations still operate on the assumption that if employees have to use a system anyway, usability is not a priority. As a result, UX is often treated as a nice-to-have - important in online banking, mobile apps, or sales journeys, but not in the tools used by advisors, analysts, underwriters, or back-office teams. In internal systems, however, interface quality has a direct impact on case handling speed, error rates, and the level of control over the process. Poor UX is therefore not an aesthetic issue, but a source of operational losses that most often become visible in teams’ day-to-day work.

Anna Rennert

Customer Experience

UX Audit for Banking Apps

Data, Cloud & AI Services

Data Maturity Model

AI & Data for Banks

AI & Data for Insurance

Software Engineering

Performance Engineering

Security

Altkom Loan Origination

Altkom Digital Banking Platform

Altkom Digital Leasing Platform

Altkom Insurance Suite

Insurance platform for LMG Försäkrings AB S.A.

Services for Banking

Altkom Loan Origination

Altkom Digital Banking Platform

AI & Data for Banks

Mobile Apps for Banking

UX Audit for Banking Apps

Services for Insurance

AI & Data for Insurance

Underwriting Automation

Altkom Insurance Suite

Insurance platform for LMG Försäkrings AB S.A.

Services for Leasing

Altkom Digital Leasing Platform

Data Maturity Model

Marta Rutkowska

Content Specialist

Written by: Marta Rutkowska

Join the newsletter