Skip to content

About

No description, website, or topics provided.

Resources

Stars

5 stars

Watchers

0 watching

Forks

Repository files navigation

Founder OS — your company's brain in a markdown repo

A template for founders. Your pitch deck, financial model, investor pipeline, customer research, decision log, and sales pipeline — all in one markdown repo that Claude Code can read, write, and keep updated.

A repo is no longer just code storage — it's the cheapest, most portable agent substrate ever invented. Markdown is what LLMs were trained on. Git gives you a free audit trail. Folders can encode pipeline stages, investor relationships, narrative atoms, model assumptions, and decision history better than any SaaS tool.


The dashboard — composed from markdown, lives only on your laptop

Founder OS dashboard — full page

Type /dashboard in Claude Code. Claude reads every markdown file in the repo — including the gitignored *.local.md files where you keep your bank balance, cap-table draft, and soft-committed term-sheet numbers — and composes a single self-contained HTML cockpit at _dashboard.html. The HTML itself is gitignored. Sensitive data on screen, never on GitHub.

Re-run /dashboard whenever you want a fresh view. Edit a deal in markdown, regenerate, refresh the browser.

→ Skip to the dashboard section for the build details.


Table of contents

  1. The core idea (read this first)
  2. What this is (for founders)
  3. What's in the box
  4. Quickstart — make it yours in 10 minutes
  5. The customisation prompt (copy this)
  6. How to add documents — the dropzone
  7. The dashboard — your company at a glance
  8. What never gets pushed to GitHub (the .gitignore)
  9. Day-to-day prompts
  10. Folder reference
  11. What you'll need to clean / replace
  12. License + credits

The core idea (read this first)

The repo is your data layer. The deck, financial model, investor update, dashboard, and sales emails are generated on demand from that data layer.

You store You generate
narrative/ (one-liner, problem, solution, etc.) pitch/slides.md via /pitch
traction/kpis.md, model/runway.md Monthly investor update via /investor-update
Every markdown in the repo + *.local.md files A live cockpit via /dashboard
pipeline/, people/, companies/ Sales follow-ups, lookalike outbound
decisions/ Future-self memory of why you chose what

Single source of truth. Edit narrative/one-liner.md once → next deck, next investor email, and next dashboard all update.

The artifacts that ship in this template (pitch/slides.md, traction/updates/*.md) are examples of what those generators produce. They get overwritten when you run the generator for your own business — that's the point.


What this is (for founders)

If you're early-stage and you've ever felt this:

  • "I have a half-finished pitch deck in Pitch, a financial model in Excel, an investor list in Notion, customer interview notes in Granola, decisions in Slack threads, and a sales pipeline in nothing."
  • "I keep updating the deck when I should be updating the model first, but they reference the same numbers and I can't keep them in sync."
  • "I have to write an investor update and I don't know where the numbers are."
  • "I want to know what we decided about pricing six weeks ago and why, and I can't find the conversation."

…this template is for you.

It's a single repo of markdown files that holds:

  • Your story (one-liner, problem, solution, why-now, why-us, market, moat, FAQ)
  • Your deck (slide content, speaker notes, appendix — branchable per audience)
  • Your model (assumptions, scenarios, runway, headcount plan, unit economics)
  • Your traction (KPIs, milestones, monthly investor update archive)
  • Your product (vision, current state, roadmap, user feedback)
  • Your customers / users (ICP, interview transcripts)
  • Your market intel (competitors, market sizing, trends)
  • Your investor pipeline (one file per fund/angel — thesis, status, intros, asks)
  • Your sales pipeline (deals as files in stage folders — git mv between stages)
  • Your people + companies (relationships outlast deals)
  • Your team (cap table, hiring plan, decision rights)
  • Your decisions (Annie Duke style decision journal)
  • Your rhythm (monthly log, daily inbox, weekly KPI snapshot)

Claude Code is the interface. You ask in plain English; Claude reads files, writes new ones, keeps things in sync, drafts in your voice, and surfaces what's stale.

Why a markdown repo beats a stack of SaaS tools (at this stage)

  • Single source of truth. When narrative/one-liner.md changes, the deck pulls from it. The investor update pulls from it. The website hero pulls from it. Never out of sync.
  • Versioned. Git history is a free audit trail. git blame model/assumptions.md tells you who changed CAC and when.
  • Branchable. git checkout -b vc-pitch makes a parallel reality. Same data, different framing. Diffs show you exactly what changed between the founder view and the investor view. No SaaS tool does this.
  • AI-readable. Markdown is what LLMs were trained on. Claude reads everything in milliseconds.
  • Portable. If Claude Code dies tomorrow, your files still work in Codex, Cursor, plain text, your own eyes. No lock-in.
  • Cheap. GitHub free + Claude Code subscription. No per-seat fees. No "Pro plan to add custom fields."

Who this is for

  • Pre-seed and seed founders building a startup
  • Solo founders still in idea/research mode
  • Two- or three-person teams that need shared context
  • Bootstrappers who want investor-grade hygiene without investor-grade overhead
  • Founders who also run consultancies to fund their bet (very common — the example data shows exactly this dual shape)

It probably won't suit you if you have > ~10 people on the team, > ~30 investors active in your pipeline, or you've raised Series A. At that scale, dedicated tools start earning their cost.

Who this is also for

A markdown repo + Claude Code is a generic substrate. Beyond founders, the same shape works for:

  • Independent consultants tracking clients + pipeline
  • Brand / design / content studios
  • Recruitment agencies (replace pipeline/{leads → won} with {sourced → placed})
  • Real estate brokers (replace with {lead → viewing → offer → closed})
  • Fractional CFOs / CMOs / CTOs
  • Coaches, therapists, private practices
  • Boutique professional services firms

The customisation prompt below renames stages and adapts the templates for any of these.


What's in the box

sample-crm/
├── CLAUDE.md                ← operating manual (Claude reads every session)
├── README.md                ← you are here
├── inbox.md                 ← rolling triage of unfiled stuff
│
├── narrative/               ← THE STORY
│   ├── one-liner.md
│   ├── problem.md
│   ├── solution.md
│   ├── why-now.md
│   ├── why-us.md
│   ├── market.md
│   ├── moat.md
│   └── faq.md
│
├── pitch/                   ← THE DECK
│   ├── slides.md            (the deck itself, branchable per audience)
│   ├── notes.md             (speaker notes)
│   └── appendix.md
│
├── model/                   ← THE FINANCIAL MODEL
│   ├── assumptions.md
│   ├── revenue-model.md
│   ├── unit-economics.md
│   ├── scenarios.md         (bear / base / bull)
│   ├── headcount-plan.md
│   └── runway.md
│
├── traction/                ← THE METRICS
│   ├── kpis.md              (weekly snapshot)
│   ├── milestones.md
│   └── updates/             (monthly investor updates archive)
│
├── product/                 ← THE THING YOU'RE BUILDING
│   ├── vision.md
│   ├── current-state.md
│   ├── roadmap.md
│   └── feedback.md
│
├── customers/               ← USERS / EARLY CUSTOMERS
│   ├── icp.md
│   └── interviews/          (one file per user interview, verbatim)
│
├── research/                ← MARKET INTELLIGENCE
│   ├── competitors.md
│   ├── market-size.md
│   └── trends.md
│
├── investors/               ← INVESTOR CRM (one file per fund/angel)
│
├── pipeline/                ← SALES (deals in stage folders)
│   ├── 1-leads/
│   ├── 2-discovery/
│   ├── 3-proposal/
│   ├── 4-active/
│   ├── 5-won/
│   ├── 6-lost/
│   └── 7-paused/
│
├── people/                  ← humans (tiered by confidence)
├── companies/               ← organisations
├── team/                    ← cap table, hiring plan
├── decisions/               ← decision journal
├── playbooks/               ← reusable methods (voice, pricing, formats)
├── numbers/                 ← week-to-week operating snapshot
├── log/                     ← monthly journal
│
├── dropzone/                ← drop ANY file, run /intake — Claude routes it
├── _dashboard.html          ← single-page founder cockpit (gitignored, generated by /dashboard)
├── .gitignore
└── .claude/
    ├── commands/            ← /today /pitch /investor-update /log-decision /new-investor /new-deal /move-stage /update-model /intake /lookalike /weekly
    └── skills/              ← customise-repo / pipeline-review / proposal-builder

Quickstart — make it yours in 10 minutes

  1. Clone the repo.

    git clone https://github.com/antfildes10/sample-crm.git my-startup
    cd my-startup
  2. Open Claude Code in the folder.

    claude
  3. Paste the customisation prompt below. Claude will interview you about your business, wipe the Kindred / Quay Studio sample data, and rewrite CLAUDE.md, playbooks/voice.md, and your story atoms in narrative/.

  4. Try it.

    /today
    

    Claude will tell you what's on your plate, what to chase, what's stale, and which decisions are due to revisit.

  5. Drop a file (PDF, screenshot, recording, CSV) in dropzone/ and run /intake — Claude reads it and files the structured info into the right place.

That's it. You have a working founder OS.


📋 The customisation prompt (copy this) 📋

Open Claude Code in the cloned folder. Paste everything inside the code block below as your first message. Claude will take it from there.

I just cloned this Founder OS repo and I want to make it mine.

Please walk me through customising it conversationally — ask me ONE question at a time, wait for my answer, then ask the next. Do not dump a list.

═══════════════════════════════════════════════════════
STEP 1 — Get oriented
═══════════════════════════════════════════════════════

Read these files first so you understand the shape:
- CLAUDE.md
- README.md
- narrative/one-liner.md
- narrative/problem.md
- pitch/slides.md
- model/assumptions.md
- traction/kpis.md
- investors/_template.md
- pipeline/3-proposal/bramwell-mortgages.md
- playbooks/voice.md
- playbooks/pipeline-stages.md

Then tell me, in 4 sentences, what the structure is and how the layers connect (story → deck → model → traction → relationships → decisions). Wait for me to say "good" before continuing.

═══════════════════════════════════════════════════════
STEP 2 — Interview me (one question at a time)
═══════════════════════════════════════════════════════

Q1. What's your startup / business called, and what do you do in one sentence?

Q2. What stage are you at? (Idea / pre-seed / seed / Series A / bootstrapped / no-fundraise.)

Q3. Who's on your team right now? Names + roles. (One person is fine.)

Q4. Do you have any of these already, even in rough form? Tell me which:
    - A pitch deck (paste the one-liner if so)
    - A financial model (paste the headline assumptions if so)
    - A list of investors you've talked to or want to
    - A sales pipeline / waiting list / design partner list
    - User interview notes
    - A decision you've recently made that you want logged
    Pick whichever you have — we'll seed those in.

Q5. What's your sales / business pipeline shape (if you have one)?
    Default stages: 1-leads → 2-discovery → 3-proposal → 4-active → 5-won → 6-lost → 7-paused
    If you're a recruiter, broker, coach, etc. — tell me your stages and I'll rename folders.
    If you don't have a pipeline yet (idea stage), say "skip" and we'll leave it alone.

Q6. Paste an example of something you've written recently to a customer, an investor, or in a pitch document. I'll calibrate your voice from it.

Q7. What's the single most important thing on your plate this week? (Becomes the priority read at the top of CLAUDE.md.)

Q8. Want me to seed any of your real investors / customers / deals now, or keep it blank?

═══════════════════════════════════════════════════════
STEP 3 — Show me the plan
═══════════════════════════════════════════════════════

Before doing anything, give me a numbered list of what you'll change:
- Files to delete (sample data)
- Files to rewrite (CLAUDE.md, narrative/*, playbooks/voice.md)
- Folders to rename (only if my pipeline differs)
- Files to seed (from what I gave you in Q4 + Q8)

Wait for me to say "go".

═══════════════════════════════════════════════════════
STEP 4 — Execute
═══════════════════════════════════════════════════════

When I say go:

1. Delete every file in pipeline/*/ EXCEPT the _template.md
2. Delete every file in people/, companies/, investors/, customers/interviews/, decisions/, log/ EXCEPT _template.md files
3. Wipe to skeleton (keep headings, blank the data):
   - narrative/*.md (rewrite for MY business based on Q1+Q2+Q4)
   - traction/kpis.md, traction/milestones.md
   - model/assumptions.md, model/revenue-model.md, model/runway.md, model/scenarios.md, model/headcount-plan.md, model/unit-economics.md
   - product/vision.md, product/current-state.md, product/roadmap.md, product/feedback.md
   - customers/icp.md
   - research/competitors.md, research/market-size.md, research/trends.md
   - team/overview.md, team/cap-table.md, team/hiring-plan.md
   - pitch/slides.md, pitch/notes.md, pitch/appendix.md
   - numbers/this-week.md, numbers/revenue.md, numbers/runway.md
   - inbox.md
4. Rewrite CLAUDE.md: my team, my priority read, my stage, my context
5. Rewrite playbooks/voice.md based on the writing sample I gave in Q6
6. If pipeline stages differ (Q5): rename pipeline/{N}-{name}/ folders + update playbooks/pipeline-stages.md
7. Seed real entries (Q4 + Q8) into the right places: investors/, pipeline/, customers/interviews/, decisions/
8. Initialise this month's log/{YYYY-MM}.md with today's date and a starter note

═══════════════════════════════════════════════════════
DO NOT TOUCH
═══════════════════════════════════════════════════════

- dropzone/.gitkeep, dropzone/README.md
- .gitignore
- .claude/ (commands + skills work for any business)
- README.md (this file — keep it so I can re-customise later)
- All _template.md files (templates Claude uses to spawn new entries)
- playbooks/discovery.md, playbooks/pricing.md, playbooks/proposal-template.md, playbooks/pitch-format.md, playbooks/investor-update-format.md, playbooks/decision-format.md
  (Leave the structure. Suggest I edit these later to match my own methods.)

═══════════════════════════════════════════════════════
STEP 5 — Hand-off
═══════════════════════════════════════════════════════

Show me a summary:
- What was wiped
- What was rewritten
- What's in my customised CLAUDE.md (paste it)
- What's in my customised narrative/one-liner.md
- A list of suggested next prompts: /today, /pitch, /investor-update, /new-investor, /log-decision

Then tell me: "Try one of those next, or drop a file in dropzone/ and run /intake."

═══════════════════════════════════════════════════════
RULES
═══════════════════════════════════════════════════════

- Never invent business data I didn't give you. Empty fields are fine; "TBD" is fine.
- Never include "Co-Authored-By Claude" or any AI attribution in commits or file content.
- Confirm before any destructive operation.
- One question at a time. Conversational.

Begin with Step 1.

Re-running customisation later (you've changed direction, your team grew, your stages shifted)? Type /customise-repo — same workflow as a slash command.


How to add documents — the dropzone

You have a folder called dropzone/ at the root. It's the single obvious place to drop incoming files — pitch decks you've drafted in PowerPoint, signed term sheets, screenshots of investor emails, customer interview recordings, business cards, contracts, CSVs from your old CRM, anything.

How it works

  1. Drop one or more files into dropzone/.
  2. In Claude Code, type /intake.
  3. Claude:
    • Lists every file
    • Tells you what it thinks each one is (term sheet / contract / interview recording / business card / etc.)
    • Asks permission before doing anything
    • Reads each file and routes the structured info into the right place (pipeline/, investors/, customers/interviews/, decisions/, log/, people/, companies/)
    • Asks whether to move the original to permanent storage (still gitignored) or delete it
  4. You confirm. Done.

Example: a signed term sheet

You drop atlantic-bridge-term-sheet-signed.pdf in dropzone/. You run /intake. Claude:

  • Identifies it as a signed term sheet
  • Reads the PDF
  • Extracts: investor, valuation, amount, board seat, pro-rata, anti-dilution
  • Asks: "Append these to investors/atlantic-bridge.md's activity log? Update team/cap-table.md with the post-money projection? Move the PDF to investors/atlantic-bridge/contracts/2026-04-15-term-sheet.pdf (gitignored)? Log a decision via /log-decision atlantic-bridge-lead?"
  • You say yes
  • The summary lands in git. The PDF stays on your laptop. Your co-founder can read the summary without ever seeing the signed PDF.

Example: a customer interview recording

You drop 2026-04-15-aine-call.m4a. You run /intake. Claude:

  • Identifies it as an audio recording
  • Transcribes (if tools available) or notes "manual transcription needed"
  • Extracts: who, when, key quotes, ICP fit signal, pilot fit, action items
  • Creates customers/interviews/2026-04-15-aine-stafford.md
  • Updates people/aine-stafford.md with new exchange
  • If a quotable insight exists, flags it for narrative/problem.md

What to drop

File type What Claude does
PDF (term sheet, contract, signed agreement) Extracts terms → activity log
Pitch deck (.pptx, .pdf) Pulls slide content → cross-references against narrative/
Screenshot of investor email / DM Reads, logs to investors/{slug}.md
Meeting recording (.m4a, .mp4) Transcribes → customers/interviews/ or investors/{slug}.md
Email export (.eml, .txt) Parses → activity log
Business card scan Creates a Tier-3 person stub
CSV from old CRM Asks how to map → bulk-creates entries
Anything else Asks you what it is

What NOT to drop

  • Anything you wouldn't want existing on disk if your laptop got stolen
  • Source documents you need to keep authoritative elsewhere (Claude is allowed to delete from dropzone/ after processing — keep originals safe)
  • Files containing other people's confidential info that you don't have rights to process

The dashboard — your company at a glance

Run /dashboard in Claude Code → Claude reads every markdown file in the repo (including the gitignored *.local.md files where you keep sensitive numbers) → composes a single-page HTML cockpit at _dashboard.html → you open it in any browser.

A modern SaaS-product dashboard in the Linear / Monday.com / HubSpot tradition: collapsible sidebar, sticky top bar with universal search and quick actions, six tabbed views (Overview · Pipeline · Investors · Customers · Decisions · Reports), a slide-over drawer for drill-ins, and ⌘K search across everything.

Overview

Dashboard Overview — KPI tiles, priority strip, pipeline funnel, activity timeline

The first tab. What matters this week at the top, then four KPI tiles (Bank balance · MRR · Pipeline · Pre-seed), a condensed pipeline funnel, an activity timeline (avatar + actor + verb + object + relative time), and the latest customer interview quote alongside a top-investors strip.

Pipeline (kanban)

Dashboard Pipeline — kanban with 7 stage columns and Monday-style deal cards

Seven stage columns from 1-leads → 7-paused. Each column shows count + total stage value. Deal cards carry the company name, type, owner avatar (deterministic colour per name), days-since-contact dot (green / amber / red by recency), value, and Priority / Invoice late flags. Click a card → opens its source markdown. Toggle to a sortable List view via the top-right control. Filter chips above (Owner / Stage / Priority).

Investors

Dashboard Investors — donut chart, summary tiles, sortable table with status pills

Status donut (committed green, engaged blue, pitched cyan, intro-needed gray, passed dimmed) with 5 tracked / €50K soft in the centre. Three summary KPI tiles to the right (Soft committed with progress bar, Days to close, Active conversations). Sortable table with status pills + priority pills + cheque ranges + last-contact dates. Click a row → slide-over drawer with the investor's full markdown.

Customers

Dashboard Customers — KPI tiles, customer list with type pills, recent interview quotes

Four KPI tiles (Paying / Pilots / Total customers / Avg ACV) on top. Two-column body: customer list with type pills (paying green, pilot amber) and MRR per row, alongside recent interview quote cards with ICP yes-ideal / ICP yes chips.

Decisions

Dashboard Decisions — KPI counts and decision cards sorted by revisit-due-first

Four KPI tiles (Decided · Due to revisit · Overdue · Reversed). Decision cards in a 2-up grid, sorted with revisit-due-first (red border when overdue, amber when within 30 days). Each card shows the decision ID, status pill, title, summary, decided date, days-until-revisit, and owner avatar.

Reports

Dashboard Reports — 12-month trend chart, 90-day activity heatmap, runway burn-down

The chart-heavy tab. Three-line trend chart (MRR · Pipeline · Pilots) with 3/6/12-month tab switcher. Below: 90-day GitHub-style activity heatmap (in Anthropic-orange palette, hover for daily detail) and a 52-week runway burn-down with current-burn vs post-seed projection.

Universal search (⌘K)

Press ⌘K (or click the search bar) → an overlay opens that searches across deals, investors, customers, decisions, and interviews simultaneously. Result types are grouped, results click through to the source markdown.

The gitignore story

The dashboard contains your live bank balance, your soft-committed term-sheet numbers, your cap-table draft. None of that should be on GitHub.

So:

  • _dashboard.html is gitignored. Never pushed.
  • **/*.local.md is gitignored. This is where you keep sensitive notes (e.g. numbers/bank-balance.local.md, team/cap-table-detail.local.md, personal-notes.local.md). Claude reads them when generating the dashboard. They never leave your laptop.
  • The committed markdown files reference the local files where relevant ("see numbers/bank-balance.local.md for live balance"), so co-founders pulling the repo know the structure without seeing the numbers.

Refreshing

The dashboard is static — it doesn't auto-refresh. Re-run /dashboard whenever you want a fresh view. On macOS:

open _dashboard.html      # opens in default browser

On Linux: xdg-open _dashboard.html. On Windows: start _dashboard.html.


What never gets pushed to GitHub (the .gitignore)

The repo is in git, which means anything you commit gets pushed (publicly, or to a private repo — still visible to whoever has access). The .gitignore decides what stays on your laptop and what goes up.

The principle: markdown summaries in git. Raw PII never. Audit trail without leak risk.

What's blocked by default:

Pattern Why
dropzone/* (except .gitkeep + README.md) You drop sensitive stuff here. Stays local.
.env, *.key, credentials.json, secrets/ API keys, OAuth tokens. Obvious.
**/bank-statements/, **/*-statement-*.pdf Raw bank exports — markdown summary in numbers/runway.md is in git. The PDF isn't.
**/contracts/*.pdf, **/contracts/*.docx, **/signed/ Signed agreements. Terms summary is in markdown. The signed PDF stays local.
**/*.local.md, **/scratch/, **/_drafts/ Scratch notes you want Claude to read locally but never commit.
**/*.psd, **/*.ai, **/*.sketch, **/*.fig Source design files — too big, rarely change here.
.DS_Store, Thumbs.db, .idea/, .vscode/ Editor and OS noise.
.claude/local/, .claude/settings.local.json Per-machine Claude settings.

To check what would be committed before pushing:

git status
git diff --stat HEAD

If you accidentally commit something sensitive: tell Claude "I just committed a file I didn't mean to. Help me remove it from history." It'll walk you through the right move (git rm --cached, git filter-repo, or BFG depending on what's needed).


Day-to-day prompts

After you've customised the repo, these are the prompts you'll use most often.

Daily

  • /today — what to do, what to chase, who's waiting on you, decisions due to revisit
  • "What's the biggest cash lever this week?"
  • "Which deal / investor is most likely to slip?"

Founder workflows

  • /dashboard — regenerate _dashboard.html (single-page cockpit with bank balance, runway, pipeline kanban, investor table, recent decisions, KPI trends, activity feed). Reads every markdown in the repo INCLUDING gitignored *.local.md files. The dashboard is itself gitignored — it contains sensitive numbers, never goes to GitHub.
  • /pitch — regenerate pitch/slides.md from narrative/, traction/, model/, team/. Same data, freshly composed.
  • /pitch vc — same but framed for VCs.
  • /pitch customer — framed for prospects.
  • /investor-update — generate this month's investor update from the repo into traction/updates/.
  • /log-decision pricing-hold — capture a decision (Annie Duke style).
  • /new-investor atlantic-bridge — spin up an investor file with thesis + fit + intro paths.
  • /update-model — change a model assumption, recompute scenarios + runway.

Sales workflows

  • /new-deal galway-fintech — a new prospect just landed
  • /move-stage bramwell-mortgages 4-active — they signed
  • /lookalike mossfield-botanicals — find 10 prospects that look like our last closed-won and draft cold messages

Anything

  • /intake — process whatever's in dropzone/
  • /pipeline-review — structured weekly sanity check
  • /weekly — generate this week's update

Branching for audiences

git checkout -b investor-pitch

Then in Claude:

"Rewrite CLAUDE.md and pitch/slides.md as if speaking to a seed investor. Keep the data, change the framing."

git diff main shows you exactly what changed between the founder view and the investor view. No SaaS tool does this.


Folder reference

Path What's in it Edit how often
CLAUDE.md Operating manual, auto-loaded every Claude session Once per quarter
inbox.md Triage list Daily
narrative/*.md Story atoms — pulled by deck + investor updates When story sharpens
pitch/slides.md Deck content. Branchable per audience Per-pitch
model/*.md Financial model — assumptions, scenarios, runway Monthly
traction/kpis.md Weekly KPI snapshot Weekly
traction/milestones.md Targets and outcomes Weekly
traction/updates/ Monthly investor update archive Monthly
product/*.md Vision, current state, roadmap, feedback Monthly
customers/icp.md Who you're for Quarterly
customers/interviews/ One file per user interview Per interview
research/*.md Competitors, market, trends Quarterly
investors/{slug}.md One per fund/angel — thesis, status, intros Per investor touchpoint
pipeline/{stage}/{deal}.md One deal per file in stage folder Per deal
people/{slug}.md Humans, tiered by confidence Per touchpoint
companies/{slug}.md Organisations Quarterly
team/*.md Cap table, hiring plan, advisors Per change
decisions/D{date}-{slug}.md One per material decision When decisions happen
playbooks/*.md Reusable methods Once, then rarely
numbers/*.md Operating week-to-week numbers Weekly
log/{YYYY-MM}.md Monthly journal Daily
dropzone/ Drop files for Claude to file As needed
.claude/commands/ Slash commands (sector-agnostic) Rarely
.claude/skills/ Auto-loaded by relevance Rarely

What you'll need to clean / replace

If you skip the customisation prompt and want to clean manually, here's the explicit list:

Files to delete entirely

  • All pipeline/*/ files EXCEPT _template.md
  • All people/ files EXCEPT _template.md
  • All companies/ files EXCEPT _template.md
  • All investors/ files EXCEPT _template.md and README.md
  • All customers/interviews/ files EXCEPT _template.md (if any)
  • All decisions/ files EXCEPT _template.md
  • All log/ files

Files to rewrite from scratch

  • CLAUDE.md — describes Kindred + Quay Studio currently. Replace with your team/business.
  • playbooks/voice.md — currently captures the example voice. Rewrite.
  • narrative/one-liner.md, problem.md, solution.md, why-now.md, why-us.md, market.md, moat.md, faq.md — the story atoms.
  • pitch/slides.md, pitch/notes.md, pitch/appendix.md — the deck.
  • model/assumptions.md, revenue-model.md, unit-economics.md, scenarios.md, headcount-plan.md, runway.md.
  • product/*.md.
  • customers/icp.md.
  • research/*.md.
  • team/overview.md, cap-table.md, hiring-plan.md.
  • traction/kpis.md, traction/milestones.md.

Files to wipe to skeleton (keep headings, blank the data)

  • numbers/this-week.md, numbers/revenue.md, numbers/runway.md
  • inbox.md

Files to edit but keep the structure

  • playbooks/discovery.md, pricing.md, proposal-template.md, pipeline-stages.md, pitch-format.md, investor-update-format.md, decision-format.md

Files to leave alone

  • README.md (this file)
  • .gitignore
  • dropzone/.gitkeep, dropzone/README.md
  • All .claude/ commands + skills
  • All _template.md files

License + credits

MIT. Take whatever's useful, fork it, ship your own version.

Built as the demo artefact for a Claude Code Dublin talk: "How to use a GitHub repo as your company's brain."

This pattern owes obvious debts to:

  • Brad Feld's CompanyOS — running a VC firm from markdown files
  • Garry Tan's gstack + gbrain — YC-shape engineering team in skills + 4,000+ contact CRM
  • Karpathy's LLM Wiki — raw → wiki → CLAUDE.md, knowledge that compounds
  • Geoffrey Litt's malleable software — Notion-MCP, slash commands as live tooling
  • Annie Duke + Shane Parrish — the decision journal pattern
  • dkorobtsov/pitch-deck plugin — branches per audience for fundraising
  • Anthropic's own How Anthropic teams use Claude Code documentation
  • Sahil Lavingia, Dennis Yang, and the wave of 2026 Substack practitioners building markdown OSes in public
  • Danielle Morrill's cooking-with-claude — for the kitchen analogy that ties it all together

If this is useful, tell another founder. If you build a sector-specific fork (recruitment, real estate, fractional CFO, coaching, etc.), open a PR adding it to a list of community forks.

About

No description, website, or topics provided.

Resources

Stars

5 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors