Clear answers before we talk.
For founder-led businesses, remote-first teams and small B2B companies in Europe that want clearer communication, more reusable content and more controlled workflows.
This page answers the practical questions first: fit, offer logic, AI boundaries, privacy-first infrastructure, pricing logic, rights and realistic limits.
What this page is for
Clarity before a call.
The goal is not to answer every edge case. The goal is to help you see quickly whether the fit is right and where the real boundaries are.
What the work combines
- Cinematic editing and post-production
- AI-assisted content workflows
- Video avatars and explainer formats
- Privacy-first stack setup on EU-hosted infrastructure
Section 01
Fit & starting points
Start with the buying questions first: who this is for, how the offers connect, and what the best entry point usually is.
1
Who is Nomadic Filmworks a good fit for?
Nomadic Filmworks is a strong fit for founder-led businesses, remote-first teams and small B2B companies in Europe that want clearer communication, more reusable content and more control over how workflows, files and delivery are handled.
It is especially useful when:
- your expertise is real, but your communication still feels vague or inconsistent
- you already have useful recordings or knowledge, but no clear system around them
- your team is losing time to scattered tools, manual handovers or weak content reuse
- privacy, delivery control or EU-hosted workflows matter in practice
Selected mission-driven projects can still be a fit, but that is not the main commercial focus.
2
Are these separate services or one connected offer?
They are connected parts of one production logic.
- Editing makes quality and message clarity visible
- AI-assisted workflows make content reusable
- Video avatars make recurring knowledge easier to access
- Privacy-first systems create more operational control
Not every project needs all four. But many projects become more useful when they stop being treated as separate worlds.
3
What is the best way to start?
That depends on the actual bottleneck.
- If your main issue is underused footage or weak storytelling, editing is often the right start.
- If you already have useful recordings but barely reuse them, an AI-assisted content workflow is often better.
- If the real pain is scattered tools, manual handovers or file chaos, the privacy-first stack is usually the right entry point.
The goal is not to push you into the biggest package. The goal is to identify the smallest useful start.
4
Do I need all four building blocks?
No.
Some clients only need strong editing. Some mainly need a content workflow. Some need a smaller operational stack. Some need a combination.
The point is not to add more services than necessary. The point is to build a setup that actually solves the problem without unnecessary complexity.
Section 02
Content & source material
Most projects do not fail because there is no content. They fail because good source material is underused, badly structured or routed through weak workflows.
5
Can this work with existing videos, webinars, interviews or recordings?
Yes. In many cases, existing material is the best starting point.
You do not need a giant new production if there is already useful source material. Often the real issue is not lack of content, but lack of structure, reuse and editorial decisions.
6
Do I need a large content backlog for this to make sense?
No.
One strong recurring source can already be enough if the workflow is designed carefully. The goal is not endless output. The goal is a smaller, more reliable system around material you already have or can produce realistically.
7
Do you also edit the core source video?
Yes, where needed.
A good workflow usually starts with source material that is already clear, usable and worth reusing. If the base video needs editorial work first, that can be part of the project before the reuse workflow is built around it.
8
Do you also film on site?
My core offer is focused on editing and post-production, not full on-location production as a standard service.
Smaller supplementary shoots may be possible in selected cases, but they are not the default scope. If a project depends on a larger shoot, it is better to define that clearly instead of implying something broader than the current offer.
9
How do we handle files and handover?
For many projects, files are exchanged through a private Nextcloud setup on EU-hosted infrastructure. That keeps uploads, delivery and collaboration more structured than ad-hoc file transfers across scattered tools.
Deliverables are defined in the offer. Depending on the project, that can include final exports, shorter versions, subtitle files, structured folders or handover notes.
Section 03
AI, avatars & boundaries
AI can remove repetitive work. It should not flatten the message, invent claims or replace judgment where trust matters.
10
How do you use AI in projects?
AI is used as a tool, not as a replacement for judgment.
- transcription
- draft text blocks
- subtitle support
- content variations
- workflow support and repetitive admin logic
What AI should not do is flatten your message, invent claims or remove editorial responsibility. The important decisions remain human.
11
Will AI write and publish everything automatically?
No.
The value is not blind automation. The value is reducing repetitive work while keeping review, control and credibility intact. If communication should remain trustworthy, someone still needs to make real decisions.
12
When do video avatars actually make sense?
Video avatars are useful when the goal is repeatable explanation, not emotional storytelling.
Good use cases include:
- onboarding
- training
- FAQ-style explainers
- internal knowledge transfer
- multilingual updates
They are usually less suitable for sensitive stories, trust-heavy founder communication or anything that clearly needs real human presence.
13
Can sensitive material stay on a more private setup?
Where it makes sense, yes.
I also work with self-hosted components such as Nextcloud and n8n and can build workflows that reduce unnecessary third-party exposure around files, routing, delivery and selected automations.
That does not replace legal advice or guarantee blanket compliance. But it can create a much more controlled and transparent setup.
Section 04
Privacy-first stack
This is a lean operational base for small-team reality, not a bloated infrastructure project and not a promise of magical compliance.
14
What does the GDPR-Ready Operations Stack include?
The GDPR-Ready Operations Stack is a fixed-scope starter setup for solo founders and small teams that want a more independent operational base.
Current typical scope:
- Hetzner server setup in Germany
- Nextcloud for files and collaboration
- Baserow as a lightweight database layer
- 1 custom n8n automation
- documented handover
- 30-minute walkthrough call
It is meant as a practical foundation, not as an oversized infrastructure project.
15
Is this fully managed hosting or ongoing IT support?
No.
This is a scoped setup and handover engagement, not a permanent managed hosting contract and not 24/7 incident response.
The goal is to give you a documented, understandable setup that you can continue yourself or hand over later with less friction.
16
Is this guaranteed to be GDPR-compliant?
No honest provider should promise that as a blanket claim.
What I can offer is a more privacy-aware, EU-hosted and technically more controllable setup with fewer careless dependencies. Legal compliance still depends on your actual processes, contracts and responsibilities.
17
When is a privacy-first stack a good fit — and when is it not?
It is a good fit when:
- your files and workflows are spread across too many tools
- your team wants more control over delivery and access
- privacy and data location matter in practice
- you want a small, understandable base instead of SaaS sprawl
It is not a good fit when:
- you want enterprise infrastructure
- you expect fully outsourced ownership forever
- you need strict uptime SLAs and permanent managed operations
- you do not want any self-hosted responsibility at all
Section 05
Process, pricing & practicalities
This is where scope becomes concrete: project start, handover, pricing logic, timelines, agreements, rights and the kinds of work I will decline.
18
How does a project usually start?
Usually with a short message about your situation.
You do not need a polished brief. A few useful points are enough:
- what you are trying to improve
- what already exists
- where the friction is
- what kind of outcome you need
From there, we clarify whether the project makes sense and what scope is realistic.
19
Do you work done-for-you or as a handover partner?
Usually both in a practical mix.
I build and test with a real use case, then hand things over clearly enough that you are not left with guesswork afterwards.
That balance matters: useful execution first, understandable ownership second.
20
How do you price your work?
Where scope is standardized, I prefer fixed prices.
Where scope depends heavily on source material, complexity or decision-making, I scope it after a short conversation and send a written offer.
That means fixed-price entry offers where the scope is clear, and custom pricing where the work is genuinely variable.
21
How long does a typical project take?
That depends on scope, material and responsiveness.
- smaller editing work can move relatively quickly
- AI-assisted content workflows usually need time for testing and refinement
- avatar work depends on script clarity and assets
- stack work depends on the starting situation and the chosen scope
If a deadline is unrealistic for one person working carefully, I will say that early.
22
Can you sign an NDA or DPA / AVV?
Yes, within a reasonable scope.
For sensitive projects, confidentiality and data-processing responsibilities can be defined clearly so your team or data protection contact can review the setup properly.
23
Who owns the final material and the raw files?
That depends on the agreement, licensing and any third-party assets involved.
As a rule:
- your source material remains yours
- final deliverables are licensed or transferred as agreed in writing
- third-party elements such as music, stock or platform-dependent assets may have their own usage conditions
The clean version is simple: rights and limitations should be clarified before delivery.
24
Do you use my material to train AI models or for other clients?
No. Not without your explicit consent.
Project material is used for your project. If AI services are involved, they are used for defined tasks such as transcription, drafting or workflow support, not as unrestricted permission to reuse your material elsewhere.
25
Are there projects you do not take on?
Yes.
I do not take on work that:
- promotes hate, dehumanisation or misinformation
- depends on clearly unrealistic expectations around budget, speed or scope
- requires me to pretend weak source material will somehow become excellent through magic
I may also decline projects where the setup or material is so weak that I cannot stand behind the result.
Next step
If the fit looks right, send a short outline.
You do not need a polished brief. A few lines about what feels messy, what already exists and what outcome you want are enough for a first assessment.
