Standard engagement
Prompt & Eval Library Setup
Stop versioning prompts in Notion. Treat them like code.
A one-time install: your prompts versioned in git, evals running in CI, and an A/B harness so prompt changes ship like any other deploy. Two weeks. Hand-off to your team after.
from $3,500
2 weeksPromptfooBraintrustLangSmithGitHub Actions
What ships during the engagement.
Prompt repo structure + naming conventions
Eval suite — at least 3 quality dimensions per prompt
GitHub Actions workflow that runs evals on PR
What you walk away with.
- Prompts in git with diff history, not in a Notion doc
- CI evals on every prompt PR
- A/B harness for safe prompt rollouts
“They scoped, shipped, and operated our RAG pipeline in twelve days. Citation accuracy on our eval set landed at 92%, and ongoing tuning costs us less than a Slack seat.”
- We use LangChain prompts — does that work?
- Yes. We support raw text, LangChain ChatPromptTemplate, and Anthropic message format out of the box.
- What if a prompt change breaks evals?
- CI fails the PR. The author sees a diff of which eval cases regressed and by how much.
Want to scope Prompt Library?
A short call to confirm fit and timeline.