Changelog

Today Neumannic ships its Phase 1 launch. The product is two surfaces: a Studio for long-form chat and document work that feels editorial rather than tabbed, and an Agents board where each kanban card is a task an AI takes from kickoff to done. Both surfaces sit on top of the same memory layer, the same pricing structure, and the same data-handling posture.

Pricing launches at five tiers. Trial gives you fourteen days to evaluate without a card. Solo is for the operator running their own brand. Team is for small agencies and in-house marketing teams. Agency is built for growing agencies running multiple clients in parallel; Agency ships at launch rather than waiting for a second release wave. Enterprise is for customers who need custom contracts and a dedicated relationship.

Every paid tier gets multi-provider AI routing. Neumannic is not locked to a single model vendor — your requests route through a mix of providers based on what each task needs, with automatic fallback if a provider is having a bad day. We never retain your prompts or model outputs at any provider; every request runs under a zero-retention commitment that we will not trade away for a faster cache.

Collaborative editing in the Studio preserves comments correctly when documents change. Comments anchor to the content they were written about, not to a line number, so editing the paragraph above doesn't orphan the review note below. Funnels — the marketing automation surface — run as linear sequences rather than branching trees; we made this choice deliberately to keep funnel maintenance simple as your team grows.

What we have not shipped in Phase 1: copying data across workspaces (the workaround is manual export/import — full migration tooling lands in Phase 2), publishing content by emailing it from your inbox (Phase 1.5), public portfolio pages for showing your work to prospects (Phase 1.5), and a few advanced collaboration patterns we are intentionally building ourselves rather than licensing. The roadmap pages will track each one as the release lands.

A note on the team that built this: every decision in the product was ratified by the founder against a single canonical spec. Where we made a trade-off, we wrote down why. Where we chose between two providers, we kept both as candidates so the choice can be reversed if a better option appears. The architecture is built to age well, not to ship first.

Thanks for being here. The docs live at the help center, support email is hello@neumannic.com, and the next release entry will go right here — the Phase 1.5 surface is already in the planning queue.