QUESTIONS, answered

ValidStitch is currently waitlist-only. The marketing site is live, and the first paid workflow is planned around uploading a design, validating it, reviewing each issue, and saving a production setup sheet.

The first audience is anyone who loses time or material to embroidery file mistakes: beginners, Etsy sellers, embroidery shops, and digitizers. Each persona page explains the same workflow from that operator's point of view.

The roadmap centers on SVG and common embroidery formats such as DST, PES, JEF, EXP, VP3, XXX, and SEW. Specific format support should be confirmed in-product before relying on a production export.

ValidStitch validates practical production risks such as hoop fit, tiny details, density risk, stitchability, color complexity, file-preparation issues, and missing production setup context.

Embroidery risk changes by context. A design that is acceptable on one garment, fabric, hoop, backing, thread, needle, or placement can become risky on another setup.

A blocking issue is a problem that should be fixed or explicitly accepted before production. The product should keep that decision visible so the final setup sheet does not hide risk.

A warning is a possible production risk. The design may still be usable, but the operator should review the issue, decide whether to fix or ignore it, and keep that choice documented.

Some issues can be auto-fixed or preview-fixed when the change is deterministic and low risk. Other issues need guided review because the safest answer depends on design intent and production setup.

Automatic changes can damage a logo, alter customer artwork, or hide a production decision. ValidStitch should only auto-fix when the result is predictable, reversible, and explainable.

Yes. Test stitching is still recommended before bulk production, especially with a new fabric, stabilizer, thread, needle, hoop, garment placement, or machine combination.

The first paid product is expected to use credits, with a working assumption around a paid validation-and-fix pass per uploaded file. Final launch prices and bundles should be confirmed before checkout goes live.

Product policy should make project privacy clear and provide controls for promotional or marketplace use. Public legal pages are marketing-site notices and should be reviewed before accepting paid uploads.