The Lifecycle Marketing Report 2026
AdalFi logo

How AdalFi turned customer intelligence into funded loans

Revamp took on the work of prioritizing eligible customers, tailoring communication, and following through to a funded outcome. AdalFi increased funded-loan conversion by 24% relative to its holdout group while reducing weekly campaign, segmentation, and reporting work by 76%.

AdalFiDigital Lending & FintechCustomer activation, reactivation, and product adoption
24%
lift

Funded-loan conversion relative to holdout

76%
reduction

Weekly campaign, segmentation, and reporting work

9.5×
return

Incremental contribution generated per dollar of Revamp fees

The opportunity was clear but execution took too much work

AdalFi already knew which customers qualified for its lending products. It had eligibility information, approved limits, and a history of customer behavior.

Turning that information into action required another set of decisions. Who should be contacted now? Which product was relevant? Should the next message introduce an offer, help someone complete an application, or reconnect with a customer who had gone quiet?

The team could work through those decisions manually for a campaign. Doing so continuously across customers and products required repeated audience building, message preparation, follow-up, and reporting. As circumstances changed, the work started again.

Revamp took responsibility for that ongoing execution, from deciding the next customer action to measuring whether it led to a funded loan.

Start with one workflow and a clear measure of success

The initial scope focused on eligible customers who had not progressed to a funded loan. AdalFi and Revamp agreed on the starting population, the products it could receive, the actions Revamp would manage, and the conditions that required a human handoff.

The engagement was measured on funded-loan conversion and incremental economic value. Applications and responses helped explain progress through the journey. The operating scorecard also tracked the team's workload and communication efficiency.

That starting scope gave both teams a concrete workflow to launch, inspect, and improve before expanding coverage.

From kickoff to live operation

First live workflow

After one month of setup

Customer setup meetings

Approximately three 30-minute meetings

Ongoing involvement

Revamp handles daily execution; Slack Connect coordination and roughly monthly check-ins

1
Setup monthDefine the first workflow

Agreed on the customer population, product eligibility, success measures, communication rules, and handoff conditions. Reviewed the existing process and its bottlenecks.

Deliverable

A scoped workflow, baseline scorecard, data requirements, and clear responsibilities.

2
Setup monthConnect and configure

Arranged CRM and other necessary access. Connected customer and outcome data to the existing delivery infrastructure, then configured customer states, decision rules, and message approaches.

Deliverable

A working journey that AdalFi could inspect, with representative examples and a launch checklist.

3
End of setup monthReview and launch

Reviewed examples with AdalFi, resolved exceptions, and launched the agreed customer cohort with the holdout in place. Live customer engagement began after the month of setup.

Deliverable

A live workflow and visibility into customer progression, exceptions, and delivery.

4
After launchOperate and improve

Revamp managed follow-through, reassessed customer state, reviewed outcomes, and adjusted the approach. Most coordination and tuning took place through Slack Connect.

Deliverable

Ongoing workflow operation, asynchronous coordination, and roughly monthly check-ins on progress.

How Revamp moved customer context into action

Customer context
Eligibility, limits, behavior, journey state
Next action
Prioritize the best objective
Communication
Tailor timing, channel, and message
Follow-through
Adapt as behavior changes
Funded outcome
Measure progression and funding

Revamp combined each customer's approved product eligibility, limits, prior engagement, and current journey state. That context informed both the objective and the approach.

For an eligible customer who had not engaged, the next step could be introducing a relevant product. For someone with an unfinished application, it could be helping them take the next step. For a returning customer, it could be assessing a different eligible product.

The workflow updated as real behavior changed. An application started, a customer responded, eligibility changed, or a loan was funded. Revamp used those events to decide whether to continue, change the approach, stop a message, or involve AdalFi's team.

AdalFi retained responsibility for credit decisions and product rules. Revamp managed the customer engagement within those boundaries.

Test the approach before sending the message

Revamp used digital twins, models grounded in customer context, to compare possible communication approaches before using them in a live journey. The simulations helped select the objective, framing, and next question to test with the customer.

Example workflow

— illustrative
Before sending
Known context
  • Returning borrower
  • Eligible for two products (personal loan, salary advance)
  • Revisited repayment details
  • Unfinished application
Three approaches tested
Larger loan limit
Salary advance
Explain repayment schedule
Why this approach

Repayment uncertainty is the model's hypothesis for why the application stalled. That is a hypothesis to test in the live journey.

Live execution
Action taken

Approved explanation of the repayment schedule with a clear next step.

What happens next

Actual responses and application events determine whether Revamp continues, adjusts the approach, or routes a question to AdalFi.

Success measured

Actual application progression and funding. Simulated responses inform the approach; real customer behavior determines the outcome.

This example illustrates the decision process. In operation, new customer behavior and funded outcomes informed subsequent decisions.

What each team owned

AdalFi

  • Provided the relevant customer, eligibility, and outcome data.
  • Set product rules, permitted communications, and escalation requirements.
  • Reviewed the initial journey and representative examples.
  • Handled credit decisions and issues requiring its specialists.
  • Joined roughly monthly progress check-ins and provided input through Slack Connect as needed.

Revamp

  • Connected the agreed data and configured the workflow.
  • Prioritized customer actions and tailored timing and communication.
  • Operated follow-through and adapted the journey as customer state changed.
  • Surfaced exceptions with the relevant customer context.
  • Managed day-to-day execution, reported outcomes, and handled most tuning through Slack Connect.

AdalFi's team supplied business judgment and specialist input when needed. Revamp absorbed the recurring work of assembling audiences, managing journeys, and reviewing what should happen next. Monthly check-ins maintained visibility and the working relationship; routine operation did not depend on regular meetings or day-to-day management by AdalFi.

Results measured through funded outcomes

AdalFi reserved 15% of otherwise eligible customers as an untreated holdout. Funded-loan conversion and disbursed value were evaluated against that comparison. Operating workload was evaluated separately against the previous process.

Measurement period

Approximately three months during the pilot

Initial cohort

Approximately 10,000 eligible leads

Funded-loan conversion
24% relative lift versus holdout
A greater share of eligible customers reached funding.
Disbursed value per eligible customer
31% increase
More lending value was generated per eligible customer.
Weekly campaign, segmentation, and reporting work
76% reduction
The team spent less time operating the workflow.
Messages per funded loan
28% reduction
Fewer messages were required for each funded outcome.
Return on Revamp fees
9.5×
Incremental contribution generated relative to Revamp fees over the measurement period.

Funded-loan conversion is reported as a relative change, not a percentage-point increase. Return on fees uses incremental contribution economics; loan principal is not treated as revenue.

Expand coverage as the operating model proves out

The engagement expanded across activation, dormant-customer reactivation, and adoption of additional eligible products. AdalFi managed more than eight concurrent products or lifecycle objectives without adding corresponding lifecycle headcount.

Once the operating system was in place, the time from approval of a new product or objective to customer activation fell from six weeks to four days.

The same customer context could now support additional workflows. New products and changing customer circumstances became inputs to the existing operation, with outcomes informing what to do next.

Your Turn

Bring us one customer workflow your team cannot consistently work through. We'll map the opportunity, the work Revamp would own, and the business outcome to measure.

Discuss your workflow

Client

AdalFi logo

Results

24%

Funded-loan conversion relative to holdout

76%

Weekly campaign, segmentation, and reporting work reduction

9.5×

Incremental contribution generated per dollar of Revamp fees

Share this case study

Could this apply to your business?

Bring us one customer workflow your team cannot consistently work through.

Discuss your workflow