SAASPOCALYPSEverdict #COINPROFILE-C8D0
scanned 2026.07.22 · 16:59
subject of investigation

coinprofile.com

crypto payments & remittances
verdictCONTESTED
wedge score
42
/100
wedge thesis

the door is regulatory and capital: cross-border crypto-to-fiat remittance and virtual cards are gated by payouts, banking partners, and KYC, not product UX — that's the real moat.

real walls — pick your flank·ship in ·run for $26.00 + usage
the doordata
wedge

where the walls are.

methodology →
the door

no proprietary corpus — they're running on off-the-shelf data.

watch out

the regulatory wall is real — actual licenses, audit posture, custodial duty.

capital
8.0/10
investment the incumbent had to make
why this scorehigh confidenceSignificant non-software capital required for banking partnerships, custodial flows, payouts, and card issuance makes...

Significant non-software capital required for banking partnerships, custodial flows, payouts, and card issuance makes this expensive to replicate.

  • Wedge thesis: gated by payouts, banking partners, and KYC
  • Challenges: banking partnerships & regulated payouts listed as 'nightmare' requiring months and substantial capital
  • Card issuing/integration requires partnerships, certification, and minimum balances
technical
4.0/10
depth of the underlying engineering
why this scoremedium confidenceModerate engineering and integration complexity (KYC, card APIs, payouts) but not exotic technical research or...

Moderate engineering and integration complexity (KYC, card APIs, payouts) but not exotic technical research or realtime systems.

  • Challenges: integrating KYC providers described as medium difficulty with SDKs available
  • Lacks signals of advanced algorithms, realtime/collab, or bespoke infra
  • Proposed stack: Vercel, KYC provider, card issuance partner — standard integrations
network
2.0/10
users compound users
why this scorehigh confidenceNo evidence of marketplace, multi-sided liquidity, UGC, or viral social graph—distribution is product-adjacent but...

No evidence of marketplace, multi-sided liquidity, UGC, or viral social graph—distribution is product-adjacent but not a moat here.

  • Report focuses on regulatory/capital moat, not network effects
  • No detected signals of marketplaces, UGC, or partner ecosystems in report
  • Distribution signals (knowledge_graph_present etc.) are null
switching
6.0/10
stickiness of customer data + workflow
why this scoremedium confidenceCustomer switching friction exists due to payouts, custodial fiat flows, and approval chains with banks, but UX-level...

Customer switching friction exists due to payouts, custodial fiat flows, and approval chains with banks, but UX-level alternatives are possible for non-critical users.

  • Take_sub: users can't replicate payout rails or custodial fiat flows without licenses and partner banks
  • Challenges: migrating payout/custody relationships involves negotiations and certifications
  • Negated: UX alternatives exist and are easy to find
datadoor
2.0/10
proprietary data accumulates over time
why this scorehigh confidenceNo indication of proprietary behavioral or transaction datasets being leveraged as a defensible training/fraud asset...

No indication of proprietary behavioral or transaction datasets being leveraged as a defensible training/fraud asset in the report.

  • Report emphasizes regulatory/capital moat, not proprietary data advantages
  • No mention of accumulated non-exportable datasets or fraud/risk models
  • Stack signals show standard providers, implying limited proprietary data capture
regulatory
9.0/10
real licenses, not SOC 2 theater
why this scorehigh confidenceRegulatory burden (KYC/AML, banking relationships, payouts, card issuing) is core to the product and is explicitly...

Regulatory burden (KYC/AML, banking relationships, payouts, card issuing) is core to the product and is explicitly cited as the main moat requiring licenses and ongoing audits.

  • Wedge thesis: 'door is regulatory and capital' and 'can't replicate payout rails or custodial fiat flows without licenses and partner banks'
  • Challenges list AML/regulatory compliance across jurisdictions as 'nightmare' with ongoing legal costs and audits
  • Card issuing and banking partnerships require certifications and regulatory approvals
take

the blunt take.

This looks like a payments/remittance wrapper built on crypto rails serving Africa — valuable, but not something a solo indie can replace because the hard bits are banking relationships and compliance, not front-end features.

Users can find UX alternatives quickly, but they can't replicate payout rails or custodial fiat flows without licenses and partner banks; competing on price or UX alone will lose to incumbents who hold the rails.

cost

cost of competing.

what they charge
undisclosed — likely fees on FX / card / remittance
varies
/ per txn
homepage shows no clear subscription; revenue likely per-transaction spreads
annual:scales with volume
what running yours costs
01 · Banking & payouts relationships / custody setup??? — setup and monthly minimums
02 · Compliance & KYC tooling (third-party) — ID verification, AML)$25.00
03 · Vercel (hobby tier)$0.00
04 · Domain$1.00
05 · Card issuing/processing passthrough fees (partner dependent)??? — per txn
TOTAL / mo$26.00 + usage
▸ break-even:approximately never
build

what you're up against.

partnerships months · compliance months/years · engineering ongoing
easy
medium
hard
nightmare
01
easy
Marketing copy & landing UX
Polish messaging and flows for conversion — small team work.
02
medium
Integrating KYC providers
Work with Sumsub/Jumio — SDKs exist but edge cases and false positives consume ops time.
03
hard
Card issuing / virtual card integration
Requires partnerships (card networks, issuers) and certification; not just API wiring.
04
nightmare
Banking partnerships & regulated payouts
Negotiations, minimum balances, local licensing — months and substantial capital.
05
nightmare
AML / regulatory compliance across jurisdictions
Ongoing legal costs, audits, and risk of freezing funds — this is the moat.
stack

their position.

detected signals· measured
hostingVercel
recommended stack · inferred
inferVercel (hobby tier)inferKYC provider (Sumsub/Jumio) — paidinferCard issuance partner (e.g., Railsbank/Stripe Issuing) — partner APIinferCloudflare R2 or S3 (light usage)
rivals

who else has tried this.

option A
Self-host & partner via Stripe Issuing + TransferWise
use established rails for card issuing and cross-border transfers where available; easier compliance and known contracts.
option B
P2P crypto remittances (lower-tech)
users can use Paxful or LocalCryptos plus local cash-out services to avoid building payout rails.
option C
Traditional remittance services (WorldRemit, TransferWise)
if reliability and fiat payout are the goal, these incumbents handle licensing and bank rails for you.
compare

similar scans.

same shape - different moat
ready to wedge in?
Get the wedge plan. Cancel some plans.
▸ generated with love, by a heartless robotverdict v2.5 · saaspocalypse.dev