COMPANY PLAYBOOK
Niteo
Niteo turns the operating knowledge of a small open-source company into a living, contributable handbook on GitHub.
System principles
- Keep process in open documentation team members can change.
- Do not turn customer support into a specialist silo.
- Share company outcomes with the team.
Tensions and trade-offs
- Openness creates strong context in a small team while key-person risk and maintenance load remain.
- Everyone doing support creates customer knowledge but interrupts specialist work.
PRACTICES
How Niteo builds its operating system
01
Bonus
Transparent profit sharing
Profit sharing is a written people policy connecting company results with team contribution.
- How it works
- Program scope and distribution rules remain accessible in the handbook.
- Why it is used
- Connects shared company outcomes to the team’s economic outcome, not only shareholders.
- Trade-off
- Year-to-year profit variability reduces reward predictability.
- Best fit
- Small, outcome-oriented companies with measurable profitability.
02
Customer insight
Everyone participates in support
Customer support is not left as a closed knowledge area separated from product and operations.
- How it works
- Team members handle support requests directly through defined processes and guides.
- Why it is used
- Carries customer language and product problems to decision makers.
- Trade-off
- Context switching can fragment deep-work time.
- Best fit
- Small SaaS teams whose product decisions benefit quickly from customer contact.
03
Production flow
Visible workflow through Kanban
Work moves through a pull system with visible status and boundaries.
- How it works
- Projects and operational work are tracked through a shared Kanban process.
- Why it is used
- Makes work in progress and bottlenecks visible to a small team.
- Trade-off
- Flow metrics can become card-moving ceremony when detached from customer value.
- Best fit
- Small multi-role teams and continuous operational flows.