Skip to main content

Posts

AI and the Economics of Customer Retention

Why understanding customer risk is ultimately a financial problem Customer retention is often discussed as a matter of satisfaction. Keep customers happy. Respond quickly. Improve support. Reduce friction. All of those things matter. But from a business perspective, retention is also an economic system. Every customer relationship has value. Every intervention has a cost. Every failure to act has a potential consequence. And every decision about whether to contact, compensate, prioritise, escalate or ignore a situation involves trade-offs. This means that Customer Experience should not be separated from financial reasoning. A modern Customer Intelligence platform should help answer questions such as: Which customers are at risk? How much revenue is exposed? What is the expected value of intervening? Which interventions have historically worked? How much should the organisation spend to protect a relationship? Which problems are causing the greatest financial damage? Which customers rep...
Recent posts

What a Week! From House Renovations to Fever, Exhaustion and an Unexpected Reunion

What a week! There are weeks when everything follows a reasonably predictable routine. You wake up, deal with whatever needs your attention, make some progress with your projects, complain about a few inconveniences, and eventually go to bed with the comforting impression that life is more or less under control. And then there are weeks like this one. What started as an entirely ordinary Monday turned into a rather unpleasant combination of house renovations, airport collections, family visits, persistent rain, an unexpected illness, several days in bed, and an interesting conversation that connected me with another piece of my father's past. It was certainly not the week I had planned. In fact, the entire experience derailed practically everything I intended to accomplish, including writing this very blog post. I had other subjects waiting, several ongoing projects demanding attention, and a renovated house still requiring an apparently endless collection o...

TV Serie - Slow Horses (2022) - Season 6

Log Episode 1 [Wed, Sep 16, 2026] - 2026-Sep-19 Episode 2 [Wed, Sep 23, 2026] - 2026-Sep-23 Episode 3 [Wed, Sep 30, 2026] - 2026-Oct-03 Episode 4 [Wed, Oct 7, 2026] - 2026-Oct-07 Episode 5 [Wed, Oct 14, 2026] - 2026-Oct-14 Episode 6 [Wed, Oct 21, 2026] - 2026-Oct-23

TOMS - How Should a Desktop Application Make Money? Thinking Through Licensing, Add-Ons, Cloud Services and Localisation

As I move further into the development of my event-planning desktop application, I am reaching a part of the project that has nothing to do with C++ classes, Qt widgets or file formats. I need to decide how the product could eventually make money. That question sounds simple. Build software, choose a price and sell it. In reality, the business model influences quite a few technical decisions: licensing, update delivery, account management, documentation, cloud infrastructure, downloadable content, localisation and possibly even how much server-side functionality I want to introduce. There is also a principle I want to preserve from the beginning. This is intended to remain a real desktop application. I do not want to turn it into SaaS simply because recurring revenue is attractive. The user should be able to install the application, create an event, work on it locally and retain control of the resulting files. That does not prevent online service...

Home Lab Front-End Data Store: Choosing a Small, Purpose-Driven Toolset

Based on a LinkedIn post originally published on 1 April 2026 The toolset used on my home-lab platform is intentionally small and purpose-driven. Tools are selected to help me understand, diagnose and operate the system. They are not introduced simply because they are popular, provide an attractive interface or promise to automate another part of the environment. Each tool must answer a specific operational question. The objective is not to own the largest toolbox. It is to ensure that every tool has a clear role and makes the platform easier to understand. Tools create operational architecture A tool is never completely external to the system it operates. Once introduced, it creates dependencies: someone must install and update it; its configuration must be protected; its access model must be understood; its output must be interpreted; and operators may gradually become dependent on the view it provides. A new tool may simplify one task while increasing the complexity of the overall p...