One assistant that knows how your business works
and does the parts nobody wants to do.
You have probably already tried a chat assistant and found that it writes well but knows nothing about your company. Meanwhile, somebody is still checking things, chasing people, filing documents, and answering the same questions, usually the person in the company who has better things to do. We build the assistant that does both, and we are the ones who keep it working.
Talk to usWhat it is
An assistant on the surface, and the automation underneath that actually does things.
Every client gets their own assistant, running on its own infrastructure inside the EU, connected to their systems with their permission, and told about their business: what you sell, how you work, who your people are, and what your words mean. It answers questions, and it runs processes, and the more of your systems you connect it to, the more of the running it does.
Underneath it sits ordinary automation that does the work that has to happen the same way every time. The assistant is the part you talk to, and that automation is what makes it more than a conversation.
Three things separate it from the chat window you have already tried.
It knows your business, because everything it is told and everything it reads becomes memory: a set of notes and files that belong to you, rather than a conversation one person has had with it. What you told it in March is still true in September.
It can reach the things you actually work with, because there is a system around it and not just a window to type into. The pieces it is made of talk to each other on a private network of their own, and the only parts of it that anything outside can reach are the ones you asked for and the monitoring that tells us when something has stopped.
It belongs to the company rather than to one person. Who uses it, and what each of them can see, is yours to decide, and what it learns stays with the company instead of leaving in somebody's chat history.
We run our own company on it
We are not running a demonstration version of it. It is the same infrastructure, the same assistant, and the same automation underneath, wired into our accounting, our CRM, the chat our people work in, our code, and the infrastructure under it.
It keeps our accounts and our records where they are supposed to be, and drafts what goes out. It sits in our meetings and turns them into decisions somebody can still find six months later. It makes the small changes to our own software and puts them live. And before anybody starts a new piece of work, it writes down what that work needs, then checks the finished thing against it.
All of it waits for one of us to approve before it takes effect.
Your own setup would reach as widely as ours does, and the reason is where it lives. An assistant that is built into somebody else's software can only see what the owner of that software decided to let it see, and one that runs on its own can see whatever you connect it to.
We built all of it for ourselves. Once we saw what it did to the way the company runs, we decided it was worth offering to others.
In practice
Twelve situations you might recognise, and what can be done about them.
These are the situations that come up most often. What gets built is always shaped around your version of one of them, or around something that is not on this list at all. What is worth doing, and whether your systems will support it, is something we work out before anything gets built, by going and looking at how the work happens in your business.
Three people run through all of this: the one who writes things, the one who remembers things, and the one who notices things. In a large company, those are three different people. In most companies, they are one person having a hard week.
The one who writes things
Answering the mailbox. A customer asks where their order is. The assistant finds the order in your system, sees that it shipped on Tuesday and is sitting at a depot, and writes the reply with that in it. One of your people reads it and sends it. The time this saves is not the typing, it is the three windows somebody had to open before they could start typing.
Preparing a quote. A request arrives for work you have done something like before. The assistant finds the quotes you sent for those jobs, drafts a new one line by line, and shows you which past job each number came from. You change what you want and send it. Nobody has to remember which old quote was the good one, or go looking for it.
Finding people worth talking to. It researches companies, works out whether there is a real reason to get in touch, and drafts the approach. You see what it found and why before you decide whether any of it goes anywhere.
The one who remembers things
Reading what arrives. Contracts, invoices, reports, and anything else that lands as a document gets read, summarised, and filed into a set of notes you can open and read yourself. Then ask what you agreed with a supplier two years ago, and you get the answer with the document attached, so you can see for yourself where it came from.
Turning meetings into decisions. It joins the meeting and afterwards pulls out what was decided and what somebody now has to do. You check that it got it right, and then it is written down with the date, the people, and the reasoning behind it. Six months later, when somebody asks why you decided that, there is an answer.
Being ready for a call. Before a meeting, it puts together who you are seeing, what you agreed with them last time, what is still open, what has happened since that they do not know about, and where each of those came from. It arrives wherever you already read things. Nobody has to prepare in the car.
Asking the company a question. What is our policy on this? What did we tell this customer last year? Which supplier did we stop using, and why? It answers from what your company has already written down, with the source attached, and it answers somebody on the warehouse floor differently from how it answers the person running the company. Every business has one person everybody interrupts. This is mostly for the week they are on holiday.
Answering without opening four things. Where is this order, and has it been invoiced? Has this customer paid, and what did we ship them last month? It reads your systems at the moment you ask, so the answer is what is true at that moment, and not what somebody remembered when you asked them.
The one who notices things
Chasing what is late. It knows what you ordered, what date the supplier confirmed, and what has actually arrived. When something slips, it writes the chase, and it writes the fourth one differently from the first, because it knows this supplier has slipped before and what was said last time. You read it and send it.
Noticing before you do. Stock below where it should be. An order that has not moved in three days. A delivery that was due on Monday. It tells you what happened, what usually happens next, and what it suggests doing, in the place you already read messages, which is a more useful thing to receive than an alert.
Deadlines you agreed to and forgot. Notice periods, renewal dates, warranties, anything with a date in a document nobody has opened since it was signed. It tells you before the window closes, and it quotes the clause it is reading from, so you are reading the wording you actually signed.
When somebody joins or leaves. Accounts, access, equipment, the document pack, the right people told. The parts that are always the same happen on their own, and the parts that need a decision come to you first. The leaving side is the one that matters: almost every business has an account still live for somebody who left last year.
Limits and checks
Some things wait for you. Some things are not available to anybody.
An assistant that can act on your systems is a different thing from one that can only talk, so what it is allowed to do matters as much as what it can do.
Most of what happens is not the assistant deciding anything. Talking to your systems, moving the data, applying the rules that have to come out the same every time: that is done by ordinary software which behaves the same way on every run. The assistant does not go rummaging through your database, it is handed the few things an answer needs and asked to do the part that genuinely takes judgement. That is most of why it is quick, and why nothing gets sent to the AI model that did not need to go there.
Beyond that, some things are enforced around it rather than asked of it. The passwords and logins to your systems are held by the automation and not by the assistant, so the assistant never sees them and has nothing to hand on. It reaches only the systems you have connected, and connecting another one is a decision you make, since it has no way to arrange that itself. Where a connection was set up for reading only, nothing can be written through it, whatever the assistant is asked to do. None of that depends on the assistant behaving well, because it is a property of where it runs, not an instruction it has been given.
The same goes for your own rules. A line that must not be crossed, a price floor, a limit on what can be promised, a threshold above which a second person has to agree: that rule sits in the system instead of in the assistant's instructions, and it cannot be talked out of something it cannot see.
Who can see what works the same way, and in some businesses the law decides it for you: a warehouse team that should not see what you pay your suppliers, a firm whose client files must never meet each other. The limit is applied before anything is looked up, so nobody gets an answer built out of files they are not allowed to open, because those files are never opened for them in the first place. Setting those limits, and changing them later, is work we do with you.
An email or a document that arrives from outside your business can carry instructions that are meant for the assistant, not for you, and no assistant can reliably tell the difference. None of this rests on it telling the difference: something arriving that way cannot reach a password the assistant never holds, cannot write through a connection set up for reading, and cannot reach anything you have not connected it to. Reading is the one thing those limits do not stop, so text arriving that way can steer what the assistant looks at, within whatever you have connected and within the same limits on who can see what. How far that can go is therefore set by how much you connect it to, and that is yours to decide.
Other things wait for a person: anything that leaves your business, and anything that cannot be undone. Those two are where we start, and wherever else your business wants somebody to look first, that waits as well. You decide each time, and that is not a setting the assistant can reach, so adding one, moving one, or taking one away is a conversation with us rather than a switch somebody can find.
What you are shown at that moment is more than the finished thing with a button under it: what it looked at, what it found, what it concluded and why, and then the draft.
An approval step that shows you only the output becomes a reflex within a week, because you click it while doing something else, and after that nobody is reviewing anything. Seeing the work is what keeps the approval a real decision.
All of it is recorded, so the day somebody asks why something went out, there is an answer with a name and a time on it.
Where this sits
Large companies have people for this. The rest of us need another way.
In 2025, one in five EU companies with ten or more staff was using AI in some form. Split by size, the picture is sharper: fifty-five percent of large companies, thirty percent of medium ones, and seventeen percent of small ones.
That gap is not about money, because the tools cost roughly the same for everybody. Separate research into smaller firms found that about half say their people do not have the skills to use this kind of tool, and among those not using it at all, more than half give that as the main reason.
When companies do start, a lot of it does not survive. A survey of more than a thousand companies across Europe and North America found that forty-two percent had abandoned most of their AI projects, up from seventeen percent a year earlier, and that on average close to half of the trials they ran were dropped before going live.
The missing piece is not the software, it is somebody whose job it is to make it work and keep it working. That is the part a licence cannot give you, and it is why this comes with an engineer rather than a login.
What you have probably already looked at
A consultancy or a systems integrator. They work in months and in six figures, which is the right shape for rebuilding how a whole company works and the wrong one for a handful of processes that are quietly costing you hours. Most also will not take on a job below a certain size, and this kind of work never reaches it.
An automation tool somebody set up. Fast, cheap, and genuinely useful, right up until something changes in a system it depends on. A connection breaks, a permission needs granting again, a field gets renamed, and it quietly stops. Nobody did anything wrong, and the tool is not the problem; it is that nobody owns it, so nobody notices for two weeks.
A chat assistant. These remember now, which they did not a year ago, and they can be connected to a drive, a calendar, even a mailbox. What they remember is one person's conversation, mixed in with whatever else that person uses it for, and it stays theirs. What your colleague worked out last month is not available to anybody else, and when one of those connections stops working, it is you who finds out and you who fixes it.
This does what the automation and the chat assistant do, and somebody owns it. It knows your business because it has been told about it and can read your own information, and it acts because there is automation underneath it that runs the same way every time, with a person responsible when that breaks. Sometimes the honest answer is that you need less than that, and when it is, we say so before anybody has built you anything.
How it starts
Nothing gets built until somebody has looked.
A first call.
Thirty to sixty minutes, and it costs nothing. We get to know your operation, what you have already tried and why it did not stick, what you would want it doing first, and whatever you want to ask. By the end, you have an idea of what this could look like for you, and we know where an audit would need to look.
An audit.
One to two weeks, depending on how much there is to look at. We go through how the work actually happens: which tasks eat the hours, what data you have and what state it is in, and what has already been automated and where that could work better. You end up with a written report saying what is worth automating, what it will cost, what difference it should make, and in what order.
Building it.
We set up your own environment, connect it to the systems the work depends on, and shape each piece around how your operation runs. It gets tested on your own data, starting small and widening once it is working, and then runs alongside what you do now so you can see it working.
Then it runs.
An engineer who knows your setup is watching it, fixing what breaks, and keeping it working as things around it change. Every month you get a short written account of what it has been doing, in whatever terms matter for your operation. Nobody has to ask how it is going.
What it costs
Three levels of work. Your systems decide which.
The same piece of work can sit at different levels, depending on what it has to reach. Answering a mailbox for a shop platform that is easy to connect to is a small job. The same thing for an older system that can only be reached through its database is a larger one. So what sets the level is how many systems are involved, how much work each one takes to reach, and how many people depend on the result.
| Workflow | Integration | Operations | |
|---|---|---|---|
| What it covers | One or two processes automated | Several processes, or your core system connected | Multiple systems and several people, across the business |
| Audit | 350 | 700 | 1,800 |
| Build | 2,900 | 7,500 | 16,000 |
| Every month | 129 | 349 | 899 |
| Included support | 1 hour a month | 3 hours a month | 7 hours a month |
Prices are in euros, before VAT.
After the first call, you will have an estimate of which level you are likely to be, and the audit price that goes with it. The audit is what settles it, and it can go either way: if the work turns out smaller than it looked, you pay the smaller level, and if it turns out larger, you pay the larger one, while the audit price you already paid stays where it was. Either way, the report gives you the build price before you decide whether to go ahead. Half of what you pay for it comes off the build if you go ahead within thirty days.
Other things are available as add-ons, agreed separately: more support time, the ability to build your own automations, additional assistants each with a job of their own, and letting it deal with your customers directly.
And if what you need is bigger than Operations, that is a custom build and not a level on this table, which makes it a conversation rather than a price.
If it is just you
The same thing, at one desk.
Everything above is the same product whether a company runs it or one person does. The version for one person is called Private, and it is not a cut-down version of the business one.
It remembers properly, through a memory system of its own and the same set of notes and files built out of your own material. It works on the things you actually use, and it keeps working when you are not there to ask. That is the difference from a chat subscription.
We set it up for you on infrastructure of its own, brief it on how you work, and put it in whichever channel you want to use it in. There is no audit and nothing to build, so it takes days, not weeks.
Connecting it to your own things is where it becomes yours, and you can do that yourself, because building your own automations is included at this level. On the business levels, it is something you ask for separately, because anything built there runs on a system other people depend on, and what the extra pays for is us staying answerable for that system while somebody else is changing it. Here the only person affected is you.
What you build can reach everything the assistant already knows about you, and you are not the one keeping it running. If you would rather we did the connecting, that is something we can arrange separately.
99 a month, including VAT. Three months minimum, with no setup fee.
Questions we get
What it can do, and what it takes
Could we just build this ourselves?
You could. What sits underneath is built on open-source technologies that we have customised, and somebody technical could put a version of it together. What that does not include is the infrastructure you would then be paying for and keeping alive, or somebody whose job it is to notice when it stops. Both of those come with this, and keeping it working next month is a job somebody actually has. If you already have that person, you may not need us.
Can you connect to the systems we already use?
Usually, yes. What matters is what a system lets you read and write, which ranges from a modern interface to an older one you reach through its database. Finding out what yours allows is part of the audit, and it is most of what decides which level you end up at. Where a system cannot do what the work needs, building that into it is something our engineers can take on as their own piece of work.
What language does it work in?
Whichever one it is spoken to in. If somebody writes to you in German, it reads German and drafts the reply in German, and your own people can work with it in Slovak while a colleague works with it in English. The same goes for what it reads, so a contract in one language and a question in another is nothing unusual.
How soon does it do anything useful?
The audit is one to two weeks, and the smallest builds are running about a month after that. Larger ones take longer, because there is more to connect. In both cases, it runs alongside what you already do before you depend on it.
How much of our own time does this take?
Most of the work is ours, but not all of it. The audit needs a few conversations with the people who actually do the work, and access to the systems it looks at. The build needs somebody who can answer a question when something is unclear, and somebody who can say yes. How much that adds up to depends on what is being built and how many of your systems it touches, which is one of the things worth working out on the first call.
Can it deal with our customers directly?
Not to begin with. The default is that it drafts and one of your people sends. Letting it talk to your customers means an assistant of its own, not this one pointed outwards, so what it can see is only what your customers should see. It is an add-on, agreed separately.
Your data, and who sees it
Does what we give it go into a model?
Nothing you give it is used to train a model. We do not use any provider in a configuration that trains on customer data. The infrastructure your data sits on is inside the EU, and the model your assistant uses is chosen for each client, so where those need to sit inside the EU as well, that can be arranged. We sign your own data processing agreement.
Who at your end can see our data?
Nobody, unless something has to be fixed in your live systems. Where it can be done that way, the work is built on test data or on a copy of your systems and pointed at the real thing once it is ready. When somebody does have to look at live data to fix something, that is the engineer who works on your setup and nobody else, and nothing is copied outside your own environment.
Can different people see different things?
Yes. Who has access and what each of them can reach is set when it is built and changed through us, so it is not something somebody can alter by finding a setting. For a firm with walls between clients or matters, that is one of the first things we work out.
What it costs, and the terms
Who owns what gets built for us?
You own what is specific to you: the workflows, the configuration, and everything the assistant has been told about your business. The tooling underneath stays ours and is licensed to you as part of the system.
What if we need more support than the hours included, or want to add something new?
Extra support time is charged at a standard hourly rate, the same regardless of which level you are on. Something genuinely new, like another process automated or another system connected, is a separate piece of work that we agree with you before it starts.
Is the AI usage included, or is there a bill behind the bill?
It is included, and there is no per-use line on your invoice. The amount is sized to how much you use it, and the figure is written into what you sign, not something you discover later. For a business, that sizing is one of the things the audit measures. If you go past it, the extra is invoiced, and if that happens every month, it means the figure no longer matches what you are doing, so we set a new one rather than keep billing you the difference.
Do unused hours carry over?
They do not. They are there so somebody is available when you need them, and not as a balance you spend down.
Are we tied in?
There is a three-month minimum once it goes live, and it is month-to-month after that.
Is there anything off for paying for a year?
Ten percent, if you pay it up front.
When something goes wrong, and leaving
What if it gets something wrong?
You tell us, which is part of what the included support is for. Someone looks at what let it through and changes that, a rule, a check, the way it handles that particular case, so the same thing does not happen twice. Everything it did is recorded, so finding the cause is usually quick.
What if something breaks outside business hours?
Support is in business hours, Central European time, so that is when it gets looked at. When something goes wrong, it usually stops there instead of carrying on and making it worse. Whatever happened is in the record, so fixing it does not start with working out what went on.
If we leave, can we take it with us?
It runs in an environment that is yours, and everything about your business goes with you. The notes and files it works from are ordinary files you can read and copy anywhere, your configuration and your workflows are yours, and we would hand over what is running and how it works. The tooling underneath is ours and is licensed to you while you are with us, so that part would need replacing, and you would need somebody technical to pick it up from there. We keep nothing of yours. Thirty days after the service ends, the environment is destroyed with everything in it, and the backups of it are cleared at the same time. The thirty days are there so you can still come back for a copy you forgot, and if you would rather all of it went on that last day, say so and it will.
Tell us what is taking your time.
Thirty to sixty minutes, at no charge. Come with whatever is slowing you down most and whatever you want to ask. We go through it with you, so you have a clearer idea of what could be done about it and what the next step would be.
If what you need is a system built for you instead of an assistant running in your business, that is the other half of what we do.