Pricing

Build knowledge-base products, not publish pipelines

Consultants, Obsidian teams, and subject-matter experts use TPS Report to codify reports, publish member-gated collections with public teasers, and power agent chat on a Graph RAG–indexed corpus — Layer 1 publish + Layer 2 AI brain in one platform.

Member-gated KB portals Graph RAG metadata Optional Obsidian sync

Why KB builders hit a wall

Publish Stack Fragmentation

Obsidian for writing, Quartz for static HTML, Stripe for gating, a RAG pipeline for chat — four tools, four failure points before your KB product ships.

Flat Docs, Dumb Retrieval

GitBook and generic RAG treat every page equally. Agents pull wrong chunks, miss canonical sources, and hallucinate when context is ambiguous.

Expertise Trapped in Vaults

Your best reports live in Obsidian or Notion — private, unindexed, unmonetized. Turning expertise into a product means months of custom engineering.

Loading use cases...

Who builds with TPS Report

From solo experts to KnowOps agencies — teams shipping gated KB products with agent-ready metadata.

ProfessionalCurrent RealityWith TPS ReportImpact
Knowledge Consultant
Ships vertical KB products for clients		Every engagement rebuilds Obsidian → static → paywall → RAG. Margins erode on glue work.One platform: codify reports, gate access, index for agents. Deliver a branded KB product in days, not quarters.3 months → 1 week
Obsidian Power User
Digital garden / second brain		Publish plugins render HTML but lack subscriber tiers, agent metadata, or chat on the vault.Optional Obsidian sync into TPS Report. Keep vault workflow; add publish, gating, and Layer 2 AI brain.Weeks of DevOps → same-day publish
Agency / KnowOps Team
Multiple client knowledge bases		GitBook per client, separate vector DBs, no shared metadata contract across KB products.Scoped collections per client with consistent Graph RAG frontmatter. Scale KB delivery without one-off stacks.Per-client stack → repeatable playbook
Subject-Matter Expert
Monetizing research & reports		PDFs and Substack posts are not agent-queryable. No structured defer/canonical routing for complex topics.Publish report collections with public teasers and member gates. Signups unlock the library; subscribers chat with your codified corpus.Manual Q&A → self-serve AI on your KB
Internal Enablement Lead
Team wiki → customer-facing KB		Notion/Confluence works internally but cannot become a gated, agent-ready product without a rewrite.Migrate or author in TPS Report. Same content model serves humans (publish) and agents (Graph RAG index).Dual systems → single source of truth

Knowledge Consultant
Ships vertical KB products for clients

Current Reality

Every engagement rebuilds Obsidian → static → paywall → RAG. Margins erode on glue work.

With TPS Report

One platform: codify reports, gate access, index for agents. Deliver a branded KB product in days, not quarters.

Impact

3 months → 1 week

Obsidian Power User
Digital garden / second brain

Current Reality

Publish plugins render HTML but lack subscriber tiers, agent metadata, or chat on the vault.

With TPS Report

Optional Obsidian sync into TPS Report. Keep vault workflow; add publish, gating, and Layer 2 AI brain.

Impact

Weeks of DevOps → same-day publish

Agency / KnowOps Team
Multiple client knowledge bases

Current Reality

GitBook per client, separate vector DBs, no shared metadata contract across KB products.

With TPS Report

Scoped collections per client with consistent Graph RAG frontmatter. Scale KB delivery without one-off stacks.

Impact

Per-client stack → repeatable playbook

Subject-Matter Expert
Monetizing research & reports

Current Reality

PDFs and Substack posts are not agent-queryable. No structured defer/canonical routing for complex topics.

With TPS Report

Publish report collections with public teasers and member gates. Signups unlock the library; subscribers chat with your codified corpus.

Impact

Manual Q&A → self-serve AI on your KB

Internal Enablement Lead
Team wiki → customer-facing KB

Current Reality

Notion/Confluence works internally but cannot become a gated, agent-ready product without a rewrite.

With TPS Report

Migrate or author in TPS Report. Same content model serves humans (publish) and agents (Graph RAG index).

Impact

Dual systems → single source of truth

Why TPS Report is different

Codify Once, Publish & Index

Author in the online editor or sync from Obsidian. Graph RAG metadata (hyde_questions, defers_to, canonical_for) travels with every report.

Gated KB Products

Public previews for SEO, member-only reports for depth, and a built-in signup funnel—readers return to the same page unlocked. Ship a monetized portal without wiring auth yourself.

Layer 2: AI Brain Included

Chat and agents retrieve from your published corpus — not a file dump. Metadata routing tells agents which report is canonical and which to skip.

Build vs. stitch-together

DIY: SSG + RAG + gating

Obsidian / MD authoring setup 8 hours
Quartz / Astro static pipeline 24 hours
Auth, plans, paywall 40 hours
RAG ingest + chunk tuning 32 hours
Agent chat UI + hosting 24 hours
Total: ~128 hours ($12,800+) before first KB product

With TPS Report

Codify reports + metadata 4 hours
Publish + member gate + funnel 1 hour
Index + Graph RAG routing automatic
Enable chat on corpus 1 hour
Client handoff / subscriber launch 2 hours
Total: ~8 hours to live KB product

Result: ship KB products, not infrastructure projects

Consultants productize expertise instead of maintaining publish pipelines. Same margin on delivery — less ops drag.

Ready to ship a KB product with an AI brain?

Codify your expertise, publish gated collections, and let agents retrieve the right context from your corpus.

Layer 1: Publish Layer 2: AI brain Graph RAG metadata