A PoC function with no product team is a prototype graveyard.
Impressive demos. Nothing in production.
Who we are
Who we are
An engineering company in Barcelona, building the software that automates professional-services work — and owning it afterwards.
We automate the administration that professional-services businesses drown in, and then we keep the result alive.
Our first customer runs energy-efficiency work in Spain. Agenhumos, an organisation OS, is ours outright — built, owned and run end to end.
Where we came from
CognitX, our sister company, has built deep expertise in this work. We learn from what they have built, and we build far more AI-native than was possible when they started.
Why Mainloop exists
Most automation programmes fail the same way, and the failure is structural rather than a problem with the people.
A product team with no PoC function builds things nobody asked for.
Real software. For a problem that was never checked.
Almost every company has exactly one of the two, and blames the people rather than the structure. We exist to be both halves, joined.
That join is the name. A main loop is the part of a program that runs continuously — and here what running a product teaches becomes the next thing worth building.
The join
Every project passes through the same hardening step. A prototype goes in; production software comes out.
One organisation, two parts
PoC Services
Business-fluent engineers embed in a business, work out how it actually runs, and prove the value fast with agentic builds. They end by handing over, not by staying.
The Tech Lab
A Product Owner and a developer take the hardened product and own it for its life — gathering needs, continuing to build, running it. This is the half that usually gets skipped.
What is actually being bought
Not any individual project — the method. A repeatable path from idea to running product, applied the same way every time. It is the only reason a small team can carry a portfolio rather than heroically carrying one thing.
What we build →