initial commit

AGENTS.md

@@ -0,0 +1,90 @@
+# AGENTS.md
+
+## Project overview
+
+This repository is a documentation-first workspace for a startup concept.
+
+The startup thesis is a B2B2C fintech platform that processes or reconciles customer payments, calculates commissions in real time, gives employees fast access to earned commissions, and gives employers better controls and analytics around commission payouts.
+
+## Current strategic thesis
+
+- Start in Brazil.
+- Lead with `Pix`-based instant access to earned commissions.
+- Use a regulated financial partner for custody, payouts, card issuance, and compliance.
+- Treat cards and stored balances as later retention tools, not the initial wedge.
+- Treat advances as a later employer-backed feature, not the first product.
+- Build employer analytics from payment-linked data.
+
+## What this company is
+
+- commission infrastructure
+- a ledger and payout orchestration layer
+- an employer workflow product with employee financial utility
+
+## What this company is not
+
+- not a generic neobank
+- not a full payroll processor
+- not a full CRM
+- not a payday lender
+
+## Repository status
+
+- There is no production code yet.
+- The repo currently stores strategy and planning documents.
+
+## Key documents
+
+- `docs/core-idea.md` - canonical summary of the product and business model
+- `docs/brazil-market.md` - Brazil-specific thesis and go-to-market notes in pt-BR
+- `docs/market-memo.md` - competitor map, differentiation, and investor-style memo
+- `docs/positioning-and-landing-copy.md` - messaging and homepage copy directions
+- `docs/year-one-roadmap.md` - phased roadmap for the first year
+- `docs/ideas-for-review.md` - review file for ideas not yet integrated into the core docs
+
+## Language conventions
+
+- Write in English by default.
+- Keep `docs/brazil-market.md` in pt-BR.
+- Keep fintech terminology consistent: `Pix`, `commission ledger`, `earned commission access`, `employer-backed advance`, `stored balance`.
+
+## Transcripts
+
+- Transcripts of previous sessions are available under the sessions/ subdir, in case extra context is necessary.
+
+## Product assumptions to preserve
+
+- Early architecture should rely on a licensed partner rather than direct custody.
+- The safest wedge is real-time access to earned commissions, not general lending.
+- The payment event is the source of truth for commission creation whenever possible.
+- The employer buyer needs controls, auditability, and analytics, not just a payout rail.
+- The employee experience matters because faster access and later card usage can improve retention and platform utility.
+
+## Reference competitors and adjacent players
+
+Use this current market framing unless new evidence clearly changes it:
+
+- `DailyPay`
+- `Branch`
+- `PayQuicker`
+- `Hyperwallet`
+- `CaptivateIQ`
+- `Caju`
+- `Dock`
+
+These companies validate parts of the stack, but the current thesis is that few combine payment-linked commissions, worker liquidity, employer controls, and Brazil-native rails into one product.
+
+## Prioritization guidance for future agents
+
+- Prioritize docs and plans that sharpen the Brazil-first wedge.
+- Keep the distinction between `earned access` and `credit` very clear.
+- Prefer practical operator language over generic fintech buzzwords.
+- If you extend product plans, sequence features conservatively: ledger and instant payouts first, analytics and stored balance second, cards third, employer-backed advances later.
+
+## Open areas worth exploring later
+
+- deeper regulatory mapping for Brazil launch structure
+- partner comparison across BaaS, payment processors, and card issuers
+- pricing design for employers versus workers
+- reserve rules for refunds, disputes, and chargebacks
+- target vertical selection and design-partner outreach strategy

README.md

@@ -0,0 +1,26 @@
+# Payroll Planning Workspace
+
+Documentation-first workspace for a Brazil-first B2B2C fintech concept focused on payment-linked commissions, instant access to earned balances, and employer controls around payouts and analytics.
+
+## Document index
+
+- `docs/core-idea.md` - canonical summary of the product, operating model, and money flow
+- `docs/brazil-market.md` - Brazil-specific thesis, local constraints, and go-to-market notes in pt-BR
+- `docs/market-memo.md` - market gap, competitor map, differentiation, and business model framing
+- `docs/positioning-and-landing-copy.md` - messaging directions, landing-page copy, and narrative structure
+- `docs/year-one-roadmap.md` - phased plan for the first year of product and partner execution
+- `docs/ideas-for-review.md` - ideas from external conversations that are not yet part of the core docs
+
+## Suggested reading order
+
+- `docs/core-idea.md`
+- `docs/brazil-market.md`
+- `docs/market-memo.md`
+- `docs/positioning-and-landing-copy.md`
+- `docs/year-one-roadmap.md`
+
+## Notes
+
+- Write in English by default; keep `docs/brazil-market.md` in pt-BR.
+- The repository currently holds strategy and planning documents, not production code.
+- Session transcripts live under `sessions/`.

docs/brazil-market.md

@@ -0,0 +1,191 @@
+# Tese para o mercado brasileiro
+
+## Resumo
+
+A melhor entrada para esta ideia no Brasil e uma plataforma B2B2C que conecta recebimento, calculo de comissao, ledger interno e acesso instantaneo ao saldo via `Pix`.
+
+O produto inicial nao deve ser vendido como banco digital nem como credito ao consumidor. A tese mais forte e:
+
+`transformar cada venda validada em saldo de comissao disponivel quase em tempo real`
+
+## Por que o Brasil primeiro
+
+- `Pix` ja criou expectativa de movimentacao instantanea e barata.
+- O mercado convive com atraso no pagamento de comissoes e com o uso informal de `vales`.
+- Existem instituicoes financeiras, cooperativas, BaaS e emissores abertos a parcerias.
+- Ha muitos segmentos com equipes comerciais comissionadas e operacao digital crescente.
+- O argumento de valor e simples: menos atraso, menos friccao operacional e mais retencao do time de vendas.
+
+## Dor local que o produto resolve
+
+### Para a empresa
+
+- Calculo manual de comissao.
+- Fechamento mensal demorado.
+- Falta de visibilidade sobre passivo de comissao.
+- Uso informal de `vales`, com pouca governanca.
+- Dificuldade para reconciliar recebimento, comissao, estorno e repasse final.
+
+### Para o vendedor
+
+- Venda feita hoje, dinheiro disponivel so dias ou semanas depois.
+- Dependencia de `vale` para cobrir caixa pessoal.
+- Falta de transparencia sobre o que foi ganho, o que esta disponivel e o que ainda esta pendente.
+
+## ICP inicial
+
+O foco deve ser empresas brasileiras com time comercial comissionado e recebimento digital identificavel.
+
+Segmentos promissores:
+
+- franquias e operacoes de varejo com vendedores comissionados
+- clinicas de estetica, odontologia e procedimentos eletivos
+- academias e servicos recorrentes com equipe de vendas
+- escolas, cursos e educacao privada com captacao comercial
+- telecom, distribuicao e revendas com metas e bonificacao variavel
+
+## Proposta de valor no Brasil
+
+### Para a empresa
+
+- Automatizar o calculo e o repasse de comissoes.
+- Reduzir dependencia de `vales` informais.
+- Melhorar retencao e motivacao do time.
+- Ter visao confiavel de performance comercial e custo de comissao.
+- Ganhar previsibilidade de caixa e de passivo.
+
+### Para o colaborador
+
+- Ver a comissao quase em tempo real.
+- Sacar instantaneamente via `Pix` quando o saldo estiver disponivel.
+- Ter mais clareza sobre metas, historico e projecao de ganhos.
+- No futuro, usar saldo por cartao sem precisar sacar tudo.
+
+## Produto recomendado para o Brasil
+
+### V1
+
+- recebimento via parceiros de pagamento
+- motor de regras de comissao
+- ledger com estados `ganho`, `disponivel` e `liquidado`
+- saldo para colaborador e empresa
+- saque instantaneo via `Pix`
+- dashboard basico para empresa e vendedor
+- trilha de auditoria por transacao, comissao e ajuste
+
+### V2
+
+- saldo retido em carteira
+- analytics de performance e passivo de comissao
+- regras de reserva para estorno e chargeback
+- alertas e projecoes
+- piloto de adiantamento com respaldo do empregador
+
+### V3
+
+- cartao prepago ou debito
+- maior retencao de saldo na plataforma
+- integracoes com ERP, POS, CRM ou software vertical
+
+## Parceiros locais que importam
+
+### Infra financeira
+
+- instituicao de pagamento, banco parceiro ou BaaS para custodia e movimento regulado
+- exemplos de infraestrutura para avaliar: `Dock`, `QI Tech`, `Celcoin`
+- cooperativas e bancos menores podem ser parceiros comerciais ou institucionais, incluindo nomes como `Sicredi`, dependendo do modelo
+
+### Processamento de pagamentos
+
+- parceiros para `Pix`, boleto e cartao
+- exemplos para avaliar: `Pagar.me`, `Stripe BR`, `Adyen`
+
+### Emissao de cartao
+
+- exemplos para avaliar: `Dock`, `Pomelo`, `Swap`
+
+### KYC e KYB
+
+- exemplos para avaliar: `idwall`, `BigDataCorp`
+
+### Juridico e regulatorio
+
+- escritorio com experiencia em instituicao de pagamento, arranjos de pagamento, `Pix`, LGPD e temas trabalhistas
+
+## Consideracoes regulatorias
+
+O produto encosta em varias frentes e precisa de mapeamento juridico desde cedo.
+
+- Banco Central: estrutura de `Pix`, conta transacional, instituicao de pagamento, regras de reporte e compliance.
+- Direito do trabalho: natureza da comissao, reflexos em folha, desconto de adiantamentos, regras contratuais com empregador.
+- LGPD: dados financeiros e de performance do colaborador.
+- CDC e transparencia: fees, prazos, disponibilidade e regras de estorno.
+
+Recomendacao pratica:
+
+- comecar debaixo da licenca e da infraestrutura de um parceiro regulado
+- evitar custodia direta no inicio
+- evitar vender o produto inicial como emprestimo
+
+## Como tratar `vales`
+
+No Brasil, `vale` e um substituto informal para um problema real de liquidez. O produto pode reduzir esse comportamento sem virar credito agressivo logo no inicio.
+
+Sequencia recomendada:
+
+- acesso ao que ja foi ganho e validado
+- liberacao conservadora de parte do saldo antes da liquidacao total
+- adiantamento com respaldo do empregador
+- so depois, se fizer sentido, credito com underwriting proprio
+
+Mensagem correta:
+
+- nao: `emprestimo para vendedor`
+- sim: `acesso controlado a comissao ja gerada`
+
+## Go-to-market no Brasil
+
+### Primeiro movimento
+
+- fechar 5 a 10 design partners com dor forte de comissao e operacao relativamente simples
+- priorizar empresas em que o evento de venda e facil de mapear ao pagamento
+- vender para dono, financeiro, operacoes e gestor comercial
+
+### Canais de distribuicao
+
+- venda direta para SMB e mid-market
+- parceria com software vertical, POS e adquirencia
+- grupos de franquia
+- escritorios contabeis e consultorias de operacao ou folha
+
+### Pitch inicial
+
+- reduza trabalho manual no fechamento de comissoes
+- de ao time acesso mais rapido ao que ja foi ganho
+- troque `vales` informais por um processo auditavel
+- tenha visao em tempo real de performance e passivo de comissao
+
+## Modelo economico mais provavel
+
+- fee de plataforma para a empresa
+- fee por volume processado ou por pagamento conciliado
+- fee por saque, ou plano com franquia de saques
+- camada premium de analytics
+- depois: interchange de cartao
+- depois: compartilhamento de economia financeira, se permitido pelo arranjo com parceiro
+
+## Principais riscos no mercado brasileiro
+
+- estorno ou chargeback depois da liberacao da comissao
+- disputa entre empresa e vendedor sobre regra de comissao
+- dependencia excessiva de um parceiro bancario ou de BaaS
+- classificacao regulatoria errada do produto
+- onboarding ruim para empresa e colaborador
+
+## Tese final para o Brasil
+
+O melhor posicionamento nao e `mais um app de EWA` e nem `mais um banco digital`.
+
+O melhor posicionamento e:
+
+`a infraestrutura de comissao em tempo real para empresas brasileiras, com saldo disponivel via Pix e visibilidade operacional para o empregador`

docs/core-idea.md

@@ -0,0 +1,197 @@
+# Core Idea
+
+## One-line thesis
+
+A B2B2C fintech platform that turns customer payments into real-time commission balances, gives employees instant access to earned commissions, and gives employers a reliable system of record for commission payouts and performance.
+
+## The problem
+
+### Employers
+
+- Commission calculation is often manual, delayed, and hard to audit.
+- Sales teams ask for informal advances when payroll cycles lag behind real sales activity.
+- Finance teams struggle to forecast commission liability and reconcile payouts.
+- Sales performance data is scattered across spreadsheets, POS tools, CRMs, and payroll systems.
+
+### Employees
+
+- A sale can happen today, but the commission may not be usable for days or weeks.
+- Early access to money often depends on asking for an informal advance.
+- There is rarely a clear view of what has been earned, what is available, and what is still pending.
+
+## The product
+
+The product sits between customer payment collection and employer payout.
+
+- A customer makes a payment.
+- The platform receives the payment event directly, or receives trusted payment data from a partner.
+- A commission engine applies employer-defined rules.
+- The internal ledger allocates balances between employer and employee.
+- A safe portion of the employee's commission becomes available immediately.
+- The employee can cash out instantly, and later can also spend from a wallet or card.
+- The employer gets the remaining balance on a defined settlement schedule.
+- Both sides get visibility into earnings, payouts, and performance.
+
+## Core product layers
+
+### Payment collection or orchestration
+
+- Accept customer payments directly, or integrate with the employer's processor.
+- Use payment events as the source of truth for commission creation.
+
+### Commission rules engine
+
+- Support percentage-based, tiered, and custom rules.
+- Lock an auditable calculation for every sale or payment event.
+- Track exceptions, reversals, and dispute states.
+
+### Ledger and balances
+
+- Maintain an internal double-entry ledger.
+- Track at least three states: `earned`, `available`, `settled`.
+- Keep clear subledgers for employee balances, employer balances, fees, reserves, and adjustments.
+
+### Instant access rails
+
+- Start with instant bank transfer or `Pix` cash-out.
+- Later add stored balance inside the app.
+- Later add a prepaid or debit card linked to the balance.
+
+### Employer analytics
+
+- Real-time commission liability.
+- Sales staff performance based on actual money movement.
+- Forecasts for payouts, reserve needs, and commission trends.
+
+### Optional later financing layer
+
+- Employer-backed advances.
+- True risk-based credit only after the business has reliable repayment and reversal data.
+
+## Recommended money flow
+
+The safest early structure is partner-led custody.
+
+- A regulated bank or licensed financial partner holds funds.
+- The platform owns the application layer, commission logic, ledger, and payout orchestration.
+- Cards, `Pix`, KYC, and regulated money movement are handled through partners.
+
+Example flow:
+
+```text
+Customer pays R$1,000
+        |
+        v
+Partner-held account receives funds
+        |
+        v
+Commission engine calculates split
+        |
+        +-- Employee commission: R$200
+        +-- Employer balance: R$800
+        +-- Platform fee and reserve logic applied
+        |
+        v
+Employee sees commission balance in app
+        |
+        +-- Instant cash-out
+        +-- Hold balance
+        +-- Later: card spend
+```
+
+## Product thesis
+
+This should not start as a generic wallet, a payroll platform, or a payday loan app.
+
+The strongest wedge is:
+
+`real-time commission access tied to actual payment events`
+
+That positioning matters because it keeps the first product grounded in employer ROI, worker liquidity, and trusted payment data.
+
+## Revenue model
+
+The business should start with software and money movement economics, not balance-sheet lending.
+
+- Platform or SaaS fee for employers.
+- Take rate or processing fee on payment volume.
+- Payout fee or bundled payout plan.
+- Premium analytics tier.
+- Later: interchange from card spend.
+- Later: float-sharing or treasury economics if allowed by partner structure.
+- Much later: advance fee for employer-backed early access products.
+
+## What the company is not
+
+- Not a general neobank.
+- Not a full payroll processor.
+- Not a full CRM or sales engagement tool.
+- Not a payday lender.
+
+The company is best understood as `commission infrastructure`.
+
+## Phased expansion
+
+### Phase 1
+
+- Payment-linked commission calculation.
+- Employer and employee onboarding.
+- Ledger with `earned`, `available`, and `settled` states.
+- Instant payout access.
+- Employer and employee dashboards.
+
+### Phase 2
+
+- Stored balance and wallet behavior.
+- Better analytics and forecasting.
+- Reserve and holdback controls for refunds and chargebacks.
+- Early employer-backed advance logic for selected customers.
+
+### Phase 3
+
+- Card issuance.
+- Spend directly from balance.
+- More balance retention and interchange revenue.
+- Deeper employer integrations.
+
+### Phase 4
+
+- Multi-entity support.
+- Broader partner distribution.
+- Carefully controlled credit products if the data and regulation support them.
+
+## Key risks and guardrails
+
+### Regulatory boundary
+
+- Do not begin by directly holding deposits or acting like an unlicensed financial institution.
+- Use a licensed partner for custody and regulated money movement.
+
+### Reversals and chargebacks
+
+- Do not make all commissions instantly withdrawable on day one.
+- Use availability rules, reserves, and holdbacks.
+
+### Commission disputes
+
+- Require explicit employer-approved rules.
+- Preserve a full audit trail for every calculation and adjustment.
+
+### Labor and tax treatment
+
+- Distinguish `earned access` from `credit`.
+- Map payroll, withholding, and deduction obligations with counsel before product launch.
+
+### Partner dependence
+
+- Expect early dependence on bank, card, and processor partners.
+- Build the ledger and business logic so the company can swap infrastructure providers later.
+
+## Current strategic recommendation
+
+- Start in Brazil.
+- Lead with `Pix`-based instant access to earned commissions.
+- Use partner-led custody and compliance.
+- Treat stored balances and cards as retention tools, not the initial wedge.
+- Treat employer analytics as a second major value driver.
+- Delay true lending until the core ledger and payout engine are reliable.

docs/ideas-for-review.md

@@ -0,0 +1,36 @@
+# Ideas For Review
+
+This file captures ideas raised in external conversations that are not yet integrated into the main planning docs. It is a parking lot for later review, not an approved roadmap.
+
+## Potential additions
+
+### Employer availability controls
+
+- Let employers configure what share of earned commission becomes available immediately.
+- Support policy rules by role, channel, product, or refund-risk profile.
+- Add employer-set caps, waiting windows, and override rules for cash-out eligibility.
+
+### Clearer balance messaging
+
+- Make the employee-facing UX explicit: `earned` now, `available` later, with concrete wording such as `earned now, withdrawable in X days`.
+- Pair that messaging with visible explanations for employer policy, refund risk, and dispute timing.
+
+### Deeper analytics modules
+
+- Show progress toward target or quota at the individual employee level.
+- Track refund or chargeback rates by employer, location, channel, or seller.
+- Trigger alerts when employee performance drops or when refund behavior starts affecting availability.
+- Consider a premium analytics tier only after the core workflow proves valuable.
+
+### Pricing and economics to evaluate
+
+- Test employer pricing tiers based on payment volume, workflow complexity, or payout usage.
+- Define the economics of employer-backed advances, including whether part of the fee is shared with the employer.
+- If retained-balance incentives are explored later, keep them aligned with partner-held custody and avoid making float the primary value case.
+
+## Ideas raised but not aligned with the current thesis
+
+- Direct custody or wording that implies customer funds sit in the company account.
+- Float as an early core revenue driver.
+- Using retained funds to build a lending business before the ledger, controls, and reversal data are mature.
+- Making advances an early flagship feature instead of a later employer-backed extension.

docs/market-memo.md

@@ -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`.

docs/positioning-and-landing-copy.md

@@ -0,0 +1,134 @@
+# Positioning and Landing Copy
+
+## Core positioning
+
+This company should not present itself as a generic earned wage access app.
+
+The stronger frame is:
+
+`commission infrastructure for real-time sales teams`
+
+## Category statement
+
+We help employers turn verified sales into instantly accessible commission balances, with employer controls, worker payouts, and performance visibility built into one system.
+
+## Short positioning line
+
+Turn every sale into an instantly usable commission balance.
+
+## Headline options
+
+- Turn every sale into an instantly accessible commission.
+- Give sales teams instant access to earned commissions.
+- Real-time commissions for modern sales teams.
+- The fastest way to move from customer payment to salesperson payout.
+- Commission payouts, employer controls, and worker access in one platform.
+
+## Subhead options
+
+- We help employers calculate commissions from real payment events, make safe balances available immediately, and give teams a better way to access what they have earned.
+- Replace delayed commission cycles and informal advances with a real-time ledger, instant payouts, and clear employer visibility.
+- Built for commission-heavy businesses that want faster payouts, cleaner operations, and better sales performance data.
+
+## Product pillar copy
+
+### Real-time commission engine
+
+Calculate commissions from verified payment events instead of waiting for payroll cycles and spreadsheet reconciliations.
+
+### Instant worker access
+
+Give employees access to eligible commission balances right away, starting with instant cash-out and later expanding to wallet and card spend.
+
+### Employer control and auditability
+
+Set payout rules, track reserve logic, and keep a reliable audit trail across every sale, split, payout, and adjustment.
+
+### Payment-linked performance data
+
+See team performance, commission liability, and payout trends from real money movement rather than disconnected reporting tools.
+
+## Employer value props
+
+- Reduce manual commission operations.
+- Replace informal advances with a controlled workflow.
+- Improve salesperson retention and motivation.
+- Get a clearer view of commission cost and team performance.
+- Create a better employee experience without building internal fintech operations.
+
+## Employee value props
+
+- See what you have earned sooner.
+- Access eligible commissions faster.
+- Stop relying on informal paycheck advances.
+- Track progress and earnings in one place.
+- Later, spend directly from your balance.
+
+## Messaging to avoid
+
+- Avoid describing the product as a payday loan.
+- Avoid leading with float economics or holding customer cash.
+- Avoid broad claims about replacing payroll or becoming a bank.
+
+## Best narrative arc for a homepage
+
+### Hero
+
+Headline plus a subhead focused on real-time commission access.
+
+### Problem section
+
+Show the old flow: sale now, commission later, advance requests in between.
+
+### Solution section
+
+Show the new flow: payment event, commission split, available balance, instant access.
+
+### Employer section
+
+Focus on automation, controls, and analytics.
+
+### Employee section
+
+Focus on liquidity, visibility, and trust.
+
+### Proof section
+
+Use three proof points:
+
+- built around verified payment events
+- instant payout access
+- auditable employer controls
+
+### CTA section
+
+Push a design-partner conversation, not a self-serve signup.
+
+## CTA options
+
+- Talk to us about your commission workflow.
+- See how real-time commission payouts could work for your team.
+- Become a design partner.
+- Explore a commission infrastructure demo.
+
+## Sample hero copy
+
+### Option A
+
+Headline: Turn every sale into an instantly accessible commission.
+
+Subhead: We help commission-heavy businesses calculate payouts from real payment events, give teams faster access to eligible earnings, and keep employer controls and visibility in one place.
+
+CTA: Become a design partner
+
+### Option B
+
+Headline: Real-time commissions for modern sales teams.
+
+Subhead: Replace delayed commission cycles and informal advances with a payment-linked ledger, instant payout access, and cleaner employer operations.
+
+CTA: See the workflow
+
+## Elevator pitch
+
+We are building the financial operating layer between customer payments and salesperson earnings. Employers get automated commission calculation and better visibility. Sales teams get faster access to earned commissions. The result is a more trusted, more useful, and more immediate commission system.

docs/year-one-roadmap.md

@@ -0,0 +1,185 @@
+# Year-One Roadmap
+
+## Guiding principle
+
+Do not start by building a broad neobank or a consumer lending app.
+
+Start with the smallest product that proves the core wedge:
+
+`payment-linked commission calculation plus instant access to earned balances`
+
+## Success goal for year one
+
+By the end of 12 months, the company should prove that employers will adopt a commission-led payout workflow and that employees will use it for faster access to earnings.
+
+The year-one target is not maximum feature breadth. It is proof of product-market fit for the core loop.
+
+## Foundation and partner design
+
+### Months 0-2
+
+#### Objectives
+
+- validate the first customer segment
+- choose partner model for custody, payouts, and compliance
+- lock the ledger and commission system design
+
+#### Workstreams
+
+- run design-partner interviews with target employers
+- map employer commission workflows and exception cases
+- choose payment and banking partner shortlist
+- define balance states: `earned`, `available`, `settled`
+- define reserve and holdback logic for reversals
+- specify onboarding flows for employers and employees
+
+#### Deliverables
+
+- product requirements for v1
+- legal and regulatory issue map
+- partner shortlist and integration plan
+- event model for payments, commissions, adjustments, and payouts
+
+#### Exit criteria
+
+- 5 to 10 serious design partners in pipeline
+- clear v1 scope that does not depend on lending
+- chosen path for `Pix` and custody infrastructure
+
+## Core ledger and instant payout access
+
+### Months 2-5
+
+#### Objectives
+
+- launch the first working employer flow
+- prove that a verified sale can become an eligible commission balance
+- enable instant cash-out for employees
+
+#### Product scope
+
+- employer onboarding
+- employee onboarding through partner KYC
+- payment ingestion or payment reconciliation
+- commission rules engine
+- internal ledger
+- employee balance with `earned`, `available`, and `settled`
+- employer settlement scheduling
+- instant payout access via `Pix` or equivalent instant transfer rail
+- employer dashboard with payout and commission views
+- employee dashboard with balance and payout history
+
+#### Operational scope
+
+- manual support for edge cases
+- conservative limits on instant availability
+- dispute and adjustment workflows
+
+#### Metrics
+
+- number of active employers
+- commission volume processed
+- payout latency
+- adjustment and reversal rate
+- employee activation rate
+
+## Analytics and stored balance
+
+### Months 5-8
+
+#### Objectives
+
+- make the product more valuable to employers
+- improve employee retention of balances
+- reduce the need for manual reporting
+
+#### Product scope
+
+- stored balance in the app
+- clearer balance segmentation and reserve visibility
+- employer analytics for team performance and commission liability
+- projections for upcoming payouts
+- employee insights on earnings pace and history
+- alerts for anomalies and budget spikes
+- admin tools for corrections and policy configuration
+
+#### Metrics
+
+- percent of balances retained in-platform
+- dashboard usage by employers
+- frequency of manual interventions
+- repeat payout behavior per employee
+
+## Card and retention tools
+
+### Months 8-10
+
+#### Objectives
+
+- make the balance more useful without requiring immediate cash-out
+- unlock interchange economics
+
+#### Product scope
+
+- prepaid or debit card issuance through a partner
+- spend from available balance
+- card controls and transaction views
+- balance retention incentives tied to usage, not explicit interest promises
+- stronger notifications and mobile experience
+
+#### Metrics
+
+- card activation rate
+- card spend volume
+- balance retention before and after card launch
+- support load per active user
+
+## Scale features and controlled advance pilot
+
+### Months 10-12
+
+#### Objectives
+
+- deepen product value for employers
+- test a tightly controlled version of advance functionality without becoming credit-led
+
+#### Product scope
+
+- multi-entity or franchise support
+- API or integration layer for ERP, CRM, or POS tools
+- employer cash flow forecasting
+- pilot of employer-backed advances with strict limits
+- improved risk rules for refunds, clawbacks, and employee exits
+
+#### Metrics
+
+- employer expansion within existing accounts
+- integration adoption
+- advance usage and repayment behavior
+- loss or exception rate on pilot advances
+
+## What should stay out of scope in year one
+
+- standalone consumer lending
+- full payroll replacement
+- broad international expansion
+- feature-heavy consumer banking experience
+- deep CRM functionality
+
+## Year-one product philosophy
+
+The roadmap should stay disciplined.
+
+- build the commission ledger first
+- prove instant access to earned money second
+- add retention tools third
+- add credit only after the company has the data and controls to support it
+
+## Recommended milestone sequence
+
+- prove employer demand for payment-linked commission automation
+- prove worker demand for instant access to eligible balances
+- prove safe operating rules around reversals and disputes
+- prove that analytics improves employer retention
+- prove that cards increase balance retention
+- only then test employer-backed advance products

sessions/session-ses_2fe5.md

@@ -0,0 +1,705 @@
+# Payment processing with early commission payouts and bank partnerships
+
+**Session ID:** ses_2fe58810cffeU8IzEZHZRCZF25
+**Created:** 3/18/2026, 3:54:07 PM
+**Updated:** 3/18/2026, 4:18:46 PM
+
+---
+
+## User
+
+The core of the idea is: a company that process payments and pays out commissions to employees before sending the money to employers
+However there are some other parts of the idea that I'm still not sure how to put together, for example:
+1) Partnering with banks so that they hold the money and manage that
+2) What are the technologies we can use to process payments 
+
+---
+
+## Assistant (Plan · gpt-5.4 · 24.6s)
+
+A cleaner way to frame the idea is:
+
+- A business receives customer payments.
+- Your platform calculates commissions owed to employees from those payments.
+- The funds are held with a regulated bank partner, not by you directly.
+- Your system instructs payouts to employees first, then sends the remaining balance to the employer.
+
+That gives you a clearer model: payment orchestration + commission ledger + regulated banking partner.
+
+What usually fits best
+
+- `You` are the software and workflow layer: calculate splits, track balances, trigger payouts, reporting.
+- `Bank partner` holds the money in safeguarded/FBO-style accounts and handles regulated money movement.
+- `Payment processor` collects the incoming payment.
+- `Payout rails` send money to employees and employers.
+
+How the bank partnership piece usually works
+
+- You generally do not want to custody funds yourself early on.
+- Instead, partner with a sponsor bank or Banking-as-a-Service provider.
+- The bank holds funds, manages compliance requirements around accounts/movement, and settles transactions.
+- Your platform keeps a ledger of who is owed what and sends payment instructions through APIs.
+
+Typical model
+
+- Customer pays `1000`.
+- Your rules engine says employee commission = `200`.
+- Bank-held account receives `1000`.
+- Platform ledger records:
+  - employee payable `200`
+  - employer payable `800`
+- Payout engine sends `200` to employee, `800` to employer.
+
+Key legal/regulatory point
+
+- This starts to look like `payments + payroll + earned commissions`, so regulation matters a lot.
+- Depending on geography, you may touch:
+  - money transmission
+  - payroll/wage laws
+  - KYC/KYB/AML
+  - card/network rules
+  - tax reporting
+- So the safest early approach is usually: `bank + licensed payment partners + your software layer`, rather than becoming the regulated entity yourself.
+
+Tech stack options
+
+- **Payment acceptance**
+  - `Stripe`, `Adyen`, `Checkout.com`
+  - Good for cards, basic ACH, merchant onboarding
+- **Banking / money movement**
+  - `Stripe Treasury`, `Modern Treasury`, `Moov`, `Increase`, `Dwolla`
+  - Good for ACH, wires, RTP, virtual accounts, balance tracking
+- **Identity / compliance**
+  - `Plaid` for bank linking
+  - `Alloy`, `Persona`, `Sardine` for KYC/KYB/fraud
+- **Ledger / commissions engine**
+  - Internal double-entry ledger
+  - Or tools like `Modern Treasury Ledgers`, `Formance`, `TigerBeetle`
+- **Core app stack**
+  - Backend: `Node.js/TypeScript`, `Python`, or `Go`
+  - DB: `PostgreSQL`
+  - Queue/workflows: `BullMQ`, `Temporal`, `SQS`
+  - Audit/reporting: event log + immutable ledger tables
+
+A practical MVP shape
+
+- Employer onboarding
+- Employee onboarding
+- Payment collection
+- Rules engine for commission calculation
+- Internal ledger for split accounting
+- Manual or scheduled payouts
+- Dashboard for balances, payouts, disputes, reports
+
+Best first partnership strategy
+
+- Start with a provider that already has bank relationships and payout rails.
+- Don’t begin by negotiating directly with a large bank unless you already have scale.
+- A common sequence is:
+  1. use `Stripe/Adyen` for incoming payments
+  2. use `Modern Treasury/Moov/Increase` for payout orchestration
+  3. add direct bank relationships later if volume justifies it
+
+The hardest parts are usually not the code
+
+- commission rule complexity
+- timing of fund availability
+- reversals/chargebacks
+- compliance and licensing boundaries
+- disputes between employee and employer
+- tax and payroll treatment of commissions
+
+If you want, I can next help with one of these:
+1. turn this into a one-paragraph startup description
+2. design the full product/payment flow step by step
+3. suggest a concrete MVP stack for building this in 3 months
+
+---
+
+## User
+
+Right, so what I am thinking is having accounts for the employers and employees and credit money to their accounts in our system when we receive the payments. We need to find a way to incentivise them to leave their money with us for as long as possible to earn interest off off the cash that we're holding. One way I was thinking of doing this is by having credit/debit cards for the users so that they could spend their money directly from their account, while still leaving the option for them to wire that money to their own bank account. I'm considering starting this company in either switzerland or brazil, given that I have people in both countries that I could leverage and bring into this startup. I don't know much about the swiss market, but I know that the brazilian market currently has some smaller banks that seem eager to find partnerships to gain market share, Sicredi for example. Also, in brazil we have PIX which makes wiring money fast and cheap, which could be a great selling point, something along the lines of being able to tell the sales staff that they can instantly have access to their commissions the moment the customer makes a payment.
+
+---
+
+## Assistant (Plan · gpt-5.4 · 34.2s)
+
+You’re moving from “commission payout software” toward a much bigger model: `stored balances + instant access + cards + bank transfers`. That can be powerful, but it changes the company a lot.
+
+The key strategic split
+
+- If you only calculate commissions and trigger payouts, you’re mainly a software/payments orchestration company.
+- If you hold balances in user accounts, let them keep funds, offer cards, and earn yield on float, you start to look like a fintech / neobank / regulated money business.
+
+That second version is much more valuable, but much harder.
+
+What I think is strongest in your idea
+
+- The best wedge is not “we hold your money.”
+- The best wedge is “salespeople get instant access to commissions the moment a sale clears.”
+- In Brazil, that pitch is especially strong because `PIX` makes instant movement normal and expected.
+- A card attached to the balance makes the money feel immediately usable, which is a real behavioral incentive not to cash out.
+
+Important caution on “earning interest off the cash”
+
+- This is attractive economically, but it is also where regulation gets much more serious.
+- You generally cannot just “hold client money and earn interest on it” however you want.
+- You need to be very clear on:
+  - who legally holds the funds
+  - whether funds are customer assets or your operating cash
+  - whether yield/interest belongs to the customer, the bank, or your platform
+  - whether your product becomes regulated as stored value, e-money, deposit-like activity, or money transmission
+- So the safer version is usually:
+  - partner bank or licensed institution holds funds
+  - your platform maintains the subledger and user experience
+  - cards and transfers are issued through licensed partners
+  - your economics come from interchange, SaaS, take rate on processing, float-sharing agreement if allowed, and treasury arrangements
+
+Your proposed product architecture
+
+- Employer account in your app
+- Employee account in your app
+- Incoming payment lands into safeguarded/partner-held funds
+- Your ledger allocates the split instantly
+- Employee sees commission balance immediately
+- Employee can:
+  - spend with card
+  - transfer out to bank
+  - maybe keep balance for future spending
+- Employer receives remaining balance on schedule or instantly
+
+That is a coherent product.
+
+Why Brazil looks stronger than Switzerland for the first launch
+
+- `PIX` is a huge distribution advantage for instant payouts.
+- User behavior already accepts real-time transfers.
+- Smaller financial institutions may be more open to partnerships.
+- The pain point around delayed commission access feels easier to explain.
+- Switzerland is wealthy and credible, but likely harder as a first market unless you already have strong local regulatory and banking access.
+
+My default view: start in `Brazil`, not Switzerland, unless your Swiss network includes real bank/compliance operators.
+
+Why cards are smart
+
+- A card makes the balance useful without forcing bank withdrawal.
+- That increases retention of funds in the system.
+- It also creates interchange revenue.
+- It changes the product from “payout tool” to “financial home for commission earners.”
+
+But cards should probably be phase 2, not day 1.
+
+Recommended rollout
+
+1. `Phase 1`: instant commission ledger + PIX payout
+- receive merchant payment
+- calculate split
+- show employee available commission immediately
+- let employee cash out instantly via PIX
+- let employer settle on schedule
+
+2. `Phase 2`: stored balance
+- employee can keep balance in app
+- employer can hold operating balance for future payouts
+- basic wallet behavior
+
+3. `Phase 3`: card issuance
+- prepaid/debit card tied to stored balance
+- spend directly from commission account
+- optional employer expense or draw features later
+
+4. `Phase 4`: treasury economics
+- negotiated bank yield/float arrangements
+- maybe employer incentives for keeping balances
+- maybe employee rewards instead of explicit interest
+
+Better incentive framing
+
+Instead of saying “leave money with us so we earn interest,” design the product so users naturally keep balances because it is useful:
+
+- instant commission availability
+- free PIX transfers
+- card spend with cashback/rewards
+- early access to future commissions
+- bill pay / payroll-like convenience
+- employer bonuses for keeping payout reserves on platform
+
+That is commercially cleaner and safer to message.
+
+Core risks you should think through now
+
+- **Regulatory boundary**: are you software, payment institution, wallet, or something deposit-like?
+- **Fund timing**: when is money truly available vs still reversible?
+- **Chargebacks/refunds**: what happens if you already paid the employee?
+- **Labor law**: are instant commissions legally “earned wages,” “advances,” or something else?
+- **Partnership dependence**: your bank/program manager/card issuer can become a bottleneck.
+- **Unit economics**: instant payouts and card programs only work if fees, fraud, and support stay under control.
+
+My practical recommendation
+
+- Build the company narrative around `instant commission access infrastructure for employers and sales teams`.
+- Start with `Brazil`.
+- Use `PIX` as the hero feature.
+- Do not make “we profit from holding your cash” the public core story.
+- Structure the first version with a licensed financial partner holding funds.
+- Add cards only after the payout/ledger engine works reliably.
+
+A clean positioning statement
+
+- “We help companies collect payments and give sales teams instant access to earned commissions, with employer and employee balances managed through regulated financial partners.”
+
+If you want, I can next do one of these:
+1. turn this into a proper startup thesis and business model
+2. map the exact money flow and partner stack for a Brazil-first launch
+3. compare Brazil vs Switzerland in a founder-style decision memo
+
+---
+
+## User
+
+One practice that is quite common place in Brazil, that this company could potentially reduce, but probably not eliminate is what they call "vales", which are essentailly advances on their paycheck. I think there's good potential in also making it a feature in the business, letting employees borrow against their paycheck for a small fee/interest.
+
+---
+
+## Assistant (Plan · gpt-5.4 · 19.7s)
+
+That can be a strong feature, but it splits into two very different products:
+
+- `Earned wage access` — employees withdraw commission/pay already earned but not yet settled.
+- `Consumer credit` — employees borrow against expected future paycheck/commission.
+
+Those look similar in the app, but operationally they are very different.
+
+My recommendation
+
+- Start with `earned commission access`, not lending.
+- Treat it as “access to already-earned money” whenever possible.
+- Only explore true advances/credit later, once you have repayment data and employer integrations.
+
+Why this matters
+
+- `Earned access` is easier to explain: “you already earned it, we just make it available sooner.”
+- `Lending` creates heavier risk around underwriting, defaults, collections, regulation, and reputation.
+- In Brazil, a product that feels like replacing `vales` is attractive, but you do not want to become just another salary-advance lender.
+
+Best product framing
+
+- Employee makes a sale.
+- Payment is received or sufficiently authorized.
+- Your engine calculates commission instantly.
+- A safe portion becomes `available now`.
+- Employee can:
+  - withdraw via `PIX`
+  - spend via card
+  - keep balance in wallet
+- For amounts not yet fully settled, you can show:
+  - `available now`
+  - `pending settlement`
+  - `future estimated commissions`
+
+That lets you reduce `vales` without promising money too early.
+
+Rollout path
+
+1. `Phase 1: Early access to earned commissions`
+- no true loan
+- only release funds tied to clear sales/payment events
+- set conservative availability rules
+
+2. `Phase 2: Employer-backed advances`
+- employer opts in
+- employer agrees payroll deduction / settlement logic
+- advance limits based on verified earnings history
+
+3. `Phase 3: Risk-based credit`
+- only if economics and regulation make sense
+- requires underwriting, loss reserves, collections, disclosures
+
+Key design choice
+
+- Use `employer-backed advance` before `standalone consumer lending`.
+- If the employer contract helps recover advances from payroll/commissions, risk drops a lot.
+- That keeps the product closer to B2B2C infrastructure than pure retail credit.
+
+Big risks to solve
+
+- **Settlement risk**: what if customer payment reverses after employee got paid?
+- **Commission disputes**: what if employer later changes the commission amount?
+- **Legal classification**: earned wage access vs credit product
+- **Collections**: what happens if employee leaves the company?
+- **Abuse**: employees repeatedly pulling advances before reversals/refunds are known
+
+Practical guardrails
+
+- Only advance against `verified and rule-locked` commissions
+- Keep a reserve/holdback for refunds and chargebacks
+- Cap instant access to a percentage, not 100%, at first
+- Require employer integration and approval
+- Price it as a transparent convenience fee, not compounding debt
+- Avoid language that makes it sound like payday lending
+
+Strong positioning
+
+- “We help companies eliminate informal paycheck advances by giving employees controlled, instant access to earned commissions.”
+
+What I’d plan next
+
+- Define three balance states: `earned`, `available`, `settled`
+- Make `PIX instant cash-out` the core Brazil feature
+- Keep wallet/cards as retention tools
+- Defer true lending until you have data on repayment, reversals, and employer behavior
+
+If you want, I can next do one of these:
+1. draft a Brazil-first product roadmap including this feature
+2. map the risk rules for `earned access` vs `advance`
+3. write a founder memo on why this should start as EWA, not lending
+
+---
+
+## User
+
+Another part that I think can be valuable to companies is the possibility of giving them information on the performance of sales staff through amount of commissions, projections, some other forms of telemetry, etc
+
+---
+
+## Assistant (Plan · claude-opus-4.6 · 28.4s)
+
+That's a natural extension and it gives the product a second value proposition beyond money movement: `sales intelligence powered by real transaction data`.
+
+Why this is strong
+
+- You already have the data because payments flow through your system.
+- Most commission tracking today lives in spreadsheets or disconnected CRMs.
+- Employers currently have to reconstruct sales performance from multiple sources.
+- Your platform sees the actual money, so your data is inherently more trustworthy than self-reported CRM entries.
+
+What you can offer
+
+**Real-time dashboards for employers**
+
+- Total commissions paid per employee, team, region, period
+- Revenue per salesperson
+- Average deal size and frequency
+- Commission cost as percentage of revenue
+- Top performers vs underperformers
+- Trends over time (weekly, monthly, quarterly)
+
+**Projections and forecasting**
+
+- Projected commission liability for the month based on current pace
+- Expected payout amounts before settlement
+- Seasonal patterns and trend analysis
+- Cash flow forecasting for the employer (how much they need in the system to cover upcoming payouts)
+
+**Employee-facing insights**
+
+- "You've earned X this month, Y this quarter"
+- Progress toward targets or tiers
+- Comparison to personal history
+- Estimated next payout
+
+**Alerts and anomalies**
+
+- Sudden drop in an employee's sales
+- Unusually high refund/chargeback rate for a salesperson
+- Commission costs trending above budget
+- Employees approaching advance limits
+
+**Operational telemetry**
+
+- Time from sale to commission availability
+- Payout speed and method distribution
+- Cash-out frequency per employee
+- Balance retention rates
+
+Why this matters strategically
+
+- Analytics transforms your product from `payment plumbing` into `business intelligence`.
+- It makes the employer the buyer, not just the payer.
+- It increases switching costs — once employers rely on your dashboards, leaving is harder.
+- It opens a path to premium/enterprise pricing tiers.
+
+Important nuance
+
+- The analytics should come from data you already collect through payment processing.
+- Do not try to become a full CRM or HR platform.
+- Stay focused on `money-linked sales performance`, not general employee management.
+
+How it fits in the product
+
+| Layer | What it does |
+|---|---|
+| Payment engine | Collect, split, settle |
+| Ledger / wallet | Track balances, enable instant access |
+| Cards / PIX | Make money usable |
+| Analytics | Make the data useful to employers |
+
+The analytics layer is essentially free to build incrementally because the underlying data already exists in your ledger. It's a reporting and visualization problem, not a data collection problem.
+
+Pricing angle
+
+- Basic analytics included in the platform fee
+- Advanced analytics (projections, anomaly detection, custom reports, API access) as a premium tier
+- That gives you a SaaS-like revenue stream alongside transaction-based revenue
+
+Recommended approach
+
+- Ship basic dashboards early — even simple charts increase perceived value significantly.
+- Add projections and alerts as you accumulate enough historical data.
+- Let employer feedback drive which analytics matter most.
+- Do not over-invest in analytics before the core payment/payout engine works.
+
+At this point, the full product vision is becoming clear:
+
+1. **Payment collection** — employer receives customer payments through you
+2. **Commission engine** — rules-based split calculation
+3. **Instant access** — employees see and use earned commissions immediately
+4. **Wallet + cards + PIX** — money stays in system, usable without withdrawal
+5. **Earned wage access / advances** — reduce informal "vales"
+6. **Sales analytics** — employer gets performance intelligence from real payment data
+7. **Float economics** — platform earns from balances, interchange, fees
+
+That is a coherent, defensible fintech product.
+
+Do you want me to now pull all of this together into one of these:
+1. A structured startup thesis / business model document
+2. A phased product roadmap with priorities
+3. A technical architecture plan for building the MVP
+
+---
+
+## User
+
+1
+
+---
+
+## Assistant (Plan · claude-opus-4.6 · 59.7s)
+
+
+
+Here is the structured startup thesis and business model.
+
+---
+
+# Startup Thesis: Instant Commission Infrastructure
+
+## One-liner
+
+A B2B2C fintech platform that sits between employers and sales staff, processing customer payments, instantly calculating and distributing commissions, and providing financial accounts with cards and instant transfers — while earning from float, interchange, fees, and SaaS.
+
+---
+
+## Problem
+
+**For employers:**
+- Commission calculation is manual, error-prone, and delayed.
+- Payroll cycles create lag between a sale and the salesperson getting paid.
+- Informal advance practices ("vales") are unstructured, create accounting friction, and expose the company to risk.
+- Visibility into sales performance is fragmented across CRM, payroll, and spreadsheets.
+
+**For employees (sales staff):**
+- Commissions arrive days or weeks after the sale.
+- Accessing earned money early requires asking for informal advances.
+- No single place to see earnings, track performance, or manage commission income.
+
+---
+
+## Solution
+
+A platform that:
+
+1. Receives customer payments on behalf of the employer.
+2. Instantly calculates the commission split using employer-defined rules.
+3. Credits the employee's account with earned commission in real time.
+4. Lets employees spend (card), transfer (PIX), or hold their balance.
+5. Settles the employer's share on their preferred schedule.
+6. Provides both sides with analytics, projections, and reporting.
+
+---
+
+## How money flows
+
+```
+Customer pays R$1,000
+        │
+        ▼
+┌─────────────────────────┐
+│  Partner bank / FBO     │  ← Regulated entity holds funds
+│  account receives funds │
+└─────────────────────────┘
+        │
+        ▼
+┌─────────────────────────┐
+│  Platform ledger splits  │
+│  Employee: R$200         │
+│  Employer: R$800         │
+│  Platform fee: deducted  │
+└─────────────────────────┘
+        │                │
+        ▼                ▼
+   Employee acct    Employer acct
+   (available now)  (settles on schedule)
+        │
+        ├── PIX cash-out (instant)
+        ├── Card spend (interchange)
+        └── Hold balance (float)
+```
+
+---
+
+## Revenue model
+
+| Stream | Description | Phase |
+|---|---|---|
+| **Transaction fee** | % or flat fee on each payment processed | 1 |
+| **PIX/transfer fee** | Small fee per cash-out (or free with limits) | 1 |
+| **Float income** | Interest/yield on balances held with bank partner | 2 |
+| **Card interchange** | Revenue share on card transactions | 3 |
+| **Advance fee** | Flat fee for early access to not-yet-settled commissions | 2 |
+| **SaaS tier** | Premium analytics, custom rules, API access, multi-entity | 2 |
+
+The strongest early revenue is likely `transaction fee + advance fee`. Float and interchange grow with balance retention and card adoption.
+
+---
+
+## Target market (Brazil first)
+
+**Initial segment:**
+- Small and mid-size companies with commission-based sales teams (5–200 salespeople).
+- Industries: retail, insurance, real estate, auto dealers, door-to-door sales, telecoms resellers.
+
+**Why Brazil:**
+- PIX makes instant transfers a baseline expectation.
+- "Vales" culture creates a clear pain point to solve.
+- Smaller banks (e.g., Sicredi, cooperatives) are actively seeking partnerships to grow.
+- Large underbanked/underserved workforce in commission-based roles.
+- Regulatory environment has a clear framework for payment institutions.
+
+**Why not Switzerland first:**
+- Harder to find flexible bank partners without existing scale.
+- Smaller addressable market for commission-heavy sales forces.
+- Higher regulatory and operational costs to start.
+- Consider Switzerland as a second market or for a different product angle (e.g., wealth/treasury for employers).
+
+---
+
+## Product roadmap
+
+### Phase 1 — Core (months 1–4)
+- Employer onboarding and configuration
+- Employee onboarding (KYC via partner)
+- Payment collection (PIX, boleto, card via payment processor)
+- Commission rules engine (percentage, tiered, custom)
+- Internal double-entry ledger
+- Employee balance: `earned` / `pending` / `settled`
+- PIX instant cash-out for employees
+- Employer settlement on schedule
+- Basic employer dashboard (commissions paid, per-employee breakdown)
+- Basic employee dashboard (earnings, available balance, cash-out history)
+
+### Phase 2 — Retention + advances (months 4–7)
+- Employee wallet with stored balance
+- Earned wage access: early access to earned-but-unsettled commissions
+- Employer-backed advance feature (payroll-deductible)
+- Reserve/holdback logic for refunds and chargebacks
+- Employer analytics: performance trends, projections, commission cost ratios
+- Employee insights: earnings pace, personal trends
+- Alerts: anomalies, budget thresholds, refund spikes
+- Premium SaaS tier for analytics
+
+### Phase 3 — Cards + scale (months 7–12)
+- Prepaid/debit card issuance (via card program manager)
+- Card spend from commission balance
+- Interchange revenue
+- Float optimization with bank partner
+- Multi-entity / franchise support
+- API for employer system integrations (ERP, CRM, POS)
+- Employer cash flow forecasting
+
+### Phase 4 — Expansion (12+ months)
+- Risk-based credit / true advances (if regulation allows and data supports)
+- Employee rewards / cashback programs
+- Second market entry (Switzerland or other LatAm)
+- Employer expense management features
+- White-label or embedded finance partnerships
+
+---
+
+## Key partnerships needed
+
+| Partner type | Role | Examples (Brazil) |
+|---|---|---|
+| **Sponsor bank / BaaS** | Hold funds, compliance, account infrastructure | Sicredi, QI Tech, Dock, Celcoin |
+| **Payment processor** | Accept PIX, boleto, cards | Pagar.me, Stripe BR, Adyen |
+| **Card issuer / program manager** | Issue prepaid/debit cards | Dock, Pomelo, Swap Financial |
+| **KYC/KYB provider** | Identity verification | idwall, BigDataCorp |
+| **Legal / regulatory counsel** | Payment institution licensing, labor law | Local fintech law firm |
+
+---
+
+## Regulatory considerations (Brazil)
+
+- **Payment institution license**: likely needed if holding client funds or issuing payment instruments. Can potentially operate under a bank partner's license initially.
+- **Central Bank oversight**: PIX participation rules, reporting obligations.
+- **Labor law**: commission classification, payroll deduction rules for advances, tax withholding obligations.
+- **Consumer protection (CDC)**: transparency on fees, right to information.
+- **LGPD**: data protection for employee financial data.
+- Early recommendation: operate under a licensed partner's umbrella, pursue your own license when volume justifies it.
+
+---
+
+## Core risks
+
+| Risk | Mitigation |
+|---|---|
+| Settlement reversal after payout | Holdback reserves, conservative availability windows |
+| Commission disputes | Employer-signed rules, audit trail, dispute workflow |
+| Employee default on advances | Employer-backed payroll deduction, conservative limits |
+| Bank partner dependency | Contractual protections, plan for multi-partner |
+| Regulatory classification | Legal counsel from day 1, operate under licensed partner |
+| Fraud / identity | KYC at onboarding, transaction monitoring |
+| Low balance retention | Card + UX incentives to keep funds in-platform |
+
+---
+
+## Unit economics sketch (per employer, per month)
+
+Assuming: 20 employees, R$500 avg commission, 80% cash-out rate
+
+| Item | Value |
+|---|---|
+| Total commissions processed | R$10,000 |
+| Transaction fee (2%) | R$200 |
+| Advance fees (10% of employees, R$5 each) | R$10 |
+| Float income (20% retained, ~1% monthly yield) | R$20 |
+| Interchange (Phase 3, est.) | R$15 |
+| **Monthly revenue per employer** | **~R$245** |
+| Target: 200 employers | **~R$49,000/mo** |
+
+These are rough and conservative. The real leverage comes from larger employers and higher retention rates.
+
+---
+
+## Competitive positioning
+
+- Not a payroll company. Not a bank. Not a CRM.
+- "Commission infrastructure" — the financial operating system between employer payments and sales team earnings.
+- Closest comparisons internationally: `Earned wage access` (DailyPay, Caju, Xerpay) crossed with `payment splitting` (Stripe Connect model) crossed with `sales performance analytics`.
+- Differentiation: you process the actual payment, so you have the most trustworthy data and the fastest path to commission availability.
+
+---
+
+## Founding team needs
+
+- **Product / business lead**: understands the employer sales pain, can sell to mid-market companies.
+- **Engineering lead**: can build ledger, payment integrations, real-time systems.
+- **Fintech / regulatory lead**: understands Brazilian payment institution rules, bank partnerships, compliance.
+- Ideally, at least one founder with direct relationships at potential bank partners.
+
+---
+
+That covers the thesis, model, market, roadmap, risks, and economics. Want me to go deeper on any section, or move toward technical architecture or a specific partnership strategy?
+
+---
+