Blog/Product Strategy
Product Strategy

WUKAD’s AI Financing Advisor at Money20/20 Riyadh: One Application, Many Offers

i
iFynx StudioSep 20, 2026 · 7 min read
wukad ai financing advisor money2020 riyadh

Advice before the offer — and a single door to banks

At Money20/20 Middle East in Riyadh (14–16 September 2026), WUKAD launched an AI-powered financing advisor that lets customers assess financial and credit standing, ask questions, and receive financing options tailored to their data — plus a broader “buyout financing” product. Managing Director Ahmed Tarboush told Sharikat Mubasher the platform’s point is to end the grind of approaching multiple providers and re-running credit checks: one app application, then available offers from banks and financing companies appear automatically. Founded in 2025 and headquartered in Riyadh, WUKAD is a licensed digital brokerage regulated by the Saudi Central Bank (SAMA).

Product craft for regulated marketplaces

1. Explainability is table stakes. An advisor that “recommends” without showing why an offer fits (or fails) credit standing will lose trust in a SAMA-regulated context. Surface drivers in plain Arabic and English.

2. Marketplace UX ≠ lender UX. WUKAD sits between consumers and many lenders. Design comparison cards, fee clarity, and cooling-off states that protect the customer when agents suggest options.

3. Buyout financing changes journey maps. Debt consolidation flows need stronger confirmation and education modules — iFynx would prototype these as motion-guided checklists, not a single chat bubble.

iFynx takeaway

Money20/20’s Riyadh stage keeps rewarding products that compress multi-bank friction into one governed experience. Build advisors that teach credit standing, then route to offers — not black-box matchers that surprise customers at signature time.


Marketplace advisor UX: one application, many regulated offers

WUKAD’s Money20/20 pitch — assess standing, ask questions, receive tailored options — only works if the customer understands who is advising, who is lending, and what data moved between them. Ambiguity here is a conduct risk.

  • Show advisor role vs lender role on every offer card; never let branding imply WUKAD is the bank unless it is
  • Disclose which fields were shared with each bank before the customer taps “continue with this offer”
  • Hard-gate soft-pull vs hard-pull credit checks with bilingual consent and a plain-language impact note
  • Offer comparison table: APR/profit rate, fees, tenure, early settlement, required documents — sortable, not chat-only
  • Expire stale offers visibly; showing yesterday’s rate after bank repricing destroys trust

A chat that “feels smart” but cannot produce a comparable offer grid will lose to a boring bank PDF. Win on clarity.


Edge cases for Saudi SME and consumer financing advisors

Riyadh launch energy fades when the first awkward cases hit support. Script them now.

  1. Customer has multiple CR numbers / trade names — advisor must ask which entity is borrowing
  2. Partial bureau data: explain gaps without blaming the customer in shaming tone
  3. Offer A requires salary certificate, Offer B accepts bank statement — document checklist must switch per offer
  4. Customer starts in Arabic, switches to English mid-funnel — preserve answers; never reset the application
  5. Bank returns a conditional approve; UI must show conditions as actionable tasks, not a wall of PDF text

If support cannot see the exact offer payload the customer saw, disputes become he-said-she-said.


Ops playbook for bank partners on the other side of the door

The “single door” only scales if bank partners get clean, versioned application packages and clear SLAs.

  • Partner portal: application status webhooks with reason codes banks already use internally
  • Reject reasons mapped to customer-safe Arabic/English copy — no raw core-banking codes on screen
  • Weekly quality report: incomplete docs %, avg time-to-decision, top three drop-off fields
  • Kill-switch per bank if error rates spike; do not keep routing traffic into a broken connector
  • Joint incident channel owned by WUKAD ops + bank relationship manager — not only engineering Slack

Advice-before-offer is a product promise. Keep the downstream bank plumbing as polished as the advisor chat.

Treat this as an operating practice, not a one-off redesign workshop. Schedule a monthly review of the metrics and checklists above, assign a single accountable owner, and keep a short changelog of product fixes shipped since the last review. When stakeholders ask for more visual polish, redirect the conversation to the open defects that still block conversion, trust, or operator adoption. Depth compounds when the same checklist is reused across markets with only locale-specific payment, language, and compliance adjustments.

How a financing marketplace journey should work, step by step

A “one application, many offers” product sounds simple, but every step carries trust and compliance weight. A well-designed journey for a regulated financing broker usually looks like this:

  1. Purpose first. Ask what the money is for (personal need, car, home, consolidation) before asking for data. It frames which products are even relevant.
  2. Consent with clarity. Explain which data will be pulled, from where, for how long, and who will see it. In Saudi Arabia, the Personal Data Protection Law has been enforceable since 14 September 2024 (after a one-year grace period from 14 September 2023), so consent and purpose limitation are legal requirements, not nice-to-haves.
  3. Verified identity. Use national digital identity flows instead of manual uploads wherever the provider supports them, and design for the app-switch back into your product.
  4. Affordability before offers. Show the customer a plain summary of what they can likely afford, based on income and existing obligations, before showing any offer.
  5. Comparable offers. Present offers in a consistent format: amount, tenor, total cost, monthly instalment, fees and Sharia structure where relevant. Never rank offers by commission without saying so.
  6. Decision and hand-off. Make the hand-off to the chosen lender explicit: what is shared, what the customer signs, and where support comes from after that point.

What “AI advisor” should and should not mean

An AI advisor in a lending context is most valuable when it explains, not when it decides. Good uses include translating financial terms into plain Arabic or English, answering “why was I shown this offer?”, summarising the difference between two offers, and flagging information the customer has not yet provided. Risky uses include generating eligibility promises, inventing rates, or nudging customers toward a higher amount than they asked for. Grounding the assistant in the actual offer data and product terms, and refusing to answer outside that data, keeps it honest.

Saudi Arabia’s AI Ethics Principles, published by SDAIA, list transparency and explainability, fairness, privacy and security, and accountability among their seven principles. Those map directly onto product requirements: show reasons, test for unfair outcomes across customer groups, minimise data, and keep a human accountable for credit decisions.

Buyout and consolidation flows need extra care

Debt buyout products move a customer from one lender to another. The UX should make three things impossible to miss: the outstanding balance being settled, the new total cost compared with the old one, and any early settlement fees. A side-by-side “before and after” view, with a confirmation step that restates the numbers, prevents the most common complaints.

Metrics that tell you the experience is working

  • Application completion rate by step, so you can see where customers drop.
  • Share of customers who open the “why this offer” explanation.
  • Time from application to first offer.
  • Complaint and cancellation rates within the cooling-off period.
  • Repeat visits without new applications (a sign of confusion, not engagement).

Arabic-first content for financing products

Financing terms are hard enough in one language. In a Saudi marketplace, the Arabic version should be written first, not translated last. Use consistent terms for each product type across every screen, offer card and contract summary. Keep numbers in a consistent format, show the currency (SAR) next to every amount, and make sure that profit rates, annual percentage rates and total cost are labelled so that a customer can compare like with like. Test the copy with real customers: a sentence that reads clearly to a product manager can still confuse someone applying for financing for the first time.

Operational readiness

A marketplace that promises fast offers needs operations to match. Define service levels with each partner lender for response times, build a status page inside the app that shows where each application stands, and give support staff a view of the same timeline the customer sees. When a lender declines, tell the customer clearly and, where possible, explain what they could change, such as the amount or the tenor, without implying a guaranteed outcome.

Frequently asked questions

Is a financing marketplace the same as a lender?

No. A broker or marketplace connects customers with licensed lenders; the lender makes the credit decision and holds the loan. The product must make this distinction clear to customers.

Can an AI advisor approve financing?

It should not present itself that way. Credit decisions sit with the licensed lender under its credit policy; the advisor can explain options and requirements.

Which data should we ask for first?

The minimum needed to match products: purpose, amount, income range and employment type. Ask for documents only when a specific offer requires them.

How do we keep offers comparable?

Normalise every offer into the same fields and show total cost, not only the monthly instalment.

Related: Nafath and UAE Pass onboarding UX · Saudi PDPL compliance checklist. Building a financing app for the Kingdom? See iFynx app development for Saudi Arabia and AI development for Saudi Arabia.