![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520139680_qb2th1mx7.png\")
\n \n A Complete Website Redesign and Custom Content Management System Built from Scratch:
NOTION BACKEND
CURSOR AS MAIN DEVELOPMENT TOOL
100 HOURS OF AI-ASSISTED DEVELOPMENT
This is a comprehensive case study on using Notion as an enterprise-grade CMS backend
This custom-built platform replaces traditional website builders like Squarespace by leveraging Notion's database relationships, rollups, and API to create a sophisticated content management system. The project demonstrates you can build a professional e-commerce website using Notion as the backend, with a custom sync layer that transforms 11 databases into 22 optimized PostgreSQL tables, enabling dynamic content delivery and cross-database intelligence.
The system reduces operational costs from $500-600/year to $30-120/year while dramatically improving content management efficiency. New page creation drops from 25-40 minutes to 5-10 minutes, with updates propagating automatically across the entire site. The architecture supports both dynamic pages (pulling from database properties) and static pages (using Notion's page content), creating a hybrid content delivery system that matches the sophistication of enterprise CMS platforms.
A key feature of this approach is its educational value for understanding database design and system architecture. The project serves as both a functional website and a comprehensive learning resource, showing how Notion's intuitive interface can teach complex database relationships that directly translate to professional development skills. The modular architecture allows others to adapt similar approaches for their own projects, whether building simple websites or complex data-driven applications.
The case study includes detailed breakdowns of the three-layer architecture (CMS Backend, Sync Layer, Dynamic Frontend), cost comparisons with traditional alternatives, AI coding strategies, security considerations, and practical lessons learned. The ultimate goal is to demonstrate that sophisticated web applications are now accessible to non-developers through the combination of Notion's database capabilities and AI-assisted development tools.
","category":"","type":"Notion","tags":["Tutorials"],"price":null,"url":"","payment_link":"","free_file":"","thumbnail_url":"/resource-images/Notion 8.5x11 Thumbnail 2.png","cover_image":"/resource-images/Notion 8.5x11 Thumbnail 2.png","featured":true,"status":"Don't Display Button","header_video":"","page_content":"I'm happy to say that I have fully released my new website. This is something that I have wanted to do for years now, and ultimately I am very happy with the results after a few months of hard, dedicated work. With this new website, I will be able to update information faster, create new pages and releases in a much more streamlined way, as well as enhance users' experience when navigating through the actual website itself.
With this case study, my whole goal is to tell you my full experience of building this website from scratch and give a bit of a sneak peek of how this helped me understand a bit more of how programs (like Notion) can actually teach you the core concepts of eventually building your own systems. I'll also explain a bit about using AI agents such as Cursor and what really helps me see the benefit for AI tools and their abilities for future projects, including how to use them in Notion.
Why Now? The timing finally aligned when my Squarespace subscription renewal approached in early September. Rather than commit to another year of limitations, I decided this was the moment to build something that could truly scale with my growing music catalog and complex content relationships.
This case study documents my complete journey from never having written a line of production code to deploying a fully functional e-commerce website in ~100 hours. The combination of powerful AI coding assistants and my existing understanding of database relationships from Notion created a unique opportunity to bridge the gap between system design and technical implementation.
\nThis is a fully integrated content management and delivery platform built from the ground up. The architecture has three main layers that I designed to be both powerful and easy to maintain.
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520140066_x5640ms39.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520140279_fdhvicz4c.gif\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520140710_ogo14ozni.png\")
\n \n It turns Notion into a powerful content management system using database relationships, rollups, and automated workflows. Eleven interconnected databases manage everything from compositions to media to subscriber lists, with complex relations and rollups that keep all the data connected properly across the entire system. The sophisticated relationship modeling creates 22 tables in the Postgres database, demonstrating the advanced relational architecture required to handle all the many-to-many connections between compositions, media, collections, and other content types. Content on the homepage, catalog listings, and resource connections all update automatically based on how the databases are connected.
To give a more complex example: Take a multi-movement composition like "Resolutions: Suite for Brass Trio." In Notion, I relate this composition to multiple media files (audio for each movement), pricing information, and collection groupings. On the website, this creates a dynamic composition page where the Buy Now button automatically shows current pricing and availability, the audio player includes all related recordings, and Previous/Next buttons let visitors navigate through the entire work in the correct sequence. All of this data comes from different databases but appears as one cohesive experience - and updating any relationship in Notion instantly changes how everything displays on the website. This is why my 11 databases require 22 Postgres tables: the many-to-many relationships between compositions, movements, media files, collections, and purchase options create the junction tables needed to make this sophisticated functionality work.
The sync system acts as a manual bridge between Notion and PostgreSQL. When I make changes in Notion, I run a sync command (node dual-sync) that pulls all the database content and relationships, then transforms them into optimized PostgreSQL tables.
The system intelligently creates junction tables for many-to-many relationships and handles all the database complexity automatically, but only when I choose to run the sync.
It is a modern, component-based website that's database-driven with flexible content delivery. The system intelligently adapts between dynamic database queries and static page content depending on what works best for each use case. The responsive component system means when I update something, it changes everywhere automatically, supporting advanced features like searchable catalogs, media players with metadata, and automated homepage features, all mobile-optimized and focused on performance and user experience.
This cross-database intelligence means that when I add a new composition with related media in Notion, it doesn't just appear on the individual composition page - it automatically shows up in the searchable media catalog, homepage features, and any other component that pulls from those databases. For example, the search page dynamically aggregates content from multiple databases to display compositions, media files, and their metadata in one unified interface. Update one relationship in Notion, and it instantly propagates across every page that uses that data. This is what zero hardcoded content really means - the entire site rebuilds itself based on database relationships.
Hybrid Content Delivery: Dynamic vs Static Pages
The system intelligently adapts between two content delivery methods depending on the use case. Dynamic pages (like compositions, media catalogs, and search results) pull from database properties for consistent relational display and automatic cross-database intelligence. Static pages (like resources, blog posts, and specialized content) pull directly from Notion page content, giving me complete creative control with rich formatting - file uploads that become download buttons, embedded YouTube videos, custom layouts, multi-column sections, and callouts. This essentially turns Notion into a full-featured page builder that syncs to the website with all formatting intact.
Even more powerful, I can embed dynamic database content within static page layouts. For example, resource pages use custom formatting from Notion page content, but can also include related news updates through database relations. These updates automatically appear both in the dedicated news section and embedded within the relevant resource pages, creating true hybrid content delivery.
When viewing a composition, users access an overlay that dynamically pulls together all related content - media files, purchase options, score videos, and audio files from multiple databases. Clicking "Next" automatically updates everything for the next movement, with all connections maintained through database relationships.
I design reusable widgets that pull specific data from the databases and can be deployed throughout the website - like the full media player and specialty design carousels. These overlays appear consistently across different pages.
The system includes automated e-commerce where payment links stored in Notion dynamically populate across all relevant pages. Using direct Stripe integration with PDF delivery via Mailgun APIs, I can update pricing once in Notion and it automatically updates throughout the website - keeping the core site stable if any payment issues occur.
\n![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520140876_8irl07oe9.gif\")
\n \n If you are not familiar with Notion, let me introduce you to what is one of the best teaching tools out there for learning about database design in the most fun way possible. While Notion is often represented as this all-in-one app for tasks, journaling, habit tracking, and other productivity needs, the real power isn't in the complexity it can accomplish, but rather the simplicity in its core design and ease of connecting to the web.
Put it this way: I love Notion. As a Notion Ambassador, I've helped organizations implement it into their workflows, and I use it extensively for my personal life management. Many people see Notion as just a powerful note-taker or task manager, but the real power comes from the fact that everything is a carefully curated building block that can relate to online functionality.
![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520141290_etxz9w2ug.png\")
\n \n Before building this website, I spent years creating increasingly sophisticated systems in Notion that taught me advanced database design. Here are some examples:
With the API, you can build incredibly creative systems—either purely in Notion itself or push that information out through APIs. Once you realize how Notion systems operate compared to actual software, everything becomes incredibly clear about how you can scaffold true SaaS products. It's more like a very fast software builder than a traditional productivity app.
What makes Notion truly limitless is that it removes traditional constraints found in other tools. Instead of being locked into rigid templates or predetermined workflows, every element becomes modular and interconnected. You can relate databases in complex ways, create sophisticated automations, and build systems that grow with your needs. This flexibility means Notion adapts to your thinking process rather than forcing you to adapt to the software's limitations.
While tools like Airtable excel at pure database management, Notion's unique advantage is that it functions like a website builder with databases embedded within pages. This hybrid approach is crucial for website development because you're not just managing data - you're creating the content experience.
Notion feels like a playground where you can experiment with page layouts, database views, and content relationships in real-time.
Airtable has more rigidity - it's excellent for structured data management but doesn't give you the creative freedom to rapidly prototype content layouts and user experiences that translate directly to website design.
\nWhen building my website, this distinction became crucial. The ability to create prototype pages in Notion that combined rich content with database relationships meant I could design the entire user experience before writing any code. With Airtable, I would have managed the data well, but I'd still need separate tools for content creation and layout design (atleast to my knowledge).
![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520141413_g9jhqdb2i.png\")
\n \n In reality, all the systems of Notion are not necessarily brand new concepts. What's intriguing and really powerful about the tool is how accessible they've made complex processes. Not only that, but they made Databases fun! You can learn not just how databases work from this system, but then you also can learn how to code with the formulas on top of that. Notion's formula system taught me how to query and manipulate data across related databases, which directly translated to understanding how building the 22 Postgres tables needed to work together. The rollup properties showed me data aggregation concepts that became crucial for the many-to-many relationships between compositions, media, and collections. You get to learn automations and how they work with their automation editor. And then you can go a step further by investigating the API. Finally, they have just added AI agents, which I think is going to change the game even further. It's helping promote working in systems like Cursor in a very natural way.
Notion basically helps you understand how when databases are related to one another and they start talking to each other, how you can transform that data to be useful information and then how you basically can search for that data and/or filter it out naturally. On top of that, it's not just about data. What makes Notion fun is the fact that it has some pre-integrated views that help it become more powerful with their different use cases. Not to mention, the text editor that is integrated specifically into Notion is so fast and really fun to actually build in.
Notion isn't just a productivity app - it's an intuitive gateway to understanding professional database design and system architecture. The skills you learn building complex Notion systems directly translate to real software development, giving you a massive head start when working with AI coding tools.
\nDon't get me wrong—Squarespace does have some dynamic capabilities and can create attractive websites quickly. But as my music catalog grew and my needs became more sophisticated, I kept running into fundamental limitations that became increasingly frustrating.
While I could customize layouts to some extent, the real problem was being stuck in a rigid system that forced manual work for everything. The biggest frustration was having to manually upload and embed audio/video files for each composition every single time, instead of being able to create simple relationships where media could be dynamically linked. There was no way to say "this composition relates to these three audio files" - I had to manually place each file on each page. This made managing a growing catalog of 70+ compositions with multiple media files each absolutely tedious.
This was the killer limitation. Squarespace can pull from collections (their version of databases), but you can't create meaningful relationships between different content types. I couldn't relate compositions to multiple media files, link movements to parent works, or automatically populate related content across different page types. Each piece of content lived in isolation.
While Squarespace templates look professional, they force you into predetermined layouts and functionality. I couldn't create the dynamic media overlays I wanted, couldn't build cross-referenced content systems, and definitely couldn't implement the sophisticated database relationships that my music catalog needed. Every composition looked identical regardless of its complexity or unique requirements.
As my catalog grew, managing content became exponentially more time-consuming. Adding a new composition meant updating multiple pages manually, checking that everything linked correctly, and ensuring consistency across the entire site. With no automation or relationship intelligence, every content update was a manual, error-prone process.
When most organizations build custom systems like this, they create a dedicated admin page where you can manage all the content - but that requires significant development time and expertise just to build the admin interface itself.
What I did with this system is essentially made Notion my admin page where I can edit all the content and maneuver everything. Instead of spending additional development time building a custom admin interface, I get all of Notion's powerful editing capabilities, database views, relationship management, and user-friendly interface for free. This lets me focus development effort on the user-facing website while having enterprise-level content management tools built in.
Here's what I think is the most important aspect of this entire system: this is literally just my own code—files and folders on my computer that I fully control and store myself. If I have a problem with hosting, if a platform changes pricing, or if anything else comes up, I own all the data and all the code. I'm not locked into any single service because everything lives on my machine.
But here's the key insight that makes this approach incredibly powerful: while the data stays in Notion for easy editing, it also syncs to Postgres, so I can still move off of Notion if something happens with it in the future. This dual-layer approach gives me the best of both worlds. Notion provides probably the easiest and simplest way to connect via online functionality for website development—their API is incredibly developer-friendly and their database system is intuitive. But the Postgres buffer means I'm never truly locked in.
Since this is my own codebase stored as files and folders, I can maneuver and pivot however I need to if any problems come up. Moving to a different platform or hosting provider is not a horrible and time-wasting endeavor—I can move anytime I want because I control every piece of the system. Even if Notion significantly changed their API or pricing, everything would keep running from the Postgres database while I figure out the next steps.
Beyond the cost issue, Squarespace's template constraints became the bigger obstacle.
The before and after comparison below shows exactly why I had to make this change:
![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520141572_x3epi5qkg.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520141769_kzguhzoff.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520141948_x37bbybef.gif\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520142367_4m64ki8ix.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520142602_an7our9f2.gif\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520143120_jpzt0011m.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520143356_hzrslrseh.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520143482_hdi7d7uax.gif\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520144907_00teli5v4.png\")
\n \n ![\"\"](\"/images/notion-as-an-e-commerce-cms_1763520145052_ffkzbtnrq.gif\")
\n \n The biggest difference is that I now have much more flexibility in what I'm able to do. In Squarespace, I was stuck with template constraints that forced a one-size-fits-all approach—manually uploading media for each composition, being limited to predetermined layouts, and constantly fighting against the system's rigidity.
With the custom system, I have complete control over both the database relationships and the design implementation. When I add a new composition with multiple movements in Notion, the website automatically creates the appropriate navigation, connects all related media, and displays everything in the right context. That's what true customizable control delivers.
Here's a clear comparison of what this custom build actually costs versus traditional alternatives:
Bottom Line: ~100 hours + ~$500 (AI) (Could be Reduced) + $1-$10/month vs. $340/year (Squarespace) or $15-$60K + $100-$500/month (custom development)
*Note: High AI/API cost was primarily due to lack of knowledge of best practices for AI models and learning good prompts for systems. This was my first coding build and large-scale AI usage (previously only used for simple no-code automation). This cost could easily be reduced with research and understanding which models work best.
Workflow Benefits:
*Note: some of these numbers are estimates are coming from some personal research and AI estimates. With that, take the estimate numbers as you will.
Traditional Workflow:
These projections are just the numbers that I experienced through the system. For me, I was already paying for Notion's $20/month business plan, so I consider that a sunk cost. I'm basically paying for the website for at most $10/month, but it's all dependent on usage and traffic, so it's often actually less. I'm saving a lot of money a year, I get full autonomy and control, and I'm updating my pages way faster. To be honest, it's just more fun doing it this way.
Value isn't just in cost savings - it's in control. The ~$500 AI learning cost becomes a permanent skill investment, while the 90% reduction in ongoing costs ($500-600/year → $30-120/year) gives you budget freedom to experiment with additional integrations and features that would be impossible on platforms.
\nIf we are being technical with this, this is definitely in the category of vibe coding and/or context coding. Through this build, I experimented with both aspects of this process, as well as writing/updating the code myself as well. I should mention my Notion background first for context: I already knew how to build apps and systems before this because I experimented with Notion for about three years. So when I got to the prompting side and building specifically in Cursor, it ultimately became very clear that "if I just want to make a system that's similar to Notion" while I prompt and know how the architecture works, I can "build this basically like I would in Notion."
Your existing knowledge becomes a force multiplier with AI. Because I understood database relationships from Notion, I could communicate complex requirements using familiar vocabulary. Instead of explaining database theory from scratch, I could say "relate compositions to media with rollup data" and the AI immediately understood the architecture I needed. However, AI amplifies your existing knowledge - you remain the architect and decision-maker - you still need to be the director of the system and manage it.
I think one of the most fascinating things was when I decided to switch from using the API directly from Notion to update the website to syncing with Postgres. What was really cool about building that sync between Notion and Postgres is it taught me what a relation table actually meant. And as soon as I figured that out and saw what was actually happening, it became 10 times faster to actually problem-solve, fix some issues, and make everything sync up correctly.
\nSuccess came from understanding when to use which tool and structuring my workflow for maximum effectiveness:
ChatGPT → High-level architecture discussions and visual design.
Cursor → Implementation and code execution
Claude Sonnet → Complex backend problems and logic
Understanding these tool differences significantly reduced both development time and costs compared to using just one AI throughout the entire process.
\nThese are just some snippets of what I took away from this build. For me, this was a really good time to do this because I think this agent form of using AI is definitely not going anywhere. Notion did just launch their AI agents, and they honestly speed up my workflows in Notion greatly. It's like using the Cursor agents but doing it in Notion, which is flat out amazing. Again, not perfect, but all these prompting examples still apply.
You will need to know how software systems work and get that knowledge before you can really build. Before diving into your project, you can make a little test demo of it, but I would do research on how the systems actually are supposed to work before fully diving in and making something that is production-ready.
AI won't automatically be able to create the most amazing, functional, or operational setup, even with multiple problems. You still need to be the director of the system and manage it. Research and figure out the right knowledge. You must know your system, and you must keep track of what you're building. This is for both long-term and short-term. AI chats are still not the brevity of the knowledge.
When building your architecture, before diving deep into what you do, be sure this is the way you want to build your system. I highly recommend experimenting and having like a test little function and/or a little app before doing something that you really think is important. A good example is the Notion API and transitioning over to Postgres. Transitioning this functionality actually glitched out a lot of my system. If I just started with Notion syncing into Postgres, it would've saved so much development time and headache.
There are certain triggers and certain words you need to bring up in order to get the responses and the build that you want. For instance, if you go with any chatbot and you think something's supposed to search on the web because the AI probably doesn't know specifically about that answer, you need to say, "This is something you need to search for," and that prompts it to actually go and search on the web. This is crucial because AI doesn't know what to avoid and what to prioritize. When talking and working with AI, the input you give it matters. With that said, you don't need to be necessarily hyper-fixated on your most pinpointed and accurate words when giving instruction. Focus on the triggers and the main points.
For me, with this experience, because I worked so much in Notion, I basically just made what I wanted from a Notion setup but did it through HTML and other forms of code. Having deep knowledge of relations and rollups accelerated development tremendously because I could communicate complex requirements using Notion vocabulary that the AI immediately understood. Instead of explaining "create junction tables for many-to-many relationships," I could say "relate compositions to media with rollup data" and skip straight to implementation. I know how my system fully works, and I know how things are all connected. I don't know exactly every single line of code and every single function, but I know operationally how it's supposed to operate and do what it's supposed to do. That's crucial.
Know exactly what you want your end goal to be, and you don't need all the answers of how it's supposed to work. You need to be open to the creative solutions of how they're supposed to connect, but also be able to understand what is happening in front of you—how everything actually operates.
Beyond the core principles, one of the most practical things I learned was being specific about purpose + scope when working with AI. Instead of vague requests, structure your prompts around these two dimensions:
| Purpose Categories | Scope Categories | Example in Practice |
| Building: "Create a new component that..." | UI/Frontend: Layout, styling, component behavior, user interactions | Instead of "Make the homepage better" Say: "Build me a new hero section component that displays dynamic composition data from the database with responsive card layouts" |
| Fixing: "Debug this specific issue where..." | Backend/API: Database queries, server logic, data processing, integrations | Instead of "The media player isn't working" Say: "Fix the backend API issue where the media player component isn't receiving the correct metadata from the Postgres sync layer" |
| Optimize: "Optimize this existing code to..." | Data Flow: How information moves between systems, state management | Instead of "Clean up this messy code" Say: "Optimize the data flow between the Notion sync and frontend display to reduce redundant API calls and improve loading times" |
| Information: "Help me understand how this works..." | Architecture: System design, relationships between components | Instead of "How should I structure this?" Say: "Help me with the architecture of this data system - specifically how compositions and media files should relate to each other between Notion and Postgres" |
May-July 2025 → Architecture planning and tool evaluation (~10-15 hours total)
July 22, 2025 → Committed to custom build with AI - development phase begins
Early August 2025 → Notion database architecture finalized and initial sync layer built
Mid-August 2025 → E-commerce integration and payment systems completed (most tedious phase)
Late August 2025 → Frontend components and dynamic page rendering implemented (main development focus)
September 6, 2025 → Website deployed and fully operational
Total: ~110-115 hours (10-15 hours research/planning + 100 hours active development from July 22-September 6)
\nNow, you can tell that this still took a very long period of time—100 hours of my labor. To give context on where that comes from: this project was being developed entirely from scratch for myself as a someone who has not built a fully coded project at all, which meant doing the design, figuring out how the architecture should work, figuring out the layout of all the pages and how the cross-database relationships should display, doing research on different website layouts and how they're supposed to look. And then on top of that, continuously building brand-new relation layers and junction table connections throughout the system.
To be transparent, I love building complex projects—it's similar to how I approach composing 20-minute long pieces with intricate, recurring motives. 100 hours might sound like a lot, but for me it's genuinely enjoyable, especially when learning new skills. I typically tackle one major project per year, and this was mine for 2024. Next year, I'll probably focus on smaller builds until I'm ready for another big undertaking.
\nBuilding a custom dynamic system introduces specific challenges you need to be prepared for:
I'll let you know in a future Update!
Even if Notion significantly changed their API, everything is backed up in Postgres so the website would keep running. The sync layer is modular and could theoretically pull from a different source, and I control all the data unlike being locked into a platform.
The key insight: Having Postgres as a buffer between Notion and the website means API changes become optional updates rather than emergency fixes.
\nIf you are a developer, if you deal with programs like Notion, if you are into software design, and you know how software and information is built and developed, definitely try and build a website with Notion as the backend, with AI Tools for help.
The answer also comes down to "know what you want to build." Understand the architecture of what you are building. Experiment before deploying your professional software. Please review the code and/or the info that you have built. Maybe not line-by-line, but look at the main structure to be sure everything looks okay. Double-check security issues. Understand APIs and the security risks and possible pitfalls and problems that might come. Learn the primary definitions of the systems that you will be building and changing. Examples would be CSS terms and database components and properties. I think it also comes down to what you are wanting to build and how comfortable you are with the software you've already either experimented with or used.
I don't regret my time with Squarespace as it taught me how to start building layouts and the general scheme of how websites work, but I am incredibly thankful that I did transition to make my own system.
This project has been incredibly encouraging, and I'm already planning to continue developing new systems and elements for this website. More information on that to come in future updates!
One of the biggest payoffs from this build has been gaining the confidence and capabilities to tackle even more sophisticated applications in the future. Building my very own music catalog has shown me what's possible when you combine deep system knowledge with AI tools. I have a genuine urge and drive to keep building.
As a musician approaching development through systems thinking, this project demonstrates how musicians with deep systems knowledge can build sophisticated technical solutions. I'm definitely interested in pursuing this as enjoyable, meaningful work and continuing to build more advanced projects.
If this case study has sparked your interest, here's how you can start your own journey:
The combination of Notion's intuitive database system and AI-assisted development has made sophisticated web development accessible in a way that wasn't possible just a few years ago. The barrier isn't technical skill anymore - it's systems thinking and the willingness to learn.
The future of building is collaborative—between you and AI, between your existing knowledge and new possibilities. If you understand how data should connect and flow, you have everything you need to build sophisticated technical solutions.
I'm happy to say that I have fully released my new website. This is something that I have wanted to do for years now, and ultimately I am very happy with the results after a few months of hard, dedicated work. With this new website, I will be able to update information faster, create new pages and releases in a much more streamlined way, as well as enhance users' experience when navigating through the actual website itself.
With this case study, my whole goal is to tell you my full experience of building this website from scratch and give a bit of a sneak peek of how this helped me understand a bit more of how programs (like Notion) can actually teach you the core concepts of eventually building your own systems. I'll also explain a bit about using AI agents such as Cursor and what really helps me see the benefit for AI tools and their abilities for future projects, including how to use them in Notion.
Why Now? The timing finally aligned when my Squarespace subscription renewal approached in early September. Rather than commit to another year of limitations, I decided this was the moment to build something that could truly scale with my growing music catalog and complex content relationships.
This case study documents my complete journey from never having written a line of production code to deploying a fully functional e-commerce website in ~100 hours. The combination of powerful AI coding assistants and my existing understanding of database relationships from Notion created a unique opportunity to bridge the gap between system design and technical implementation.
\nThis is a fully integrated content management and delivery platform built from the ground up. The architecture has three main layers that I designed to be both powerful and easy to maintain.
\n \n \n \n \n \n \n \n It turns Notion into a powerful content management system using database relationships, rollups, and automated workflows. Eleven interconnected databases manage everything from compositions to media to subscriber lists, with complex relations and rollups that keep all the data connected properly across the entire system. The sophisticated relationship modeling creates 22 tables in the Postgres database, demonstrating the advanced relational architecture required to handle all the many-to-many connections between compositions, media, collections, and other content types. Content on the homepage, catalog listings, and resource connections all update automatically based on how the databases are connected.
To give a more complex example: Take a multi-movement composition like "Resolutions: Suite for Brass Trio." In Notion, I relate this composition to multiple media files (audio for each movement), pricing information, and collection groupings. On the website, this creates a dynamic composition page where the Buy Now button automatically shows current pricing and availability, the audio player includes all related recordings, and Previous/Next buttons let visitors navigate through the entire work in the correct sequence. All of this data comes from different databases but appears as one cohesive experience - and updating any relationship in Notion instantly changes how everything displays on the website. This is why my 11 databases require 22 Postgres tables: the many-to-many relationships between compositions, movements, media files, collections, and purchase options create the junction tables needed to make this sophisticated functionality work.
The sync system acts as a manual bridge between Notion and PostgreSQL. When I make changes in Notion, I run a sync command (node dual-sync) that pulls all the database content and relationships, then transforms them into optimized PostgreSQL tables.
The system intelligently creates junction tables for many-to-many relationships and handles all the database complexity automatically, but only when I choose to run the sync.
It is a modern, component-based website that's database-driven with flexible content delivery. The system intelligently adapts between dynamic database queries and static page content depending on what works best for each use case. The responsive component system means when I update something, it changes everywhere automatically, supporting advanced features like searchable catalogs, media players with metadata, and automated homepage features, all mobile-optimized and focused on performance and user experience.
This cross-database intelligence means that when I add a new composition with related media in Notion, it doesn't just appear on the individual composition page - it automatically shows up in the searchable media catalog, homepage features, and any other component that pulls from those databases. For example, the search page dynamically aggregates content from multiple databases to display compositions, media files, and their metadata in one unified interface. Update one relationship in Notion, and it instantly propagates across every page that uses that data. This is what zero hardcoded content really means - the entire site rebuilds itself based on database relationships.
Hybrid Content Delivery: Dynamic vs Static Pages
The system intelligently adapts between two content delivery methods depending on the use case. Dynamic pages (like compositions, media catalogs, and search results) pull from database properties for consistent relational display and automatic cross-database intelligence. Static pages (like resources, blog posts, and specialized content) pull directly from Notion page content, giving me complete creative control with rich formatting - file uploads that become download buttons, embedded YouTube videos, custom layouts, multi-column sections, and callouts. This essentially turns Notion into a full-featured page builder that syncs to the website with all formatting intact.
Even more powerful, I can embed dynamic database content within static page layouts. For example, resource pages use custom formatting from Notion page content, but can also include related news updates through database relations. These updates automatically appear both in the dedicated news section and embedded within the relevant resource pages, creating true hybrid content delivery.
When viewing a composition, users access an overlay that dynamically pulls together all related content - media files, purchase options, score videos, and audio files from multiple databases. Clicking "Next" automatically updates everything for the next movement, with all connections maintained through database relationships.
I design reusable widgets that pull specific data from the databases and can be deployed throughout the website - like the full media player and specialty design carousels. These overlays appear consistently across different pages.
The system includes automated e-commerce where payment links stored in Notion dynamically populate across all relevant pages. Using direct Stripe integration with PDF delivery via Mailgun APIs, I can update pricing once in Notion and it automatically updates throughout the website - keeping the core site stable if any payment issues occur.
\n\n \n If you are not familiar with Notion, let me introduce you to what is one of the best teaching tools out there for learning about database design in the most fun way possible. While Notion is often represented as this all-in-one app for tasks, journaling, habit tracking, and other productivity needs, the real power isn't in the complexity it can accomplish, but rather the simplicity in its core design and ease of connecting to the web.
Put it this way: I love Notion. As a Notion Ambassador, I've helped organizations implement it into their workflows, and I use it extensively for my personal life management. Many people see Notion as just a powerful note-taker or task manager, but the real power comes from the fact that everything is a carefully curated building block that can relate to online functionality.
\n \n Before building this website, I spent years creating increasingly sophisticated systems in Notion that taught me advanced database design. Here are some examples:
With the API, you can build incredibly creative systems—either purely in Notion itself or push that information out through APIs. Once you realize how Notion systems operate compared to actual software, everything becomes incredibly clear about how you can scaffold true SaaS products. It's more like a very fast software builder than a traditional productivity app.
What makes Notion truly limitless is that it removes traditional constraints found in other tools. Instead of being locked into rigid templates or predetermined workflows, every element becomes modular and interconnected. You can relate databases in complex ways, create sophisticated automations, and build systems that grow with your needs. This flexibility means Notion adapts to your thinking process rather than forcing you to adapt to the software's limitations.
While tools like Airtable excel at pure database management, Notion's unique advantage is that it functions like a website builder with databases embedded within pages. This hybrid approach is crucial for website development because you're not just managing data - you're creating the content experience.
Notion feels like a playground where you can experiment with page layouts, database views, and content relationships in real-time.
Airtable has more rigidity - it's excellent for structured data management but doesn't give you the creative freedom to rapidly prototype content layouts and user experiences that translate directly to website design.
\nWhen building my website, this distinction became crucial. The ability to create prototype pages in Notion that combined rich content with database relationships meant I could design the entire user experience before writing any code. With Airtable, I would have managed the data well, but I'd still need separate tools for content creation and layout design (atleast to my knowledge).
\n \n In reality, all the systems of Notion are not necessarily brand new concepts. What's intriguing and really powerful about the tool is how accessible they've made complex processes. Not only that, but they made Databases fun! You can learn not just how databases work from this system, but then you also can learn how to code with the formulas on top of that. Notion's formula system taught me how to query and manipulate data across related databases, which directly translated to understanding how building the 22 Postgres tables needed to work together. The rollup properties showed me data aggregation concepts that became crucial for the many-to-many relationships between compositions, media, and collections. You get to learn automations and how they work with their automation editor. And then you can go a step further by investigating the API. Finally, they have just added AI agents, which I think is going to change the game even further. It's helping promote working in systems like Cursor in a very natural way.
Notion basically helps you understand how when databases are related to one another and they start talking to each other, how you can transform that data to be useful information and then how you basically can search for that data and/or filter it out naturally. On top of that, it's not just about data. What makes Notion fun is the fact that it has some pre-integrated views that help it become more powerful with their different use cases. Not to mention, the text editor that is integrated specifically into Notion is so fast and really fun to actually build in.
Notion isn't just a productivity app - it's an intuitive gateway to understanding professional database design and system architecture. The skills you learn building complex Notion systems directly translate to real software development, giving you a massive head start when working with AI coding tools.
\nDon't get me wrong—Squarespace does have some dynamic capabilities and can create attractive websites quickly. But as my music catalog grew and my needs became more sophisticated, I kept running into fundamental limitations that became increasingly frustrating.
While I could customize layouts to some extent, the real problem was being stuck in a rigid system that forced manual work for everything. The biggest frustration was having to manually upload and embed audio/video files for each composition every single time, instead of being able to create simple relationships where media could be dynamically linked. There was no way to say "this composition relates to these three audio files" - I had to manually place each file on each page. This made managing a growing catalog of 70+ compositions with multiple media files each absolutely tedious.
This was the killer limitation. Squarespace can pull from collections (their version of databases), but you can't create meaningful relationships between different content types. I couldn't relate compositions to multiple media files, link movements to parent works, or automatically populate related content across different page types. Each piece of content lived in isolation.
While Squarespace templates look professional, they force you into predetermined layouts and functionality. I couldn't create the dynamic media overlays I wanted, couldn't build cross-referenced content systems, and definitely couldn't implement the sophisticated database relationships that my music catalog needed. Every composition looked identical regardless of its complexity or unique requirements.
As my catalog grew, managing content became exponentially more time-consuming. Adding a new composition meant updating multiple pages manually, checking that everything linked correctly, and ensuring consistency across the entire site. With no automation or relationship intelligence, every content update was a manual, error-prone process.
When most organizations build custom systems like this, they create a dedicated admin page where you can manage all the content - but that requires significant development time and expertise just to build the admin interface itself.
What I did with this system is essentially made Notion my admin page where I can edit all the content and maneuver everything. Instead of spending additional development time building a custom admin interface, I get all of Notion's powerful editing capabilities, database views, relationship management, and user-friendly interface for free. This lets me focus development effort on the user-facing website while having enterprise-level content management tools built in.
Here's what I think is the most important aspect of this entire system: this is literally just my own code—files and folders on my computer that I fully control and store myself. If I have a problem with hosting, if a platform changes pricing, or if anything else comes up, I own all the data and all the code. I'm not locked into any single service because everything lives on my machine.
But here's the key insight that makes this approach incredibly powerful: while the data stays in Notion for easy editing, it also syncs to Postgres, so I can still move off of Notion if something happens with it in the future. This dual-layer approach gives me the best of both worlds. Notion provides probably the easiest and simplest way to connect via online functionality for website development—their API is incredibly developer-friendly and their database system is intuitive. But the Postgres buffer means I'm never truly locked in.
Since this is my own codebase stored as files and folders, I can maneuver and pivot however I need to if any problems come up. Moving to a different platform or hosting provider is not a horrible and time-wasting endeavor—I can move anytime I want because I control every piece of the system. Even if Notion significantly changed their API or pricing, everything would keep running from the Postgres database while I figure out the next steps.
Beyond the cost issue, Squarespace's template constraints became the bigger obstacle.
The before and after comparison below shows exactly why I had to make this change:
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n The biggest difference is that I now have much more flexibility in what I'm able to do. In Squarespace, I was stuck with template constraints that forced a one-size-fits-all approach—manually uploading media for each composition, being limited to predetermined layouts, and constantly fighting against the system's rigidity.
With the custom system, I have complete control over both the database relationships and the design implementation. When I add a new composition with multiple movements in Notion, the website automatically creates the appropriate navigation, connects all related media, and displays everything in the right context. That's what true customizable control delivers.
Here's a clear comparison of what this custom build actually costs versus traditional alternatives:
Bottom Line: ~100 hours + ~$500 (AI) (Could be Reduced) + $1-$10/month vs. $340/year (Squarespace) or $15-$60K + $100-$500/month (custom development)
*Note: High AI/API cost was primarily due to lack of knowledge of best practices for AI models and learning good prompts for systems. This was my first coding build and large-scale AI usage (previously only used for simple no-code automation). This cost could easily be reduced with research and understanding which models work best.
Workflow Benefits:
*Note: some of these numbers are estimates are coming from some personal research and AI estimates. With that, take the estimate numbers as you will.
Traditional Workflow:
These projections are just the numbers that I experienced through the system. For me, I was already paying for Notion's $20/month business plan, so I consider that a sunk cost. I'm basically paying for the website for at most $10/month, but it's all dependent on usage and traffic, so it's often actually less. I'm saving a lot of money a year, I get full autonomy and control, and I'm updating my pages way faster. To be honest, it's just more fun doing it this way.
Value isn't just in cost savings - it's in control. The ~$500 AI learning cost becomes a permanent skill investment, while the 90% reduction in ongoing costs ($500-600/year → $30-120/year) gives you budget freedom to experiment with additional integrations and features that would be impossible on platforms.
\nIf we are being technical with this, this is definitely in the category of vibe coding and/or context coding. Through this build, I experimented with both aspects of this process, as well as writing/updating the code myself as well. I should mention my Notion background first for context: I already knew how to build apps and systems before this because I experimented with Notion for about three years. So when I got to the prompting side and building specifically in Cursor, it ultimately became very clear that "if I just want to make a system that's similar to Notion" while I prompt and know how the architecture works, I can "build this basically like I would in Notion."
Your existing knowledge becomes a force multiplier with AI. Because I understood database relationships from Notion, I could communicate complex requirements using familiar vocabulary. Instead of explaining database theory from scratch, I could say "relate compositions to media with rollup data" and the AI immediately understood the architecture I needed. However, AI amplifies your existing knowledge - you remain the architect and decision-maker - you still need to be the director of the system and manage it.
I think one of the most fascinating things was when I decided to switch from using the API directly from Notion to update the website to syncing with Postgres. What was really cool about building that sync between Notion and Postgres is it taught me what a relation table actually meant. And as soon as I figured that out and saw what was actually happening, it became 10 times faster to actually problem-solve, fix some issues, and make everything sync up correctly.
\nSuccess came from understanding when to use which tool and structuring my workflow for maximum effectiveness:
ChatGPT → High-level architecture discussions and visual design.
Cursor → Implementation and code execution
Claude Sonnet → Complex backend problems and logic
Understanding these tool differences significantly reduced both development time and costs compared to using just one AI throughout the entire process.
\nThese are just some snippets of what I took away from this build. For me, this was a really good time to do this because I think this agent form of using AI is definitely not going anywhere. Notion did just launch their AI agents, and they honestly speed up my workflows in Notion greatly. It's like using the Cursor agents but doing it in Notion, which is flat out amazing. Again, not perfect, but all these prompting examples still apply.
You will need to know how software systems work and get that knowledge before you can really build. Before diving into your project, you can make a little test demo of it, but I would do research on how the systems actually are supposed to work before fully diving in and making something that is production-ready.
AI won't automatically be able to create the most amazing, functional, or operational setup, even with multiple problems. You still need to be the director of the system and manage it. Research and figure out the right knowledge. You must know your system, and you must keep track of what you're building. This is for both long-term and short-term. AI chats are still not the brevity of the knowledge.
When building your architecture, before diving deep into what you do, be sure this is the way you want to build your system. I highly recommend experimenting and having like a test little function and/or a little app before doing something that you really think is important. A good example is the Notion API and transitioning over to Postgres. Transitioning this functionality actually glitched out a lot of my system. If I just started with Notion syncing into Postgres, it would've saved so much development time and headache.
There are certain triggers and certain words you need to bring up in order to get the responses and the build that you want. For instance, if you go with any chatbot and you think something's supposed to search on the web because the AI probably doesn't know specifically about that answer, you need to say, "This is something you need to search for," and that prompts it to actually go and search on the web. This is crucial because AI doesn't know what to avoid and what to prioritize. When talking and working with AI, the input you give it matters. With that said, you don't need to be necessarily hyper-fixated on your most pinpointed and accurate words when giving instruction. Focus on the triggers and the main points.
For me, with this experience, because I worked so much in Notion, I basically just made what I wanted from a Notion setup but did it through HTML and other forms of code. Having deep knowledge of relations and rollups accelerated development tremendously because I could communicate complex requirements using Notion vocabulary that the AI immediately understood. Instead of explaining "create junction tables for many-to-many relationships," I could say "relate compositions to media with rollup data" and skip straight to implementation. I know how my system fully works, and I know how things are all connected. I don't know exactly every single line of code and every single function, but I know operationally how it's supposed to operate and do what it's supposed to do. That's crucial.
Know exactly what you want your end goal to be, and you don't need all the answers of how it's supposed to work. You need to be open to the creative solutions of how they're supposed to connect, but also be able to understand what is happening in front of you—how everything actually operates.
Beyond the core principles, one of the most practical things I learned was being specific about purpose + scope when working with AI. Instead of vague requests, structure your prompts around these two dimensions:
| Purpose Categories | Scope Categories | Example in Practice |
| Building: "Create a new component that..." | UI/Frontend: Layout, styling, component behavior, user interactions | Instead of "Make the homepage better" Say: "Build me a new hero section component that displays dynamic composition data from the database with responsive card layouts" |
| Fixing: "Debug this specific issue where..." | Backend/API: Database queries, server logic, data processing, integrations | Instead of "The media player isn't working" Say: "Fix the backend API issue where the media player component isn't receiving the correct metadata from the Postgres sync layer" |
| Optimize: "Optimize this existing code to..." | Data Flow: How information moves between systems, state management | Instead of "Clean up this messy code" Say: "Optimize the data flow between the Notion sync and frontend display to reduce redundant API calls and improve loading times" |
| Information: "Help me understand how this works..." | Architecture: System design, relationships between components | Instead of "How should I structure this?" Say: "Help me with the architecture of this data system - specifically how compositions and media files should relate to each other between Notion and Postgres" |
May-July 2025 → Architecture planning and tool evaluation (~10-15 hours total)
July 22, 2025 → Committed to custom build with AI - development phase begins
Early August 2025 → Notion database architecture finalized and initial sync layer built
Mid-August 2025 → E-commerce integration and payment systems completed (most tedious phase)
Late August 2025 → Frontend components and dynamic page rendering implemented (main development focus)
September 6, 2025 → Website deployed and fully operational
Total: ~110-115 hours (10-15 hours research/planning + 100 hours active development from July 22-September 6)
\nNow, you can tell that this still took a very long period of time—100 hours of my labor. To give context on where that comes from: this project was being developed entirely from scratch for myself as a someone who has not built a fully coded project at all, which meant doing the design, figuring out how the architecture should work, figuring out the layout of all the pages and how the cross-database relationships should display, doing research on different website layouts and how they're supposed to look. And then on top of that, continuously building brand-new relation layers and junction table connections throughout the system.
To be transparent, I love building complex projects—it's similar to how I approach composing 20-minute long pieces with intricate, recurring motives. 100 hours might sound like a lot, but for me it's genuinely enjoyable, especially when learning new skills. I typically tackle one major project per year, and this was mine for 2024. Next year, I'll probably focus on smaller builds until I'm ready for another big undertaking.
\nBuilding a custom dynamic system introduces specific challenges you need to be prepared for:
I'll let you know in a future Update!
Even if Notion significantly changed their API, everything is backed up in Postgres so the website would keep running. The sync layer is modular and could theoretically pull from a different source, and I control all the data unlike being locked into a platform.
The key insight: Having Postgres as a buffer between Notion and the website means API changes become optional updates rather than emergency fixes.
\nIf you are a developer, if you deal with programs like Notion, if you are into software design, and you know how software and information is built and developed, definitely try and build a website with Notion as the backend, with AI Tools for help.
The answer also comes down to "know what you want to build." Understand the architecture of what you are building. Experiment before deploying your professional software. Please review the code and/or the info that you have built. Maybe not line-by-line, but look at the main structure to be sure everything looks okay. Double-check security issues. Understand APIs and the security risks and possible pitfalls and problems that might come. Learn the primary definitions of the systems that you will be building and changing. Examples would be CSS terms and database components and properties. I think it also comes down to what you are wanting to build and how comfortable you are with the software you've already either experimented with or used.
I don't regret my time with Squarespace as it taught me how to start building layouts and the general scheme of how websites work, but I am incredibly thankful that I did transition to make my own system.
This project has been incredibly encouraging, and I'm already planning to continue developing new systems and elements for this website. More information on that to come in future updates!
One of the biggest payoffs from this build has been gaining the confidence and capabilities to tackle even more sophisticated applications in the future. Building my very own music catalog has shown me what's possible when you combine deep system knowledge with AI tools. I have a genuine urge and drive to keep building.
As a musician approaching development through systems thinking, this project demonstrates how musicians with deep systems knowledge can build sophisticated technical solutions. I'm definitely interested in pursuing this as enjoyable, meaningful work and continuing to build more advanced projects.
If this case study has sparked your interest, here's how you can start your own journey:
The combination of Notion's intuitive database system and AI-assisted development has made sophisticated web development accessible in a way that wasn't possible just a few years ago. The barrier isn't technical skill anymore - it's systems thinking and the willingness to learn.
The future of building is collaborative—between you and AI, between your existing knowledge and new possibilities. If you understand how data should connect and flow, you have everything you need to build sophisticated technical solutions.
NOTION BACKEND
CURSOR AS MAIN DEVELOPMENT TOOL
100 HOURS OF AI-ASSISTED DEVELOPMENT
Read More about How The Redesign was Created Here
This custom-built platform replaces traditional website builders like Squarespace by leveraging Notion's database relationships, rollups, and API to create a sophisticated content management system. The project demonstrates you can build a professional e-commerce website using Notion as the backend, with a custom sync layer that transforms 11 databases into 22 optimized PostgreSQL tables, enabling dynamic content delivery and cross-database intelligence.
This is a comprehensive case study on using Notion as an enterprise-grade CMS backend
![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520002360_pgx50ox1f.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520003030_xi9fjpg7r.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520003647_8172sxr7v.gif\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520005602_x67ugwk9i.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520005930_mexjrxn4s.gif\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520007248_kzfa023lt.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520007512_rari39fpu.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520007693_zupl01i3n.gif\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520028381_e11mb9iot.png\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520028977_pqf7eu3lg.gif\")
\n \n The system reduces operational costs from $500-600/year to $30-120/year while dramatically improving content management efficiency. New page creation drops from 25-40 minutes to 5-10 minutes, with updates propagating automatically across the entire site. The architecture supports both dynamic pages (pulling from database properties) and static pages (using Notion's page content), creating a hybrid content delivery system that matches the sophistication of enterprise CMS platforms.
A key feature of this approach is its educational value for understanding database design and system architecture. The project serves as both a functional website and a comprehensive learning resource, showing how Notion's intuitive interface can teach complex database relationships that directly translate to professional development skills. The modular architecture allows others to adapt similar approaches for their own projects, whether building simple websites or complex data-driven applications.
![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520032927_y07mozpuh.gif\")
\n \n ![\"\"](\"/images/Website-Redesign!-Custom-Coded-E-Commerce-with-Notion-2025_1763520036416_wijk53d2f.png\")
\n \n The case study includes detailed breakdowns of the three-layer architecture (CMS Backend, Sync Layer, Dynamic Frontend), cost comparisons with traditional alternatives, AI coding strategies, security considerations, and practical lessons learned. The ultimate goal is to demonstrate that sophisticated web applications are now accessible to non-developers through the combination of Notion's database capabilities and AI-assisted development tools.
![\"\"](\"/images/Brandon-has-been-named-a-Notion-Ambassador-2025_1763519995327_tevnm7uei.png\")
\n \n Brandon Dicks has been officially named a Notion Ambassador, joining an exclusive group representing the all-in-one productivity platform. This recognition acknowledges his work helping musical organizations transform their operational workflows through sophisticated Notion implementations.
As a Notion Ambassador, Brandon leverages his background as both a musician and systems architect. This role positions him to influence product development, create educational content, and mentor organizations in advanced Notion implementations.
Brandon has helped numerous organizations streamline operations through sophisticated Notion-based systems:
Church Music Ministries: Comprehensive management systems for repertoire coordination, performer scheduling, and resource distribution across multiple venues and performance contexts.
Educational Institutions: Integrated platforms for student lesson management, progress tracking, and automated billing workflows with Zoom integration and resource portals.
Professional Ensembles: Member management portals with automated permissions and dynamic file distribution based on instrument and concert selection.
As a Notion Ambassador, Brandon will continue developing educational resources, mentoring organizations, and contributing to product development discussions focused on empowering professionals to build scalable systems.