blumi builds AI agents that are employed, not installed. Each one has a job, its own credentials, an onboarding, a manager who corrects it, and a review every week. Nothing it cannot undo happens without a person.
Built on seven agents running inside Artivive, a company serving more than 750,000 creatives worldwide. Every one of them is bespoke. No two companies get the same colleague.
Under each badge: what it is doing right now. Turn one over for what it may reach. Slide sideways for the rest.
Today 09:14
A replayed day, written from real work.
Names and companies are invented. The work is not.
Drag the line.
The models are the same. The difference is everything around them: a job description, a schedule, a manager, credentials, a queue that belongs to someone. A tool answers when asked. A colleague notices at 07:35 that three tickets share one cause.
That is what blumi builds. Not a chat window with your logo on it. A colleague with a file.
Before a line of code, there is a job description. What the colleague is responsible for, what output a person checks, when it works, who it reports to, and what is not in the job. If the job cannot be written down, there is no colleague in it, and we say so.
Every one of these is written for one company. None of them is a template.
You are finance. Try switching on a refund.
A colleague gets its own credentials, issued for its job and nothing wider. A key that can read payments cannot refund one, whatever the colleague is told and whoever is telling it. The limit is set at the provider, not in a prompt, so it holds on a bad day too.
Every use of every key is logged with the colleague's name on it. Like a badge at a door.
The first weeks are reading. Then drafting, with a person reading every draft. Then one lane at a time, each released when the corrections stop coming. Trust is earned in the file, not assumed in the contract.
This is the part most projects skip. It is the part that decides whether the colleague is still there in six months.
Hello Anna, you are right, August was charged twice. I have asked for the second charge to be refunded and you will see it within five working days. Sorry for the trouble.
Mira, support
You are Jonas, head of support.
Sending to someone new, paying, deleting, promising a date. The colleague drafts, explains why it is waiting, and waits. Refuse it and it asks what should change, redrafts, and waits again. It does not sulk and it does not sneak.
This is not a limitation we accept. It is the job. Nothing leaves without a person, and every decision is logged with the person's name on it.
A correction typed once is filed with who gave it and when, and checked on every later draft. The colleague does not need to be told twice, and it does not forget when someone new joins the team.
Over a year that file is the most valuable thing in the company: how you actually want the work done, written down by doing it.
You are Jonas. It is Sunday evening.
What it did, what it got wrong, what it was corrected on. Then it proposes one fix, and a person approves it or not. Nothing changes on its own, and nothing that went wrong is quietly forgotten.
This is the point where "employee" stops being a metaphor. A tool gets updated. A colleague gets reviewed.
Support at a travel agency, at a chain of bike shops and at an architecture studio is the same word and three different jobs: different access, different rules, a different person to wait for, a different first sentence. The colleague that is right for one would be fired at the other two in a week.
There is no template for this. That is why blumi does not sell one.
Switch the company. What changes is marked.
Pick one and ask what you would ask a candidate: what it does, what it will not do, how it is onboarded, what happens when it is wrong. It answers for itself.
If it repeats and has an output someone can check, there is probably a colleague in it. If not, you will hear that too. Your message goes to one person and nowhere else.
One person reads this: Sergiu Ardelean, the founder of blumi, who built and runs the seven colleagues inside Artivive. No newsletter, no third party, nothing shared.