The build prompt for a B2B portal with dealer accounts, customer-specific price lists, account balances, order approvals and ERP integration.
Built for: Wholesalers, distributors and manufacturers
In a B2B portal, every customer sees different prices, payment terms and approval chains. Account balances, quote-to-order conversion and ERP sync call for a data model that's completely different from B2C e-commerce.
The prompt brings customer groups, price lists, minimum order rules, payment-term and credit-limit tracking and ERP webhooks together in a single architecture.
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for B2B Wholesale Portal:
Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan.
Write a flawless PRD. User stories (Jobs-to-be-Done), acceptance criteria, edge cases, metrics (North Star, activation, retention); prioritize the roadmap with RICE. Scope an MVP that ships in 7 days.
Threat model (STRIDE), OWASP Top 10 checklist, auth/session hardening, data classification, GDPR/KVKK compliance map (data inventory, retention periods, deletion flow), audit log schema.
Event tracking plan: North Star and supporting metrics, event/property dictionary, funnel and retention definitions, data warehouse schema, dashboard list, data quality tests.
Preloaded in step 2 of the Studio; change any of the 7 layers.
Every feature appears in the prompt as a "Spec + API + UI + Tests" line.
Sample idea: "A wholesale ordering portal for dealers with customer-specific pricing and on-account billing". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# B2B Wholesale Portal - MASTER BUILD PROMPT Stack: Next.js 16 (App Router), Hono + CF Workers Goal: A wholesale ordering portal for dealers with customer-specific pricing and on-account billing This prompt builds a full-stack B2B Wholesale Portal in 8 steps. Each step consumes the previous step's output. 4 experts' knowledge combined. Steps: 1. PRD & User Stories 2. Design System (Figma tokens) 3. DB Schema & API Contract 4. Auth & Billing Implementation 5. Core Features Build 6. AI Integration (RAG + Agents) 7. SEO/AEO & Analytics 8. Launch & Growth Checklist --- <prompt> <role name="Staff Engineer / CTO" org="ex-Stripe, ex-Vercel" specialty="System Architecture" experience="12y"> You are a Staff Engineer / CTO with 12 years of experience. Specialty: System Architecture. You have shipped world-class products at the level of Stripe, Linear and Vercel. </role> <context> Project: B2B Wholesale Portal - A wholesale ordering portal for dealers with customer-specific pricing and on-account billing Type: B2B Wholesale Portal Vision: Dealer approval, price list groups, minimum order quantities, payment-term and credit-limit checks, an order approval chain, e-invoicing and ERP sync (NetSuite / SAP Business One), and a sales rep dashboard. Target user: Wholesalers, distributors and manufacturers - Pain: - Budget: Competitors: USP: Monetization: Subscription (MRR), Commission % | Payments: Stripe Tech Stack: Next.js 16 (App Router), Hono + CF Workers, Supabase, Supabase Auth, Resend Features: RBAC + Permissions, Team Invite & Roles, Advanced CRUD + Bulk Ops, Audit Logs, Webhooks & Events, Analytics Charts, Notifications Center Compliance: KVKK/GDPR Lang: EN </context> <task> Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan. General: production quality, copy-paste ready level of detail. </task> <technical_architecture> - Frontend: Next.js 16 (App Router) - App Router, Server Components, partial prerendering - Backend: Hono + CF Workers - Edge runtime, RPC, zod validation - DB: Supabase - pgvector for semantic search, type-safe ORM, RLS policies - Auth: Supabase Auth - Passkeys first, org/team model - Search: - typo-tolerant, faceted - Realtime: Resend - presence, CRDT-ready Payment flow: Stripe -> Webhook -> Background job -> Entitlement update -> Audit log </technical_architecture> <feature_matrix> - [ ] RBAC + Permissions -> Spec + API + UI + Tests …
The prompt asks for a sync service that treats the ERP as the single source of truth, plus an idempotent webhook consumer.
The price list + customer group + quantity tier model comes ready in the data schema, and the CTO persona provides an example table structure.
Claude Code, Cursor, Windsurf, v0, Lovable, Bolt and ChatGPT. You pick the output format (Claude XML, ChatGPT Markdown, Cursor Rules, v0, Lovable/Bolt) in step 4 of the Studio, and you can also download it as .cursorrules or CLAUDE.md.
Yes. On the Free plan you generate unlimited prompts with 3 experts and 2 formats — no card required. 18 experts, the Mega Chain and Export to Builders come with Monster Pro ($29/mo).
A fast, SEO-ready storefront on Next.js + headless commerce: product catalog, cart, Stripe or Iyzico/PayTR checkout and search. Build prompt ready.
The build prompt for a multi-vendor marketplace with seller onboarding, commissions, split payments, order management and search.
The build prompt for D2C subscription e-commerce: monthly box plans, a preference quiz, delivery schedules and churn-reduction flows.
The build prompt for a social network app with feeds, follows, real-time notifications, moderation and content recommendations.
The build prompt for a creator platform with subscriptions, digital product sales, membership tiers and creator payouts.
The build prompt for a job board with job posting, application management, applicant tracking (ATS), employer packages and SEO-ready job pages.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.