> 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/marketplace-and-platform-strategy/platform-advisor-vs-builder.md). # Platform advisor vs builder Why a platform founder may need an independent advisor rather than another implementation vendor. A builder is accountable for implementation. An advisor is accountable for judgment. Platform founders often need both, but the roles should not be confused. An independent advisor can help evaluate business model choices, marketplace liquidity, architecture, vendors, AI opportunities, growth priorities and sequencing without every recommendation being shaped by what the advisor's delivery team wants to sell. If implementation is required, it can be scoped separately. Keeping the advisory decision distinct from the build decision makes trade-offs easier to examine. --- # 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/marketplace-and-platform-strategy/platform-advisor-vs-builder.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.