Archaius Creative

How task-level semantic search cut Archaius Creative's quote turnaround to under 2 minutes

Quoting took 45 minutes and still depended on who you asked. Now it takes 2, and the answer is always the same.

Video ProductionCustom AI AutomationUSA
95%Reduction in quoting time
±10%Estimate accuracy against actual hours
300+Past projects turned into a live quoting engine
The Challenge

A quoting process built on memory and guesswork

Archaius had hundreds of completed projects, logged hours, and detailed time-tracking sitting in their system. The problem was getting to it.

Every new inquiry meant 45 minutes of manual digging through old files, trying to piece together comparable work from memory. And because there was no system anyone could draw from, the number you got depended entirely on who built it.

It wasn't just slow. It was also fragile. The studio's best estimating instincts lived in a few people's heads, buried alongside years of project data trapped in free-form descriptions that nothing could search. As inquiry volume grew, so did the inconsistency.

Our Approach

A two-phase build that delivered a live quoting engine

Agent Loopr's foundation was Archaius's underlying data. The entire build followed a single principle: Turn 300 finished projects into a search engine that replicates how the studio's best estimator actually thinks, powered by Claude (claude-sonnet-4-6).

01
Phase 1 · Structured data foundation

Custom Teamwork MCP server, built with Claude Code

Rather than relying on manual exports, Agent Loopr built a real MCP server, Anthropic's own protocol for connecting AI systems to external tools, directly into Archaius's existing Teamwork system. The server was built using Claude Code and pulled the studio's complete project history and time-tracking records out cleanly, automatically, and in full.

Data extraction

Full history

Pulled from Teamwork via a purpose-built MCP server.

02

Data audit and quote variable definition

Every project record was reviewed to understand what existed and where the gaps were. From there, the variables that genuinely determine project cost were identified: runtime, complexity, scope, client-supplied assets, and task-level breakdowns across editing, motion graphics, color, and audio.

Cost drivers identified

5 variables

Runtime, complexity, scope, assets, and task-level breakdowns.

03

Full history restructured into a two-layer dataset

The entire project history was reorganized into a project table linked to a task table. Details buried in free-form descriptions were pulled out and mapped into consistent, searchable fields, giving the system a clean and reliable foundation to work from.

Data model

2 layers

Projects linked to tasks, every field consistent and searchable.

04
Phase 2 · The AI quoting engine

Six-agent pipeline turns raw notes into structured signal

The extraction layer runs as a sequence of specialized agents, data preparation, extraction, filtering, categorization, verification, and human-in-the-loop review. Claude reads each project's raw notes the way an experienced estimator would, pulling out the fields that actually drive a quote.

Specialized agents

6 agents

Prep, extract, filter, categorize, verify, and human review.

05

Task-level semantic search with Claude and Qdrant

The matching engine searches across individual tasks, not just whole projects. Embeddings stored in a Qdrant vector database surface genuinely comparable work, regardless of which project it originally came from.

Search granularity

Task-level

Qdrant embeddings surface comparable work across projects.

06

Claude handles the scoring and reasoning layer

Matching isn't just keyword similarity. Claude weighs how closely each past task resembles the new one, discounts outlier “nightmare projects,” favors recent work, and scales its reasoning by task type, since a longer runtime affects editing far more than motion graphics.

Matching method

Reasoned, not keyword

Weighted by similarity, recency, and task type.

07

An evaluation harness keeps Claude's output honest

Every extraction is scored against verified historical actuals, field by field, measuring how closely Claude's output matches the real numbers from past projects. The team trusts the system's accuracy because it's tested, not assumed.

Accuracy

Tested, not assumed

Scored field-by-field against verified historical actuals.

08

Team-wide quoting interface with full transparency

A clean FastAPI-backed web interface brings the whole system together. Any team member can enter a handful of project details and receive a task-level hour breakdown in seconds. Every estimate shows exactly which past projects and tasks it drew from, so the output is auditable and open to human judgment.

Quote turnaround

Seconds, auditable

Task-level breakdown with a trail back to comparable work.

Our Impact

What changed when 300 projects started working for them

<2minQuote turnaround

45 min to under 2 min

Quote turnaround dropped by 95%. A process that used to pull someone off billable work for nearly an hour now finishes in seconds, for any team member using it.

Accurate to within ±10%

Every estimate is grounded in Archaius's verified project history. Backed by an evaluation harness that scores Claude's output against real historical numbers, the studio can now send clients figures they can stand behind.

±10%Estimate accuracy
300+Projects queryable

300+ projects now queryable in seconds

Years of finished work that lived in free-form descriptions and individual memories became a structured, searchable asset. Every new project added makes the engine sharper.

1 source of truth

Estimates no longer depend on the estimator. Any team member runs the same query and receives the same defensible output, with a clear trail back to the comparable work behind every number.

1Source of truth
Anyone on the team can quote a job in two minutes now and back it up with real numbers. The estimate doesn't change based on who you ask.
Archaius CreativeStudio team · AI quoting engine
Placeholder · client quote pending approval
The Stack

Tools and technologies used on this project

AI & Retrieval

Reasoning, embeddings, and task-level semantic search.

icon1
icon2
icon3

Backend & Data

A typed API over a structured, two-layer project dataset.

icon1
icon2

Source & Deploy

Project data in, a live quoting engine out.

icon
icon2

One coherent stack — extraction, retrieval, and reasoning, grounded in real project history.

Ready to talk about
what you're building?

Book a 30-minute call and come as you are. No preparation needed on your end.

Book a Discovery Call