narratiQ
narratiq.de ↗Founder & CTO — fully remote, sole engineer
An analysis platform that helps publishers review manuscripts. Designed, built, and operated end to end — architecture, backend, frontend, and deployment — as the only engineer. Built as a classical, self-authored Python workflow that calls language models with structured, auditable output, not an agent system: there is no orchestrator and no autonomous agent layer in the product. Runs in production on DigitalOcean and Vercel, currently processing manuscripts in early pilot runs with a publisher. Top-10 finalist, CONTENTshift 2026, with a presence at the Frankfurt Book Fair.
Chapter-aware chunking instead of retrieval
Manuscripts that don't fit a single model call are split along chapter boundaries and refined sequentially — a deliberate alternative to embeddings and vector search, because a full review has to judge the whole work, not just the most similar passages.
Cost telemetry per model call
Every call is logged with prompt, completion, and cache tokens, feeding a daily cost cap — visibility into spend without checking a provider dashboard.
AI stack rebuilt around fewer, declarative calls
Nine separate calls became one merged call plus four genre calls, described as data rather than scattered logic — cost per full analysis dropped to about a third.
Time saved, in my co-founder's estimate
My co-founder, a former publishing director, puts a manual manuscript screening at roughly 25 hours; with the platform it takes about four.
