> For the complete documentation index, see [llms.txt](https://documentarians.gitbook.io/metadocumentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentarians.gitbook.io/metadocumentation/product/roadmap.md).

# Roadmap

Roadmap September 2019 - January 2020

## **New Collective Page**

In response to your feedback, we've made some big improvements to the design and functionality of Collective pages (and individual and organization profiles too)**.**

* Owner: Pia
* Status: v1 Shipped 09-23-2019
* Metric(s): 
  * Related complaints and support requests
  * Fewer people contacting us instead of projects
  * Conversions to contribution flow
  * Increasing one-time donations
  * More custom tiers
  * How many Collectives use customization options
  * Page load time

## **Homepage Redesign**

We are re-focusing on projects that want to manage funds through the platform and we are re doing our homepage accordingly.

* Owner: Xavier
* Status: In Progress
* Launch: October
* Metrics:
  * Collectives create from homepage
  * Page load time
  * Clarity of message (qualitative) - we feel confident about

## **Onboarding Flow & Business Model**

* Owner: Xavier
* Status: Researching
* Launch: TBD
* Metrics
  * More self-hosted and unhosted Collectives created
  * Increase per-Collective revenue

## **Expense Flow Redesign:**

* [Issue](https://github.com/opencollective/opencollective/issues/2394)
* Owner: Alanna (and Pia)
* Status: Design 
* Implementation: End of October
* Metrics:
  * More expenses filed
  * Less support requests
  * Less host admin time spent
  * Way fewer issues with invoices (fewer expense comments)
  * Use of the new features (ex batch expenses)

## **Back your Stack**

* Owner: François 
* Status: Ready to Deploy 
* Metrics: 
  * Subscriptions created to Back your Stack. 

## **Key questions for prioritization**

**This is what we ask ourselves to decide what gets done and what doesn't.**

* Does this serve our mission? 
* Will this make us financially sustainable within a year?
* Is it feasible to build and maintain with our team and runway?
* Can this make us move faster?
* Does this increase quality and not technical debt?
* Will this bring us more Collective and financial contributors?
* Is this already solved elsewhere or is it our unique contribution?
* Can we measure the success of  this?

## Template for new projects

* Github issue
  * explain the feature. 
  * Link to other opened issues or data. 
  * Include details below.
* Kickoff
  * Organize a special meeting or on a scheduled one. 
* Project owner. 
  * Role: Facilitator, decision-maker, producer. 
  * It's ultimately responsible for (needs to do or organize who does)
    * Delivery 
    * Q\&A
    * Docs & Comms 
    * Post-ship plan for maintenance 
* Success metric(s)
* Timeframe - kickoff and delivery, main milestones / roadmap


---

# 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://documentarians.gitbook.io/metadocumentation/product/roadmap.md?ask=<question>&goal=<endgoal>
```

`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.