Building the company of the future

We build products at a speed that was previously impossible.Then we teach others how.

This is what a company looks like when the delivery work runs on agents. Two founders. Four products shipped and running. An internal agentic platform of orchestrators, subagents, skills and hooks, with a human gate on everything that matters.

2 months

from idea to production, on Treneris

Find the gapDemo, not MVPPrice it firstBuild with agentsFirst customers
1 / 5Find the gapA real problem someone already pays to work around, not an interesting idea.The one stage AI does not compress.

What we build

Four products, all of them in use.

See all the work
Treneris

SaaS · Coaching operations

Treneris

A single system a personal trainer runs a whole practice from, instead of a spreadsheet, a chat thread and a payment app.

InCreatorz

SaaS · Creator tooling

InCreatorz

Everything a LinkedIn creator does in a week, moved out of a dozen browser tabs into one workspace with its own browser extension.

Augmented.club

Platform · Learning delivery

Augmented.club

The platform our own programs run on, built because no off-the-shelf tool could keep a room of engineers in sync with what was on screen.

Avenola

SaaS · Food production ERP

Avenola

Production planning for bakeries running more than one site, where a missed batch and a failed compliance record cost the same money.

How we build

The obvious question about this speed, answered.

  1. 1An internal agentic platform of orchestrators, subagents, skills and hooks does the repetitive part of delivery.
  2. 2Finding the code, writing it, type-checking, building, testing and auditing all run unattended, sandboxed and in parallel.
  3. 3Merges, schema changes, anything touching production and every judgement call stop and wait for a person.
  4. 4No change is reported as done without the checks for the surfaces it touched, and every review finding has to survive an agent whose only job is to refute it.
  5. 5The standards did not move. What moved is the cost of meeting them, which is why more verification runs now, not less.
Read how it works

The method we publish

Augmenting one team moves the bottleneck. Augmenting every role compounds.

This is the part that is genuinely ours: not a tool, but the operating model around it. We publish it in full, and it is what augmented.club teaches.

Every role

not only engineering, which is why it compounds

BuildShareGovernMeasureReinvest
1 / 5Everyone builds their ownOrchestrators and micro-tools, made by the person who does the work, on their own real work.Bottom-up, because automation has to encapsulate the know-how of whoever does the job.

Who builds it

Two people, and the platform they built to work with.

The engineers who designed the agentic platform are the ones who ship on it, on every product listed above.

Adam Bilišič

Adam Bilišič

Founder

Architecture and agent design

Twelve years in professional software, eight of them leading engineering teams for enterprise clients, most recently as CTO of a Swiss company. Owns system architecture across the four products and the agentic layer above it: retrieval systems, agent design, and the orchestrators that carry a change from a written intent to a reviewed pull request.

Jerguš Frajt

Jerguš Frajt

Founder

Delivery and platform engineering

Ten years as a full-stack engineer delivering complex systems for Swiss enterprise clients. Owns delivery across the stack and the parts of the platform that decide what runs unattended: the subagents, the verifiers that every change has to pass, and the hooks that stop work before it can reach production unchecked.

The surest way we find a problem worth building for is a domain partner who lives inside it, which is why some of our products are built with one.

How that works