> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/get-started/readme/find-your-starting-point.md). # Find your starting point Different teams use The Wallet Crew for different reasons. Some need the product model first. Others need data flows, launch sequence, or technical reference. This page points each role to the right first pages. #### **Marketing & CRM** Marketing and CRM teams usually arrive asking how the platform works and what it actually does. The useful first model is simple: design a pass, distribute it, then keep it current after installation. [Understand the platform](/get-started/readme/understand-platform.md) gives that lifecycle in one page. [Learn wallet fundamentals](/get-started/readme/wallet-fundamentals.md) explains how passes behave in Apple Wallet and Google Wallet. When the goal shifts to acquisition and conversion, [Enrolment](https://docs.thewalletcrew.io/guides-enrolment/) is the right hub for website, email, and in-app entry points. #### **IT / Data / Security** IT, data, and security teams usually arrive asking how data is synced and which system owns what. The main question is usually data flow, not only integration. The Wallet Crew often stores identifiers and operational metadata, while core systems stay the source of truth. Start with [Understand the platform](/get-started/readme/understand-platform.md), especially the “How it works” section, to place the platform in the stack. Then move to [Structure](/developers-guides/pass-architecture/structure.md) for identifiers, ownership, and pass architecture, and use [Connectors](https://docs.thewalletcrew.io/connectors/) to review supported integration patterns. #### **Developer** Developers usually arrive asking where the technical reference starts and how authentication works. The shortest route is the [Developers](https://docs.thewalletcrew.io/developers-guides/) area, which groups pass architecture and API key setup. The [API reference](https://docs.thewalletcrew.io/api-reference/) is the next stop for endpoints, payloads, and response shapes. Use [Connectors](https://docs.thewalletcrew.io/connectors/) when the project depends on an existing integration instead of a custom flow. #### **Project manager** Project managers usually arrive asking how The Wallet Crew fits into the existing stack and what happens first. The fastest orientation starts with the [Implementation Roadmap](/get-started/readme/implementation-roadmap.md), which lays out the common launch sequence from kickoff to go-live. It shows when data ownership, distribution, and operational validation should be decided. [Understand the platform](/get-started/readme/understand-platform.md) explains where The Wallet Crew sits between source systems and wallet channels. [Connectors](https://docs.thewalletcrew.io/connectors/) helps map the project against existing CRM, POS, ticketing, and marketing tools. #### **Stakeholder / Executive** Stakeholders and executives usually arrive asking whether the platform is documented clearly enough to support a decision. The quickest confidence check starts with [Understand the platform](/get-started/readme/understand-platform.md). It gives a short, factual view of the product model, scope, and operating principles. [Implementation Roadmap](/get-started/readme/implementation-roadmap.md) shows that delivery follows a defined sequence, with clear phases and validation points. Together, those pages show how The Wallet Crew fits into a real programme without going into technical detail. --- # 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://docs.thewalletcrew.io/get-started/readme/find-your-starting-point.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.