Who EVA Is For
eva beginner 3 min read
What this means for you
EVA is sized for one. If a prospect says “we want to roll this out across the team,” that is a polite no — there is no multi-user mode and there is not going to be one.
The pitch
For the engineer who already writes Claude prompts in scratch files, EVA replaces the scratch directory with a searchable catalog they keep on their own workstation.
Who it’s for
- In: solo engineers and senior ICs running Claude prompts daily
- Out: product teams looking for shared prompt governance, marketers wanting a no-code prompt builder, students learning what an LLM is
Proof points
- Zero accounts, zero auth, zero billing surface
- Single-tenant by design — every prompt in the catalog is written for one named owner, not a team role
- Catalog ships pre-loaded with the maintainer’s working prompts; not a SaaS shell
quadrantChart title EVA fit by user type x-axis "Casual LLM use" --> "Daily prompt authoring" y-axis "Team workflow" --> "Solo workflow" quadrant-1 "Right fit" quadrant-2 "Wrong category" quadrant-3 "Use ChatGPT" quadrant-4 "Use a team tool" "Senior IC at 11pm": [0.85, 0.9] "Prompt-curious PM": [0.3, 0.55] "Five-person AI team": [0.8, 0.2] "Student learning LLMs": [0.25, 0.85]neighbors on the map
- Prompt Artefact Directory Layout scaffolding a new prompt under prompts/
- eva eval Cases, Assertions & Judges adding a new case to eval.yml