Practacular — Practice-Multiplier Write-up
How an Obsidian graph substrate gives accountants advanced semantic RAG plus flat grep-RAG over an entire practice.
This page is a structural placeholder. The full practice-multiplier write-up — describing the Obsidian graph as a substrate, how advanced RAG and grep-RAG combine, what's queryable in plain English, and the productivity numbers we've measured — is in active drafting and will publish here. Want a preview by email? Get in touch.
The thesis in one sentence
An accounting practice operates at higher leverage when its accumulated knowledge — every tax review, every compliance memo, every client engagement, every workpaper — becomes instantly queryable in plain English by every accountant on the team.
The substrate: an Obsidian graph as the knowledge layer
Practacular's substrate isn't a database in the conventional sense. It's an Obsidian vault — a directory of plain-text Markdown files with structured frontmatter and explicit cross-references — deployed across the practice. Every accountant has access to it. Every change is version-controlled. The whole graph is queryable two ways:
- Advanced semantic RAG — vector search across the embedded graph for "soft" matches: queries that find conceptually similar tax positions, comparable engagements, related compliance precedents.
- Flat grep-RAG — exact-string search across the corpus for "hard" matches: a specific section of the Income Tax Act, a specific client name, an exact date. Faster than semantic search and more deterministic.
Both paths feed the same LLM. The accountant asks one question; the substrate routes between paths or blends both, depending on what the question needs.
What's in the graph
- Every tax review the practice has ever completed, structured by entity, year, and outcome.
- Every compliance memo, with the regulatory citations indexed.
- Every client engagement, with deadlines, deliverables, and decisions linked.
- Every workpaper, with the client and engagement context attached.
- The institutional knowledge that used to live only in senior partners' heads — now searchable.
What changes for the practice
A junior accountant asks Claude in plain English: "What's our position on cross-border IP holding companies for South African residents?" The substrate retrieves the three most-relevant prior memos, the relevant SARS interpretation note, and a record of how the practice has positioned similar arrangements before. The accountant gets a grounded answer in seconds — not a Slack message to the senior partner, not three hours of digging through a shared drive.
Tax review cycles compress because the precedent is already structured. Compliance lookups stop being manual. Onboarding a new accountant becomes a question of giving them substrate access — they have instant peripheral vision over the practice's accumulated experience.
The numbers we've measured
[Specific productivity metrics from live customer practices will publish here once we have written permission from each customer to attribute the numbers. Indicative range from internal benchmarks: tax review prep time -40%, compliance lookup -65%, junior-onboarding-to-productive -50%.]
The three risk gates apply here too
Audit log on every query and every commit. Credential boundary so the substrate never types into client systems on its own. Outbox-gated approval for any write-back to client records. Same constraints, same safety story, different vertical.
What this means for your practice
The practice-multiplier pattern isn't unique to accountancy. Any professional-services firm with accumulated knowledge — legal, advisory, engineering, architecture — fits the same shape. If you're curious whether the pattern fits yours, get in touch.
Related
Atteste — Operator-Substrate write-up →
Visit practacular.com →
← Back to Context Design Co