When teams grow, systems age or AI reshuffles everything.
As a senior freelancer, I take on the leadership of digital teams, interim management in critical phases and digital development in the AI era — including refactoring of existing codebases. Wherever experience, structure and speed have to come together.
I'm not the executor on call. I'm the first call when structure is missing and speed matters.
Typical phases I get called into.
Digital team without a lead
The team delivers, but nobody sets direction. You need someone who provides direction, prioritises and keeps up the pace.
Legacy code in the AI era
A codebase carries the business but has become sluggish. Refactoring, modernisation and sensible AI integration — without a big bang.
Knowledge walking out the door
A key person leaves. Handovers, documentation and process knowledge are missing — and need to be secured fast.
Growth without structure
Roles are unclear, workflows are missing, communication channels jam. The team works, but not efficiently.
Three focus areas. Seven operational fields.
Interim management
For vacancies, handovers, peaks and critical project phases. I take on responsibility — not just hours.
Leading digital teams
Operational leadership of developers, designers and marketing specialists. Clear priorities, short paths, reliable delivery cycles.
Digital development in the AI era
Architecture and product decisions designed with AI in mind. From prototype to tooling to integration into existing products.
Refactoring existing codebases
Modernising legacy in a structured way — without a big bang. With tests, a clear migration strategy and a realistic timeline.
Team building & structure
Building roles, workflows, responsibilities and interfaces. Clear, documented, transferable.
Onboarding & knowledge
Creating structures, securing knowledge, onboarding new team members better. So nothing gets lost.
Digital advertising & communication
Strategy, management, content, social, campaigns, website and digital projects.
When do I need support?
Pick a phase. I'll show you what changes after 30 days.
A key position is open.
When? Immediately. Once the gap stays open for more than three weeks.
I take over the operational role — not as a placeholder, but with a mandate. Structures remain, even when the successor arrives.
A major account is won — the team for it isn't in place yet.
When? Before kick-off. When promises and capacity don't match.
I set up the foundation: roles, processes, delivery cycles. From day one the client experiences reliability instead of improvisation.
The team grew fast — roles and workflows didn't.
When? When friction costs more energy than the work itself.
I clarify responsibilities, establish workflows and interfaces — documented and lived, not just an org chart.
Deadlines slip, priorities change daily, the overview is gone.
When? Before the client notices. At the latest, once they have.
I sort things out: what counts, what waits, what gets cut. Clear escalation paths, honest deadlines, a plan that holds.
A key person is leaving — their knowledge is about to leave too.
When? Ideally before their last day. Otherwise right after.
I keep the day-to-day running, organise the leaver's knowledge and hand it over to the successor in a structured way.
Not everything. But the right things.
What's measurably better after 30 days.
Clear priorities
Everyone on the team knows what counts this week — and what doesn't.
Clean handovers
Knowledge no longer lives in individual heads — it's documented.
Processes that work
Workflows click. Interfaces are clear. Escalations become rarer.
Operational relief
The internal team can focus again on what it does best.
Transparent communication
Clients, stakeholders and the team know where they stand.
Structures that last
What I've built keeps working after my engagement ends.
In fast. Sort clearly. Deliver reliably.
Analyse
Week one: listen, read, talk to stakeholders. Understand where it really jams.
Prioritise
Three to five work sites that matter in the first 30 days. Clearly named, clearly shared.
Deliver
Take responsibility. Steer. Escalate. Document — all in parallel.
Hand over
Build structures that work without me. A clean exit is part of the job.