Blog
Notes on knowledge work
Field notes from building a reading memory. Updated weekly.
Tags
Your reading, as one knowledge graph
You don't read in silos, so why store reading in them? Pith distils everything you save into one knowledge graph — and the adjacencies it surfaces are where the insight lives.
Every claim cites its source — and why that beats a chatbot that invents one
A chatbot will hand you a confident sentence with no idea where it came from. Pith hands you the same sentence with the saved source attached. For defensible work, that difference is the whole job.
Reading memory for your AI: Pith's hosted MCP server
Your AI assistant has no memory of what you've read. Pith's hosted MCP server gives it one — a cited reading memory it can query, with every claim linked back to its source.
The Founding Practice deal — fifty firms, locked for life.
The first 50 consulting firms that subscribe to Practice get a lifetime locked rate of €25/seat per month. No expiry, no review, no upgrade tax. Once.
Why Pith Lab? On principles and the workshops that make them real.
Pith was always the principle: what remains when you boil reading down to its essence. The lab is where that distillation actually happens, week after week.
Concepts, not folders: how a knowledge base earns its keep over time
Folders make sense when you're filing. Concepts make sense when you're thinking. A knowledge base for consultants needs the second.
Briefings, not newsletters: the right output for a consulting knowledge base
Most teams confuse curation with publication. A weekly briefing is what you actually need — and it's not the same thing as a newsletter.
Why every consulting firm should run a private knowledge base
Email threads, scattered Slack channels, shared drives. Works at three; falls apart at thirty.