> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/roadmap-kickoff-to-launch.md). # Roadmap: Kickoff to Launch ## Kickoff #### Welcoming and orientation A first view of your app! You’ll get a slide deck with views of your custom community app, a walkthrough of core functionality, and the *potential* to download a very early version of the app. **Action items** * Ask questions * Learn all you can about the app function #### Training 2-3 focused sessions with the individuals who will be responsible for app management. These sessions will focus primarily on how to add content to the Admin Hub. **Action items** * Attend sessions * Practice event, resource, and user creation/invitation #### Content upload The trained administrators will spend a week or two making sure that all upcoming events, essential resources, and service providers are ready for members. **Action items** * Add all upcoming events and essential resources * Pre-approve members #### App store approval and app download Gather will submit the finished product to the app store for approval. Once approved, the app will show up in the Apple and Google Play stores for download. Only those pre-approved will be able to log in. **Action items** * Admins should download the app and log in *** ## Beta Launch #### Establishing testers 5-8 trusted community members (whether staff, longtime participants, or friends) will be chosen to test the app before its public launch. **Action items** * Select beta testers * Send out invitations to beta testers *ONLY* #### Beta launch meeting A quick meeting to ensure all parties feel comfortable to share the app with testers. The testers themselves are free to attend, but it isn't strictly necessary. **Action items** * Ensure beta testers understand what they're testing, what they should be on the lookout for, and the period of time they'll have to test the app. #### Testing Testers will spend 1-2 weeks exploring the app and engaging with content, taking note of any issues, areas for improvement, and ideas. **Action items** * Check in with testers to make sure they're engaging #### Feedback Gather will host feedback sessions to collect critiques and make the necessary changes before a public launch. **Action items** * Send us any bugs or ideas * Sit tight! We will handle the rest of feedback collection and fixes *** ## Pre-launch #### Marketing plan Organizations should develop a plan to get the app into members' hands. This could be a mass email prior to launch, incorporating it into member onboarding, requiring it for upcoming event registrations, or any other method the organization thinks works best for their members. Our recommendations can be found in the [⁠⁠Enrolling members: Your recipe for success⁠](/roadmap-kickoff-to-launch/enrolling-members-your-recipe-for-success.md) document! **Action items** * Develop marketing plan or idea * Share with Gather team * Develop any necessary materials, such as a website page #### Go-no-go Is everyone ready? Is all content in place, and are all bugs resolved? If all parties are feeling comfortable and confident about the app launch, they can proceed to the announcement. **Action items** * Meet and confirm the app is ready for launch #### Announce launch Not every organization will need to announce launch (depending on their marketing approach), but for many, this is the window to make members aware that an app is coming out, that they are enrolled in it, and to expect an invitation soon. **Action items** * Send out mass email/text to alert members of new app *** ## Launch #### Send out invites On launch day, all the invitations will be sent, and members can download the app, go through onboarding, and begin engaging with the content. **Action items** * Tick those send SMS boxes! #### Support new members New tech can always be confusing, so it’s important to be highly responsive and supportive as members get used to the new app. Help provide instructions for event registration, tips for resource navigation, and recommendations for when to message providers. **Action items** * Communicate availability for questions from members #### Continue to update and monitor content The app is living and breathing– as your calendar updates, it should too! Stay on top of event management and new community resources to ensure members have the most accurate and highest amount of information available to them. **Action items** * Add new upcoming events in perpetuity * Add new resources as they become available * Invite new members as they enter your program/s * Remove members who no longer access your services #### Continued support The Gather team will always be there for questions, bug fixes, and new feature ideas. We can’t wait to see your organization flourish, and get your ideas about how to make this tool even stronger! ![](https://3024605654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu9PavPKMcvtJuywiEX1R%2Fuploads%2Fld3n0EUha1RL6gBS2Krz%2FGather_Apps_For_Good.png?alt=media) --- # 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.joingather.org/roadmap-kickoff-to-launch.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.