initial commit
This commit is contained in:
168
docs/market-memo.md
Normal file
168
docs/market-memo.md
Normal file
@@ -0,0 +1,168 @@
|
||||
# Market Memo
|
||||
|
||||
## Thesis
|
||||
|
||||
There is a clear product gap between commission software, faster worker payouts, and Brazil-native embedded finance.
|
||||
|
||||
Many companies solve one layer of the stack well. Very few appear to own the full loop from customer payment to commission calculation to worker access to funds. That creates an opening for a Brazil-first platform built around real-time commission availability.
|
||||
|
||||
## The gap in the market
|
||||
|
||||
Commission-heavy businesses still operate with delayed payroll cycles, spreadsheet-based commission workflows, and informal employee advances. Workers want faster access to earnings. Employers want control, auditability, and better visibility.
|
||||
|
||||
Existing vendors tend to split into separate categories:
|
||||
|
||||
- faster pay or earned wage access
|
||||
- payout rails and disbursement infrastructure
|
||||
- commission calculation and analytics software
|
||||
- employee wallet or card experiences
|
||||
- Brazil payment and card infrastructure
|
||||
|
||||
The opportunity is to combine these into a single workflow built around a verified payment event.
|
||||
|
||||
## Competitor map
|
||||
|
||||
| Company | What it does well | Missing piece relative to this idea |
|
||||
|---|---|---|
|
||||
| `DailyPay` | Earned wage access, employee liquidity, employer integrations | Not centered on payment-linked commissions or commission-heavy teams |
|
||||
| `Branch` | Workforce payments, employee app, card, embedded finance | More generic worker finance than commission-specific infrastructure |
|
||||
| `PayQuicker` | Fast commission payouts, cards, payout portals | Weaker employer-side commission operating system and Brazil-specific positioning |
|
||||
| `Hyperwallet` | Global payout orchestration | Infrastructure layer, not a commission system of record |
|
||||
| `CaptivateIQ` | Commission calculation, visibility, forecasting | No native money movement or worker access to balances |
|
||||
| `Caju` | Brazil employee finance and card experience | Not the source of truth for commission creation and payout logic |
|
||||
| `Dock` | Brazil financial infrastructure for accounts, cards, `Pix` | Not a direct competitor; more likely an enabling layer |
|
||||
|
||||
## What is differentiated here
|
||||
|
||||
The strongest version of this company is not just a wallet and not just an analytics tool.
|
||||
|
||||
It is:
|
||||
|
||||
`a commission ledger that turns verified sales into immediately usable balances`
|
||||
|
||||
That positioning changes the product in important ways:
|
||||
|
||||
- the source of truth is a payment event, not a later payroll export
|
||||
- the employer gets workflow, controls, and analytics
|
||||
- the employee gets liquidity without relying on informal advances
|
||||
- the company can monetize software, payment flow, and later retained balances
|
||||
|
||||
## Why Brazil first
|
||||
|
||||
Brazil is the more compelling launch market than Switzerland for this specific thesis.
|
||||
|
||||
- `Pix` makes instant access behaviorally normal.
|
||||
- Informal paycheck advances or `vales` create a visible pain point.
|
||||
- Smaller financial institutions and infrastructure partners may be more open to collaboration.
|
||||
- Commission-heavy SMB and mid-market businesses are common.
|
||||
- The value proposition is concrete and easy to explain.
|
||||
|
||||
Switzerland may still matter later, but Brazil provides the clearer wedge, larger behavioral advantage, and stronger infrastructure fit for instant commission access.
|
||||
|
||||
## Recommended wedge
|
||||
|
||||
The initial product should avoid trying to become a broad payroll platform or a credit-led consumer app.
|
||||
|
||||
The recommended wedge is:
|
||||
|
||||
- process or reconcile customer payments
|
||||
- calculate commissions in real time
|
||||
- make a safe portion of earned commissions available immediately
|
||||
- let workers cash out via `Pix`
|
||||
- give employers dashboards, controls, and reporting
|
||||
|
||||
This creates value for both sides without requiring the company to start as a full lending business.
|
||||
|
||||
## Differentiation versus adjacent players
|
||||
|
||||
### Versus `DailyPay` and `Branch`
|
||||
|
||||
- lead with real-time commission access, not generic earned wage access
|
||||
- use payment-triggered earnings instead of payroll-cycle files
|
||||
- speak directly to commission-heavy employers
|
||||
|
||||
### Versus `CaptivateIQ`
|
||||
|
||||
- move from commission visibility to commission execution
|
||||
- turn calculation into money movement and employee utility
|
||||
|
||||
### Versus `PayQuicker` and `Hyperwallet`
|
||||
|
||||
- own employer workflows and analytics, not just disbursement rails
|
||||
- focus on Brazil-native behavior and infrastructure
|
||||
|
||||
### Versus `Caju`
|
||||
|
||||
- own the commission event and payout logic, not only the employee finance interface
|
||||
|
||||
## Business model
|
||||
|
||||
The business should start with software and movement fees, then layer in higher-margin economics over time.
|
||||
|
||||
Early revenue:
|
||||
|
||||
- employer platform fee
|
||||
- payment or reconciliation take rate
|
||||
- payout fee or bundled payout plan
|
||||
- analytics tier for larger employers
|
||||
|
||||
Later revenue:
|
||||
|
||||
- interchange from card spend
|
||||
- float-sharing or treasury economics if allowed by partner structure
|
||||
- employer-backed advance fees
|
||||
|
||||
The key is to avoid depending on balance-sheet lending to make the model work.
|
||||
|
||||
## Go-to-market
|
||||
|
||||
### Target customers
|
||||
|
||||
- Brazil-based SMB and mid-market employers with commission-heavy teams
|
||||
- businesses where payment events are digital and attributable
|
||||
- verticals such as franchise retail, clinics, education, auto, telecom, and other sales-led operations
|
||||
|
||||
### Buyer
|
||||
|
||||
- owner
|
||||
- finance lead
|
||||
- operations lead
|
||||
- sales manager
|
||||
|
||||
### Core pitch
|
||||
|
||||
- reduce manual commission work
|
||||
- reduce informal advances
|
||||
- help retain and motivate sales staff
|
||||
- create a trusted real-time view of commission liability and performance
|
||||
|
||||
### Distribution channels
|
||||
|
||||
- direct sales to design partners
|
||||
- vertical SaaS and POS partnerships
|
||||
- franchise groups
|
||||
- accounting and payroll-adjacent referral channels
|
||||
|
||||
## Defensibility
|
||||
|
||||
If the company succeeds, defensibility should come from workflow ownership and data position rather than pure infrastructure.
|
||||
|
||||
- payment-linked truth rather than self-reported sales data
|
||||
- employer-configured commission logic embedded in operations
|
||||
- worker adoption through payout utility and later card usage
|
||||
- analytics built on actual money movement
|
||||
- multi-layer monetization across software, payments, and retention tools
|
||||
|
||||
## Key risks
|
||||
|
||||
- payment reversals after employee funds are made available
|
||||
- employer disputes over commission rules
|
||||
- regulatory boundaries around custody, wage access, and credit
|
||||
- dependence on a single bank, BaaS, or card partner
|
||||
- low balance retention if the product offers no reason to keep funds in-platform
|
||||
|
||||
## Bottom line
|
||||
|
||||
This idea is attractive because it sits in the overlap of three proven categories: commission software, worker liquidity, and embedded finance.
|
||||
|
||||
The market does not appear empty, but it still looks fragmented. A Brazil-first product that turns every validated sale into an auditable, instantly accessible commission balance could occupy a distinct category: `real-time commission infrastructure`.
|
||||
Reference in New Issue
Block a user