← All Docs

2026-03-07-shared-business-infrastructure-brainstorm

Shared Business Infrastructure Brainstorm

Date: 2026-03-07 Status: Ready for planning

What We’re Building

A Claude Code skills monorepo that serves as shared operational infrastructure for 4-6 businesses (mixed services + products). The system provides both on-demand AI assistance and automated workflows across websites/marketing, accounting, operations, and creative production.

The monorepo uses Claude Code’s native skill system as the “operating system” — shared skills handle cross-business concerns, while per-business configurations customize behavior.

Context

  • Number of businesses: 4-6 (mixed services and products)
  • Current tooling: Mostly manual/ad-hoc — building from near-zero
  • AI model: Both assisted (on-demand) and automated (scheduled/triggered)
  • Primary operator: Aaron (technical, comfortable with Claude Code)
  • First phase: Websites and marketing (static/marketing sites)

Why This Approach

Claude Code Skills Monorepo was chosen over a web app or hybrid approach because:

  1. Fastest to operational — No app to build, host, or maintain. Skills are just markdown + code.
  2. Leverages existing tool — Claude Code is already the daily interface. Skills compound naturally.
  3. Right scale — For a single operator managing 4-6 businesses, a CLI/AI-first workflow beats a dashboard.
  4. Near-zero existing tooling — No legacy systems to integrate with. Clean start.

Key Decisions

  1. Monorepo structure — One repo for all businesses. Shared skills in a common directory, per-business configs in business-specific directories.
  2. Skills-first architecture — Claude Code skills are the primary unit of automation. Each capability (invoice generation, content creation, site deployment) is a skill.
  3. Websites/marketing first — Start with static/marketing sites across businesses to establish the shared infrastructure pattern before expanding to accounting, operations, etc.
  4. Static sites — Business websites are content-focused (landing pages, blogs, portfolios), not full web applications.
  5. Hybrid AI usage — Some skills are interactive (Claude helps you), some are automated (scheduled content, reports).

Proposed Monorepo Structure

sendy-adventures-admin/
├── CLAUDE.md                     # Global AI instructions + skill registry
├── shared/
│   ├── skills/                   # Shared Claude Code skills
│   │   ├── website-deploy/       # Deploy static sites
│   │   ├── content-create/       # Generate marketing content
│   │   ├── seo-audit/            # SEO analysis and recommendations
│   │   ├── social-post/          # Social media content + scheduling
│   │   ├── invoice-generate/     # Create and send invoices
│   │   ├── expense-track/        # Log and categorize expenses
│   │   └── report-generate/      # Financial and operational reports
│   ├── templates/                # Shared templates (invoices, emails, etc.)
│   └── automations/              # Scheduled/triggered workflows
├── businesses/
│   ├── zendee-adventures/
│   │   ├── CLAUDE.md             # Business-specific AI context
│   │   ├── config.yaml           # Business metadata, branding, accounts
│   │   ├── website/              # Site source (Astro/Hugo/11ty)
│   │   └── docs/                 # Business-specific docs
│   ├── business-2/
│   │   ├── CLAUDE.md
│   │   ├── config.yaml
│   │   ├── website/
│   │   └── docs/
│   └── ...
├── docs/
│   └── brainstorms/
└── .github/
    └── workflows/                # CI/CD for site deployments

First Phase: Websites + Marketing

What’s in scope:

  • Static site generator setup for each business (likely Astro or Hugo)
  • Shared deployment skill (build + deploy to Vercel/Netlify/Cloudflare Pages)
  • Content creation skill (blog posts, landing page copy, meta descriptions)
  • SEO audit skill
  • Social media content skill
  • Per-business branding/config (colors, tone of voice, target audience)

What’s NOT in scope (yet):

  • Accounting/invoicing (Phase 2)
  • Operations/task management (Phase 3)
  • Creative production pipelines (Phase 4)
  • Web dashboards or GUIs
  • Multi-user access

Open Questions

  1. Static site generator choice — Astro, Hugo, or 11ty? Astro is modern and flexible, Hugo is fast, 11ty is simple. Need to pick one for consistency.
  2. Hosting platform — Vercel, Netlify, or Cloudflare Pages? Affects deployment skills.
  3. Content scheduling — How should automated content publishing work? GitHub Actions on cron? External scheduler?
  4. Business configs — What metadata does each business need? (domain, brand colors, social accounts, tone of voice, target audience?)
  5. Naming — Is “sendy-adventures-admin” still the right repo name for a multi-business infrastructure repo?

Success Criteria

  • Can deploy a static site for any business with a single Claude Code command
  • Can generate on-brand content for any business using shared skills + business config
  • Adding a new business is as simple as creating a new directory with a config file
  • Shared skills work identically across businesses, customized only by config