Multi-Site SaaS Platform with Marketplace, Attribution, Subscription, Payment & Settlement Logic

## Job Description We are looking for a senior full-stack developer or a small senior development team to build a complex web-based SaaS platform. The platform will connect multiple websites, partner services, product providers, subscription products, booking products, and sales channels into one central system. Customers may submit inquiries, bookings, orders, or subscription purchases from different websites or embedded widgets. The system must track where the customer came from, which product was sold, which partner fulfilled the order, which channel deserves attribution, and how commissions or revenue shares should be calculated. This is not a simple landing page, e-commerce store, or basic marketplace. We need a scalable platform with strong backend architecture, clean data modeling, event tracking, partner portals, admin dashboards, embedded widgets, subscription handling, payment integration, commission logic, settlement ledgers, clawback handling, audit logs, and role-based access control. Detailed product documents will be shared only after NDA. --- ## What We Are Building At a high level, the platform includes: * Central SaaS backend for managing offers, products, partners, customers, leads, orders, bookings, subscriptions, and settlements * Multi-site and multi-platform architecture * Product catalog that can support physical products, booking products, digital products, subscription products, usage-based products, and service packages * Embedded widget/plugin that can be installed on third-party or affiliated websites * Lead tracking and event tracking * Attribution logic for websites, partners, campaigns, sales agents, affiliates, creators, or distributors * Partner portal for service providers and vendors * Admin dashboard for internal operators * Subscription plan and entitlement management * Payment intent / invoice flow * Commission and revenue-share rules * Settlement ledger with pending, confirmed, payable, paid, canceled, refunded, and clawback statuses * Reporting dashboard * Audit logs and role-based access control The system should be designed as a flexible SaaS platform, not as a one-off website. --- ## Key Functional Areas ### 1. Core SaaS Platform The platform should manage: * Offers and product catalog * Customers and leads * Partners and vendors * Orders, bookings, and subscriptions * Payment status * Conversion events * Commission rules * Revenue-share rules * Settlement ledger * Customer benefits, cashback, coupons, or rewards * Clawbacks, cancellations, refunds, and reversals * Reports and dashboards ### 2. Product Catalog The product catalog should be flexible enough to support: * Physical products * Booking products * Service products * Digital products * Subscription products * Usage-based subscription products * Consultation products * Package products * Third-party partner products The system should not be hardcoded for one product category. ### 3. Embedded Widget / Plug-in We need an embeddable widget or script that can be installed on external websites. The widget should support: * Offer display * Lead capture forms * Booking/order forms * Source website tracking * Campaign tracking * Event tracking * API key or domain validation * Reporting per installed website ### 4. Attribution Engine The system should track and determine: * Which website generated the customer * Which campaign generated the lead * Which partner owns the product * Which platform sold the product * Which sales agent, affiliate, creator, or distributor should receive credit * How to handle duplicate or multi-touch attribution ### 5. Settlement Engine The settlement module should support: * Commission calculation * Fixed commission * Percentage commission * Margin-share commission * Hybrid commission * Pending settlement * Confirmed settlement * Payable settlement * Paid settlement * Clawback handling * Cancellation and refund adjustments * Monthly partner statements * Exportable reports ### 6. Subscription and Entitlement Management The system should support subscription products. Required concepts include: * Subscription plan * Subscription * Invoice * Payment intent * Payment event * Entitlement * Usage metering * Renewal * Cancellation * Upgrade/downgrade * Revenue sharing for subscription products ### 7. Partner Portal Partners should be able to: * Log in * View assigned leads or orders * Update customer/order status * Manage their own offers if permitted * View settlement reports * Download monthly statements * Respond to support or operational requests ### 8. Admin Dashboard Internal operators should be able to: * Manage customers and leads * Assign partners * Manage offers * Track order and booking status * Track payment status * Track conversion events * Confirm commissions * Review settlements * Process clawbacks * Manage partner accounts * Manage site/widget performance * View reports * Review audit logs --- ## Preferred Tech Stack We are open to recommendations, but the developer should be comfortable with a modern SaaS stack. Possible stack: * Frontend: React, Next.js, Vue, or similar * Backend: Node.js / NestJS, Django, FastAPI, Laravel, or similar * Database: PostgreSQL preferred * Queue / Jobs: Redis, BullMQ, Celery, or similar * Auth: Role-based access control, JWT/session auth, optional 2FA * Infrastructure: AWS, GCP, DigitalOcean, Docker, or similar * API: REST or GraphQL * Optional: Webhooks, event tracking, analytics pipeline, multi-tenant SaaS architecture Please suggest your preferred stack and explain why. --- ## Required Experience We strongly prefer candidates who have previously built similar systems. Relevant experience includes: * SaaS platforms * Marketplace platforms * Partner portals * Affiliate or CPA tracking systems * Commission settlement systems * Multi-vendor platforms * Booking platforms * Subscription SaaS platforms * CRM or lead management systems * Embedded widgets or third-party website integrations * Payment or invoice systems * Financial ledger or audit-log systems * Multi-tenant admin systems Please attach links to similar projects you have completed. We prefer concrete portfolio links, live URLs, GitHub repositories, demo videos, screenshots, or case studies. Applications without relevant examples may be considered lower priority. --- ## Important Requirements We need someone who can think through product logic, not just code screens. You should be able to: * Review PRDs and identify missing logic * Design scalable data models * Suggest better architecture when needed * Break large product requirements into milestones and sprint tasks * Build clean, maintainable code * Document APIs and database structures * Work with event-driven flows * Understand commission, settlement, and clawback logic * Implement secure role-based access control * Maintain audit logs for sensitive actions * Communicate clearly and regularly * Work under NDA * Keep all project information strictly confidential --- ## First Milestone The first milestone will likely include: 1. Sign NDA 2. Review product documents 3. Propose technical architecture 4. Define database structure and core entities 5. Review and refine API structure 6. Break the MVP into development milestones 7. Build initial admin dashboard, offer catalog, lead management, and basic event tracking 8. Prepare foundation for partner portal and embedded widget Please include in your proposal how you would approach the first 2–3 weeks. --- ## Expected Deliverables Expected deliverables may include: * Technical architecture document * Database ERD * API specification * Backend API * Admin dashboard * Partner portal * Event tracking module * Attribution module * Settlement ledger module * Subscription module * Embedded widget / plug-in * Reporting dashboard * Deployment setup * Basic technical documentation --- ## Engagement Type We are open to: * Hourly contract for a senior full-stack developer * Fixed-price milestone contract * Small senior team with one clear technical lead Please include your preferred working model. --- ## Proposal Instructions Please answer the following questions in your proposal: 1. Have you built a SaaS platform, marketplace, affiliate, CPA tracking, commission, booking, subscription, or settlement system before? Please describe briefly. 2. Please provide links to relevant portfolio projects, live products, GitHub repositories, demo videos, screenshots, or case studies. 3. What backend and frontend stack would you recommend for this project? 4. How would you design a system that tracks leads, conversions, attribution, commissions, subscriptions, settlements, and clawbacks? 5. Have you built embedded widgets or scripts that run on third-party websites? 6. Have you built partner portals or multi-vendor admin systems? 7. How do you usually structure a multi-tenant SaaS database? 8. Are you comfortable signing an NDA before seeing detailed documents? 9. Are you an individual developer or an agency? 10. What is your availability over the next 4–8 weeks? 11. What is your hourly rate or milestone estimate? 12. What information would you need from us before starting the architecture review? --- ## Confidentiality This project involves confidential product, business, and technical information. Detailed product documents will only be shared after NDA. Please do not apply if you cannot work under confidentiality obligations. Do not request confidential business details before NDA. We will first evaluate your experience, portfolio, technical approach, and communication style.