biz/ — the danielslater.dev business workspace

The living knowledge base for the dev-services business. Started 2026-07-17 from a multi-agent strategy session (5 Sonnet research legs → 3 Opus designs → 3 Opus adversarial critiques → 1 Opus synthesis, ~620k tokens). Daniel works with this corpus over time — every future session (Claude or otherwise) should treat it as the commercial source of truth.

Layout

File	What it is
`BUSINESS-MODEL.md`	The recommended model: positioning, ICPs, product ladder + pricing, channel plan, unit economics, 12-month roadmap, risks, KPI checkpoints.
`DECISIONS.md`	The settled-decisions log. Only entries here count as settled — the model doc proposes, this log disposes. Newest on top.
`ROADMAP.md` · `BOARD.md`	Operational plan (now/next/later) + the active-task board.
`PROSPECTS.md`	Living pipeline tracker: client prospects + partner/referral targets.
`career-opportunities.md`	Personal full-time job leads (kept here per Daniel's call; distinct from the agency pipeline).
`clients/` · `agents/`	Per-client state (metrics/data-requests) + the agent registry.
`research/`	Dated research drops, one markdown file per sweep (raw JSON alongside where it exists).

How to work with it

In Claude Code: open a session anywhere in ~/dan-hub — memory points here. Ask for updates, new research legs, or pricing changes; new research lands in research/ as a dated file, decisions get logged in DECISIONS.md.
In NotebookLM (or similar): create a notebook and add BUSINESS-MODEL.md, DECISIONS.md, and the research/*.md files as sources (markdown drops straight in; skip the .json). Re-sync sources after big updates — NotebookLM doesn't watch files.
Conventions: prices in ZAR with USD/GBP alongside; plan-math uses an R16.0/$ buffer (spot ~R16.33 as of 2026-07-17). No hospitality anywhere, ever (employer separation). Stack-agnostic capability language in anything client-facing.