You email maven@maven-pm.com with a project brief and CC your team. Maven assigns an AI PM persona who replies in the thread, extracts tasks, assigns them to participants, follows up when things stall, and sends a structured closing summary when the project wraps. Everything happens through email. No apps, no dashboards, no logins for your collaborators. Active collaborators (people who reply) are billed at $6/month. Lurkers are free.
The full process
Detailed walkthrough
Write your project brief as an email
Open any email client — Gmail, Outlook, Apple Mail, Fastmail, or any other. Compose a new email to maven@maven-pm.com. In the subject line, put the name of your project (e.g., "Q3 marketing campaign" or "Website redesign"). In the body, describe what you want to accomplish, who is involved, any deadlines, and relevant context. There is no form, no template, no account setup required. A plain email is all you need.
CC your collaborators
Add your team, clients, vendors, or contractors to the CC field. They will receive Maven's responses as normal email replies and can participate by replying — no account creation, no app download, no login required. Anyone with an email address can collaborate on a Maven project.
Maven assigns a PM persona and reads the brief
Within minutes of receiving your email, Maven assigns a named PM persona to your project. Current personas include Sofia, Marcus, Priya, and others. The persona replies directly in your email thread, introduces themselves, confirms what they've understood about the project scope, and asks clarifying questions if the brief is ambiguous.
Tasks are extracted and assigned
Maven reads the project brief and any subsequent replies to extract deliverables — the concrete outcomes that need to happen for the project to succeed. These are assigned to specific participants based on their stated roles, expertise signals from the conversation, and ownership cues in the thread. Maven tracks status (pending, in progress, completed, blocked) for each deliverable.
Follow-ups happen automatically
When a task deadline passes without resolution — or when a participant hasn't replied in a reasonable window — Maven follows up directly in the thread. It doesn't wait silently. It nudges the responsible party, surfaces the blocker to you when it needs a decision, and escalates persistently quiet participants visibly rather than letting them hide.
Blockers are surfaced, not buried
When Maven detects a blocker — a dependency that hasn't resolved, a missing input, a conflicting requirement, or a participant who isn't responding — it flags it explicitly in the thread. Blockers don't hide in a task list that no one checks; they become visible signals in the email conversation you're already in.
Project closes with a structured summary
When all deliverables are resolved, Maven sends a close-out summary to the entire thread. The summary includes: decisions made during the project, tasks completed (with assignees), open items that weren't resolved, and a chronological overview of the project. The email thread becomes a permanent, searchable record of the project.
Common questions about how Maven works
Maven receives your email via Postmark (an email delivery service), processes the thread using a large language model (LLM) to understand context and extract tasks, and replies via the same email thread using a named PM persona. All coordination happens within the email threading protocol — Maven's replies are linked to the original thread, so your email client groups them correctly.
You email maven@maven-pm.com with a project brief and CC your team. Maven assigns an AI PM persona (like Sofia or Marcus) who replies in the thread, extracts tasks, assigns them to participants, tracks status, follows up when things stall, and sends a closing summary when the project wraps. Everything happens through email — no apps, no dashboards, no logins for your collaborators.
No. Maven works through standard email. You don't integrate Maven with your inbox, install a browser extension, or configure anything. You email an address and Maven participates in the thread. The only setup is creating a Maven account, which takes one email.
Yes. Each email thread is a separate project context. Maven tracks projects independently — tasks, participants, and timelines don't bleed between threads. There's no limit on concurrent projects.
Maven reads the forwarded context, synthesizes what's already happened, and picks up from the current state of the thread. It won't replay history as new. Include a brief note at the top of your forward explaining what role you need Maven to play going forward.
Maven infers responsibility from multiple signals: explicit assignments in the thread ("@Sarah can you handle the design?"), role descriptions in the brief, subject-matter mentions ("our developer Marcus"), and historical response patterns. When ownership is unclear, Maven asks a clarifying question directly in the thread.
Ready to try it?
Email maven@maven-pm.com with any project. Your PM persona replies within minutes.
Email maven@maven-pm.com