Industry Sector: Financial Services
Business Function: Operations
A payments processor wanted to increase revenue from small and medium merchants by optimizing collections, repricing less sensitive merchants, and retaining high-value customers at risk of churn. With a fragmented data landscape of tremendous scale, they could not run the analyses necessary to act on these ideas.
At the scale that this processor operates, there were two primary challenges:
Complete view of merchant activity — The company developed an unprecedented understanding of their customer base with a large volume of integrated data on customer activity, pricing, payment terminals, billing, fraud, and credit history.
Improved collections — Analysts develop statistical models to rate accounts by how likely they are to pay. High-likelihood accounts are routed to internal collections teams, while low-likelihood accounts are referred to third-party collectors.
New pricing strategies — Analysts perform high-scale analysis to assess the impact of different fee structures on customer retention. Sales teams use these insights to better price new accounts and reprice existing accounts to prevent churn.
A financial analyst uses Foundry to go through a re-pricing exercise for merchants to ensure retention but also maximize revenue.
This use case implements the following Pattern. Follow the link below to read more about a particular Pattern and learn how it is implemented within Foundry.
Want more information on this use case? Looking to implement something similar? Get started with Palantir. ↗