StackPack is a community for the people running the work - marketing leads, agency owners, automation builders, and founders. The folks shipping campaigns, GoHighLevel funnels, n8n workflows, MCP servers, and the systems that hold them together. The chat is open, and an AI coach works the room beside you.
No course library. No motivational keynotes. Members compare playbooks, swap audits, review each other's code, and break problems open in live rooms - then post what they learned so the next person doesn't repeat the same wall.
The mix is the point. Marketers fix code with developers. Operators learn what to automate from agency owners. Founders get their stack audited by people who run the same one at scale.
The community is organized around the work people actually do. Not "AI" as a topic. The specific systems, the specific tools, the specific problems that surface at 4pm on a Thursday.
Campaign workflow design, email automation, lead nurturing, marketing-tech integration, attribution reporting. The plumbing behind every campaign that doesn't fall over.
Deep GoHighLevel - custom fields, workflows, snapshots, API. Pipeline design that survives sales handoff. Onboarding systems clients actually finish.
MCP server development, Claude Code workflows, agent design, prompt caching. When to use a model, when to use a tool, when to skip the whole thing.
n8n, Make, Zapier - the right tool for the right job, and when to drop them for a script. Webhook patterns. Error handling that survives a 2am outage.
Operations automation, financial tracking, project management infrastructure, documentation that doesn't die. The connective tissue between people, tools, and money - written by people running 6-figure books and 50-person teams.
Real shape, real channels. Members post problems, audits, screenshots, and code. Other members reply with what worked for them. Office hours twice a week where you bring one thing and leave with a plan.
Need eyes on a GHL workflow that's firing twice on every form submit. Tag-based trigger plus a workflow trigger - I think they're stacking. Screenshot in thread. Anyone seen this pattern before?
Sharing the creative test framework I rebuilt last quarter. 4 hooks x 3 angles x 2 formats - structured naming so the report writes itself. Template in Drive. Tear it apart.
Cut our token bill 62% this month with prompt caching on the long system prompt. Caching strategy doc + the exact retry logic for cache misses. Posting the cache-hit graph in thread.
Looking for a tear-down of my pricing page. Three plans, no clear winner, churn at 14 days. 5 minutes of your time gets you the same back on yours.
Channels are split by what you're working on, not by skill level. Beginners and senior people post in the same room because the questions are the same - they're just at different scale.
Members ship community projects together. Some are open-source, some are private playbooks. You can lead one, contribute, or just pull the templates.
Curated n8n + Make + Zapier templates for lead capture, lifecycle, attribution, and reporting. Annotated with the gotcha each one solved.
Pre-built GoHighLevel snapshots, custom-field schemas, and API helpers. Reusable across client builds - cuts onboarding from a week to an afternoon.
Working agents for sales triage, content QA, ad-copy variants, and audit reporting. MCP-first design. Open code, real cost numbers.
The tooling behind StackPack itself - member onboarding, project routing, office-hours queue. Members build it, members use it, members get the code.
SOPs and runbooks that survive contact with reality. Markdown-first, versioned, AI-ingestable. Templates plus the rituals around them.
Google + Meta + YouTube structures that work in 2026. Account hierarchies, creative testing frameworks, attribution stacks. From operators running 5-6 figure monthly spend.
Members are deep in these. Not "we'll teach you Zapier" - we'll show you what to drop Zapier for, when, and why.
'/%3E%3Cpath d='M8 11l8-4 8 4-8 4z' fill='white' opacity='0.96'/%3E%3Cpath d='M8 16l8 4 8-4' stroke='white' stroke-width='1.6' fill='none' stroke-linejoin='round' opacity='0.78'/%3E%3Cpath d='M8 21l8 4 8-4' stroke='white' stroke-width='1.6' fill='none' stroke-linejoin='round' opacity='0.5'/%3E%3C/svg%3E)
Skool
Claude
n8n
Zapier
Make
Google Ads
Meta Ads
GitHub
Supabase
Cloudflare
Notion
StripeEvery "community" we joined had the same shape. One person at the top. A thousand lurkers. A few diehards in the comments. Content from 2022 still pinned at the top of the dashboard.
That's not a community. That's an audience.
StackPack is built around members who already do this work. Marketing leads running paid spend. Agency owners managing teams. Developers shipping MCP servers. Founders launching SaaS. The "we" you'll read across this site is honest - the answers come from members as often as from us, sometimes more.
We keep it small enough that you can actually know people. We mark content with dates so nothing rots in pinned messages. We run office hours that aren't theater - bring one thing, leave with a plan. And we remove anyone who's here to pitch instead of to build.
If that sounds like what you've been missing, the door's open.
Four build from Cebu, three from Florida, and one each from Crete, Newark and the Philippines. Every dot is a place a member has said out loud, and nobody's name is on it. Drag it, or leave it turning. The team answers across three regions now - USA, EU and Asia - based out of Miami, Warsaw and Bangkok.
One dot per place a member named, sized by how many share it
Few communities have this. Ours answers in public, builds with you, and keeps the guides current. Ask for an asset, a marketing plan, an automation or an agent and it drafts the thing with you. It works under the same rules as everyone else, and a person approves anything it cannot do alone.
Tag it in any channel and the answer comes back in a thread named after your question, so the channel stays clean. It points at the channel, the post or the guide you need, and tells you when that guide was last updated.
Ask for a landing page, a marketing plan, an automation or an agent. It drafts the asset, the copy and the flow with you, then hands you something you can run.
Send a project, a link or a screenshot. It writes the post, takes the picture, and puts it in #showcase with your name on it.
A landing page, a prompt, a workflow, an offer. You get what to fix first, in the order you would fix it, before you spend an afternoon on the wrong thing.
The room runs on a schedule now. Live sessions every month, new courses and tutorials between them, and interviews with members who are further down the same road.
One live session a week. A tool, a teardown or a build, walked through end to end.
Hands on. Bring a workflow, a campaign or a page, and leave with it working.
A smaller room for a bigger problem. Members bring one thing that is stuck, and the group works it open.
Once a year the whole pack gets in one place, for the conversations that only happen in person.
Between sessions the team answers questions daily, and new courses, tutorials and member interviews land every month.
Anyone you bring in earns you 40% of their subscription, every month they stay. Paid directly to you, no questions asked.
Members get their referral link inside the community. Share it, and the commission is yours for as long as that person is a member.
Join and ask for your linkSix answers, about a minute. It goes to the team, and if it is a fit you get an email with your invite. Skool is separate: you can subscribe there whether or not you are in the Discord.
Start free on Facebook. Move to Skool when you want the rooms, the workshops, and the office hours. The Discord chat comes with membership, and yearly adds 1-on-1 time with the team.
Facebook group. Public conversations.
Full Skool community access. Cancel anytime.
Save $194 vs monthly. Includes 1-on-1 time with the team.
Solo devs, in-house engineers, fractional CTOs. Want code review, MCP help, integration patterns.
Paid ads, lifecycle, content. Want to add the technical layer underneath without becoming a developer.
Running ops or teams. Want SOPs that get followed, automation that doesn't break, and peers who've solved it.
Building SaaS or productized services. Want critique, collaborators, and the next 3 doors opened for you.
No "welcome video and good luck." Here's the actual rhythm new members fall into.
Post what you're working on, what you're stuck on, what you're good at. Members reply. You get tagged with the skill labels that route questions to you - and you to others.
If you want, we route you to an active community build that fits your skills and goals. If you'd rather lurk for a week, fine - the door stays open.
Live session, Tuesday or Friday. You bring one specific thing - a broken Zap, a campaign that's underperforming, a code review, an offer that's not converting. You leave with an answer.
Whatever you've built, shipped, or learned in 30 days - post it. Get reactions, critiques, and the next door that opens because of it. The compounding starts here.
The Skool space has the full member list, the channels, the workshop library, and the active project threads. Look around before you pay.
Open the StackPack communityLooking for free tutorials instead? Try the arc-web GitHub for open-source tooling. StackPack is for the people working past tutorials.