The Monolith Problem
Traditional SaaS charges one price for everything. Users pay for features they'll never use. They churn because the product feels bloated. And the company can't price-discriminate between a solopreneur and an enterprise.
The add-on model fixes all three problems at once.
How 0nCore Add-Ons Work
Every add-on follows the same architecture:
- Marketplace listing — name, price, capabilities, features list
- Config schema — form fields the user fills out (topics, tone, frequency, platforms)
- Execute function — AI workflow that runs with the user's config injected into the prompt
- Cron schedule — runs automatically (daily, weekly, manual)
That's it. The user buys it via Stripe. They configure it in the dashboard. The AI runs it on schedule. No code. No setup. No maintenance.
The Content Engine Example
The Content Engine add-on ($49/mo) generates blog posts and social media content daily:
- User sets: business description, topics, tone, platforms, frequency
- Every day, the cron fires → Groq AI generates content using those config values
- Blog post → published to CRM blog
- Social posts → scheduled to LinkedIn, Facebook, X, Instagram
- Email campaign → queued for the user's contact segments
The user did zero work after initial setup. Content appears automatically, on-brand, every day.
The Vendor Marketplace (Phase 6)
The long-term play: open the add-on system to third-party developers. 70/30 revenue split via Stripe Connect. Vendors build add-ons using the 0n SDK, submit for review, and earn revenue from every install. The profiles table already has is_vendor, vendor_status, and affiliate_stripe_account_id fields. The infrastructure is ready.