# Marketing Meet.coop

**URL:** https://forum.meet.coop/t/marketing-meet-coop/134
**Category:** Marketing
**Tags:** prod, time-deliberating
**Created:** [20 June 2020 09:21 UTC](https://forum.meet.coop/t/marketing-meet-coop/134 "2020-06-20T09:21:19Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![benhylau](https://forum.meet.coop/user_avatar/forum.meet.coop/benhylau/32/12_2.png) [@benhylau](https://forum.meet.coop/u/benhylau)
#### Post date: [22 June 2020 23:04 UTC](https://forum.meet.coop/t/marketing-meet-coop/134/15 "2020-06-22T23:04:19Z")

</div>

@chris thanks for explaining the technical limitations to automated account creation. However, I don’t think that is a prerequisite to making it easy for people to sign up.

I think there are a couple options to allowing individuals to sign up, pay, and use [Meet.coop](http://Meet.coop) infrastructure:

## Option 1

What @chris proposes, to distribute the manual account creation and maintenance to member orgs. People arriving to [Meet.coop](http://Meet.coop) are greeted with a form like what @decentral1se referenced in [Governance Model - #12 by decentral1se](https://forum.meet.coop/t/governance-model/128/12) they make a subscription on OC or Stripe, and wait for an email with account details within some time frame we commit to.

## Option 2

We host an “official” [Meet.coop](http://Meet.coop) instance, and allow people to subscribe via an “official” OC hosted at [open-coop](https://opencollective.com/open-coop), and wait for an email with account details within some time frame we commit to.

I think both these are possible. I can see how some of us may favour 1 for scalability, and 2 for usability. This is where we need a way to make decisions together.

* * *

@osb do you think both the above options, with proper marketing copy on the website, can address your concerns here?

> [@Governance Model](https://forum.meet.coop/t/governance-model/128/16):
>
> Avoiding confusion and making signing up super easy is our KEY goal

> [@Governance Model](https://forum.meet.coop/t/governance-model/128/16):
>
> I’m 100% behind the idea that [meet.coop](http://meet.coop) should be able to accept individual customers

* * *

@chris on the technical side, I want to clarify the steps to account creation. My understanding is:

1. All the Greenlight containers share the same BBB backend server

2. Sysadmin manually verify payment

3. Sysadmin manually login into the correct Greenlight container

4. If it’s a admin account run `rake admin:create[name,email,password,role]`  
If it’s a user account run `rake user:create[name,email,password,role,provider]`

5. Sysadmin send email to new customer with access information

Does that sound correct? Is the _user account_ the same thing as when I sign up using [https://demo.meet.coop/b/signup](https://demo.meet.coop/b/signup)?

I understand that the commands for listing accounts, updating accounts and removing accounts are missing, but how do you see those relevant in signup/onboard flow?

Do you think 1-4 can be automated via a Stripe (not familiar with OC API) webhook triggered execution of these steps?

---

_[View the full topic](https://forum.meet.coop/t/marketing-meet-coop/134)._