FOMO·crypto·Scan 2026-06-23 to 2026-06-23·Run 20260624000050
White-label social crypto SDK so neobanks embed copy-trading and gasless first-purchase in weeks, not years.
Tier-2 and Tier-3 neobanks in LatAm, Southeast Asia, and MENA have millions of engaged users who demand crypto features but defect to standalone crypto apps. Building ERC-4337 embedded wallets, gas abstraction, and a social trading layer in-house requires 18 or more months and a dedicated blockchain engineering team that most neobanks cannot afford or retain.
By Bizidea Research/
Overall rating3.9/ 5.0
3
Market
$95.6M TAM growing 33% across priority markets; five incumbents identified, none combining bank-owned social discovery with local compliance packaging.
4
Differentiation
Bank-owned social graph and per-jurisdiction compliance modules create switching costs the competing CEX white-labels structurally cannot match.
4
Execution
30.6x LTV/CAC, 2.2-month payback, and 72% gross margin are top-decile; four model flags—including six-logo revenue concentration—moderate the execution score.
5
Timeliness
Fomo's $75M raise, SEC wallet clearance, and ERC-4337 production proof converge in one news cycle—a rare breakout window with five supporting signals.
Section
Why now
Fomo's $75M Series B proves B2C social trading works at scale — 625K traders, $4B volume, 68K first-time buyers — creating a validated playbook and competitive urgency for neobanks that want equivalent features without building from scratch.
The SEC cleared non-custodial wallet interfaces in June 2026, removing the last major legal deterrent that kept regulated fintech companies from embedding self-custody crypto in consumer apps and triggering compliance teams to greenlight previously stalled projects.
ERC-4337 account abstraction is now production-proven at Fomo's scale, collapsing the engineering risk that previously blocked neobanks from building on chain-level infrastructure — the SDK can be built entirely on battle-tested primitives.
Fomo's announced expansion into equities, perpetuals, and prediction markets signals that social trading infrastructure will become a horizontal asset-class-agnostic layer, giving a B2B SDK company a multi-year expansion roadmap that grows with neobank needs.
Catalyst.Fomo's $75M Series B at a $550M valuation and the SEC's simultaneous clearance of non-custodial wallet interfaces (June 2026) open a 12-month window before Coinbase and Binance can launch competing white-label programs.
Section
The idea
The SDK ships in four modules: (1) an embedded wallet layer built on ERC-4337 that handles key creation, recovery, and gas sponsorship behind the existing neobank login — no seed phrase, no bridge, no separate app; (2) a social trading graph that surfaces live positions, community leaderboards, and one-tap copy-trade over the neobank's existing friend graph; (3) a fiat on-ramp adapter supporting Apple Pay, local card networks, and bank transfer so users complete their first trade in one checkout flow; and (4) a compliance layer that auto-generates position disclosure notices and enforces jurisdiction-specific limits for non-custodial broker-dealer exemptions. Neobanks call a single REST API; the SDK handles chain routing, gas optimization, and social data indexing. The first paying customer can go live in six to eight weeks with a team of two engineers, with no blockchain expertise required.
What's different. Every competing white-label option (Coinbase Prime, Binance Connect) sells exchange access and has a structural incentive to route user loyalty to the CEX, not the neobank. This SDK is channel-agnostic infrastructure the neobank owns entirely. The social graph module is the defensible moat: it indexes cross-wallet position data within the neobank's permission boundary, creating a leaderboard that a bare CEX API cannot replicate and that compounds in value as more users join the neobank's network rather than a shared CEX pool. Compliance automation pre-configured per jurisdiction cuts the legal review cycle that stalls neobank product launches from six months to six weeks, turning regulatory complexity from a barrier into a switching cost for incumbent competitors.
Startup thesis
Beachhead
Neobanks in Brazil and Mexico with 1M–5M registered users that already offer stock CFDs, have visible user churn to crypto apps, and want to ship gasless spot crypto with copy-trade but have no in-house blockchain team.
Wedge
A drop-in SDK for embedded ERC-4337 wallet creation, gas sponsorship, and one-tap Apple Pay or local payment crypto purchase — live in a neobank app in under eight weeks with two engineers.
Non-obvious insight
The bottleneck to the next 100 million crypto users is not another exchange — it is the social proof moment that converts a skeptic into a buyer. Fomo's data shows roughly 11% of its user base made their very first crypto purchase because they saw a friend's live trade on a leaderboard. Neobanks already own that social graph — friend payment circles, P2P history, referral networks — but lack the crypto rails to activate it. Every major CEX white-label program has a structural disincentive to help neobanks win: they want the user on their platform, not the neobank's. A channel-agnostic SDK that packages ERC-4337 wallets, gas sponsorship, and a portable social graph is the infrastructure layer that CEXes will never offer but neobanks urgently need.
Venture-scale path
Wallet infrastructure across five anchor neobanks unlocks a cross-app social trading graph spanning millions of users; the company then monetizes protocol fee share, premium analytics, and a cross-app leaderboard network that becomes the Bloomberg Terminal for on-chain retail traders — eventually expanding into equities, perpetuals, and prediction market data as neobanks follow Fomo's announced multi-asset roadmap.
Target user
Primary user
CPO or Head of Product at a Tier-2 or Tier-3 neobank with 500K–5M DAUs in LatAm, SEA, or MENA
Secondary user
Fintech super-apps in emerging markets seeking crypto revenue without a blockchain engineering team
Economic buyer
CPO or VP Product at the neobank
Go-to-market seed
First customer
A Brazilian neobank with 1M–3M registered users, an existing stock CFD product, and internal data showing 8–15% of DAUs with external crypto apps installed — willing to run an eight-week paid pilot with a two-engineer integration team.
Buying trigger
The CPO reads Fomo's Series B press coverage, checks internal retention data, and discovers a measurable user cohort churning to Mercado Bitcoin or Bitso — the data point that creates internal urgency and unlocks an innovation budget allocation.
Current alternative
Building in-house over 18+ months with a dedicated blockchain team, or licensing a generic CEX API such as Coinbase Prime or Binance Connect that provides no social layer and routes user loyalty to the CEX rather than the neobank.
Switching reason
Eight-week time-to-live, a built-in social and copy-trade layer that CEX APIs structurally cannot offer, and a compliance module pre-configured for LatAm regulatory requirements — the combination a two-person neobank mobile team cannot replicate in under two years.
Pricing hypothesis
Monthly per-active-wallet platform fee (target $0.50–$1.50 per MAW) plus 10–15 basis points of protocol fee share on trading volume, with a minimum monthly commitment of $5,000 for the first three anchor customers.
Jobs to be done
Job
Current alternative
Success metric
When a neobank CPO sees users churning to Fomo-type apps, help them ship a gasless social crypto feature in eight weeks, so they can retain users and generate fee revenue without building blockchain infrastructure in-house.
In-house build over 18 months, or generic CEX API with no social layer and user loyalty owed to the CEX rather than the neobank.
Percentage of neobank DAUs completing a first crypto trade within 30 days of feature launch; target 5% or higher in the first cohort.
When a neobank user sees a friend's live winning trade on the leaderboard, help them copy the trade in one tap via Apple Pay, so they experience their first on-chain purchase with zero friction and no separate app download.
Downloading a standalone crypto app, completing KYC, funding a separate wallet, and placing a manual trade — a flow with 70–80% drop-off at each step.
First-purchase completion rate above 60% for users who tap the copy-trade button, with tap-to-confirmed-trade latency under four seconds.
Signal · 4/5Three independent same-day sources confirm Fomo's $75M raise, $4B volume, and 68K first-time buyers; Index Ventures, USV, and Benchmark participation signals strong institutional conviction in the social trading thesis.
Pain · 4/5Neobanks face measurable user churn to Fomo-type apps and an 18-month build timeline for equivalent infrastructure — a strategic revenue and retention threat that CPOs feel acutely and that a generic CEX API cannot resolve.
Wedge · 5/5The eight-week embedded wallet SDK is narrow, testable, and directly tied to a documented Fomo signal — the wedge is a specific REST API endpoint, not a broad platform vision, and the first customer profile is tight enough for direct outreach.
Defense · 3/5Social graph data and compliance automation create a moat over time, but early adoption depends on moving faster than Coinbase and Binance launching white-label programs — a credible threat within 18 months that requires anchor contracts and exclusivity provisions to blunt.
Scale · 4/5Hundreds of mid-tier neobanks globally represent a large addressable market; fee share on $4B-plus trading volume across ten neobank partners approaches $40M ARR, with upside from the cross-app social graph network effect and multi-asset expansion.
Fiat on-ramp providers supporting LatAm and SEA local payment methods
Blockchain data indexing providers for social graph feeds
Key activities
SDK development, maintenance, and L2 gas optimization
Regulatory tracking and compliance module updates per market
Enterprise sales and onboarding for anchor neobank customers
Key resources
ERC-4337 wallet and gas sponsorship infrastructure on Ethereum L2s and Solana
Social graph indexer for cross-wallet position data within partner permission boundaries
Compliance rule engine maintained per jurisdiction
Value propositions
Gasless embedded crypto trading live in eight weeks with no blockchain team required
Social copy-trade layer and leaderboards that CEX white-label APIs cannot replicate
Pre-built compliance module covering non-custodial broker-dealer exemptions for LatAm and SEA
Customer relationships
Dedicated integration engineer during eight-week onboarding sprint
Monthly product review and fee-share reporting dashboard
Developer Slack community shared across all partner neobanks
Channels
Direct enterprise sales to CPOs and VPs of Product at target neobanks
Fintech conference presence in São Paulo, Singapore, and Dubai
Developer-led growth via open SDK documentation and sandbox environment
Customer segments
Tier-2 and Tier-3 neobanks in LatAm, SEA, and MENA with 500K–5M registered users
Fintech super-apps seeking crypto revenue without blockchain engineering headcount
Cost structure
Gas sponsorship float for first-time wallet activations
Blockchain infrastructure and social graph indexer hosting
Enterprise sales and solutions engineering headcount
Per-jurisdiction regulatory counsel
Revenue streams
Monthly per-active-wallet platform fee ($0.50–$1.50 per MAW)
Protocol fee share on trading volume (10–15 basis points)
Professional services for custom compliance modules in new jurisdictions
Section
Market
Market sizing
Market sizing overview
TAM
$95.6MBottom-up proxy = 39.8M current crypto owners across Brazil, Mexico, Indonesia, Singapore, and the UAE; assume only 20% are realistically reachable through digital-bank distribution and $12 annual platform revenue per active wallet => 39.8M × 20% × $12 = $95.6M.
SAM
$52.4MBeachhead narrows to Brazil, Mexico, and Indonesia; their combined 36.4M current crypto owners discounted to a 12% bank-channel reachable share at the same $12 annual revenue per active wallet yields about $52.4M.
SOM
$7.2MYear-3 reachable share assumes six live partners averaging 100k active trading wallets each and roughly $12 annual platform revenue per active wallet => 6 × 100k × $12 = $7.2M.
Executive takeaways
The investable wedge is not generic “crypto in banking,” but a white-label social activation layer that helps digital banks turn existing user graphs into first-trade conversion loops.
Customer urgency is strongest where grassroots crypto adoption is already mainstream and mobile financial apps are normalizing embedded crypto or Web3 features.
The gap is real but narrow: incumbents cover wallets, on-ramps, custody, or social trading separately, but few package social discovery, local funding, and jurisdiction-specific compliance for bank channels.
Market sequencing will matter as much as product quality; Brazil and selected hub markets are easier to pursue first than every high-demand country at once.
Market definition
Software and infrastructure for digital banks and super-apps to embed gasless crypto trading, social discovery, and bank-owned distribution without building a crypto stack from scratch.
Customer and buyer
Primary users are product, growth, and payments teams at digital banks or super-apps; the economic buyer is usually the CPO, GM of consumer payments, or VP Product, with compliance and engineering leadership acting as co-approvers.
Buying triggers
High grassroots crypto adoption in Brazil, Mexico, Indonesia, Singapore, and the UAE means banks can treat embedded crypto as a mainstream retention and revenue feature rather than a science project.[13][19][20][21][22][23]
Neobanks and super-apps are already shipping crypto or Web3 features inside the core app, from Nubank and bunq to GCash, Maya, GoTyme, and Grab.[27][32][35][36][37][39]
Production-ready account abstraction, gas sponsorship, on-ramp, and wallet infrastructure now make a launch timeline measured in weeks more plausible than a bespoke in-house build.[5][41][47][110][113][116]
Regulatory frameworks are concrete enough to scope launches in Brazil, Singapore, and UAE-style hubs, even while Mexico remains more constrained.[99][102][106][107][109]
Willingness to pay
Budget exists when the product is framed as activation plus regulated infrastructure, not as a discretionary social feature. Buyers already evaluate usage-based or enterprise-priced wallet, on-ramp, and trading stacks, and digital banks are extending crypto deeper into the banking surface itself.[42][58][85][92][32][33]
Category dynamics
Growth signal 33% period-over-period growth in MENA crypto activity in Chainalysis 2025 geography data.
Tailwinds
Latin America has already processed very large crypto volumes and Brazil is the region’s clear leader, which supports bank distribution as a mainstream rather than fringe use case.
Digital banks and super-apps keep pushing crypto or Web3 features into the core app, normalizing the buyer conversation.
Embedded-wallet, paymaster, and gasless-UX tooling is mature enough that the startup can buy much of the plumbing instead of inventing it.
Headwinds
Regulatory fragmentation across Brazil, Mexico, Singapore, and the UAE forces slower sequencing and more legal work than a single-market launch.
Horizontal infrastructure vendors can commoditize every non-social layer of the stack, leaving differentiation to data and workflow rather than raw wallet plumbing.
Validation signals
Fomo’s funding and user-activity narrative shows that social discovery can drive first-time crypto buying behavior.
Large digital banks are already making crypto a native banking experience rather than a separate destination.
Southeast Asian mobile-finance apps are pushing crypto or Web3 wallets into mainstream consumer surfaces.
The density of embedded-wallet and trading-infrastructure vendors is itself a demand signal: buyers already exist for every non-social layer of the stack.
Regulatory & technical constraints
Brazil now has a clearer VASP rule set, but launch design still has to fit local authorization, governance, and AML expectations.
Mexico treats virtual-asset operations as a tightly scoped regulated activity for banks and fintech institutions, which makes partner selection especially important.
Singapore and UAE-style hub launches likely require licensed payment or virtual-asset pathways, even when the startup avoids direct custody.
Gas sponsorship and smart-wallet recovery shift security design toward passkeys, paymasters, and backend policy controls rather than seed-phrase UX alone.
Embedded social trading infrastructure map
Section
Competition
Competition comes from four directions: exchange or brokerage infrastructure, wallet and auth SDKs, institution-first crypto platforms, and consumer social trading networks that validate the UX pattern. The white space is the bank-owned social conversion layer that combines local payment rails, social discovery, and jurisdiction-specific compliance.
Competitor
Stage
Wedge
Pricing
Strength
Weakness vs. us
Coinbase Developer Platform
incumbent
Embedded wallets, on-ramp, paymaster, and smart-account tooling for developer teams.
Usage-based pricing and rewards on docs pages; enterprise contracting for larger programs.
Deep docs and adjacent on-ramp plus paymaster tooling reduce launch complexity.
Does not center on a bank-owned social graph, local bank workflow, or emerging-market compliance packaging.
Fireblocks / Dynamic
incumbent
Institution-grade wallet infrastructure plus embedded-wallet distribution after the Dynamic acquisition.
Quote-based enterprise stack, with Dynamic positioned as free-to-start and scale-up friendly.
Strong security posture, enterprise trust, and explicit neobank positioning.
Institution-first posture is powerful, but the stack is not purpose-built around social trading and bank-owned discovery loops.
Privy
scale-up
Developer-first embedded wallets, auth, gas sponsorship, and global wallet UX.
Free-to-start with enterprise expansion.
Excellent onboarding UX and flexible wallet abstraction for product teams.
Stops short of regulated trading orchestration, local payments, and bank-specific social features.
Zero Hash
scale-up
Regulated trading, on-ramp, account funding, and payout infrastructure for fintechs.
Product-specific fees and enterprise contracts.
Compliance-heavy trading rails and fiat-crypto conversion are directly relevant to banks.
No native social graph or consumer discovery loop; more rails than product experience.
Bitso Business
scale-up
LatAm-focused stablecoin, payments, FX, and developer APIs.
Custom enterprise pricing and partnership-led packaging.
Local rails and LatAm positioning are strong for Brazil/Mexico adjacency.
Payments and FX are the center of gravity, not social trading or multi-region bank distribution.
Why incumbents do not win by default
Exchange and brokerage infrastructure.These vendors solve wallets, liquidity, and on-ramp rails, but they do not win by default because they rarely offer a bank-owned social graph or a distribution layer designed around neobank retention.
Wallet and authentication SDKs.Dynamic, Privy, and Turnkey reduce wallet UX friction, but they typically stop short of regulated trading orchestration, local payments, and social-trading product logic.
Institution-first crypto platforms.Fireblocks is strong on security and regulated wallet infrastructure, but its center of gravity is enterprise crypto enablement rather than a bank-specific social growth loop.
Consumer social trading networks.Fomo and eToro prove that social discovery and copy-trading behavior can drive demand, but neither is the white-label bank infrastructure layer the startup wants to become.
Section
Business plan
Social-trade SDK should launch as a Brazil-first infrastructure layer for digital banks and super-apps that already see retail crypto demand but lack an in-house blockchain team. The first customer is a Brazilian neobank with 1M-3M registered users, an existing investing product, and evidence that users are funding standalone crypto apps instead of staying in-bank. The immediate pain is measurable retention and fee leakage, while the current alternatives are an 18+ month internal build or exchange APIs that provide rails but not a bank-owned social conversion loop. The MVP should therefore combine embedded smart-wallet creation, gas sponsorship, local funding rails, leaderboards and follows, and jurisdiction-specific disclosures in one paid pilot that can go live in roughly eight weeks. Product sequencing matters: Brazil comes first because research supports clearer regulatory footing and stronger digital-bank crypto normalization, while Mexico should wait until the compliance pattern is proven with licensed partners. The go-to-market system is one coherent motion: founder-led sales to the CPO or VP Product, a paid pilot tied to first-trade conversion and time-to-live, and production pricing based on active trading wallets plus fee share on volume. Reasons to believe are the demonstrated consumer pull of social trading, the maturity of account-abstraction tooling, and the gap between infrastructure vendors and bank-owned social workflows. Reasons to doubt are equally clear: bank-channel conversion may be lower than pure consumer apps, regulators may force a leaderboard-first product before auto-copy, and incumbent wallet or exchange platforms may add enough social functionality to compress the wedge. This business is worth investigating if the company can prove two things quickly: production deployment in under 10 weeks and a measurable uplift in first-trade conversion versus a non-social embedded-crypto flow.
Problem
Tier-2 and Tier-3 neobanks in crypto-active markets lose retention and fee revenue when users leave the bank app for standalone crypto products that offer faster onboarding and stronger social proof.
The replacement options are unattractive: an in-house build needs specialist blockchain and compliance talent, while generic exchange or wallet APIs do not give the bank a differentiated social conversion loop or local launch packaging.
Solution
Provide a white-label SDK that packages embedded smart-wallet creation, gas sponsorship, local funding rails, and bank-owned social discovery so a neobank can launch embedded spot crypto in about eight weeks with a small mobile team.
Start with leaderboards, follows, watchlists, one-tap first purchase, and jurisdiction-specific disclosures; add deeper copy-trade automation only after legal and conversion evidence is proven in production.
Why we win
The product is designed around the exact gap incumbents leave open: bank-owned user graph activation, not just trading rails, wallets, or custody.
Each deployment compounds proprietary assets in permissioned social-conversion data, fraud and gas telemetry, and jurisdiction-specific compliance workflows that are difficult for horizontal SDK vendors to replicate quickly.
Strategic choices
Beachhead
Brazilian neobanks with 1M-5M registered users, an existing investing surface, visible crypto-demand leakage, and no internal blockchain team.
Wedge rationale
This slice reaches proof faster than selling to every bank or every country because the buyer already has mobile distribution, a retention problem, and a plausible innovation budget, while Brazil offers stronger evidence of crypto normalization and a clearer launch path than Mexico or a multi-country rollout. Selling first into banks that already have an investing workflow also reduces the product-education burden versus greenfield consumer fintechs.
Sequencing
The company should launch with Brazil, spot crypto, and leaderboard or follow mechanics before broad copy-trade automation because compliance interpretation is the largest early gating factor. GTM stays founder-led until the team proves that an eight-week paid pilot can convert into an annual production contract, while hiring prioritizes wallet, compliance, and implementation depth before channel scale. Partnerships with local funding and wallet infrastructure vendors come before international expansion because settlement reliability and time-to-live are more urgent than a broad geographic footprint.
Not yet
Direct Mexico launch before the Brazil compliance and conversion pattern is proven · Equities, perpetuals, and prediction markets · Cross-bank shared social graph products outside a single partner's permission boundary · Full-stack custody or broker-dealer infrastructure
Go-to-market
Wedge
Sell a paid Brazil launch pilot that embeds gasless spot-crypto onboarding and bank-owned social proof into one existing banking app, then convert that pilot into an annual production contract based on active trading wallets and trading volume.
Channels
Founder-led direct sales to CPOs, VP Product leaders, and GM consumer-payments owners at Brazilian neobanks and super-apps · Co-sell with local funding, FX, and on-ramp partners that can shorten procurement by solving money movement early · Technical co-sell with wallet and account-abstraction vendors to reduce time-to-live risk in the first pilots
Funnel targets
Target account→qualified opportunity 20-30%, qualified opportunity→paid pilot 20-35%, paid pilot→production 50%+, production logo→wallet-count or market expansion 40%+ within 12 months.
Pricing
Start with a paid 8-10 week pilot, then annual pricing based on active funded trading wallets at roughly $0.50-$1.50 per wallet per month plus 10-15 bps of trading-volume fee share and a minimum platform commitment. This matches the buyer's budget logic because the product is justified as retention and new fee revenue, not as a standalone social feature.
Product roadmap
MVP
MVP covers one partner bank in Brazil: embedded smart-wallet creation, gas sponsorship, local funding integration, bank-branded leaderboards and follows, one-tap first purchase, disclosure and limit controls, and funnel analytics from impression to first trade. It should explicitly exclude multi-asset support, cross-bank network effects, and fully automated copy-trade until legal and conversion thresholds are met.
6 months
Ship two to three Brazil pilots with configurable disclosure rules, wallet recovery, event instrumentation, and at least two local funding-partner integrations on one core chain stack.
12 months
Convert at least two pilots to production, add controlled copy-trade workflows where counsel permits, harden fraud and risk controls, and package deployment playbooks for one second-wave market through licensed partners.
24 months
Expand from Brazil proof into selected hub and high-demand markets, add reusable compliance modules by jurisdiction, and broaden into adjacent asset classes only where the same social-conversion workflow still applies.
Key bets
Leaderboard and follow mechanics can lift first-trade conversion materially even before full auto-copy is enabled. · A small bank integration team can reach first value in under 10 weeks using packaged wallet and funding modules. · Compliance packaging by jurisdiction is valuable enough to protect pricing from horizontal wallet-SDK commoditization. · The first production customers will accept active-wallet plus volume-based pricing because the product is tied to revenue and retention, not discretionary social engagement.
Business model
Revenue streams
Annual platform subscription tied to active funded trading wallets · Protocol or trading fee share on partner-bank volume · Onboarding and jurisdiction-activation fees for new markets or compliance modules
Unit of value
Active funded trading wallet inside a partner bank, with expansion by additional markets, modules, and trading volume
Target gross margin
70%
Expansion levers
Add more active wallets and more funded users inside each production bank · Launch additional jurisdictions with reusable local funding and disclosure modules · Sell premium analytics on conversion, retention, and social-trading cohort performance · Extend the same bank-owned social infrastructure into adjacent asset classes once compliance and liquidity paths are proven
Strategy map
North-star metric
Monthly active funded trading wallets inside production partner banks
Input metrics
Days from signed pilot to first live user cohort · Leaderboard impression to wallet-creation conversion · Wallet-created to first-trade conversion · Paid pilot to production conversion rate · Ninety-day retention of first-trade cohorts · Average active funded wallets per production partner
Moats to build
Permissioned social-conversion dataset linking discovery events to funded wallets, first trades, and retention · Jurisdiction-specific disclosure, limit, and approval-rule library for bank launches · Gas-sponsorship, funding-partner, and fraud telemetry that improves conversion and loss controls over time
Kill criteria
Fewer than 2 of the first 4 paid pilots reach production within 6 months of kickoff. · Pilot cohorts fail to reach at least 3% first-trade conversion from eligible monthly active users within 90 days. · Median integration time exceeds 10 weeks across the first 3 bank deployments. · External counsel concludes the intended social workflow requires licensing or feature restrictions that break unit economics in Brazil.
Milestones
0–12 months
Ship the Brazil MVP with embedded wallet, funding rails, leaderboard or follow mechanics, and disclosure controls.
Sign 4-6 design partners and convert at least 2 into paid pilots.
Put the first 2 banks into production and prove sub-10-week deployment on at least one customer.
Demonstrate first-trade conversion at or above the internal kill-threshold in a production cohort.
12–24 months
Standardize copy-trade feature gating where counsel permits and package a repeatable second-market launch path through licensed partners.
Grow to 6 production partners and validate year-3 SOM assumptions on active funded wallets.
Establish partner-sourced pipeline as a meaningful contributor to new pilots.
Launch premium analytics and compliance modules that increase ACV inside early customers.
24–36 months
Expand into selected hub and high-demand markets without losing deployment speed or gross-margin discipline.
Broaden into adjacent asset classes only where the same bank-owned social-conversion workflow remains defensible.
Develop a durable data moat in conversion, retention, and compliance telemetry across the production customer base.
Strategy map
flowchart LR
Wedge[Brazil neobank pilot] --> MVP[Wallet plus funding plus leaderboard MVP]
MVP --> Proof[First-trade conversion and production contracts]
Proof --> Expansion[More banks, jurisdictions, and asset classes]
Founding team
Role
Start timing
Rationale
Founder/CEO
Month 0
Own founder-led sales, design-partner recruitment, and product packaging because the first budget decision depends on customer truth and rapid iteration.
Founding eng
Month 0
Build the core wallet, paymaster, and event instrumentation stack required to launch the first pilot quickly.
Wallet and backend engineer
Month 1
Harden smart-wallet recovery, chain routing, and funding-partner integrations so early pilots do not become bespoke engineering projects.
Solutions and compliance engineer
Month 3
Own partner onboarding, disclosure configuration, and implementation playbooks across design partners and launch jurisdictions.
Product and regulatory lead
Month 6
Turn legal findings and pilot learnings into reusable feature gates, approval workflows, and jurisdiction modules that protect repeatability.
Partnerships lead
Month 9
Scale co-sell motions with funding, wallet, and regional launch partners once the first production proof exists.
Experiment roadmap
Horizon
Experiment
Hypothesis
Success metric
Owner
0–90 days
Interview 15 Brazilian neobank and super-app product leaders that already operate an investing or payments-led consumer app.
At least one narrow buyer segment already treats embedded crypto as an urgent retention and revenue project rather than a speculative feature request.
At least 8 interviews confirm measurable crypto-demand leakage or competitive pressure, and at least 4 accounts fit the beachhead profile.
Founder/CEO
0–90 days
Produce a market-by-market legal memo comparing leaderboard-only, follow, watchlist, and auto-copy flows for Brazil and Mexico.
Brazil supports a commercially viable MVP with fewer gating issues than Mexico.
Counsel approves a Brazil MVP feature set and identifies no blocker that forces the company into full licensing before pilot launch.
Product and regulatory lead
0–90 days
Build a pilot-ready prototype that instruments the funnel from leaderboard impression to wallet creation to first funded trade.
A packaged social-first flow can reach a design-partner demo without custom infrastructure work beyond the core SDK.
One design partner can review the full user flow and data instrumentation within 30 days of technical kickoff.
Founding eng
90–180 days
Close the first paid Brazil pilot with explicit success criteria on go-live speed, first-trade conversion, and production decision timing.
Qualified beachhead buyers will pay for launch readiness before multi-country expansion or full auto-copy exists.
One paid pilot signed and launched with a path to production review inside 120 days.
Founder/CEO
90–180 days
Benchmark at least two local funding or FX partners on approval time, fee load, failure rate, and fraud controls.
A multi-partner money-movement stack can preserve checkout speed and unit economics better than relying on one global vendor.
One preferred partner stack supports the pilot with acceptable fees and under 5% funding failure rate in test traffic.
Solutions and compliance engineer
180–360 days
Convert two paid pilots to production and test a technical co-sell motion with one wallet or account-abstraction partner.
Production proof plus partner credibility will shorten later enterprise sales cycles and support second-market expansion.
Two production contracts signed and at least 3 qualified partner-sourced opportunities created.
Partnerships lead
Risk assessment
Business plan risks — 5 mapped
Impact →
High
R2
R3
R5
R1
Medium
R4
Low
Low
Medium
High
Likelihood →
R1Regulators or bank compliance teams treat social-trading mechanics as advice or solicitation sooner than expected. · Highlikelihood / Highimpact — Start with leaderboard, follow, watchlist, and disclosure-heavy flows; require external counsel sign-off before enabling deeper copy features in each market.
R2Horizontal wallet or exchange infrastructure vendors add enough social and launch-packaging functionality to compress the wedge. · Mediumlikelihood / Highimpact — Differentiate on bank-owned graph activation, local compliance modules, and measured conversion uplift rather than generic wallet plumbing.
R3Partner banks refuse to share enough permissioned graph or behavior data to make social prompts meaningfully better than a standard embedded-crypto checkout. · Mediumlikelihood / Highimpact — Design the product to work with progressively richer signals, prove value with minimal data first, and negotiate explicit consent and data scopes in pilot contracts.
R4Funding, FX, or settlement partners become the pacing item for launches and degrade checkout economics. · Mediumlikelihood / Mediumimpact — Qualify multiple partners per market, measure failure rates and approval times early, and avoid single-vendor dependency in the first two jurisdictions.
R5Bank-channel conversion is too weak to justify low-six-figure production contracts even if the product ships on time. · Mediumlikelihood / Highimpact — Instrument control cohorts, sell on conversion proof not feature count, and narrow the ICP to banks with the strongest demonstrated crypto-demand leakage.
Risk
Likelihood
Impact
Mitigation
Regulators or bank compliance teams treat social-trading mechanics as advice or solicitation sooner than expected.
High
High
Start with leaderboard, follow, watchlist, and disclosure-heavy flows; require external counsel sign-off before enabling deeper copy features in each market.
Horizontal wallet or exchange infrastructure vendors add enough social and launch-packaging functionality to compress the wedge.
Medium
High
Differentiate on bank-owned graph activation, local compliance modules, and measured conversion uplift rather than generic wallet plumbing.
Partner banks refuse to share enough permissioned graph or behavior data to make social prompts meaningfully better than a standard embedded-crypto checkout.
Medium
High
Design the product to work with progressively richer signals, prove value with minimal data first, and negotiate explicit consent and data scopes in pilot contracts.
Funding, FX, or settlement partners become the pacing item for launches and degrade checkout economics.
Medium
Medium
Qualify multiple partners per market, measure failure rates and approval times early, and avoid single-vendor dependency in the first two jurisdictions.
Bank-channel conversion is too weak to justify low-six-figure production contracts even if the product ships on time.
Medium
High
Instrument control cohorts, sell on conversion proof not feature count, and narrow the ICP to banks with the strongest demonstrated crypto-demand leakage.
First customer
Title
CPO at a Brazilian neobank with measurable crypto-app leakage
Profile
A Brazilian neobank with 1M-3M registered users, an existing stocks or wealth surface, no blockchain team, and internal evidence that active users fund standalone crypto apps outside the bank.
Trigger
A product or retention review shows user leakage to crypto apps after competitors normalize embedded crypto, creating pressure to ship a bank-owned alternative within the current planning cycle.
Buyer
CPO or VP Product
Initial contract
$30k-$60k paid pilot over 8-10 weeks, converting to roughly $120k-$250k annual platform spend plus usage-based fee share once 25k-50k active funded wallets are live.
What must be true
Brazilian neobanks with visible crypto-demand leakage will fund a paid pilot from a retention or product-growth budget now.
Leaderboard and follow mechanics must lift first-trade conversion materially versus a non-social embedded-crypto flow inside the same bank app.
Brazil launch can remain compliant with disclosures, limits, and feature gating before full auto-copy is enabled.
Early customers will accept annualized spend in the low-six-figure range before the company has a multi-country footprint.
Reusable compliance and funding modules can carry the product into second-wave markets before horizontal vendors commoditize the non-social stack.
Open diligence questions
What exact Brazil feature set can ship without pushing the product into advice or solicitation treatment?
How much permissioned social or payments-graph data will a design-partner bank actually expose for rankings, follows, and prompts?
What first-trade conversion uplift does a bank-branded social flow deliver versus an embedded-crypto flow without social proof?
Which local funding and FX partner combination yields the fastest time-to-money with acceptable fraud and fee economics?
Will anchor customers sign for annual production after one paid pilot, or will they insist on a longer services-heavy proof period?
Investor verdict
Call
Meet / investigate further
Conviction
Compelling wedge and real buyer timing, but conviction stays conditional on Brazil compliance clarity and bank-channel conversion data.
Why believe
The startup targets a specific retention and revenue workflow that existing exchanges, wallet SDKs, and institution-first crypto platforms do not package well for bank-owned distribution.
Why doubt
The market is strategically interesting but still unproven at bank-channel conversion levels, and incumbents can compress the wedge if social functionality and local launch packaging commoditize quickly.
Next diligence
Validate with Brazil design partners that a leaderboard-first pilot can go live in under 10 weeks, convert users to first trade at target rates, and still support a production contract above minimum platform pricing.
Section
Financial model
3-year totals
Year 1 revenue
$210KEBITDA $-983K · Cash EOP $1.82M
Year 2 revenue
$2.08MEBITDA $-756K · Cash EOP $1.06M
Year 3 revenue
$5.55MEBITDA $707K · Cash EOP $1.77M
Unit economics
ARPU (annual)
$1.07M
Gross margin
72%
CAC
$140KPayback 2.2 months
LTV / CAC
30.6xLTV $4.28M
Funding ask
Round
pre-seed · $2.8M
Runway
24 months
Milestone
Reach two Brazil production banks with sub-10-week deployment proof and enough capital to scale toward six live partners with a six-month buffer.
Model sanity
Revenue engine. Base-case Y3 revenue comes from six live neobank partners ramping toward roughly 95K active trading wallets each at about $12 annual revenue per wallet.
Must go right. The implementation playbook has to keep launches under 10 weeks because one delayed bank materially reduces revenue in a six-logo model.
Model breaks if. If production launches slip a quarter and realized pricing falls toward $10 per wallet per year, the downside case turns Y3 EBITDA negative and compresses the cash cushion.
Next-round proof. Two Brazil banks live in production with measurable first-trade conversion uplift and a repeatable path to six partners are the milestones that justify the next financing.
Revenue, cash, and EBITDA — 12-month Y1 + 8-quarter Y2/Y3
Revenue (line, area)
Cash EOP (dashed)
EBITDA (bars, gray = loss)
Use of funds — $2.8M pre-seedHeadcount build by role — peak16 FTE
Founder/CEO
Engineering
Solutions & compliance
Product & regulatory
Partnerships & GTM
Sales & customer success
G&A
Year-3 scenarios — base / downside / upside
Y3 revenue
Y3 EBITDA
Cash low point
Description
Downside
$4.15M
-$210K
$410K
Production launches slip one quarter, mature partner revenue lands closer to $10 per wallet per year, and gross margin tops out near 69%.
Base
$5.55M
$707K
$1.06M
Two paid pilots convert on time, six production partners are live by Q4Y2, and each partner approaches roughly 95K active wallets by late Y3.
Upside
$6.90M
$1.28M
$1.18M
The first six partners ramp wallet activity faster, pricing holds near the top of the target range, and premium analytics modules attach inside the initial cohort.
Sensitivity — Y3 cash and revenue impact, sorted by magnitude
Variable
Downside
Upside
Cash impact
Revenue impact
ARPU
$10 annual revenue per active wallet
$13.5 annual revenue per active wallet
-$660K
-$920K
sales cycle
12-month cycle from first meeting to production
7-8 month cycle with partner-assisted procurement
-$520K
-$850K
gross margin
69% steady-state gross margin
75% steady-state gross margin
-$300K
$0K
hiring pace
Front-load three extra commercial hires before product-market proof
Delay two non-core hires until after the sixth partner is live
-$280K
-$200K
CAC
$200K CAC per production logo
$110K CAC per production logo
-$240K
$0K
churn
2.5% monthly economic churn after production
1.0% monthly economic churn
-$180K
-$350K
Scenarios
Scenario
Y3 revenue
Y3 EBITDA
Cash low point
Description
Key changes
Downside
$4.15M
$-210K
$410K
Production launches slip one quarter, mature partner revenue lands closer to $10 per wallet per year, and gross margin tops out near 69%.
ARPU realization falls from $12 to $10 per active wallet per year.
Customers 4-6 launch one quarter later than the base case.
Two paid pilots convert on time, six production partners are live by Q4Y2, and each partner approaches roughly 95K active wallets by late Y3.
Revenue per active wallet stays near the $12 research benchmark.
Launch speed remains under 10 weeks after the first two production banks.
Hiring follows the staged plan instead of pulling forward a larger sales team.
Upside
$6.90M
$1.28M
$1.18M
The first six partners ramp wallet activity faster, pricing holds near the top of the target range, and premium analytics modules attach inside the initial cohort.
Mature partner revenue rises toward $13.5 per wallet per year.
Customers 3-6 reach target wallet penetration about one quarter faster than base.
Gross margin expands to the mid-70s as implementations standardize sooner.
Sensitivity
Variable
Downside
Base
Upside
ARPU
$10 annual revenue per active wallet
$12 annual revenue per active wallet
$13.5 annual revenue per active wallet
CAC
$200K CAC per production logo
$140K CAC per production logo
$110K CAC per production logo
churn
2.5% monthly economic churn after production
1.5% monthly economic churn
1.0% monthly economic churn
sales cycle
12-month cycle from first meeting to production
9-10 month cycle to first production
7-8 month cycle with partner-assisted procurement
gross margin
69% steady-state gross margin
72% steady-state gross margin
75% steady-state gross margin
hiring pace
Front-load three extra commercial hires before product-market proof
Reach 12 FTE by Q4Y2 and 16 FTE by Q4Y3
Delay two non-core hires until after the sixth partner is live
Key assumptions (18)
ID
Name
Value
Unit
Source
A1
Model start month
2026-07
month
[report date]
A2
Opening cash after pre-seed close
2800
usdK
[BP fundingAsk $2-4M range; base case uses a $2.8M close to preserve a six-month cash buffer]
Flags: Y3 revenue is concentrated in only six bank partners, so one delayed launch or one weak wallet ramp can move the outcome materially. · The base case assumes no logo churn through Y3 and only 1.5% monthly economic churn, which is optimistic until renewals are proven. · Gross margin clears the 70% target only after implementations standardize; more than about three engineer-weeks of custom work per partner would pressure the model. · Regulatory or counsel-driven feature gating can lengthen sales cycles and pull the cash profile toward the downside case.
Section
Top risks
Coinbase or Binance launches a competing neobank SDK. Either incumbent could ship a neobank white-label program within 12–18 months, leveraging existing compliance infrastructure and brand trust to crowd out an independent SDK vendor before the social graph moat is established. Mitigation: Sign two or three anchor neobanks with 18-month exclusivity clauses in LatAm before the incumbents announce; early social graph data locked within partner permission boundaries creates a switching cost that a late incumbent entry cannot easily replicate.
Gas cost volatility squeezes sponsorship unit economics. Gas sponsorship for first-time users on Ethereum mainnet can spike 10–50x during congestion events, making per-wallet unit economics unpredictable and temporarily negative for the sponsorship float. Mitigation: Route all sponsored transactions through Ethereum L2s (Base, Arbitrum) with automatic fallback to Solana, and cap sponsorship exposure to $0.02 per transaction via cost controls baked into the SDK's transaction scheduler from day one.
Regulatory fragmentation slows multi-market expansion. Non-custodial wallet rules, copy-trading disclosure requirements, and crypto derivatives regulations differ sharply across LatAm, SEA, and MENA, creating per-market legal spend that can delay expansion timelines and inflate overhead. Mitigation: Hire one regional regulatory counsel each for Brazil, Singapore, and UAE who maintains the compliance module for that jurisdiction; charge customers a per-jurisdiction activation fee that offsets the recurring legal cost and turns compliance depth into a premium differentiator.