People and AI in one agency: why we're starting the blog over
We took down six posts an AI wrote for us. Nothing they described had actually happened here. The new blog covers what people and Jarvis really built.
Until recently this blog held six posts from 8 April 2026, three in Czech and three in English. They covered LLMs as the new operating systems, the death of the centred hero section, and, twice and almost word for word, AI agents in software development. An AI wrote them for C-level readers, and they didn't contain a single project, a single number or anyone who stood behind the words. We took them down.
There's some irony in that. We're an agency where AI does a large part of the work, and we pulled posts an AI wrote. The author wasn't what bothered us. Those posts could have run on any company's site in the world and nobody would have noticed the difference. This blog will only cover things that actually happened here.
In short: EndorphinIT is an agency where people do part of the work and Jarvis, our AI, does the rest. Jarvis may read, research and prepare on its own. A person approves anything that goes out.
What "people and AI" means here
People do part of the work and Jarvis, our AI, does part of it. Jarvis isn't a chatbot on a website. It has its own email address, writes code, deploys websites and keeps track of deadlines. It runs on its own server and has access only to what its work requires.
It works by three rules:
- It can read, research and prepare material on its own.
- Anything that goes out is approved by a person.
- It never deletes data and never pretends to be a person.
The second rule matters most to us. Jarvis drafts the email, the offer, the website or the code fix. It can send, publish or deploy only after someone from the team has checked and approved it. Pavel gets a short brief from Jarvis twice a day and answers each item with one line: yes, no, or do it differently.
What does that look like in practice? Website deploys that used to take about 3 minutes suddenly took 15 to 27. Jarvis tracked down why: a CPU limit had been left on after a server snapshot. After a restart, a build that had taken 32 minutes dropped to 4.6. Jarvis finds problems like that, explains them and proposes the fix. A person decides.
AQUNAMA: the human part
Some projects shouldn't be handed to an AI. Larger systems, automation and tailor-made projects go to our AQUNAMA team. Matej starts with a call to find out what's hurting and what should work differently. Pavel and František then design and build. Jarvis helps with research, writes tests and documentation, and watches the deadlines. People make the decisions and answer for the result.
Every project follows the same steps: an intro call, a review of your processes and data, a proposal with scope, deadline and a fixed price, development, handover with training, and then operation, where we monitor, fix and extend what we built.
The AI part: services Jarvis runs
The other half of the agency is services where Jarvis does most of the work and a person signs it off. The first one is "Website by Jarvis". You send us your website's address, Jarvis reviews it, builds a new version and sends you a preview. The preview is free. If you like it, you pay CZK 1,490 excl. VAT a month for the website, hosting and maintenance, with no setup fee. The next post walks through the whole process on a demo café.
What we'll write about
The rule for every post: only what actually happened, including what didn't work, with the numbers we measured.
Coming up:
- Jarvis rebuilt the café's website. The Website by Jarvis service step by step, shown on a café we made up.
- Jarvis at work. What Jarvis does in an ordinary week, where it got things wrong and where a person stopped it. Some of this is already on jarvisrunsit.com.
- Apps for agents. We build software whose user is an AI agent rather than a person. Each app started as something our own Jarvis needed. We use it ourselves first and only then offer it to others.
- postcache: Instagram, Threads and Facebook Pages accept photos and videos only by public URL, so an agent that publishes posts needs somewhere to put the file. postcache gives it a link that expires after a while.
- Grovehive: shared memory for AI agents, including agents with different owners. Every write is saved as a version with the agent as its author, and the service refuses any write that contains a secret key or password.
An AI on our team drafted this post too. A person read and approved it before it went up. That will be true of every post here.
Want to see what Jarvis would do with your website? Request a free preview. Have a bigger project? Book a call with Matej.