Nex Sector Tenant Pattern

The problem

Manually onboarding new clients into a multi-tenant SaaS involves fragmented tasks across database configuration, asset storage, and campaign setup. Developers often waste days repeating boilerplate work to provision tenant records, scoring logic, and mail templates.

What it does

• Generates SQL tenant records and sectors_json configurations including NACE codes and regional filters.
• Automates branding asset deployment to MinIO storage for tenant-specific UI rendering.
• Produces sector-specific cold-mail sequences and customized AI-scoring prompts based on client USPs.
• Configures DNS and email delivery settings via Resend for tenant-owned domains.
• Provides a validated onboarding checklist and smoke test protocol to move from setup to live in 90 minutes.

Frameworks & tools

Built for stacks using FastAPI, PostgreSQL, MinIO, and Resend. Integrates with KBO data pipelines and lead-scoring rubrics.

Why this beats prompting it yourself

This tool enforces the strict architectural boundaries of the Nex Prospect model, ensuring configuration data stays in the DB and assets stay in storage. It prevents manual errors in NACE code mapping and scoring weight calibration that lead to poor lead quality.

Use cases

• Onboarding a new furniture retail client requiring horeca lead generation.
• Setting up a specialized HVAC tenant with distinct scoring weights for renovation projects.
• Pivoting an existing tenant from one sector focus to another without breaking the pipeline.
• Provisioning the Nth tenant using a standardized, production-tested playbook.

Known limitations

Assumes an existing deployment of nex-prospect-blueprint. Does not support enterprise-level custom feature development outside the standard outreach flow.