Nothing Held Back
Full-stack community platform built on Bubble for one of the most active marketing communities on the internet.
Alejah Sardiniola
available for work
Nothing Held Back Pro is a paid marketing community running at $500/month. Before we built the platform, the experience was fragmented — content in one place, community in another, coaching somewhere else, and everything stitched together with workarounds that couldn't scale.
We built one system to carry all of it. A Bubble application that functions less like a single product and more like an ecosystem — with distinct layers for content, community, coaching, AI, and commerce, all sharing one database and one permission architecture.
Eighteen months. One environment. Live.
The problem
NHB had built something real — a 60,000-member free community, a high-ticket paid tier, world-class coaches, weekly live training, and a content library that kept growing. But the infrastructure couldn't carry the vision.
Members were navigating between platforms to access what they paid for. Content wasn't searchable. Coaching had no workflow — just inboxes and manual coordination. The AI tools Alen wanted to give members didn't exist anywhere they could be plugged in without a full custom build.
The community was outgrowing every platform it was on.
It needed a home that was built for it — not borrowed from someone else's template.
The solution
We built the NHB platform on Bubble from the ground up — designed for scale, not just for launch.
The architecture started with the data model, not the canvas. Every data type, every relationship, every permission scenario mapped before a single page was built. Then the access control layer. Then the integrations. Then the visible surface.
The result is a platform where every feature — from the personalized dashboard to the AI assistant to the coaching intake workflow — is connected to the same data layer, controlled by the same permission system, and accessible from one login.
Members don't navigate between tools. They live inside one environment that knows who they are and what they have access to.
What was built
- Personalized Member Dashboard — a dynamic home base that surfaces relevant content, active calls, and community activity based on each member's tier and history. Not a generic feed. A view that responds to the member.
- Community Forums — topic-organized discussion with nested replies, search, and read/unread state tracking. Built to stay alive without becoming noise.
- Content Archive — every live training call organized, timestamped, and searchable with transcripts. Members who miss a session don't miss the value.
- Coaching Workflow Engine — a structured intake, routing, and feedback system that tracks every member-to-coach interaction inside the platform. No more managing coaching through inboxes.
- Multi-Tier Access Control — membership tiers with distinct permissions controlling visibility at the feature, page, and data level. Designed from the foundation, not retrofitted.
- MindAI — an AI assistant layer connected to the NHB knowledge base, built directly into the platform via backend API workflows. Members query it on demand. It surfaces frameworks, coaching insights, and content without waiting for a live call.
Tech stack
Impact
The platform unified an ecosystem that was previously scattered across four tools into a single environment — one login, one experience, one source of truth for every member interaction.
Members now access everything they pay for in one place. Coaches work through a structured system instead of an inbox. Content that used to disappear after a live call is now permanent, searchable, and in use daily.
The AI assistant reduced the time members spend waiting for answers to questions the platform can already answer.
And the job board turned a community of marketers into a talent marketplace — adding a layer of value that no off-the-shelf platform was going to give us.
This is what a community platform looks like when you build it for the community instead of adapting the community to the platform.
Reflections
The hardest part of this build wasn't the features.
It was the discipline to not build the features first.
Every time I'm tempted to open the canvas before the data model is done, I think about this project. The permission system alone — mapping every access state for every tier before touching a single element — saved weeks of rework that would have come later.
The other thing I learned: integrations are not bonuses. They're load-bearing. Every external API — the AI assistant, payments, video, email — needed its own error handling, retry logic, and failure state. The developers who skip that step ship products that work in demos and break in production.
NHB taught me that building for scale isn't about using more powerful tools.
It's about making better decisions earlier.
The spec is the strategy. The data model is the foundation. The visible surface — the part everyone sees — that's the easy part.
Do the invisible work well, and the visible work takes care of itself.