Sales deck: Difference between revisions

From MWStake
Jump to navigation Jump to search
Line 59: Line 59:
* Some of the [[Bylaws#The_Corporation_will_engage_in_Activities_to_support_this_purpose:|Vision and Goals]]
* Some of the [[Bylaws#The_Corporation_will_engage_in_Activities_to_support_this_purpose:|Vision and Goals]]
* The worlds knowledge platform
* The worlds knowledge platform
==Statistics==
* [https://wikistats.wmflabs.org/ WikiStats]
* [https://wikiapiary.com/wiki/Main_Page WikiApiary]
* [https://docs.google.com/presentation/d/1iN7cXist50N9N0ijTyMeeHxPrmPAwDu4dxSUqbB8DlE/edit#slide=id.g148809060a_0_43 MWStake MediaWiki Presentation]
===Requested data===
#views
#searches
#visitors
#* With some work, we can give you this information about #WA itself, but not the monitored wikis.
#users
#wikis
#edits
#pages
#* Now this we can give you. It should be available via an #ask query, but maybe we need to provide a way to download the information.
#community members
#* How is this different from #users?

Revision as of 14:13, 27 May 2020

Some information about marketing collateral for the MWStake marketing sponsorship campaign.


Team

  1. Eric-Jan
  2. Markus
  3. James
  4. Bryan


Format

Most good presentations include the 4 concepts below in the introduction:

  1. Know your audience
    • The presentation/deck should be tailored to the intended audience. What are the different prospects we are aiming for?
      1. Developers/Consultants
      2. Companies/Organizations/Agencies
      3. Power Users/Admins
  2. Capture audiences attention
    • Some statistics about how used the MediaWiki software is? I thought that was the data we got from Mark/Violet, but it looks like that might be more for sponsorship leads?
  3. Establish expertise
    • Who are we
  4. Reveal topics
    • We want you to be a sponsor, here's how the goals of MWStake align with your needs

Subjects

  1. Awareness raiser
    Why should I read this deck?
    You love open source and the power of the engine behind Wikipedia? Us too. We are here to improve your experience.
  2. Mission statement
    Claim could be something like "Ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation"
    See also our mission
  3. History and Activities
    Proof that we can do it
    Since 2014, MWStake has been caring about the needs of MediaWiki maintainers.
    We raise the flag in MediaWiki events and discussions; develop and standardize functionality; exchange experience; create a network
    See our annual reports, e.g. 2018.
  4. Topics
    What did we focus on?
    Installation (Meza, Composer RfC), Integration (LDAP), Use cases (Fantastic MediaWikis Track), Networking (EMWCon)
  5. Our Team
    MWStake's current members are high profile members of the MediaWiki community.
    Many of us use or maintain MediaWiki in a professional environment, in corporations, highly visible sites or as consultants (find a better word, consultant always has a smell of "I want to make money")
  6. Corporation structure and ecosystem
    Most people will want to hear how we are related to Wikipedia and its ecosystem.
    MediaWiki Stakeholders' Group is a recognized Wikimedia affiliation.
  7. Eco system (MediaWiki community, users)
  8. Membership
  9. Benefits

Payoff

High level marketing "brand"

  • Ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation
  • Free your knowledge
  • The worlds best opensource wiki
  • The worlds best opensource knowledge management solution
  • Share the sum of the knowledge of your organization
  • Some of the Vision and Goals
  • The worlds knowledge platform

Statistics

Requested data

  1. views
  2. searches
  3. visitors
    • With some work, we can give you this information about #WA itself, but not the monitored wikis.
  4. users
  5. wikis
  6. edits
  7. pages
    • Now this we can give you. It should be available via an #ask query, but maybe we need to provide a way to download the information.
  8. community members
    • How is this different from #users?