A production RAG system has roughly five recurring cost centers and one large upfront cost.
The upfront cost is the build itself: engineering time to connect data sources, chunk and clean documents, stand up retrieval, write evaluations, and ship a usable interface or API.
For a mid-sized internal system, say two to five data sources, a few hundred daily users, hybrid search with re-ranking.
That build typically runs thirty to eighty thousand dollars over eight to twelve weeks.
Enterprise systems with SSO, audit logging, and content governance land higher, often a hundred twenty to two fifty before the first month of production traffic.
Now, here is the thing most proposals get wrong.
They start at ingestion and embeddings because that is where the pipeline starts, and teams spend disproportionate anxiety there.
But in dollar terms, embeddings are almost always the smallest line.
Embedding an entire ten-million-page corpus costs around two hundred and sixty dollars.
Rindexng quarterly is still under eleven hundred dollars per year.
The number is basically a rounding error.
What is not a rounding error is the ingestion engineering around those embeddings.
Pulling from Confluence, SharePoint, Salesforce, S3, Postgres, and a handful of SaaS APIs, handling PDFs with tables, deduplicating near-identical document versions, enforcing access controls so the retriever cannot surface a document the user is not supposed to see.
Expect twenty-five to forty percent of the build budget here.
The API integration work is usually larger than the model work.
A production RAG system has roughly five recurring cost centers and one large upfront cost.
The upfront cost is the build itself: engineering time to connect data sources, chunk and clean documents, stand up retrieval, write evaluations, and ship a usable interface or API.
For a mid-sized internal system, say two to five data sources, a few hundred daily users, hybrid search with re-ranking.
That build typically runs thirty to eighty thousand dollars over eight to twelve weeks.
Enterprise systems with SSO, audit logging, and content governance land higher, often a hundred twenty to two fifty before the first month of production traffic.
Now, here is the thing most proposals get wrong.
They start at ingestion and embeddings because that is where the pipeline starts, and teams spend disproportionate anxiety there.
But in dollar terms, embeddings are almost always the smallest line.
Embedding an entire ten-million-page corpus costs around two hundred and sixty dollars.
Rindexng quarterly is still under eleven hundred dollars per year.
The number is basically a rounding error.
What is not a rounding error is the ingestion engineering around those embeddings.
Pulling from Confluence, SharePoint, Salesforce, S3, Postgres, and a handful of SaaS APIs, handling PDFs with tables, deduplicating near-identical document versions, enforcing access controls so the retriever cannot surface a document the user is not supposed to see.
Expect twenty-five to forty percent of the build budget here.
The API integration work is usually larger than the model work.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.