Optale AS — Corporate Structure & Incentive Framework

Status: Draft for review Author: Thor Haaland, CEO & Founder Date: 2026-05-07

---

1. Purpose

This document lays out a proposed framework for how Optale structures ownership, incentives, and organizational roles as we scale from founder-led execution to a multi-division company. The goal is to get alignment from advisors and early partners before we formalize contracts, so we build the right foundation from day one.

We want feedback on: the division model, the vesting mechanics, the equity allocation philosophy, the hiring sequence, and anything we're not thinking about.

---

2. Context: Where We Are

Optale is an AI operating system for companies. We structure, govern, and operationalize a company's knowledge so that both humans and AI agents can act on it. Five products: Company Brain, Ontology, Optale Agents, Command, and Control.

Current stage:

• Revenue from active clients across digital marketing, dealflow, and staffing/WFM verticals
• Pipeline in Norwegian real estate and international expansion (US/Brasil)
• Team forming around key people but no formal equity or incentive agreements yet
• Platform infrastructure deployed and operational
• No external funding taken

Why now: We are at the inflection point where the next 3-5 people we bring in will define the company's trajectory. Getting the structure wrong here means either: (a) giving away too much too early and losing control/optionality, or (b) under-incentivizing and losing the people who matter.

---

3. Organizational Model: Four Divisions

The company is organizing around four distinct functions, each with different value-creation profiles, risk levels, and appropriate incentive structures.

3.1 C-Suite / Leadership

Who: CEO, COO/CCO, future CTO, or equivalent strategic roles. Value profile: Long-term company building, fundraising, strategy, culture, enterprise relationships. Risk: Highest commitment, longest horizon.

Kamilla Haugen is joining as the first C-Suite hire alongside the CEO. Background: jurist, operational experience through IT at Visma, enterprise tech sales, and a broad network across Norwegian business. She bridges operations, commercial, and compliance — a COO/CCO profile. Formalities and specific terms are not yet concluded.

3.2 Consultants / Domain Experts

Who: Advisory roles, industry specialists, part-time or project-based contributors. Value profile: Credibility, domain knowledge, client introductions, strategic input. Risk: Lower commitment, may work across multiple engagements.

3.3 FDE / Integration Managers

Who: People embedded with clients, building and deploying Optale's products into their operations. The Palantir forward-deployed engineer model. Value profile: Direct revenue generation, client success, product feedback loop. Risk: High intensity, client-facing. These people are the revenue engine.

3.4 Tech, Compliance & Data

Who: Engineers, data specialists, compliance officers, governance specialists. Value profile: Regulatory moat (Norway, EU, GDPR), data quality, trust infrastructure, platform reliability. Risk: Critical but less visible. Hard to replace in regulated markets.

---

4. Vesting & Incentive Framework

4.1 Core Principle: Cliff + Vesting with Hybrid Triggers

All equity grants follow a cliff + vesting model combining:

• Time-based vesting — rewards retention and sustained commitment
• Milestone/KPI-based acceleration — rewards measurable outcomes

This avoids the failure modes of pure time-based vesting (rewarding presence over performance) and pure milestone-based vesting (creating gaming incentives and short-termism).

4.2 Proposed Structure by Division

4.3 KPI Categories

KPIs should be measurable, not subjective. Proposed split:

Individual metrics (weighted ~60%):

• Client revenue generated or retained (FDE/Integration)
• Product milestones shipped (Tech)
• Compliance certifications achieved (Compliance & Data)
• Strategic objectives hit (C-Suite)

Team metrics (weighted ~40%):

• Company ARR targets
• Client NPS / retention rate
• Platform uptime and reliability
• New market entry milestones

The team component ensures nobody optimizes their lane at the expense of the whole.

---

5. Equity Allocation Philosophy

5.1 Founder Control

Non-negotiable: Founder retains majority ownership and voting control through at least the first institutional funding round.

Target allocation at pre-Series A:

5.2 Options vs. Shares

Use stock options (or the Norwegian equivalent under aksjeloven), not direct share grants:

• Cheaper to issue
• Easier to handle on departure (unvested options simply expire)
• No voting fragmentation until exercise
• Tax-efficient for employees in Norway (certain conditions)

5.3 Dual-Class Consideration

If/when external capital comes in, consider dual-class share structure (A-shares with 10x voting rights for founder). This protects control even as ownership dilutes through funding rounds. Standard for founder-led tech companies (Google, Meta, Snap, Spotify).

Norwegian corporate law (aksjeloven) allows different share classes with different voting rights, but requires explicit authorization in the articles of association. Should be set up before any external investment.

5.4 Pre-PMF vs. Post-PMF Contributors

People joining now are taking on more risk than someone joining after product-market fit. This should be reflected in:

• More generous equity terms (larger grants, lower strike price)
• But real cliffs — early generosity without cliffs creates dead equity on the cap table
• A clear distinction between "founding team" grants and "scaling team" grants

---

6. Hiring Roadmap & Division Build Sequence

Not all divisions need to be built simultaneously. The sequence should follow revenue and risk logic: hire what unblocks revenue first, then what protects the business, then what scales it.

6.1 Phased Build Plan

6.2 Phase 0: The CEO + COO/CCO Foundation

With Kamilla joining as COO/CCO, the company starts with a two-person leadership team that covers complementary ground:

This pairing means Optale can run early client engagements, build pipeline, and handle enterprise compliance conversations without immediate FDE or tech hires. It buys time to hire Phase 1 roles deliberately rather than desperately.

6.3 First Hires After C-Suite: What to Optimize For

FDE / Integration Manager #1 is the next most critical hire. This person:

• Proves the delivery model works without the founder in every engagement
• Creates the playbook that FDE #2 and #3 follow
• Bridges product and client — their feedback shapes the product roadmap
• Should have consulting or implementation background, not pure engineering

Consultant #1 is the lowest-risk, highest-signal hire:

• Part-time or project-based, minimal equity commitment
• Brings domain credibility and client introductions in a target vertical
• Validates whether the advisory model generates pipeline
• Can convert to a deeper role if mutual fit is proven

Tech hire #1 should be deferred until:

• There are 5+ active clients (platform load justifies dedicated engineering)
• Compliance requirements surface from enterprise sales (GDPR, SOC 2, ISO 27001)
• The founder can no longer maintain platform reliability alongside everything else

6.4 Cadence & Review Points

---

7. Structural Angles to Think Through

7.1 International Arms

If part of the organization operates semi-independently in a different geography (e.g., US/Brasil), the structure might look different from a Norway-based hire — potentially more entrepreneurial, with equity tied to that specific geography's performance. A sub-entity or revenue-share model may make more sense than a standard option grant. The question is how to align incentives while preserving central control.

7.2 FDE / Integration Managers as a Scaling Lever

This is the Palantir playbook: forward-deployed engineers are the wedge into enterprise accounts. Their incentive should directly reward:

• Successful client deployments
• Client expansion (upsell)
• Reusable product improvements extracted from client work

This division is where revenue scales. Incentivize accordingly.

7.3 Consultant Anti-Dilution

Consultants should get the lightest equity touch. They provide value but typically have lower switching costs and shorter horizons. Over-granting equity to consultants is one of the most common early-stage mistakes. Use cash + milestone-based micro-grants instead of standard vesting.

7.4 Pre-PMF Contributors

Early contributors who join before product-market fit are absorbing real risk. Their terms should be meaningfully more generous than post-PMF hires — but with real cliffs. The vesting clock should start at commitment, and acceleration triggers should be tied to concrete company milestones (first enterprise client, ARR thresholds, market entry) rather than subjective assessments.

---

8. Legal & Structural Prerequisites

Before formalizing any agreements:

1. Norwegian startup lawyer review — aksjeloven has specific mechanics for options and incentive programs that differ from US/Delaware norms. Get this right at the outset.
2. Articles of association update — authorize different share classes before they're needed.
3. Standard option agreement template — one template per division, reviewed by counsel.
4. Cap table model — spreadsheet modeling dilution scenarios through Series A, showing founder retention under various allocation/raise scenarios.
5. Vesting schedule formalization — cliff dates, acceleration triggers, good-leaver/bad-leaver clauses.
6. IP assignment clauses — all contributors (especially consultants and part-time roles) must assign IP to Optale AS.

---

9. Open Questions

1. Does the four-division model capture the right organizational shape, or are we missing something?
2. Are the cliff/vesting periods in the right ballpark for Norwegian market norms?
3. What's the right founder retention target at Series A? Is 65-75% pre-raise too aggressive or too conservative?
4. How should we structure international arms differently from the Norway entity?
5. What's the best Norwegian legal vehicle for stock options — direct options under aksjeloven, or a holding structure?
6. Are there Norwegian tax incentives (e.g., SkatteFUNN-adjacent) we should be leveraging for equity compensation?
7. At what point should we formalize an advisory board, and what terms are standard in the Norwegian ecosystem?
8. Is the proposed hiring sequence right — FDE first, then tech, then CTO? Or does the market demand a different order?
9. What are the biggest structural mistakes you've seen at this stage?

---

10. Next Steps

• Circulate this document for written feedback
• Schedule follow-up meeting to discuss feedback and refine
• Engage Norwegian startup lawyer for legal review
• Build cap table model with dilution scenarios
• Draft standard option agreement templates (per division)
• Update articles of association to authorize share classes
• Formalize first agreements with current key contributors

---

This is a living document. Version 2 — 2026-05-07.