> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/the-company/brand/why.workwithmad.com.md). # why.workwithmad.com Our thought leadership blog is what showcases how we work as well as allowing us to demonstrate what methodologies we use and why they are a huge part of our services. The articles range from our most used business solutions (which we use ourselves as well), to technology and design trends, as well as our most recent case studies. Also, why.workwithmad.com is our way to cut down on common questions clients or prospective clients might have. We push to cut down on this back and forth by answering \[through articles] any concerns or questions anyone might have about our working practices or even more technical design and development efforts. If you want to contribute to the blog with something you have been learning or working on there is always an open door for you to publish something. In the end, you would know best of what goes on in Mäd and what we should write about. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://process.mad.co/the-company/brand/why.workwithmad.com.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.