+Farid Humblot // for Optiml
Let's talk  →
Outside-in operating plan · for the Head of Operations brief

The Optiml
Operating System+

A 90-day backbone that turns the team across Zürich, Munich and London into one auditable operating rhythm. Built the way you build REDI: structured inputs, clear decisions, a clean audit trail.

Built from public sources, before we've spoken. This is the operating system I would install at Optiml in one quarter, and the numbers I would run it on. Where I have it wrong, that is the conversation I want.

+€8M Seed, closed +3 entities · CH / DE / UK +6 Year-1 objectives mapped +Seed → Series A

What this role is really for.

Four reads on the operating reality, before the plan. Each one shaped how I scoped the 90 days.

+ 01 / READ
Decision record · 01

A backbone, not an admin seat.

The brief says it twice: own company-wide operations, not office management. The job is to translate the founders' vision into operating rhythm, and to give the org clarity, accountability and speed. I scoped this as a systems-builder role from the first line.

Decision record · 02

Runway is bought. Now build the engine.

The €8M Seed, co-led by KOMPAS and Planet A with BitStone, The Bau Ventures and Innovation Endeavors, extended the operational horizon. The next 18 months turn that capital into a Series-A-ready operating system. That is what an Ops hire is for at this exact stage.

Decision record · 03

Three entities, one company.

Zürich HQ, plus satellites in Munich and London, means CH / DE / UK legal, payroll and employment surface. The work is making three jurisdictions feel like one org: shared comp logic, shared cadence, shared information, clean compliance under FADP and GDPR.

Decision record · 04

Founder bandwidth is the scarce asset.

Petkov, Campos and Dehnert carry product, tech and commercial. Every hour they spend on cadence and coordination is an hour off the product. The Head of Ops hands that focus back by owning OKRs, hiring ops, reporting and board prep.

The first 90 days.

Diagnose, install, scale. Each deliverable maps to one of the six Year-1 objectives in the brief.

+ 02 / PLAN
DAYS 0 – 30
Diagnose & stabilize
  • Operating audit: map every recurring meeting, decision and report. Cut the duplicates. OBJ 4
  • Stand up one source of truth in Notion: company wiki, decision log, live org map. OBJ 1·4
  • Lock the 12 board metrics and their definitions with the Fractional Head of Finance. OBJ 2·5
  • 1:1 with every team lead. Surface the three bottlenecks slowing delivery. OBJ 4
DAYS 31 – 60
Install the cadence
  • Launch the rhythm: weekly ops review, monthly business review, quarterly OKR and board cycle. OBJ 1·2
  • Run the first full OKR cascade: company → function → team, one page each. OBJ 2
  • Ship comp framework v1: role leveling and salary bands across CH / DE / UK. OBJ 3
  • Set the performance cycle: light, quarterly, tied to OKRs not theatre. OBJ 3
DAYS 61 – 90
Scale the systems
  • Automate reporting: one dashboard, refreshed weekly, no hand-built decks. OBJ 2·5
  • Build the hiring engine: scorecards, pipeline, onboarding that holds past 50 people. OBJ 3
  • Close governance gaps across entities: contracts, payroll, data residency. OBJ 4
  • Build the Series-A operations data room: 18 months of clean metrics, one board pack that runs itself. OBJ 5

The operating rhythm.

One heartbeat for the whole company. Decisions surface fast, owners are named, nothing waits for a meeting that is two weeks out.

+ 03 / CADENCE
Daily

Async standup

One thread in Slack. Yesterday, today, blockers. No meeting. Blockers surface in under a day.

// 5 min · written
Weekly

Ops review

The live metrics, the open risks, the decisions due. One owner per line. We leave with actions, not notes.

// 45 min · leads
Monthly

Business review

Function leads present against OKRs. Burn versus plan. What we will stop, start, keep next month.

// 90 min · company
Quarterly

Reset & board

New OKRs, board pack, comp and performance checkpoint. The quarter closes on one page everyone trusts.

// half day · board

One goal, cascaded.

An illustration, not a prescription. How a single company objective reaches a team without losing its edge.

+ 04 / OKR
Company · Q3
Reach Series-A operational readiness.
KR 1
Operational readiness score ≥ 80%
KR 2
12-metric board dashboard live & trusted
KR 3
Comp + leveling adopted in all 3 entities
Function · People & Org
Hiring scales without breaking the culture.
KR 1
Time-to-hire < 35 days
KR 2
Onboarding NPS > 8 at week 4
KR 3
90-day retention of new hires 100%
Team · Talent
Every open role has a scorecard and a pipeline.
KR 1
100% of roles with a written scorecard
KR 2
3 qualified candidates per role in pipeline
KR 3
Interview-to-offer feedback < 48h

The numbers the board sees.

Twelve, no more. Same definitions every quarter. The four that set the Series-A clock up top, the supporting cast below.

+ 05 / METRICS
to plan
Net new ARR
The quarterly number that sets the Series-A clock. Tracked to board plan, ±10%.
< 1.5
Burn multiple
Net burn over net new ARR. The metric a Series-A lead opens with.
≥ 110%
Net revenue retention
Expansion inside each institution, portfolio by portfolio.
≥ 18 mo
Cash runway
Months of room on current burn. Alert under twelve.
Supporting cast
Growth
Pipeline coverage
Qualified pipeline against next quarter's new-ARR target.
≥ 3x
Growth
Enterprise logos live
Institutions in production. The proof the category is real.
signed & live
Retention
Gross logo churn
Institutional accounts lost. Enterprise should barely move.
< 5% / yr
Finance
Gross margin
Software margin after delivery and hosting. Keep it clean.
≥ 80%
Finance
CAC payback
Months to earn back a new institution. Enterprise is patient, not infinite.
< 18 mo
Delivery
Time-to-onboard a portfolio
Signed to first decision in the platform. Your wedge is speed.
< 30 days
People
Headcount vs plan
Hiring on pace, key roles not left open.
±1 · roles < 60d
People
Regretted attrition
The people you wanted to keep, walking. The early-warning light.
< 5%

These are my twelve. For a company selling decision intelligence to institutions, I would weight burn multiple and net retention over raw logo count. Which two would you swap?

The readiness cockpit.

Your product turns messy inputs into one auditable decision. So does this. Seven workstreams, each with an owner and an exit metric. Apply the 90-day plan and watch Series-A readiness move.

+ 06 / COCKPIT
Operational Readiness
Optiml · outside-in model by F. Humblot
7 workstreams · Q3 plan
39
/ 100 READY
Forming
 
Each dimension is a 90-day workstream with an owner and an exit metric. Drag one to pressure-test it, then tell me which score you would change.

Three jurisdictions, one audit trail.

The administrative and legal surface across entities. Owned with the Fractional Head of Finance and external providers.

+ 07 / ENTITIES
Surface
Switzerland
Germany
United Kingdom
Entity
CH · HQ, ETH spin-off
DE · Munich hub
UK · London hub
Payroll
Swiss provider + AHV/BVG
DE provider + social
UK PAYE provider
Employment
Bands + leveling, one logic
Bands + leveling, one logic
Bands + leveling, one logic
Data
FADP
GDPR
UK GDPR
Accounting
External + Xero
External + Xero
External + Xero

I do not own the bookkeeping. I own the system and the audit trail. The Fractional Head of Finance keeps the ledger. External providers run accounting, payroll and legal. My job is one comp logic across three countries, clean compliance, and a board pack the auditors never argue with.

Why me.

No adjectives. Three links and two sentences.

+ 08 / PROOF

I build the connective tissue. At Decathlon Switzerland I run activations and CRM: cross-functional systems, data and cadence at retail scale. Before that I co-founded a B2B / B2G SaaS company from zero, ran revenue as a fractional CRO, and scaled commercial operations across eight markets. EMBA, EDHEC, top of class. EU citizen, already in Zürich.

Big-group rigor, startup speed. That is the combination this role needs.
Three operating calls I'd want your take on
OKRs quarterly, or per tertial like a lot of Swiss scale-ups run them?
One Notion for wiki and tasks, or Notion paired with Linear for delivery?
Xero across all three entities, or local books with a consolidation layer on top?
And the one only you can answer: where does the operating model strain first as you scale? Worth 30 minutes. Tuesday or Thursday afternoon next week?