Skip to content
Vogel

Operations Lead / COO (m/w/d)

MünchenOnsite · Germany
Staff · FullTime · Vogel
POSTED 24 AUGVERIFIED 5H AGO
Apply Ask
Role
77 days opentrue age
Posted 24 Aug
Payats field
€105k–205kposted
▲ +48% vs market median €105k
€92k€205k
Market p25–p75
€92k–€160k
Vogel p25–p75
€150k–€176kn=4
Munich · n=12 · 365d to 6 Nov
CompanyVogel →
29open roles
Opened · 30d
+0
Closed · 30d
−0
3d of snapshots · 30d window
Market
23,258open · Staff Other
Opened · 7d
+1,6097% of open
All other
624,310open
All tracked boards · live 10 Nov · n=23,258

The opportunity

Tax advisory is an operational business. Every booking, every payroll run, every set of financial statements follows a process, and hardly any of them has ever been systematically questioned. They work because experienced people know their workarounds. That is the lever, and in this industry nobody has claimed it yet.

The model is no longer the scarce part. Expert knowledge from real cases is, and AI labs pay a premium for exactly this. Vogel holds what no AI-native player has: decades of experience with several thousand mid-sized companies. You turn that knowledge into the standard every location works by.

Vogel acquires independent advisory firms and builds them into the strongest name in their region. Every acquisition broadens that base. Operations means carrying this model: the same processes at every location, technology people actually use day to day, and an integration that runs faster the fifth time than the first.

You own Operations end to end: harmonizing and automating processes, internal tools, IT infrastructure and the integration of every new unit. For the software we build ourselves, you drive the product side: you shape what it does and in which order, together with Moritz Vogel as managing director in the role of chief product officer. The CTO owns how it is built. You build the function from the ground up. You work directly with Moritz Vogel.

What you'll do

Harmonizing and automating

Work through bookkeeping, payroll and financial statements on site, on real cases, with the advisors who handle them daily. Harmonize processes across locations and automate what can be automated.

Decide the tool stack and its standards: what we buy, how we set it up, what we switch off. You make that call, not a committee.

Drive the product side of our own software: prototypes you build yourself, the functional data model with the advisors, acceptance and rollout. Which problem comes first you decide together with management. Our advisors are your users.

Your benchmark: every process must hold at twice the client volume without twice the people.

Integrating acquired units

Own the integration of every new location: connectivity, data migration, moving onto our processes, readiness from day one.

Turn it into a repeatable routine rather than a project. What takes months at the first location takes weeks at the fourth.

Spot, with the advisors on site, where an acquired firm does it better, and adopt it.

Team and operations

Grow the Operations team to five or six people within twelve months. You choose the people and shape their focus areas.

Own the leading metrics: digitization rate, adoption, turnaround times per location. Trace their root causes yourself.

Stay close to the system. Anyone who only delegates and follows up loses their judgment within a year.

Questions you'll answer

In a process that grew over the years, where does substance end and habit begin, and how do you decide without turning the practitioners against you?

What belongs in the standard that applies at every location, and what may an acquired firm keep?

Four initiatives, time for two: how do you decide the order?

What success looks like

After 6 months: All processes across the locations are mapped, with numbers instead of impressions. Two core-business processes run automated in daily operations, the first piece of our own software is in daily use by a team, and your first hire is selected.

After 12 months: A team of five to six people with clear focus areas. Operational metrics are measured, not estimated. The integration path is a documented routine, and the tool stack is decided.

After 24 months: Operations runs without daily involvement from management. Every further acquisition follows the same pattern, and the effort per location falls instead of growing with it.

Where it leads: from Operations to overall responsibility for running the business. Once our own software outgrows Operations, product becomes a line of its own, and your path continues with running the business. This is the management career at its most consistent, decided by contribution, not years served.

Source · VogelFirst seen 2 NovOriginal ↗