Develop go-to-market plan documentation

[turkhale]

My crucial assumption, for now, is that people have three opportunities to improve their knowledge base. Student projects, downtime in the task at work, and job switching. Other times, they are stuck and lack a chance to change something.

Osterwalder business canvas model in Logseq for Terraphim. Put a link here.

Go-to-market plan in Word (Innovate UK).

Develop a publications plan.

Demo1: Job interview (customer meeting) prep (both CV and STAR-answers techniques prep)

1. target audience — engineers switching jobs (both company and project or team)
2. demo or trial product with requires features (breakdown of features) — Logseq as CRM.
   1. missing feature Terraphim Cortex - list documents in Terraphim per role with expiration date for items
   2. add a document from the web extension to the Terraphim cloud
   3. /readit bot command adds a document to Terraphim Cortex
      1. add file to terraphim cloud
         1. security of terraphim cloud (public for demos and ensure security for people)
   4. tag document that I sent to the bot
3. marketing - what is required to market 2 to 1. Demo, webinars, YouTube (create using [terraphim.ai](http://terraphim.ai/) e-mail), forms, technical mailing lists, YCombinator, Reddit, list all channels and distribute posts with announcements by channels.
4. enabling capabilities - what is required to build 2
   1. Terraphim role = System operator
   2. public cloud instance for demo — need to create a flow
   3. private cloud instance for experiments
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)
   1. Donations.
   2. No video views over 2 days, no sharing, no questions, and requests from users.

Demo2: Certification exam prep (INCOSE CSEP)

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
   1. make a series of workshops where we create applications together with someone (Anabel, people profiles that match this)
   2. IEEE, working groups
4. enabling capabilities - what is required to build 2
   1. import of the SE competencies matrix to Logseq (need MD and publish from it)
   2. import of the SE competencies matrix to the Atomic Server
   3. Showcase post-publication for improving professional visibility
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo3: Performance review prep (SFIA demo)

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
   1. import of the SFIA csv to Logseq
   2. import of the SFIA csv to the Atomic Server
   3. import Logseq knowledge graph to Atomic Server
   4. save my SFIA profile (Logseq page md graph) with supporting evidence as a baseline for Atomic Server
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo4: Knowledge base refactoring and migration

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo5: Knowledge base quality metrics and performance

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo6: Time capsule for future me

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo7: Meaningful comments and question cues on someone's agenda, workshop program, website, speech, presentation, article, etc. (any piece of information we have on essential people)

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo7: Logseq page refactoring using BFO

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo8: RASIC matrix generation

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo9: Skills-project matching - low priority

1. target audience — project managers (real ones, with hiring capabilities, supply side)
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Demo10: Reminding what to do for the tasks that people perform rarely

1. target audience
2. demo or trial product with requires features (breakdown of features)
3. marketing - what is required to market 2 to 1
4. enabling capabilities - what is required to build 2
5. what are the success criteria or failure (how do we disprove the hypothesis as soon as possible)

Maria Keet makes a good point that can be our argument why we better than Dropbox Dash: 1.3.2 The lack of trust (or the angst) on what data went and go into the LLMs (the ‘could be your emails, googledocs, sharepoint files etc.’), that no-one was asked whether they consented to their content being grabbed for that purpose, and when some would have disapproved of inclusion if they could, there’s the powerlessness in that it seems one neither can opt out nor verify if one’s text was excluded if opt-out were to be possible. So, when you search over Outlook or Google docs, you violate the consent of your collaborators. That is a good point for privacy-first search.