> For the complete documentation index, see [llms.txt](https://docs.quilter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quilter.ai/about-quilter/why-should-i-use-quilter.md). # Why should I use Quilter? Key reasons to adopt Quilter’s AI-powered PCB layout automation, highlighting faster time-to-market, efficient iterative design, reduced errors, and optimized use of engineering talent. > Quilter can't design *every* PCB, but if it *can* design it, Quilter should. We've spoken with dozens of world-class hardware design teams and have never encountered an organization where PCB layout wasn't a bottleneck. The reality is that there are far too few experienced layout engineers to meet the rapidly growing demand for PCBs. The best organizations are experimenting with new automation and AI-powered tools to transform their cultures and become faster, more efficient, and more effective than ever. There are numerous reasons to start adopting AI-powered automation tools like Quilter; here are a few of the most common ones: ### Get to market faster Quilter dramatically reduces PCB design cycle times by automating the layout process. Traditional manual layouts can take weeks, but Quilter generates optimized design candidates within hours. Accelerating your PCB design cycles enables you to get your products to market faster, seize opportunities ahead of competitors, and respond swiftly to customer feedback and emerging market demands. ### Improve designs through iteration Quilter’s automation allows engineers to quickly and easily test multiple layout iterations, which is often impractical in manual workflows due to time constraints. With Quilter, you can rapidly explore design alternatives and trade-offs, leading to innovative solutions and higher-performing boards. More experimentation facilitates the discovery of the best design outcomes, rather than settling for the first viable option. ### Protect your best engineers Experienced PCB layout engineers are a scarce and valuable resource. Quilter offloads tedious, repetitive tasks so your most skilled engineers can focus on challenging, high-impact design decisions that truly benefit your products. By automating mundane aspects of layout, you safeguard and maximize your team’s most valuable engineering expertise. ### Eliminate costly mistakes Quilter’s physics-based rule checks and automated design processes significantly reduce the human error inherent in manual layouts. Every generated candidate undergoes rigorous validation to ensure compliance with real-world constraints, drastically lowering the likelihood of costly design errors and re-spins. Spending less time fixing mistakes means more resources are available for innovation and growth. ### Design and iterate faster Leveraging AI-driven automation, Quilter provides immediate design iterations without waiting days or weeks for manual updates. By quickly generating multiple layout options, teams can iterate rapidly, test assumptions frequently, and optimize designs efficiently. This AI-driven agility ensures continuous improvement throughout the product development process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.quilter.ai/about-quilter/why-should-i-use-quilter.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.