obsidian/Main
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-12-09 15:33:12

Browse Source 
Affected files:
0 Journal/Meetings/20251209 - Cofounder Meeting.md
This commit is contained in:
Obsidian-MBPM4
2025-12-09 15:33:12 +01:00
parent 8fe89b0e48
commit 90c8f864af
1 changed files with 32 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
0 Journal/Meetings/20251209 - Cofounder Meeting.md
View File

@@ -26,11 +26,18 @@ status: not_started
- 10% of fully diluted stock as of February 2025
- 5% of which is immediately vested, replacing the stock options contract
- 5% of which is vested over 3 years (1 year cliff --> 1.67% p.a.)
- Option to get more in a future contract
- 4870.- net
- I don't want to have to worry about money in my daily life, because it takes focus away from OneSec.
- is 50% or more below market salary (e.g. I had an offer of 125k gross)
- Budget: see below.
-
- Ziele:
- Ich sollte klare Ziele angeben
- Hiring:
- jemanden anstellen der beim Staat / Horizon50 / Innosuisse, Venture Kick, accelerators grants reinholt die non-diluting sind. --> wir müssen uns nicht darum kümmern (keine Ablenkung), hohe mögliche upsides, Entlöhnung von diesem Angestellten performance based --> incentive
- office admin
- replacement Valentin
- Fleet Management: a responsible person
@@ -46,16 +53,37 @@ status: not_started
- steuern ca 7000 --> 600 pro Monat
### Gedankenmaschine
- Ziele:
- AI workflows optimieren, vor allem für software. Automatisierte Reviews und automatisierte prompts die unsere Werte und Ziele überprüft: Keep it simple, use patterns wisely. --> Produktivität von allen developers steigern.
- Bis Ende Jahr Requirements based development aufgesetzt haben.
- Jira
- Ease Requirements
- OKR framework?
- Plan on how to enforce this development structure.
- Electrical Hardware: Do-254 inspired: get reliable and working electrical Hardware by April 2026
- Finalize setup of documentation structure
- Enforce documentation structure
- Define requirements and passing criteria for every single PCB and the collection of PCBs together
- Research what certification standards would be use those as a guideline
- Test in lab conditions and in flight.
- End of Year 1-on-1s with employees.
- feedback both ways
- Introduce OKRs:
### Points to Discuss
- Tax ruling and my equity contract.
- [ ] prepare: present email and propose strategy
- Finances:
- OneSec Planning:
- Budget: I want to properly budget the investment + anything on top that Floris is going to invest.
- Allocate X$ to Flightcontroller and within Flightcontroller to subprojects. etc
- Allocate X$ to Flightcontroller and within Flightcontroller to subprojects. etc
- Realistic OKRs --> OKR as a process: goals need to be reviewed and adapted often, else they become stale and meaningless quickly
- *Objective*: memorable, qualitative description: short, inspirational and engaging --> motivate and challenge team
- *Key Result*: 2-5 metrics that measure progress. Not more, because else you won't remember them --> should be measurable within weeks, not years! Else they are useless.
- Hiring:
- Yes Floris can manage the hiring, but we can't be that overly reluctant in hiring people. I think it has been and is smart to be slow in hiring and not exaggerate. But I think we are sometimes way too reluctant.
- [ ] prepare a list of positions that I think are essential. Think it through thoroughly, also from Florises perspective. Combine everything with a timeline
- Pilot Project
- Whats the status? What is the current state of communication?
- Job update
- Battery system
- pcb reviews -->