> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/magicworks/service-architecture.md). # Service architecture How MagicWorks structures its five service pillars and why focus matters. MagicWorks uses a focused five-pillar architecture so each service has a clear buying motion, delivery model and accountability boundary. The five pillars are Digital Marketing, Web Development, AI Consultation, Marketplace & Platform Consultation, and Brand, Research & Publishing. A focused architecture is useful for clients because it makes three things explicit: * what MagicWorks will execute, * what MagicWorks will advise on, * and what should be handled by a product, a client team or another specialist. This structure also reduces the risk of presenting every capability as a standalone service simply because the company can technically perform it. --- # 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://knowledge.magicworksitsolutions.com/knowledge/magicworks/service-architecture.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.