CONTACT M2 AI, LLC
Tell us what you need help with.
Closeout Readiness Check support is handled directly by M2 AI, LLC. Email richard@m2ai.tech and include the product name in the subject.
Product and installation questions
For installation or local-check problems, include your Windows version, Claude Desktop version, the step that failed, and the exact error message. Say whether the issue happens before a folder is read or after a report appears. Do not attach project files. Files are scanned locally, but findings and cited excerpts are returned to Claude; describe only the issue in your support email.
Activation and billing questions
For activation, recovery, cancellation, or payment help, include the email used at Stripe Checkout and a short description of what you expected. Never send a full card number, recovery key, installation private key, or Stripe credential. Billing management is normally available through the product's Stripe customer-portal link.
Privacy, accessibility, and security
Use the same email for privacy requests, accessibility feedback, or a suspected security issue. Describe the affected product surface and the result you need. For a security report, provide reproducible steps without including sensitive project material. M2 AI may ask for limited follow-up information needed to verify a privacy request or reproduce a problem.
What support can and cannot decide
Support can explain installation, product behavior, the fixed baseline, and billing. It cannot decide whether a closeout package satisfies a contract, specification, code, owner, architect, or general-contractor requirement. Those decisions remain with the responsible project professionals.
Before you send a message
Check the support guide for the most common installation, folder-access, human-review, activation, and billing issues. If the extension produced a cited report, keep that report on your computer and describe only the status that needs explanation. A concise message with the product version, operating environment, exact error, and steps already tried is normally enough to begin troubleshooting without exposing project information.