Skip to content

Explore Mintchemy

Join the private beta
Sign in

Private betaInvitations open in cohorts

Turn rough ideas into PRDs your team can build from.

A PRD workbench for product managers. Ordered Steps, AI inside each one, and a Critique that finds the gaps.

Join the private betaSee how it works

No credit card

2 of 7 Steps done

In reviewVersion 4 · saved

Checkout recovery

Step 3 of 7 · Solution · In progress

Make payment uncertainty recoverable.

Show a pending state, never a failure. Pay again stays locked for 90 seconds while the provider confirms.

Sample Document · illustration of the real screen

Why specs fail

Most PRDs are reviewed only by their author.

  1. 01Hard questions get skipped near the deadline.
  2. 02Gaps surface in build, when fixes cost most.
  3. 03Careful review depends on who has time.

How it works

Built

Seven Steps, each with one question to answer.

Work through them in order, and mark each done once answered.

  1. Problem

    What is wrong, for whom, and how do we know?

  2. Research

    What did we learn, and from where?

  3. Solution

    What are we building, described so it can be built?

  4. Scope

    What is in, what is out, and where the line is?

  5. Success metrics

    How we will know it worked, and by when?

  6. Risks

    What could go wrong, and what we would do?

  7. Rollout

    How it reaches users, and how we back out?

Not every change needs seven Steps. Start from a Template, or a blank Document.

  • Standard PRD7 Steps
  • Lean one-pager3 Steps
  • Technical RFC5 Steps
  • Experiment brief4 Steps
  • Discovery brief3 Steps

AI help

Built

AI inside the Step. You decide what stays.

Brainstorm options or add research Sources. Claims missing from their Source are dropped.

From AI output to Step contentBrainstorm in a Step, Research Sources and Markdown import, all built, and an AI agent over MCP, in development, each produce output that is held apart from the Document as a Proposal, an unpromoted idea or an uncited claim. You decide: Accept puts it into the Step content, Reject discards it, and for an import Re-point sends a mapping back to be held again.Brainstorm in a StepBuiltResearch SourcesBuiltMarkdown importBuiltAI agent over MCPIn developmentHeld apart from the Documenta Proposal, an unpromoted idea,or an uncited claimYou decideStep contentDiscardedAcceptRejectRe-point (import)

Only a person with edit access accepts AI output. Agent access is read-only.

Critique

Built

Find the gaps before engineering does.

Six reviewers read the Document. Each Finding points at its text; the Critique never edits it.

BlockerAn open Blocker keeps the Document from being marked ready.

Critique · Checkout recovery

Open: 1 blocker, 1 major, 1 minor, 1 nit.

  • BlockerRaised by Coherence

    Solution and Rollout disagree on when a customer can retry.

  • MajorRaised by QA

    The success metric has no baseline, so it cannot be tested.

  • + 2 more Findings

Sample Document · illustration of the real screen

Work with your team

Built

Share at the level each person needs.

Give access per Folder or per Document; every saved Version records who changed what, and when.

  • Built

    Bring existing specs. Import Markdown, then accept, reject or re-point each mapping.

  • In development

    Agent access. A local MCP server lets your AI tools read what you can.

Sample Document · illustration of the real screen

Where it fits

Built for PRDs, and for checking them.

If you write PRDs in Doc tools
Pages take any shape. Ordered Steps make the gaps visible.
If you write PRDs in AI chat
Not one confident draft: AI works per Step and cites Sources.
If you write PRDs in Roadmap tools
Those decide what to build; Mintchemy checks it is specified well enough.

Not a replacement for your tracker, design tool or wiki.

In the plan

What we are building next.

Planned, not available yet. We mark each built once beta users have it.

  • Planned

    Scorecard and Readiness Index

    Not ready
    • Strategic clarity86
    • User value and evidence78
    • Delivery readiness35
    • Quality and risk81
    • Alignment and operability88

    Five dimensions. The index is the weakest one, never an average.

  • Planned

    Stages

    Stage lifecycleA Document moves through the Stages Spec, Design, Develop, Test, Published. From any Stage before Published it can be Blocked or Abandoned. Moving from Test back to Develop is allowed: a return is recorded as a second occurrence.SpecDesignDevelopTestPublishedBlockedAbandoned

    Set by a person, recorded with who and when.

  • Planned

    Connected context

    Connected contextThe sample Document Checkout recovery linked to its Evidence, a Decision, a Dependency and a Delivery link.EvidenceDecisionDependencyDelivery linkCheckout recoveryDocument

    Link a Document to its evidence, Decisions and dependencies.

Sample Document · design for a planned screen

Practical answers

Before you apply.

Availability
Private beta, opening in cohorts. We email selected applicants an invitation.
Cost
No credit card. Pricing is not set yet.
AI
Runs on your Company’s own provider key. Included AI is in development.
Your data
Export any Document as Markdown at any time.
See the pricing previewAll questions

Specs reasoned through, not only typed up.

Join the private beta