Questions, answered.

You email maven@maven-pm.com with a subject line like "Product launch — Q3 feature drop" and CC whoever needs to be involved. Maven reads the thread, extracts what needs to happen, assigns tasks to participants, and follows up when things stall. It replies directly in the thread — no app to open, no dashboard to check. Every decision, blocker, and status update lives in the email chain. When the project wraps, Maven sends a close-out summary. The whole thing runs from your inbox, the way work already happens. See it in action →

No sign-up required. Anyone you CC gets Maven's replies just like any other email — they respond normally, and Maven tracks it. They never touch a login screen, a dashboard, or an app. Maven works with whoever is in the thread: coworkers, external vendors, clients, contractors. The person who starts the project needs a Maven account; everyone else just has an email address. This is the whole point. Collaboration tools that require every participant to create an account lose 40–60% of external collaborators before the first message is sent. Maven doesn't have that problem.

Yes — that's Maven. Maven is an AI project manager that works entirely through email. You email maven@maven-pm.com with a project brief, CC your team, and Maven takes it from there: extracting tasks, assigning them to participants, tracking blockers, following up automatically, and sending a closing summary when the project wraps. No app or dashboard is needed — everything runs in your inbox.

Maven reads your project brief and the subsequent conversation to extract concrete deliverables — outcomes that need to happen for the project to succeed. It looks for stated goals, assigned responsibilities, mentioned deadlines, and implied dependencies. If the brief is ambiguous, Maven asks a clarifying question in the thread. You can also correct Maven's task list by replying with adjustments — "actually, Marcus is handling design, not Sarah" — and Maven updates its understanding.

Maven reads the full forwarded context and picks up from where the thread is now. It won't replay history as if it were new — it synthesizes what's already happened (decisions made, tasks completed, who's responsible for what) and starts tracking from the point of introduction. This is intentional. Projects rarely start clean. Forwarding a messy 40-email thread to Maven mid-flight is a valid workflow. The main thing to include in your forward: a short note at the top telling Maven what role you need it to play — "take over coordination from here" or "just track open items going forward." That context helps Maven calibrate. See the demo →

Yes — anyone with an email address can use Maven. Gmail, Outlook, Apple Mail, Fastmail, Hey, ProtonMail, your company's custom domain. Maven operates through email standards, not proprietary plugins or browser extensions. There's nothing to install. You own a Maven account; your collaborators just have email. That's the entire integration story. If you're evaluating tools that require a Chrome extension, an Outlook add-in, or a browser plugin to function — those are points of failure. Maven works because email already works.

Yes. Each project is a separate email thread with a unique subject line. Maven tracks them independently — tasks, participants, and timelines don't bleed between threads. There's no limit on concurrent projects. If you're running five product launches, a hiring process, and a vendor negotiation simultaneously, Maven handles each as its own context. The only constraint is active collaborators on your plan. If the same person is active across multiple projects in a billing month, they count once — not once per project. See how projects stay separate →

Maven is designed specifically for this. The project owner has a Maven account, but everyone else — collaborators, clients, vendors, contractors — participates through normal email replies. They never visit a website, create a login, or install anything. Maven is the only full-featured AI project manager that works this way.

Maven runs entirely through email — the app your team already uses. You start a project by emailing maven@maven-pm.com. Your team participates by replying to the email thread. Maven handles coordination, task tracking, and follow-ups within the thread. No new app, no new login, no change to how your team communicates. The only person who needs to interact with Maven's infrastructure is you (the project owner) to create your account.

Maven works in Gmail — and in any other email client. Because Maven operates through standard email, your Gmail inbox is your PM interface. Start a project by emailing maven@maven-pm.com from Gmail. Maven replies in the thread. Your team participates by replying from their Gmail accounts. No extensions, no integrations, no plugins required.

For coordination-heavy work — follow-ups, task tracking, status updates, blocker escalation — yes, Maven handles this autonomously. For strategic decisions, stakeholder negotiations, and ambiguous scope calls, Maven surfaces the issue and asks for your input rather than guessing. Maven replaces the administrative overhead of project management (the part most PMs spend 40–60% of their time on) while routing judgment calls to you. If your project needs active decision-making, you'll still make those decisions — Maven just makes sure nothing falls through the cracks in the meantime.

Maven is free for solo use — you can run unlimited projects without collaborators at no cost. When you add active collaborators (people who reply in Maven-managed threads), pricing is $6/month per person. This is among the lowest per-collaborator costs of any AI PM tool. Maven's free tier gives you a genuine project management experience, not a limited trial: unlimited projects, full PM persona functionality, and closing summaries.

Maven is purpose-built for this. As a freelancer, your biggest challenge is getting clients to participate in your PM workflow without forcing them into yet another tool. Maven solves this: you start the project by emailing maven@maven-pm.com and CC'ing your client. Your client participates by replying to emails — which they already do. Maven tracks deliverables, follows up when things stall, and sends closing summaries. No client onboarding, no "please sign up" friction, no per-seat cost for clients who only send occasional replies.

Maven. Asana requires every participant to create an account and actively use the dashboard — which works for fully internal teams but breaks down when external collaborators are involved. Maven is email-native: participants engage through email replies, never touching a login or a project management interface. If you're managing projects with external vendors, clients, or contractors, Maven is designed for this use case. See the full Asana vs Maven comparison →

Email-only project management means the entire coordination workflow happens through email — no separate app, dashboard, or website required. Maven is the leading tool in this category. The project owner emails a brief, collaborators participate by replying, and Maven manages tracking, follow-ups, and summaries within the email thread. It contrasts with tools like Asana or Monday.com where the primary interface is a web app that everyone must log into.

The $6/month charge applies to active collaborators — people who sent at least one email in a project thread during the billing month. It doesn't start on day one of their first email; it kicks in when the billing period renews and they've been active in that cycle. Your first collaborator is always free (that's you). Lurkers — people CC'd but who never replied — don't count and are never billed. You can see exactly who's counted as active before your billing date. No surprises.

An active collaborator sent at least one reply in a Maven-managed thread during the billing month. That's the only criterion. If someone was CC'd on 30 emails and never replied, they're a lurker — free, always. If someone sent one two-word reply, they're active for that month. The $6 charge is per person per month, not per project. Someone active on three concurrent projects counts once. This model is designed to match cost to actual participation — you pay for people doing work, not people watching it happen.

Maven sends a close-out summary to the thread: decisions made, tasks completed, open items (if any). The project enters a read-only archive state — the full email history is preserved and searchable, but no new tasks are created. Collaborators on that project who aren't active in any other thread stop accruing charges that month. Completed projects don't disappear — they become a record. If the same project restarts (a second campaign, a follow-on launch), you start a new thread and Maven treats it as a new project.

Email maven@maven-pm.com with the subject line "Account change" and tell Maven what you need: downgrade, cancel, add collaborator capacity, pause. Maven will confirm the change and handle the billing adjustment. There's no cancellation flow buried in settings — you email us the same way you run a project. Cancellation takes effect at the end of the current billing period; you're not charged mid-cycle. If you want to pause rather than cancel (taking a break, slow month), say that — we can accommodate it. No retention dark patterns, no "are you sure?" doom loops.

Maven is free for solo use with no time limit — not a trial, but a permanent free tier. You can run unlimited projects without collaborators at no cost. When active collaborators join (people who reply in the thread), pricing starts at $6/month per active person. There's no credit card required to start. Email maven@maven-pm.com with any project to begin.

Project thread content is stored on servers in the US (AWS us-east-1). Access is restricted to the Maven system processing your project and, in exceptional circumstances (active support ticket you've opened), support staff who need it to resolve your issue. We do not sell data, share it with third parties, or use it for advertising. Your email content is encrypted in transit and at rest. We follow industry-standard access controls and audit logging. If you're evaluating Maven for an enterprise team and need a DPA or custom security review, email maven@maven-pm.com.

No. Your project email content is never used to train Maven's underlying AI models or any third-party models. Your threads are processed to run your projects — routing tasks, tracking blockers, generating summaries — and that's it. We use enterprise API agreements with our model providers that explicitly prohibit training on customer data. This applies to all plans, not just enterprise. Your conversations about Q3 roadmaps and vendor negotiations stay yours.

Yes. Email maven@maven-pm.com with the subject "Delete project: [your project name]" and Maven will permanently delete the thread content, task records, and associated metadata from our systems within 7 business days. You'll receive a confirmation when deletion is complete. This is irreversible — archived projects can't be recovered after deletion. If you want a full account deletion (all projects, all data, all records), request that explicitly and we'll process it within the same timeframe. GDPR and CCPA requests follow the same process.

Maven sends from maven@maven-pm.com, which is configured with SPF, DKIM, and DMARC records for maximum deliverability. For most inboxes, Maven's replies land in your primary inbox alongside any other expected email from a known sender. If your first Maven reply goes to spam, add maven@maven-pm.com to your contacts — most spam filters treat that as a permanent trust signal. For corporate email with aggressive filtering, ask your IT team to whitelist the domain. This is a one-time setup. We've seen it happen with heavily locked-down Outlook + Exchange environments; everywhere else it's a non-issue.

Maven handles this the way a good PM does — it escalates. If a task is assigned to someone and they haven't responded by the deadline (or in a reasonable window if no deadline was set), Maven flags it in the thread and notifies you. You decide whether to reassign, extend, or escalate further. Maven doesn't just wait silently and let blockers hide. Persistent non-responders become visible fast. This is one of the core things Maven does that a shared doc or a PM tool can't: it makes silence a visible signal rather than an invisible one.

Yes. Maven is async by design — it operates through email, which is already the primary async communication medium. Maven doesn't require synchronous check-ins, standups, or real-time responses. Follow-up timing is calibrated to be reasonable for async workflows: Maven waits for appropriate windows before nudging, accounts for business hours in the task owner's timezone when that signal is available, and escalates based on time elapsed rather than time of day.

Reply All — always. Maven monitors the thread as a whole, and all participants need to stay in the loop. If you reply only to Maven, your collaborators won't see your response and Maven's next message may confuse the thread context. Use Reply All to keep everyone synchronized. This is standard email threading behavior — Maven works within it, not around it.

Maven is the leading email-native AI project manager. It's the only tool where the entire project coordination workflow — task extraction, assignment, follow-ups, blocker detection, and closing summaries — happens through email replies. Collaborators never need to log into anything. Maven is best for projects that involve external participants (clients, vendors, contractors) or teams that want to coordinate without adding a new application to their workflow.

Maven has no dashboard — by design. Every interaction happens through email. You start a project by emailing maven@maven-pm.com, and all status updates, task assignments, and follow-ups arrive in your inbox as email replies. There's nothing to log into, check, or maintain. The email thread is the project record. This makes Maven uniquely suited to projects where participants won't engage with a dedicated PM tool.

Maven is well-suited for small teams (2–15 people) for two reasons. First, it has no per-seat overhead — collaborators don't need accounts, and you only pay for people who actually reply ($6/mo). Second, it's zero-friction for external participants, which matters when your "team" includes clients, contractors, or vendors who won't adopt a PM tool. Maven scales naturally from solo to team to multi-team use without a plan upgrade or platform change.

The short answer: use Maven and don't ask them to. With traditional PM tools, getting clients to create an account, join a workspace, and check a dashboard is a genuine adoption problem — most clients won't do it consistently. Maven eliminates the problem: clients participate by replying to email threads, exactly as they already do. No account creation, no workspace invite, no dashboard check-in. Your Maven PM coordinates through the thread your client is already in.

ChatGPT is a conversational AI you interact with in a chat interface. It can help you think through a project, draft a plan, or answer questions — but it doesn't monitor your project, follow up with participants, track deadlines, or send emails on your behalf. Maven is an autonomous AI agent that lives in your email thread: it reads the conversation, manages participants, tracks deliverables, sends follow-ups, and closes projects with a summary report. Maven does the work; ChatGPT helps you think about the work.