Build an Affiliate Lead Network Platform (CPL/CPA) for LATAM — Tracking, Offers, Leads, Admin & Payments
Budget: $15 – $25 USD
We are looking to build a web platform similar to an affiliate network, focused 100% on lead generation campaigns (CPL/CPA), targeting LATAM (starting with Chile). The system must include an Affiliate Portal and a full Admin Panel, with tracking links (streams), lead capture (hosted forms + API), lead status pipeline, statistics/reporting, and a payments module (wallet/hold/payout requests).
Core requirements (MVP)
Authentication + profiles + manual affiliate approval (RBAC)
Admin: create/manage offers (payout, GEO, rules, caps, hold), landings, creatives/resources
Affiliate: offers list/detail, request access, create streams, tracking links, stats + exports
Tracking: click logging + stream attribution (sub1..sub5 + UTMs), safe redirects, tracking domains
Leads: hosted web form + Lead Intake API, dedup rules, status pipeline (New/Valid/In Process/Confirmed/Declined/Invalid/Trash), full audit/history
Postbacks/webhooks on status changes + logs
Payments: internal wallet (multi-currency CLP/USD optional USDT), hold balance, payout requests, admin approval, payout history
Tech preferences
Frontend: React + Next.js (or equivalent)
Backend: Node/NestJS or Django
DB: PostgreSQL
Queue/Cache: Redis
Dockerized deployment + staging & production
Security best practices: HTTPS, rate limiting, RBAC, audit logs, backups (2FA recommended for admin)
Deliverables / milestones
Architecture + DB schema + API plan
Auth/RBAC + Admin base + offer management
Tracking + Streams + click logging
Lead intake + statuses + exports
Payments (wallet/hold/payout flow)
QA + docs + deployment
Screening questions
Have you built tracking/affiliate platforms or other high-concurrency systems? Share examples.
How would you separate the tracking service from the admin/portal API?
How would you design a ledger to avoid balance inconsistencies?
What anti-fraud measures would you implement for MVP?
(Full spec is provided in the attached PDF.)
Core requirements (MVP)
Authentication + profiles + manual affiliate approval (RBAC)
Admin: create/manage offers (payout, GEO, rules, caps, hold), landings, creatives/resources
Affiliate: offers list/detail, request access, create streams, tracking links, stats + exports
Tracking: click logging + stream attribution (sub1..sub5 + UTMs), safe redirects, tracking domains
Leads: hosted web form + Lead Intake API, dedup rules, status pipeline (New/Valid/In Process/Confirmed/Declined/Invalid/Trash), full audit/history
Postbacks/webhooks on status changes + logs
Payments: internal wallet (multi-currency CLP/USD optional USDT), hold balance, payout requests, admin approval, payout history
Tech preferences
Frontend: React + Next.js (or equivalent)
Backend: Node/NestJS or Django
DB: PostgreSQL
Queue/Cache: Redis
Dockerized deployment + staging & production
Security best practices: HTTPS, rate limiting, RBAC, audit logs, backups (2FA recommended for admin)
Deliverables / milestones
Architecture + DB schema + API plan
Auth/RBAC + Admin base + offer management
Tracking + Streams + click logging
Lead intake + statuses + exports
Payments (wallet/hold/payout flow)
QA + docs + deployment
Screening questions
Have you built tracking/affiliate platforms or other high-concurrency systems? Share examples.
How would you separate the tracking service from the admin/portal API?
How would you design a ledger to avoid balance inconsistencies?
What anti-fraud measures would you implement for MVP?
(Full spec is provided in the attached PDF.)