I design custom Notion and Airtable systems for founders and small teams who have outgrown scattered tools, unclear ownership, and ad-hoc workflows. This work is for teams who are moving beyond “getting by” and need systems that support visibility, accountability, and steady execution as the business grows.

<aside>

About Me

I'm Shelby Watson, founder of Musarium. I design operational systems for teams who are moving fast but need things to hold together. I have Operations experience at multiple start-ups and design Notion templates for others in my spare time.

I come from hands-on operations roles—customer success, partner management, onboarding—where I was the person actually using (and often building) the systems. I've managed donation drive operations across five states, onboarded 100+ partner organizations, and designed Airtable dashboards that cut manual work by 40%.

I know what it feels like when your team is growing, the work is getting more complex, and the tools you cobbled together six months ago are starting to crack under pressure. I also know what it feels like when a well-designed system finally clicks—when people stop asking "where does this go?" and just know.

I started Musarium because I kept building systems for myself and realized I could help other teams skip the trial-and-error phase and get straight to clarity. Musarium—a space where structure and creativity coexist. I design systems that provide operational clarity while leaving room for the way you actually work. Whether it's ops infrastructure for growing teams or personal productivity systems for ADHD brains, the approach is the same: understand how work actually flows, then build structure around that. Systems should fit the work, not force the work to fit the system.

If you're looking for someone who understands operations from the inside and can translate that into systems that actually work—let's talk.

</aside>

<aside>

:e-en--1-: Questions: [email protected]

:e-en--1-: Linkedin: https://www.linkedin.com/in/watsonrs

Explore my work, experience and systems.

Case Study: [Airtable] Donation Drive Operations System

Case Study: [Notion] ADHD-Friendly Personal Operations System

Case Study: [Notion] Job Tracker Dashboard

Resume

</aside>

<aside>

Who this is for

• A founder or operator managing real complexity
• A small team that’s outgrown ad-hoc tools
• Looking for clarity without micromanagement
• Ready for systems that support growth, not just organization

If you want something lightweight, flexible, and grounded in how work actually happens — this is likely a good fit.

</aside>

<aside>

Core Ops System — 1-Month Engagement

$1,200

What You'll Receive:

:img_0722: Custom System Build

• 1 primary operations hub (Notion workspace or base)
• 3-6 core databases designed for your workflow
• 5-10 custom views (dashboards, filtered views, role-based interfaces)
• Relational architecture connecting all databases
• Status logic and workflow automation (where appropriate)
• Clear naming and organizational structure

:img_0722: Documentation & Handoff:

• System walkthrough session (60-90 minutes)
• Written documentation explaining how the system works
• Guidance on how to maintain and adapt the system
• Access to me for questions during the build process

:img_0722: Timeline: 4 weeks from intake to delivery

</aside>

Gallery

<aside>

What this work usually involves

Teams often have some combination of the following:

• Projects spread across Notion, Airtable, Slack, and email
• Tasks tracked inconsistently or not at all
• Ownership understood informally rather than reflected in the system
• Leaders lacking a clear view of what is moving and what is stuck
• A setup that works until priorities shift or deadlines stack up

This is common when a business grows faster than its internal structure.

What I build instead:

I design systems that give teams a clear and reliable way to:

• Understand what work is active
• See who owns what
• Track progress without constant follow-ups
• Focus attention on what needs action
• Maintain the system without ongoing cleanup

The goal is a setup that holds up during busy periods and changing priorities.

</aside>

<aside>

</aside>