ClearScore · Marketplace
ClearScore Marketplace Transformation
Consumer credit marketplace · UK and Canada
ClearScore was rebuilding its marketplace platform to make product information and functionality more reusable across markets. For the credit-card journey, the challenge was to preserve a live customer experience while the platform underneath it changed. I independently designed the product-detail experience within a collaborative redesign, then became the sole designer supporting implementation across listings, question flows and details. My responsibility extended through the UK rollout and adaptation for Canada.
Role
Product Designer · Design lead during implementation
Scope
Initial design · UK delivery and Canada adaptation
Timeline
2025–2026 · Implementation from approximately Q2 2025
UK credit-card product-detail design from the programme’s milestone documentation. Historical offer content.
01 /
Challenge
Preserving a live customer journey
ClearScore’s marketplace helps people explore credit offers and continue to a lender’s application. Listings, questions and product details therefore needed to communicate a consistent offer as customers moved through the journey.
The programme aimed to preserve existing functionality while limiting revenue disruption. It was not an opportunity to implement every improvement at once.
As requirements evolved, a recurring challenge was deciding which differences between the designs and the build needed attention before the next rollout stage. Some affected presentation. Others could change how customers understood an offer or their ability to continue.
My work involved keeping the design reference current, documenting edge cases and helping stakeholders understand the customer consequence of each issue.
Previous and redesigned product-detail experiences, showing changes to information hierarchy and offer presentation.
02 /
Research
What research revealed
I conducted an unmoderated Web study with ten participants: seven on mobile Web and three on desktop Web.
Participants could find Cards and understand the product-detail tables. They considered fees, rewards and benefits alongside interest rates.
Comparing offers still required effort. Moving between listings and details meant remembering differences, while uneven product information made like-for-like comparison harder. The study also identified return-navigation friction.
These findings provided useful directional evidence. They did not establish a measured improvement in comprehension or task completion.
03 /
Decisions
Protecting clarity through implementation
Complete terms are part of offer clarity
During implementation review, I reported missing interest-free balance-transfer durations on affected listings and detail pages.
The duration was essential context. An interest-free benefit tells only part of the story if customers cannot see how long it lasts.
This was a concrete example of why review needed to go beyond visual consistency. An omitted term could affect how someone assessed the financial offer, even when the surrounding interface appeared complete.
MBNA and Lloyds listings showing interest-free balance-transfer benefits without their durations. Reported during internal beta on 18 August 2025.
Assess quality by customer consequence
Throughout implementation, I documented differences between Figma and staging, reviewed developer output and walked stakeholders through readiness risks.
The useful questions were practical:
Could customers understand the offer?
Could they read the information?
Could they continue through the journey?
At the UK halfway-rollout gate, the team accepted two app discrepancies until the following release because they did not compromise those criteria.
My contribution was to make the differences and their consequences explicit, giving stakeholders a clearer basis for deciding what needed attention immediately and what could follow.
Guaranteed credit-limit range wrapping across two lines during app implementation review.
Adapt shared patterns for local offers
I adapted the shared designs for Canada using the same documentation and review approach.
The work included local requirements around rewards valuation, fee scenarios and eligibility differences. These affected the information customers needed when assessing an offer.
Reusing the experience therefore required attention to both structure and content: which patterns could remain consistent, and where local information needed different treatment.
UK and Canadian designs showing a shared pattern adapted to local offer information.
04 /
Implementation
From a page to a connected experience
Product details were the part of the initial redesign I owned independently. Listings and question flows were designed collaboratively. Once I became the sole designer supporting implementation, I maintained the design reference across those surfaces as requirements changed. That included documenting edge cases, reviewing the build and coordinating stakeholders around readiness. The work required sustained attention to how the journey behaved as well as how individual screens looked.
05 /
Outcomes
Programme results
The marketplace migration delivered positive commercial results at programme level.
+7%
Revenue per login uplift
+8.5%
Apply-click conversion
+£400k
UK Cards revenue
These figures reflect the combined marketplace migration. My contribution covered independent product-detail design, implementation support across listings, questions and details, and adaptation for Canada.
Delivery across two markets
UK Cards reached full rollout by 26 March 2026, followed by Canada Cards by 2 April 2026.
Remaining opportunities
The ten-participant Web study identified continued friction when comparing offers and navigating between listings and details. These findings highlighted further opportunities to support customer decision-making; the study did not measure a before-and-after improvement in comprehension or task completion.
06 /
Reflections
What I would carry forward
The most useful review question was what a difference meant for the customer.
A missing offer term could change someone’s understanding of a financial benefit. Some presentation discrepancies could wait until a later release.
Explaining that consequence made readiness discussions more concrete. It helped connect detailed design review to the decisions customers were trying to make.
In a future migration, I would make those assessment criteria explicit earlier and record the rationale alongside each finding. That would make release decisions easier to discuss, revisit and apply consistently as the work moved across markets.