Files
rwo-docs/AGENTS.md
2026-04-09 16:13:59 +01:00

90 lines
4.0 KiB
Markdown

# 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
- Keep the core product geography-agnostic.
- Use a regulated financial partner for custody, payouts, card issuance, and compliance.
- Lead with fast access to earned commissions over the relevant local payout rail.
- 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.
- Keep market-specific assumptions in `docs/countries/`.
## 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/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/prototype-plan.md` - prototype scope, flows, and build sequence
- `docs/ideas-for-review.md` - review file for ideas not yet integrated into the core docs
- `docs/countries/brazil.md` - Brazil-specific thesis and go-to-market notes in pt-BR
- `docs/countries/switzerland.md` - Switzerland-specific thesis and go-to-market notes
## Language conventions
- Write in English by default.
- Country-specific docs may use local language where helpful.
- Keep fintech terminology consistent: `commission ledger`, `earned commission access`, `employer-backed advance`, `stored balance`, `instant payout rail`.
## 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.
- Country-specific differences should be layered on top of the same core ledger and workflow model.
## Reference competitors and adjacent players
Use this current market framing unless new evidence clearly changes it:
- `DailyPay`
- `Branch`
- `PayQuicker`
- `Hyperwallet`
- `CaptivateIQ`
Country-specific employer-finance apps, PSPs, BaaS providers, and issuers should be documented in the relevant country notes rather than the core docs.
## Prioritization guidance for future agents
- Prioritize docs and plans that sharpen the geography-agnostic core product.
- Keep country-level launch assumptions, partners, and regulation in `docs/countries/`.
- 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, Switzerland, and future launch structures
- partner comparison across local banking, payment processing, and card issuance stacks
- pricing design for employers versus workers
- reserve rules for refunds, disputes, and chargebacks
- target vertical selection and design-partner outreach strategy