DevPool B2B Pitchdeck

[0x4007]

Intro

At the research meeting, it was decided to create an effective b2b pitch deck for DevPool.
In this pitchdeck should be a point about the AI capabilities of the DevPool.

Ideal partners are Open Source projects that are using GitHub actively and are good in R&D. This can be identified by the amount of open issues they have on their repositories, and if they are recently active.

---

@ubiquity/ubiquibot as a good example with 96 open issues.

---

The target audience of the DevPool pitchdech is the decision-makers of such organizations.

Information

The previous pitchdeck slides can be found here

Ideas related to the DevPool pitchdeck can be found here
https://github.com/orgs/ubiquity/discussions/22

Alex`s ideas on the AI assistants can be found here
https://github.com/ubiquity/github-agents/issues/1
ubiquity/ubiquibot#487

More links on the AI ideas can be provided on request.

---

Goal

Create a first draft of the DevPool B2B pitchdeck so that we can use it to pitch partners.

Activity

• Content #60

Pitchdeck should cover at least these topics:

1. General goals and values of the DevPool
2. Open Source projects problems
3. Solutions provided by the DevPool (here can be a video)
4. Benefits for partners
5. How to start

• Format

The pitchdeck should be in the Google slides.
If video is used, it should be inserted into a Google slide.

• Stile and aesthetics

In general, the pitchdeck style should match the style of the website https://ubq.fi/
The stile and aesthetics should be discussed and approved by Alex.

@pavlovcik @diamondnegroni @Hodlatoor rfc

[0x4007]

The style and aesthetics should be discussed and approved by Alex.

It's best if I just handle it myself. Design is extremely subjective and the feedback loop is infinitely faster if it's just me doing it lol

I would prefer to focus not on the writing, so be mindful to distill the content to be extremely concise for the deck. A very common mistake I see is taking a full text document, and then just wrapping it inside of a pitchdeck. Pitchdecks should be extremely concise, not improperly encoded text documents.

[Hodlatoor]

The style and aesthetics should be discussed and approved by Alex.

It's best if I just handle it myself. Design is extremely subjective and the feedback loop is infinitely faster if it's just me doing it lol

I would prefer to focus not on the writing, so be mindful to distill the content to be extremely concise for the deck. A very common mistake I see is taking a full text document, and then just wrapping it inside of a pitchdeck. Pitchdecks should be extremely concise, not improperly encoded text documents.

We can do that for now and we should have a base template so it doesn't bottleneck on you. Take a look at the deck (content) I appended and feel free to modify. #60 (comment)

[0x4007]

I opened a pull request to show you my expectation around deliverables.

• feat: add pitchdeck content #61

[Hodlatoor]

@pavlovcik Originally you asked for a google slides since (i know, ppt files are scary) so I provided that. How do I load a useable google slides as an .md file that retains formatting and graphics?

Do we need a new version that is AI centric or add a couple of slides to cover that in the existing one?

[0x4007]

I can't think of a great solution right now on tightly associating tasks on GitHub with Google Slides.

I have mixed feelings for posting a link as a deliverable due to links being able to break. This makes auditing brittle.

So I think maybe it makes sense to only directly credit bounties for content (e.g. the text I provided an example pull request for) for now.

If pitchdecks are ongoing deliverable format for some reason, we could probably use an open source parser to consume the markdown files and spit out a presentation.

---

Some open source pitchdeck formats. If they actually are plaintext then this will make reviews straightforward.

https://chat.openai.com/share/efa513c3-e56e-410f-8a75-133fe7879029

---

Do we need a new version that is AI centric or add a couple of slides to cover that in the existing one?

You can use your best judgment. My gut feeling says add a couple slides.

[Hodlatoor]

Don't you think that creates more unnecessary work for the person trying to utilize it? The slide is ready to use with little modification on the business developers part.

we should have ready to pull repositories of collateral. like "I need to send an email to this guy, Let me go to the Google drive and associate the file"

[0x4007]

It's the same thing for that purpose. You link the .odp from GitHub instead of the google slides link.

The difference is audibility and following devpool flow.