# PLAN

The North Star for 2023 is to raise $300k to launch the project.

## SUMMARY

The focus for Q1 is product-market fit (PMF). The key to PMF at this stage is to engage with potential [users](https://also.roybahat.com/picking-your-first-customers-the-gradient-of-influence-47858b90adfd) to refine the product and demonstrate traction with growth partners. At this time, Assembly has an operating hypothetical [gradient of influence](https://also.roybahat.com/picking-your-first-customers-the-gradient-of-influence-47858b90adfd) audience. This target audience includes civic technologists. Accordingly, the focus of Q1 is to reach out to and acquire commitments from potential groups.

### OBJECTIVES

* **Funding.** Raise $300k in capital by December 31st, 2023.
* **Partnerships.** Acquire 32 Group partners by December 31st, 2023.
* **Email list.** Build an email list of 1k emails by December 31st, 2023.

## KPIs

### **Engagement**

The number of conversations held with the hypothetical users of Assembly. This number is purposefully small with a highly defined target community (gradient of influence).

### **Email List**

The number of users that sign up to the Assembly email list. Email list growth will be driven by outreach to groups (to share Assembly with their community) and through the website from organic traffic or other methods, such as through blog readership.

Looking ahead: An email list provides a market potential growth, which feeds into User Signups. Eventually, User signups and the number of operational nodes monthly will supplant emails.

### TARGETS (specific goals)

#### **Engagement**

<table><thead><tr><th width="175">METRIC</th><th width="137">January</th><th width="137">February</th><th width="92">March</th><th width="146">Q1</th></tr></thead><tbody><tr><td>Group Outreach (number of)</td><td>5</td><td>10</td><td>20</td><td>35</td></tr><tr><td>Individual Interviews (1:1)</td><td>2</td><td>5</td><td>10</td><td>17</td></tr><tr><td>Partnership Agreements*</td><td>1</td><td>2</td><td>5</td><td>8</td></tr></tbody></table>

**\****Partnerships are with Groups*

#### **Email List**

<table><thead><tr><th width="249.33333333333331">METRIC</th><th width="107">January</th><th width="140.66666666666669">February</th><th width="100">March</th><th width="100">Q1</th></tr></thead><tbody><tr><td>Partnership Agreements</td><td>1</td><td>2</td><td>5</td><td>8</td></tr><tr><td>Partner Email List -- Addressable</td><td>1,100</td><td>2,200</td><td>5,500</td><td>8,800</td></tr><tr><td>Email Sign-ups**</td><td>55</td><td>110</td><td>275</td><td>903</td></tr></tbody></table>

* I am using the median number of members on Meetup for a specific set of civic technology groups that will be part of the first phase of outreach as a proxy. As I collect more data, that number will be refined.

\*\**Assumes highly motivated and target audience with Partnership acting as advocates: 50% open rate, leading to 10% email signup.*

### CURRENT STATUS (2023) – GOALS

#### **Engagement**

<table><thead><tr><th width="257">METRIC</th><th width="105">January</th><th width="130">February</th><th width="110">March</th><th width="100">Q1</th></tr></thead><tbody><tr><td>Group Outreach (number of)</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr><tr><td>Individual Interviews (1:1)</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr><tr><td>Partnership Agreements*</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr></tbody></table>

#### **Email List**

<table><thead><tr><th width="261">METRIC</th><th width="114.33333333333331">January</th><th width="133.66666666666669">February</th><th width="119">March</th><th width="120">Q1</th></tr></thead><tbody><tr><td>Partnership Agreements</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr><tr><td>Partner Email List -- Addressable</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr><tr><td>Email Sign-ups**</td><td>TBD</td><td>TBD</td><td>TBD</td><td>TBD</td></tr></tbody></table>

## USE OF FUNDS

<table><thead><tr><th width="249.33333333333331">USE OF FUNDS</th><th width="125">Q422</th><th width="138">Q123</th><th width="100">Q124</th><th width="100">Q223 (projected)</th></tr></thead><tbody><tr><td>Growth/Marketing</td><td>$TBA</td><td>$TBA</td><td>$TBA</td><td>$TBA</td></tr><tr><td>Product/Engineering</td><td>$TBA</td><td>$TBA</td><td>$TBA</td><td>$TBA</td></tr><tr><td>Operations</td><td>$TBA</td><td>$TBA</td><td>$TBA</td><td>$TBA</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.assembly.digital/plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.