Internal Proposal

Give Growth
Engineering Superpowers

A dedicated space in the monorepo where the growth team can build their own tools, automate their workflows, and ship Whop apps — all guided by AI, with enterprise-grade security.

The Problem
The growth team has ideas. Engineering is the bottleneck.
Every automation, dashboard, and internal tool goes through the engineering backlog. Meanwhile, Bear already built a production-quality Pipedrive skill on his own.

Slow feedback loops

Every tool request sits in the eng backlog. A simple Pipedrive integration takes weeks to prioritize, days to build.

🔒

Work doesn't compound

People build things in isolation — a script here, a spreadsheet there. Nobody else uses it. When someone leaves, the tool dies. Nothing compounds across the team.

📈

Context lives in people's heads

Whop product knowledge, sales playbooks, scoring rubrics — all tribal. Not accessible to AI agents or new hires.

The Solution
A growth/ folder in the monorepo. Powered by AI.
The growth team gets their own home base. Cursor + AI skills guide them through everything — from daily CRM workflows to building and deploying tools.
🛠

Build tools

Say "build me a tool" and the AI scaffolds it. Auth, styling, monitoring, mobile responsive — all pre-wired.

Automate workflows

Say "I want to automate this" and the AI builds a reusable skill. Granola sync, call scoring, lead scraping — anything.

🚀

Ship same day

Merge to main and it's live. Or whop growth deploy. Vercel handles the rest.

📚

Full context built in

Product knowledge, sales playbooks, integration guides — all loaded as docs so the AI has context.

How It Works
Same tools as engineering. Your own namespace.

The whop growth CLI

The growth team uses the same CLI as engineers — just scoped to their world. All the complexity is hidden behind simple commands.

Whether you type the command directly or tell Cursor "start my app," the same thing happens.

# First-time setup (once)
$ whop growth onboard

# Add a new tool
$ whop growth new-tool churn-dashboard
✓ Created app/tools/churn-dashboard/

# Develop locally
$ whop growth dev
✓ Running on localhost:3100

# Ship it
$ whop growth deploy
✓ Deployed to growth-tools.vercel.app

# Check health
$ whop growth check
✓ No errors in the last 24h.

AI Skills — Your Workflows, Automated

Skills are reusable playbooks that the AI follows. Bear already built one for Pipedrive that syncs Granola meeting notes to deals — with safety rails.

The growth-create-skill lets anyone build skills like this. Describe what you do manually, and the AI turns it into an automation the whole team can use.

# What the growth team types in Cursor:

"I want to automate my end-of-day sync.
Every evening I check Granola for meeting
notes, match them to Pipedrive deals, then
check Slack channels for updates."

# What the AI does:
✓ Built growth-daily-sync skill
✓ Fetches Granola notes (last 24h)
✓ Matches to Pipedrive deals
✓ Syncs Slack channel updates
✓ Posts TLDR summaries to each deal

# Now anyone on the team can use it:
"Run my daily sync"
✓ Synced 4 meetings, 3 Slack channels
Getting Started
One command. Ready in minutes.
Everyone uses Macs. One command installs everything, authenticates, and gets them ready to build.

Day one experience

Step 1: Install Cursor (download from cursor.com)

Step 2: Open the growth/ folder

Step 3: Run one command

Step 4: Start talking to the AI

No git knowledge needed. No terminal expertise. No engineering background. The AI handles everything. Changes auto-merge when CI passes.

# The only command they ever need to run:
$ whop growth onboard

✓ Installing Node.js via Homebrew...
✓ Installing pnpm...
✓ Installing Doppler CLI...
✓ Opening browser for Doppler login...
✓ Verified access to growth project
✓ Installing dependencies...

Welcome to Growth Engineering!
Open Cursor and start building.
Say "show me what tools we have"
or "I want to build something new"
Zero Git Knowledge Required
The AI handles git. Changes auto-merge.
The growth team has never used git. The AI creates branches, saves work, and submits changes. When CI passes, changes go live automatically. No engineer reviews needed.
📄

They describe

"Add a new question to the sales quiz about payment processing fees."

AI builds + ships

Creates a branch, makes the change, commits, pushes, opens a PR, 7 CI checks run, auto-merges, deploys to production.

They see

"Done. Your new quiz question is live."

What the Team Asked For
11 requests. All buildable.
Every request from the GTM tooling notes maps to either a skill or a tool that the growth team can build themselves.
WhoWhat they wantType
BearGranola meeting notes → Pipedrive with context + next stepsBuilt
CamAuto-score every call + daily feedback report to managersSkill
CamLead scraper from Trustpilot for coaching / services / ecomSkill
CamMutual connection finder — paste socials, find warm introsSkill
RobLead finder + one-click outreach (Pipedrive dedup, LinkedIn, Apollo sequence)Skill
IkeCRM analytics — AM performance, NRR drops, champion shoutoutsSkill
Ari & IkeGift sending agent — suggest + purchase via Ramp cardSkill
AriAI agent to answer creator questions in SlackTool
ABReal-time dashboards for churning accountsTool
DerekChange fees, checkout links, feature flags via plain textTool
SkylerThird Eye for ad-hoc product questionsWorks
"Lowkey everything is downfunnel from context. So any tools we are building need to have access to granola, pipedrive, slack, etc. With full context + kickass strategic skills file on how to sell, you can easily set killer next steps."
— Bear, Sales
Distribution
Everything lives at whop.com/growth
Every tool becomes an experience on the Growth Whop. One place to find everything. Dogfooding the platform.

One Whop. Every tool.

The Growth Whop at whop.com/growth is the hub. Each tool shows up as an experience in the sidebar — right alongside chat, forums, and courses.

Team members get a membership. Managers get the dashboard view. New hires get access on day one.

This is how your creators use Whop. Now the growth team does too.

◀ whop.com/growth sidebar

Sales Onboarding
Quizzes, practice calls, leaderboard

◆ Churn Dashboard
At-risk accounts, NRR tracking

◆ CRM Analytics
AM performance, pipeline health

◆ Creator AI Assistant
Answer creator questions instantly

◆ Lead Tools
Scraper, outreach, warm intros

─────────────────────
💬 Team Chat
📣 Announcements
Proof of Concept
Migrate the sales onboarding app first.
The existing sales training dashboard (quizzes, ElevenLabs practice calls, AI scoring, leaderboard) becomes the first experience on whop.com/growth.
📝

89 quiz questions

Product knowledge, compliance, contracts, competitive intel — all become reusable context docs in growth/docs/.

🎙

AI practice calls

ElevenLabs voice roleplay with 5-dimension Claude scoring. Pattern becomes a reusable template for future tools.

🏆

Leaderboard + feedback

Rep rankings, confidence checks, coaching reflections. The growth team can iterate on all of this without asking eng.

Rollout
Phased rollout. Pilot first.
Phase 1 — Infrastructure (next week)

Build the growth engineering layer

growth/ folder, app scaffold, 6 AI skills, whop growth CLI, Doppler setup, Cursor rules, CI pipeline, documentation. The foundation everything else builds on.

Phase 2 — Pilot

Onboard 2-4 power users

Start with a small group (TBD). Cursor licenses + Doppler access via Okta. Validate the onboarding flow, fix friction, gather feedback before the full rollout.

Phase 3 — Proof of Concept

Migrate the sales onboarding app

Kill the standalone repo. Rebuild as the first tool on whop.com/growth. Proves the template, secrets, monitoring, and deployment story end-to-end.

Phase 4 — Quick Wins

Skills the team builds themselves

Granola + Pipedrive daily sync (already built by Bear). Call auto-scoring + daily reports. CRM analytics for AM performance.

Phase 5 — Migrate Existing Tools

Consolidate what already exists

Alex Heiden and Rob's lead finding tools. Cam's gift finder. Everything that's currently scattered across personal scripts and spreadsheets moves into growth/ where the whole team can use it.

Phase 6 — Internal Apps

New tools for the business

Churning accounts dashboard (AB). Creator AI assistant (Ari). Lead finder + outreach pipeline (Rob). Gift sending agent (Ari, Ike).

Phase 7 — Full Rollout

16+ people onboarded

Team-wide adoption. Every growth team member has Cursor, Doppler access, and can build tools or automations from day one.

The Result
Growth becomes self-serve.
💡

Before

Growth has an idea. Files a ticket. Waits for engineering to prioritize, build, review, deploy. Takes weeks. Some requests never ship. Tools built in isolation die when people leave.

After

Growth has an idea. Opens Cursor. Describes what they want. AI builds it, deploys it, monitors it. Same day. No engineers in the loop. Every tool compounds — the whole team uses it.


Technical Details
Architecture
One app. Many tools. Zero overhead.
A single Next.js 16 project serves all tools as route groups. Multiple Whop app listings share one base_url with different view paths. Whop's iframe model isolates tools at the browser level.

Adding a tool = adding a folder

No new Vercel project. No new Doppler config. No CI wiring. Just create a folder under app/tools/ and start building.

Auth, styling, Sentry, shared components — configured once, used by every tool. One deployment, one CI pipeline, one config.

# Directory structure
growth/app/
├── app/layout.tsx ← shared auth, Sentry, WhopApp
├── app/tools/
├── sales-onboarding/[experienceId]/
├── churn-dashboard/[experienceId]/
├── crm-analytics/[experienceId]/
└── _template/ ← copy to add new
├── app/dashboard/[companyId]/ ← admin
├── lib/whop-sdk.ts ← shared
├── lib/schema.ts ← all DB tables
└── components/ ← shared UI
CI/CD Pipeline
7 checks. Zero can be bypassed.
Every PR runs through a bulletproof pipeline. Non-engineers cannot break the main app, leak secrets, or deploy broken code.

Belt and suspenders

Cursor rules prevent mistakes at the AI level. CI enforces them at the infrastructure level. Both must pass.

CODEOWNERS splits the world: changes to app/tools/ and docs/ auto-merge. Changes to core files (layout, SDK, config, schema) require eng review.

Vercel preview on every PR. Production deploy on merge to main.

# PR opened → growth-ci.yml runs:

✓ Scope guard — nothing outside growth/
✓ Secret scan — gitleaks on the diff
✓ Protected files — core infra untouched
✓ TypeScript — tsc --noEmit
✓ Schema — drizzle-kit check
✓ Build — pnpm build
✓ Import boundary — no external imports

# + Vercel preview deploy
✓ Preview: growth-tools-pr-42.vercel.app

All green + no CODEOWNERS block
→ auto-merge → production deploy
Security
Zero secrets on disk. By design.
No secret ever touches the filesystem. Doppler injects env vars in-memory at runtime. They vanish when the process ends.
🔒

Three layers of defense

A growth team member literally cannot leak a secret through git because no secret exists as a file.

Layer 1 — Doppler
Runtime Injection

doppler run injects API keys as process env vars. No .env.local files. Nothing on disk. Tokens vanish when the process ends.

Layer 2 — Vercel
Production Secrets

Doppler auto-syncs secrets to Vercel. Growth team never runs vercel env or handles production credentials.

Layer 3 — CI + AI
Defense in Depth

Cursor rules block AI from writing tokens to code. gitleaks scans every PR diff for xoxp-, sk-, api_token=. Both must pass.

Database
Shared PlanetScale + Drizzle ORM
Tools that need persistent data (quiz scores, call transcripts, dashboard metrics) share one database. Schema changes go through PlanetScale deploy requests.
🗂

One database, prefixed tables

All tools share growth-db on PlanetScale. Tables are prefixed per tool: so_quiz_attempts, cd_accounts. No conflicts.

🔧

Drizzle ORM

Same ORM as the sales dashboard. Schema defined in lib/schema.ts. Type-safe queries. The AI handles all schema changes.

Migration CI

drizzle-kit check validates every PR. PlanetScale deploy requests for production. No manual migration commands.

Mobile
All tools are mobile responsive. Enforced.
Whop apps load on iOS and Android in iframes. The app-development Cursor rule enforces responsive design — no fixed widths, Tailwind responsive prefixes, 375px minimum. The AI literally cannot build a non-responsive page.
Cursor Rules
4 rules. First line of defense.

guardrails.mdc

Never modify files outside growth/. Never use technical jargon. Never import from outside growth/app/. Never modify protected files without flagging for eng review. Ask before destructive actions.

secret-scanning.mdc

Never write secrets to files. Store tokens in Doppler via CLI. Scan for xoxp-, sk-, api_token=, Bearer, hex hashes before every commit. Refuse if found.

app-development.mdc

Every page must call checkAccess. All UI must be mobile responsive (375px min, no fixed widths >360px, flex/grid only). Tailwind only. Server components preferred. Prefix DB tables per tool.

git-workflow.mdc

Handle ALL git ops for the user. Create branches as growth/username/desc. Commit frequently. Push and create PRs. Resolve conflicts. Never ask user to run git. Use simple language.

Pre-Launch
Engineering setup checklist
One-time setup by engineering before the pilot group can start.