Competitor Analysis & Build Direction
Europe, the USA, the Gulf and Asia. Every leading player, pulled apart area by area. This is what they built, where they fall short, and the gap Tribe should own.
No product anywhere puts all of it in one place: a real bank account that holds many currencies, fintech-level card controls, expense run by AI, an Arabic-first design, and a Shariah version.
Gulf banks bank well but handle expenses badly. Global fintechs handle expenses and AI well, but they are not real banks. Asia has the boldest ideas but barely gives out a company card. So the middle is empty — and that empty middle is exactly where Tribe belongs. And the one thing that can tie all of it together, and make every single part smarter, is AI.
Banks sit bottom-right. Spend platforms sit top-left. Neobanks land in the middle. The top-right corner, strong at both, has nobody in it.
Four things just came together. Gulf ID systems (DUL, Nafath, Emirates ID) now let a business open an account in minutes, legally and for real. Instant-payment rails (AANI, SARIE) became normal. The new UAE company tax made an auto tax-savings pot genuinely useful, not a gimmick. And Brex and Ramp proved that letting AI run expenses actually works. All the parts now exist. Nobody in the region has put them together — and nobody has made AI run through the whole product.
Each type of player is stuck by what it is. Spend platforms can't hold your money, so they can't be a real bank without a licence they don't have. Banks have the licence but move slowly, and still sign customers up through relationship managers. Global fintechs won't build Arabic-first design and a Shariah version for a region that isn't their focus. The gap isn't a mistake anyone made. It's built into who they are — which is exactly why it stays open for Tribe.
Don't pick one lane. Put a real bank, top-tier expense controls and AI in one product, make AI run through every part of it, wrap it for the Gulf in Arabic with a Shariah version — and take the corner no one else can reach.
In plain words: instead of being only a bank or only an expense app, Tribe is both, with AI everywhere, made for the Gulf. That exact mix is the empty space no rival can copy quickly.
We looked at each region for a different reason. Europe sets the bar for banking UX and FX. The USA leads on AI-driven spend automation. The Gulf is the market we are building for, and it plays by its own rules. Asia shows what is even possible.
Take Europe's banking and FX craft, the USA's AI automation and Asia's boldest ideas, then build all of it for the Gulf, where we actually ship.
In plain words: copy the single best idea from each part of the world and combine them in one product built for the Gulf. Good because we're not guessing — every piece already works somewhere.
Spend platforms beat the banks on cards and receipts for one reason: they are issuer-backed programs, not licensed banks. They never had to carry the weight of holding deposits, so they poured everything into the spend experience. That is also why they can't be a real bank. Tribe has to do both.
None of the three is complete. A bank's rails and a spend platform's UX, under one licence, is a category nobody occupies today.
In plain words: banks, neobanks and expense apps each do only part of the job. Join a bank's money-moving power with an expense app's ease-of-use in one licensed product and you own a space that's empty right now.
Nine product areas, twelve leading competitors. Each cell is strong, partial or absent. Read down a column to see who is complete. Read across a row to see where the whole market is thin.
What the grid shows: banks are thin on FX and deep expense. Fintechs are thin on roles and permissions. AI is missing at the banks and only real at Brex, Ramp and Alaan. No single column is strong on every row.
Tribe's goal is one column with no soft cells, strong on all nine rows. It has never existed. The empty cells here are the product spec.
In plain words: on the grid, every rival has weak spots. Tribe aims to be strong in all nine areas at once. The gaps in the chart literally tell us what to build.
Nine parts of the product. For each one: who does it best today, what they actually do, and the smarter, AI-powered move Tribe makes to beat them.
ENBD auto-fills from the DUL registry (~35% faster); Al Rajhi uses a Nafath 2-digit code + face-scan liveness; Tide approves >50% in ~10 min; Expensify runs the most complete documented US flow.
Pull the company details straight from the government registry (DUL / CR), confirm the owner with national ID (Emirates ID / Nafath) and a quick face check — minutes, not days. AI reads any extra document, checks the numbers match, and flags anything odd before a person even looks. The Shariah version is offered right at sign-up.
ENBD's CXO Dashboard consolidates real-time cash across entities; Mercury headlines burn rate + runway with an AI recap; Qonto pairs a cashflow chart with inflow/outflow donuts and split invoices.
A home screen led by your balance, with burn rate and runway, all your companies in one view, and live badges for approvals and missing receipts. AI writes a plain-language summary of what changed this week, warns you before cash runs low, and answers questions like “how much did we spend on travel?” in one line.
Revolut auto-routes incoming funds through a single multi-currency IBAN; Relay runs Profit-First buckets across 20 accounts; Brex layers checking / treasury / vault with 512 sub-accounts.
Real multi-currency accounts with local details for receiving money, sub-account “pockets”, and a Tax Reserve pot that auto-sets-aside VAT and company tax. AI predicts your tax bill from live spending and tells you exactly how much to keep aside.
Payhawk and Ramp hold the deepest control set, online/ATM/country/time/MCC + merchant allow-block, auto-block on overdue; Alaan's 7-step wizard is the clearest; Starling / Jago pioneer card-to-pocket.
The full set of controls, plus card-to-pocket hard budgets (the limit is the pocket balance), safe PIN/PAN reveal, and per-use toggles. AI suggests the right limit for each person from their history and quietly blocks a swipe that looks like fraud.
ENBD runs the full suite with a payment tracker; Wise / Revolut handle bulk (1,000/file); Alaan SuperPay reaches 40+ countries with cost shown upfront; Airbase automates AP end-to-end.
Local rails + SWIFT + a name-check on the receiver, bulk payments, WPS/GOSI payroll, bill-pay and multi-step approvals. AI reads a supplier invoice, fills in the payment for you, and warns if an amount or account looks wrong before you send.
Wise is definitive, mid-market rate + explicit fee + guaranteed-rate countdown + auto-cancel on drift; STC shows a pre-confirm breakdown; Mercury auto-fails on >1% drift; ZA shows savings vs a reference bank. The countdown is absent across the US, Gulf and Asia.
Ship the Wise pattern the Gulf has never had: the live rate + fee shown, a lock-in countdown, auto-cancel if the rate moves, and a “you saved this much vs a bank” line. AI watches rates and pings you to convert at the best moment. See §07.
Payhawk leads on breadth (60+ language OCR, VAT extraction); Alaan adds VAT+TRN, auto-reports and anomaly checks; Brex auto-fills, Ramp is zero-touch, Spendesk blocks on missing receipts, Qashio takes receipts over WhatsApp.
An AI-first engine: it fills in every field, pulls VAT+TRN off the receipt, checks for duplicates, rule-breaks and odd amounts, writes the report itself, and lets people send a receipt by WhatsApp or a photo of paper.
ENBD has the most granular model, 7 maker/checker/authoriser groups with per-currency amount bands; Spendesk has 8 virtual roles, Brex 11 + custom, Mercury crosses permissions with account access. None are time-bound.
Fixed role presets plus fine-grained, time-limited permissions — per feature, per person, with start and end dates that switch themselves off. AI suggests the right access for a new joiner and warns when someone has more power than their job needs. See §08.
Brex auto-adjudicates in-policy and blocks out-of-policy at authorization, and exposes an MCP endpoint; Ramp captures frictionlessly and surfaces savings; MYbank / Alipay hold the frontier, conversational credit and agentic payments.
AI decides at the swipe — approve what follows the rules, block what doesn't. Add an assistant that speaks Arabic and English, and build the data now so AI “agents” can safely pay and act for you later. See §09.
Every part already has a winning pattern somewhere in the world. Tribe's job isn't to invent — it's to put all nine under one roof, build them for the Gulf, and use AI to make each one better than the original.
In plain words: we don't need to invent anything risky. We copy what already works, bring it together, and let AI make each part sharper than the version we copied.
One FX pattern beats everything else, and no product in the US, Gulf or Asia has copied it. Wise locks a rate, counts it down, and cancels itself if the market moves against you.
STC still shows a pre-confirm cost breakdown; Mercury auto-fails above 1% drift. But only Wise guarantees the rate with a live countdown.
Ship the rate-lock countdown in phase one. It's a small build, it's the clearest "this feels world-class" moment in the whole app, and no Gulf competitor has it.
In plain words: the FX rate-lock is quick to build but makes a huge impression, and nobody in the Gulf offers it. It's the easiest way to instantly look better than everyone.
Everyone competes on how many roles they offer. Tribe competes somewhere else: fixed presets plus fine-grained permissions you can switch on per feature, per user, with a start and end date that expires on its own.
Context: Marius is on holiday, 15–25 July. Anna temporarily gains payment-approval rights that expire on their own.
Others add more roles. Tribe adds a new dimension: grant any permission to any user for a set window, and it removes itself when the window ends. No admin cleanup, no access left lying around.
Build the permission engine first, because it touches every screen. Time-bound, attribute-level access is both the core requirement and a real gap in the market.
In plain words: controlling exactly who can do what, and for how long, affects every part of the app, so build it first. It's essential and almost no rival does it well.
Every AI feature in this market sits on one ladder, from simple scanning at the bottom to AI that acts on its own at the top. Tribe should own rungs one to four now, and set things up so rungs five and six are a quick switch-on later, not a rebuild.
Match Brex and Ramp at rung four now. Then build the data so the top rungs — an assistant that acts for you, and AI agents that pay on your behalf — become a simple launch decision, not a rebuild. This is where Tribe pulls ahead of everyone.
In plain words: reach the top US AI level now, and set up the data so the most advanced AI is a quick switch-on later. That readiness is how Tribe gets ahead and stays ahead.
Each one is proven somewhere in the world, and each has an obvious use for Tribe. The chart below sorts them by impact against build effort.
Ratings are directional, the point is the ordering. The amber zone is the "do first" set: high impact, low-to-mid effort. The top-right two are the high-value frontier for later.
Start with the amber cluster: FX countdown, Tax vault, card-to-pocket, WhatsApp receipts, AI expense, government onboarding. They are cheap to build and they instantly make the product feel world-class.
In plain words: these six features are cheap to build but make the biggest impression. Do them first for the fastest “wow” at the lowest cost.
The UAE and Saudi Arabia aren't just "another region" you translate into. They run their own ID systems, payment networks, tax rules and religious requirements. Eight things are non-negotiable — and doing each one with AI is how Tribe comes out on top of the players already here.
These eight just get you in the door. The way Tribe comes out on top is AI: anyone can build the rails, but only Tribe makes them smart — reading documents, preparing tax, catching fraud and answering in Arabic. Ship all eight in phase one, and let AI turn table-stakes into a real lead.
These three are the closest competitors on the ground. They are excellent at spend. None of them is a real bank, and that shared gap is Tribe's way in.
Scores are 0 to 5 and directional. They show relative position, not exact measurement.
All three are shaped the same way, deep on spend, shallow on banking.
Match Alaan on AI expense, then beat all three on the things none of them has: real banking, rate-lock FX and time-bound permissions.
In plain words: first equal the best local rival on AI expense so we're not behind, then win with three things none of them have — a real bank account, locked FX rates, and time-limited access.
Tribe is the super-owner. Below it sit the program managers and banks, each with a fully branded instance. Below them are the merchant companies and their employees. Every feature is a switch you flip per client.
Program managers get full white-label, logo, palette, app icon and domain. Merchants below them adjust theme only. Tribe's identity never leaks downstream.
Every feature is switchable per client. A bank can ship FX and cards but hide the expense module; a fintech can do the reverse.
Build the hierarchy and the per-client toggles as core infrastructure, not an afterthought. This is what lets one codebase serve a bank and a fintech from the same deploy.
In plain words: build the ability to switch features on and off per client from the start. Good because the same single product can then be sold to very different customers with no extra rebuilds.
Two web shells and three mobile tab-bars, split by role. One rule governs all of it: a screen shows only if the role allows it and the client has that feature on. Hidden, never greyed out.
Full control in the pocket.
Pay → Send / Exchange / Request / QR. More → Accounts / Team / Reports / Settings / AI.
Spend, scan, request, nothing else.
Scan is the primary action, point-of-sale receipt capture.
Approvals first, everything else second.
Swipe-to-approve, inline from a queue or from WhatsApp / Slack.
Design each role's app as its own tab-bar, not one app full of disabled buttons. An employee should never see a screen they can't use. The interface bends to role and toggles.
In plain words: each type of user gets an app that shows only what they need, not one cluttered app with greyed-out buttons. Good because it feels simple and clean for everyone.
The full list lives in the companion spreadsheet. This is the shape of it: how the work spreads across buckets and how it splits by priority. Bar segments are directional.
The 79 Must features are the phase-one contract. Cards, Expense and Dashboards carry the most weight, so staff them first.
In plain words: phase one is a firm promise of 79 must-have features. Cards, expense and dashboards matter most, so put your best people on those first.
Five strengths come together in one product — and AI runs through all of them. On its own, each move is already proven somewhere. Together, under one licence, built for the Gulf, and made smarter by AI from end to end, they have never shipped.
Banking + card controls + AI expense + Arabic RTL + Shariah. No one has all five.
In plain words: one app does the job of five separate tools at once. Good because customers stop juggling products — and no rival can match all five.
Countdown + auto-cancel-on-drift + savings-vs-bank. Absent outside Europe.
In plain words: you see the real rate, lock it, and it cancels itself if it moves. Good because you never overpay on currency — and no one outside Europe offers it.
Per feature, per user, with start/end dates. Deeper than ENBD, Spendesk, Brex.
In plain words: give someone access to just one thing, for just a set time, and it switches off by itself. Good because access stays tidy and safe with no clean-up later.
Approve in-policy, block out-of-policy at authorization; WhatsApp / Slack approvals.
In plain words: AI approves or blocks each payment the instant it happens. Good because rule-breaking spend is stopped up front, not found weeks later.
Auto-fill, VAT+TRN, duplicate/policy/anomaly checks, auto-written reports.
In plain words: AI does the whole expense report — reading, tax, checks, and writing. Good because it wipes out hours of manual admin and errors.
Auto-skim VAT + corporate tax into a ring-fenced pot with a filing countdown.
In plain words: tax money is set aside automatically into its own pot. Good because the cash to pay tax is always there, ready.
The limit is the pocket balance, enforced at authorization.
In plain words: a card can only spend what's in its pocket; empty pocket, card stops. Good because overspending becomes impossible.
Registry auto-fill + national-ID biometric + guided liveness.
In plain words: pull company and ID details from official sources to open in minutes. Good because sign-up is both fast and trustworthy.
NL search, analytics and support in EN / AR / mixed, with human handoff.
In plain words: an assistant that fully understands Arabic and English and hands off to a person when needed. Good because Gulf users get help in their own language — something rivals do poorly.
Agent-authorisation console (scope / caps / audit). Scaffold now, ship later.
In plain words: the plumbing is ready for trusted AI to pay on your behalf, within strict limits. Good because Tribe can switch on the future safely, with no rebuild.
The empty corner, filled on purpose, by Tribe — and run by AI from the first screen to the last.
Phase one earns the right to compete: every Must feature, Gulf-native from day one, on top of the permission engine — with AI already helping inside each one. Phase two ships the AI differentiators. Phase three reaches the AI frontier.
All 79 Must features, with Arabic RTL and Gulf rails from day one, built on the permission engine.
The AI-powered features that make Tribe clearly better than the Gulf trio.
Ahead of the field, because the data model was built for it.
Every feature sits behind a per-client toggle from day one, so a phase-two capability can ship to one bank and stay off for another without a code branch.
Approve the phase-one scope: the 79 Must features, Gulf-native from day one.
Commit to building the permission engine and toggle system first. Everything else sits on top of them.
Fund a short validation sprint against the live competitor apps before the field-level specs are frozen.
Order matters. Build the permission engine and Gulf rails first, the AI-powered differentiators second, and the AI frontier third — with the toggle system running under all of it, and AI woven into every phase.
In plain words: do it in the right order — foundations first, the AI features that make us better second, the most advanced AI last. Good because each stage stands on a solid base and nothing has to be rebuilt.
Anti-pattern: Novo, single full-owner role only.
Field inventories are mostly rebuilt from feature descriptions and help docs, not verified against screenshots, since many source pages were blocked. Roles and permissions has the thinnest evidence. Native corporate spend cards barely exist in Asian SME banking; they are served by partners or virtual credentials, which is the biggest white space. FX is weak to absent outside ZA and Mox. The core Western expense workflow (OCR, transaction matching, missing-receipt chase, accounting export) wasn't confirmed in any Asian product. Radar and scatter scores here are directional, meant to show relative position rather than exact measurement. Check every field against the live apps before building.