~/matzekmedia/system/buy
matzekmedia / system

Set up with you, tuned to your work.

Claude starts every session knowing nothing about what you've decided. This system fixes that. It holds your settled judgment in plain files, loads them when a session starts, and routes what changed back before you close. The system runs on your judgment instead of a vendor's defaults. Congruence.

I set it up with you over a series of calls and tune it to the way you actually work, then stay on as your advisor while you grow it. The posture you walk away with: you see a problem, you tell Claude to build it, it exists. That is how I built the CRM I run this business on.

$500/mo, locked for founding members. No setup fee. The tier stays high-touch and capped. You apply; you don't check out.

Buying for a business? The agency side runs on one intake: everything I build, scoped from your answers.

read the argument → system/knowledge-system

What the founder engagement adds

  • Done-with-you setup over a series of calls. I walk you through the system live and get it running on your real work.
  • Ongoing optimization. I tune it toward your needs as they surface.
  • System updates. Every improvement I ship, you get.
  • The build-anything posture. You see a problem, you tell Claude to build it, it exists. Workflows, skills, custom Obsidian apps like my CRM.
  • Generous access. Calls and questions as you need them. A soft monthly ceiling exists only so no one asks for a call a day.
  • The founder community (coming). A private founder channel in the PKM Discord, included once it opens.

Who this is not for

The tier is capped, so the filter is public. Six profiles I turn away:

  • The magic-button buyer. This system makes your judgment the compounding asset, which means you supply judgment. If you want an AI that curates its own memory and runs on autopilot, the self-improving agents genuinely serve you better.
  • The hobbyist note-taker. Same machine, wrong goal. This engagement is priced for operators whose lost decisions have a dollar cost. If your notes are personal, organize them for free and keep the money.
  • The zero-setup minimalist. If your pain is configuration fatigue, this is the wrong medicine. The frictionless notes apps win on that axis; this system answers with authored structure that has to pay rent.
  • The buyer who won't live in it. The system compounds only if it's where you actually work. Kept as a seventh tool you check in on, it's an expensive notebook.
  • The team wanting a browser dashboard. Centrally administered knowledge for fifty seats is enterprise software; Guru and SharePoint do it well. This core is operator-authored and local-first. A team that wants this machine shared has its own page.
  • The business with nothing to govern. If no decision is being lost between sessions, the loss this prevents doesn't exist for you yet. Come back when it does.

Or run it yourself

Some operators want to stand it up solo. The system is available on its own, one-time, without the hands-on setup. Same files, same machine. By request while early access stays hands-on and limited. Tell me what you are working on and I will see if it is a fit.

What's included (the system)

Both ways in get the same machine: a pre-configured Obsidian vault and Claude Code setup. The core is a governance loop. Startup loads your judgment. Close routes back what shifted. The system surfaces a conflict before Claude acts on it.

  • Pre-configured Obsidian vault with lifecycle architecture
  • Claude Code configuration (CLAUDE.md, skills, procedures)
  • 3 custom Obsidian plugins (Vault Toolkit, Vault Dashboard, vault-search-indexer)
  • 20+ Python hook scripts (sandbox enforcement, auto-commit, git sync, content sanitization)
  • 7 guides covering setup through advanced use
  • Security model with tiered sandbox enforcement
  • Decision Log, Field Notes, and Roadmap starters
  • System updates via private GitHub repository

The community

A private Discord where people running the system compare setups and trade what is working. It opens once there are enough members to make it worth the room. The founder tier includes the private founder channel when it goes live.

Requirements

  • Obsidian (free, any platform)
  • Claude Code by Anthropic (requires a paid Claude plan, Pro or Max, or Anthropic API access)
  • GitHub account (free, used for product delivery and updates)
  • Python 3 and Git (free, installed during setup)
  • Docker Desktop (free, optional; powers the semantic search layer)
  • Windows, Mac, or Linux

How delivery works

01. Apply. Tell me what you are working on. The founder tier is by application and capped, so I read every note personally and reply to you directly.

02. Set up. For the founder tier, we get on calls and stand the system up around your real work. For the solo system, you clone the vault from a private GitHub org and follow the setup guide inside.

03. Run it. The setup guide walks you through installing dependencies, configuring Claude Code, and running your first session.

04. Updates ship continuously. System updates land in a separate repository in the same org. Your Claude session checks for them during weekly review and walks you through applying the ones you want.

FAQ

How does the founder tier work? I set the system up with you over calls, tune it to your work, and stay on as your advisor, for $500/mo. By application because it is high-touch and capped.

Can I just buy the system and run it myself? Yes, the solo option. Same machine without the hands-on setup. By request for now, while early access stays hands-on and limited.

Do I need a GitHub account? Yes. GitHub is the delivery channel for the vault and the update channel for system improvements. Signup is free.

How do updates work? System updates ship to a separate repository in the same private org. Your Claude session checks for them during weekly review and walks you through applying the ones you want, file by file. Nothing overwrites your setup without you seeing it.

Can I customize it? Yes. The vault is plain markdown, CLAUDE.md is text, the skills are markdown procedures, the Python scripts are open. The design expects you to edit, extend, and override. The update layer merges around your changes instead of overwriting them.

Where does my data live? On your machine. The vault is a local Obsidian folder under version control. Nothing uploads to a service the seller controls. You own the files.

Why US-only at first? Tax registration and payments are scoped to the US for the opening window. Other regions are on the roadmap.