You are here: Home » pub » What is Unicis? » quick_start

pub:company:quick_start

This is an old revision of the document!


Quick Start Guide for New Unicians

Welcome to Unicis! This page is your starting point. Read it first, then dive into the handbook sections linked below.


Your First 5 Pages to Read

Read these in order — they cover everything you need to understand how we work:


Essential Tools

Set up these tools on your first day:

Tool What it is for Access
Element / Matrix Team chat. Primary communication channel. Account created for you.
Nextcloud Files, calendar, document storage. Account created for you.
OpenProject Project management, tasks, Rocks, timesheets. Ask Peter for access.
Dolibarr CRM, invoicing, customer records. Ask Predrag for access.
Fider Product feedback and roadmap. Sign up with SSO.
GitHub Source code (Community Edition). Create your own account.
GitLab Source code (Business Edition), CI/CD. Ask Peter for access.

Full list at Tech Stack Applications.


Who to Contact

Topic Contact Channel
IT access, Devops, infrastructure Peter Zlatev (CTO) Element
HR, contracts, legal, finances Predrag Tasevski (CEO) Element
EU projects, community, support Alexander Eklöf Element
Marketing, SEO, newsletters Ksenija Jovisevic Element
Development, code review Yaroslav / Vitaliy Element / GitLab

Company Rhythm (EOS)

Our weekly and quarterly cadence:

When What Who
Monday 10:00 CET Level 10 Meeting (90 min) All team
Weekly Scorecard updated (before L10) Each metric owner
Monthly All Hands meeting All team
Quarterly Quarterly Session (3-4 hours) Leadership team
Annually Annual Planning Session (full day) Leadership team

See Traction for full details.


First Week Checklist

  1. [ ] Read the 5 pages listed above
  2. [ ] Set up Element/Matrix and join #tech, #town-square, #off-topic
  3. [ ] Set up Nextcloud account and set your calendar working hours
  4. [ ] Meet your manager for a 1:1 introduction
  5. [ ] Set up your development environment (if engineering role)
  6. [ ] Read the Scorecard to understand how we measure success