Studios

After a year with AI, most companies do not have a system. They have a collection: a chat subscription here, an automation tool there, a handful of prompts in a shared document. A studio is the answer to that. This entry explains what a studio contains, who owns it, and how operations work.

1:1

one studio per domain

netzstrategen, AI Operations model

3

months of studio operations included in the Kickstart

netzstrategen, Kickstart scope

from €990

per month for continued operations

netzstrategen, platform license

Contents

• What is a studio?
• What a studio contains
• Six studios, six domains
• Who owns the studio
• Studio operations: the three months after

What is a studio?

A studio is the workspace of a domain. It bundles everything that domain needs for AI operations: preconfigured, introduced together with the team, and supported in daily use.

The difference to a stack of tools is the fit. A tool is generic and every user has to make it fit themselves. A studio already fits: it knows the routines, the data sources and the quality standards of its domain.

The difference to an in-house build is operations. A self-written script works as long as the person who wrote it is around. A studio keeps running because operations, updates and oversight are part of the model.

In practice that means people working in the studio do not need to know which model is running underneath. What is visible is the task, not the technology.

What a studio contains

Three building blocks make up a studio. They interlock, and individually they are worth little.

• Workflows: the defined sequences. They describe which steps happen in which order, where AI executes and where a person checks.
• Agents: the acting units. They pursue a goal and draw on the defined workflows to get there.
• Cockpits: the controls. This is where you see what is running, what it costs and where it stalls.

Without workflows the agents would have no reliable building blocks. Without cockpits nobody would know whether any of it works. Only together do they make a workspace rather than a toolbox.

Then there is the invisible part: access rights, data connections, logging. It stays in the background but decides whether a studio can be operated inside a regulated company at all.

Six studios, six domains

Each domain has exactly one studio. Six are in operation: content, SEO, marketing, data, sales and service.

That one-to-one relationship is deliberate. A studio asked to serve two domains loses precisely the property that makes it useful: closeness to the vocabulary and routines of one area.

Several studios side by side, on the other hand, are the normal case once the first one holds. They are then not run in isolation but connected through a shared operating system.

Which studio comes first follows from the domain chosen in the Kickstart. Exactly one per Kickstart.

Who owns the studio

The studio belongs to the company working in it. That ownership is what makes the effort pay off.

Everything created during the Kickstart stays: the workflow that was built, the configuration, the documentation and what the team learned along the way. That holds even if the collaboration ends after the three months.

A studio is not access you rent but a workspace you keep. Operations are the service, not the ownership.

This sets the model apart from a classic SaaS subscription, where cancelling also ends access to your own configuration.

Studio operations: the three months after

The Kickstart includes three months of studio operations. During that time the studio does not run alone: two review calls, continuous optimisation, and a rollout recommendation with a concrete cost frame at the end.

Those three months are the real test. A workflow that worked once in week six proves little. A workflow that survives three months of everyday use proves a lot.

After that there are two paths. Continuing means a platform license from €990 per month, optionally with a service retainer. Stopping is equally possible. The studio and everything learned stay in-house.

So the decision is not made before the start but after four months of real operations, with numbers on the table.

Frequently asked questions about studios

Do we need a separate studio for every team?

No. A studio belongs to a domain, not to a department. If two teams serve the same routine, they work in the same studio.

What happens to the studio if we do not continue after the Kickstart?

It stays with you, including the workflow, the configuration and the documentation. What ends is the supported operation: updates, optimisation and oversight from us.

Is a studio tied to particular AI models?

No. Which model works behind a given step is a configuration question and can change without changing anything for the team. That is exactly why the description lives in the workflow and not in the tool.

Next step: choose your entry point

• Book a free diagnosis call
• All studios at a glance
• Enquire about the Kickstart