How it works
From work question to
an application that stays.
We start with your work. We connect what you already use and build what is still missing. We use AI where it adds something.
Small steps, at your own pace
You take a step, check whether it works, and only then take the next. When you can keep up, we gradually go faster.
Your goal and the time you free up
We start with what you want to achieve with your business, rather than a tool. We also discuss what you will do with the time you save.
The first hour is free. We talk about your goal.
Direction: a day or half a day to choose the goal and the first step.
Pace: up to a fixed number of hours of guidance per month.
Management: we run your environment, with the apps you use.
Build what your software lacks.
Does your current software not fit your work well? Then you get scattered lists, double work and extra steps.
That people build their own apps, dashboards and connections shows where it chafes: their work needs something their software does not offer.
- Scattered lists
- Double work
- Extra steps
From customer question to a fitting proposal.
AI uses your own knowledge and earlier work to prepare a proposal. Your systems supply current prices and availability.
‘Can you deliver the same as last year, but outdoors?’
Finds the previous quote and compares the wishes with product info and working agreements.
With the sources alongside, and the questions that are still open.
Build it yourself. Stay in control, together.
Your team wants to make something that fits the work. IT protects data and systems. Without fixed agreements, the alignment starts over with every idea.
We take away the friction, together with your team and IT.
Without access or agreements on management, your idea gets stuck.
A protected test area and a foundation you reuse.
- Your team builds
- IT stays in control
Each app still needs its own agreements.
A reusable foundation.
Try out new ideas without having to arrange access, data and management again for every application.
The sandbox is a protected test area. The register shows what is running and who is responsible. For each application, we agree who has access and who manages it.
Keep building on the same foundation, instead of starting over every time.
- What you let grow apps, connections, AI help
- Access who may do what
- Data and connections done right once
- Sandbox and register try things safely
- Management and ownership agreed up front
From information to result.
Six parts of an AI application. We set up what your application needs.
- CaptureCapture
Collect information from your work, conversations and documents.
- Knowledge and memorySecond Brain · Memory
Find knowledge and earlier agreements again, with source and context.
- Ways of workingInstructions · Skills
Instructions give direction. Ways of working record how you approach a task.
- Carry out tasksTools · Agents
Digital helpers carry out tasks with tools and connections.
- Work togetherOrchestration · Handoffs
Hand tasks and information over to a person or another helper.
- Measure and improveEvals · Scoreboard
Check quality and value. Improve with what you learn.
Privacy, security, rights and human oversight apply to the whole application.
How a project runs.
Free hour
We look at your work question together. Bring your IT colleague.
First version
Something working, fast, with your own data and your own words.
Try and improve
Your people use it in their work. With their feedback, we make it better.
Carry on without us
Your team knows how it works. You choose who manages it.
One action, step by step
What happens when you drag a card?
You move job OPD-024 for Bakkerij Jansen to “On the way”. This is what happens behind the scenes:
Step 1 of 6
You drag OPD-024 to “On the way”
Your screen shows the card in the new column right away. In the background, one small instruction sets off: “set the status of this record to On the way”.
Where do you stand with AI?
This ladder is about your people and organisation. Which rung do you recognise? We choose a step that fits.
- Explore
Discover what AI can mean for your work.
- Experiment
Try ideas and learn what works.
- Apply
Use an application in your daily work.
- Embed
Make fixed agreements and involve more teams.
- Transform
Develop new services and work together differently.
Isolation
An installation of your own
Every customer gets their own installation in the EU. Your data is kept apart from other customers’ data.
Own database, data warehouse, sign-in environment, keys and back-ups. Inside your installation the database separates your workspaces row by row, and who you are comes from your session, never from what a screen sends along.
We run your installation for you. Rather on your own server? That’s available on request, with the same software.
I work in ITBuilding blocks, hosting and the questions your IT team asks
The building blocks
From your screen to your data
Studio is a fixed base that keeps growing. Click a building block to see what it does.
Building block
Your screen
Everything you see and click. In the Studio editor you put apps together; your colleagues simply use them in the browser. You can install Studio as an app on your computer or phone.
- Works in any modern browser and can be installed as an app.
- Talks only to its own API on the same domain.
Hosting
Where Studio runs
Choose where your apps run.
We host it for you
You get your own installation on Hetzner cloud servers in the EU, with its own database, sign-in environment and keys. We run it for you.
Customer data is stored in the EU. Only what your admin releases to the assistant goes to Anthropic (US).
- On request
On your own server
Studio runs as a standard set of containers. Want to run it on your own servers? We discuss that case by case.
We work out what’s needed together with your IT partner.
Take it with you as a blueprint
You can export apps as a file and import them into another installation; this is tested automatically with every release. You request the export and get it as a file.
After a move, you authorise your connectors again.
For IT
Questions your IT team will ask
Is your question not here? Just ask.
Where is our data stored?
In your own installation on Hetzner cloud servers in the EU: own database, data warehouse, sign-in environment, keys and back-ups. Your data is kept apart from other customers’ data. We run it for you.
Which roles and permissions are there?
In each workspace you’re a member or an admin. You share documents and apps per person with view or edit rights. An admin invites new colleagues themselves.
What happens to the passwords of connected systems?
They never reach the browser and never end up in an export. They’re stored encrypted and only retrieved at the moment an integration needs them.
Can we take our apps and data with us?
Apps can be exported as a file and imported into another installation. You request the export and get it as a file.
How are updates rolled out?
Every change first passes through separate test environments and is checked automatically along the way. A failed update is rolled back.
How does Studio reach our servers or systems?
Studio fetches data from the systems you connect, through a list of allowed addresses. No integrations are switched on by default. Studio itself can only be reached through a secure, encrypted entry point.
