K · Technical layer · Simplicity

Very powerful AI.
And very simple to use.

All the complexity, hidden. You speak to it like on WhatsApp —with voice if you want— and the companion does the work. You don't have to learn any new program.

K.0101 · How you use it

The simple part

You speak to it, and that's it. In your language, the way you'd write to a coworker. With voice if your hands are busy. And if you want to change something, you tell it and it does —no forms or mandatory fields to get stuck on.

CONVERSATION · ILLUSTRATIVE
SCALE 1:50
N ↑
YOU
Build me the estimate for this BC3 with my line items.
COMPANION
Done. I've flagged 3 items that need your judgement.
YOU
Change the margin to 12% and prepare the folder for the Lleida council.
COMPANION
Updated and assembled with the templates Lleida asks for.
K.0202 · Where the rigour comes from

Why Claude Code, and not a chat

Rigour doesn't come from having 'the smartest AI' —that changes every month— but from the instrument we build it with. And that difference you already know from your trade:

There's the tool everyone uses —quick and flexible, but manual, isolated and one that doesn't know you— and there's the professional instrument —configured to your domain, with your rules and connected to your data. ChatGPT is the first; the companion we prepare for you, built on Claude Code, is the second.

Architecture

ChatGPT lets you ask the way AutoCAD lets you draw; the companion understands the whole project and keeps it coordinated, like Revit.

Engineering

ChatGPT is like that spreadsheet that's been through many hands: it works, but you don't know if someone touched the formula that matters to you. The companion is a validated, traceable procedure, the same every time.

Construction

ChatGPT is a loose Excel; the companion is the system that knows your business and applies your rules, like moving from Excel to SAGE.

K.0303 · Human comparison

And if you think in people?

Imagine you can bring in an assistant. They offer you the first one: a top graduate, super sharp. But each day he's at a different firm. He doesn't know your house or your quirks. For a one-off idea, great. For the work that matters… are you sure he's the right one?

And the second one: he gets trained with your systems, he stays, he learns your procedures. You give him the tools and the permissions, he does the work and leaves it ready for you to review and sign. Each day he learns from your feedback.

ChatGPT is the first. The companion we prepare is the second.

For brainstorming, pick the first; for work with consequences, we pick the second. And the most important: not even the best graduate replaces the senior. Your years of judgement are worth a hundred times more. That's why the companion leaves the work ready and it's YOU who always reviews and signs.

K.0404 · Myths

4 myths vs 4 realities

MYTH 01

"«I need an IT person or an IT department»"

REALITY

Only the files you already have (BC3, PDFs, Excel). We set it up.

MYTH 02

"«I have to migrate to BIM or change my tools»"

REALITY

No. The companion connects to what you already use.

MYTH 03

"«My data isn't tidy enough»"

REALITY

The knowledge feeds itself on the fly, not before starting.

MYTH 04

"«AI makes things up, I don't trust it»"

REALITY

That's why: programmed rigour, verified sources and your judgement always validating.

K.0505 · DFY vs DIY

If I can install Claude Code myself, what do you add?

Fair question. Honestly: you can install Claude Code yourself. And if you have time and inclination, it's worth trying — it's an extraordinary tool and you learn a lot doing it. The difference is not the tool; it's everything we build on top so it does your work without starting from scratch.

What we save you on day one

K.05/01

Custom MCPs for your tools

Connectors built: BC3, official records (cadastre, geological data), little-known APIs that extract data for lead qualification. Built over time and tested on real work. Not off-the-shelf.

K.05/02

Validated pipelines for your profession

Sequences already tuned for concrete problems: Terzaghi and Schmertmann for geotechnical calculation, code-compliance classification, lead qualification in construction. Each pipeline is weeks of trials to reach a reliable output.

K.05/03

Invisible professional techniques

Guardrails against unauthorised uses, PII handling, traceability of each step. The part nobody sees — but that decides whether the companion can be used with peace of mind in work with consequences.

K.05/04

Claude Code configuration itself

CLAUDE.md with your domain, agents for specialised tasks, tuned prompts, memory and session management, skills you can reuse. That layer is necessary anyway — and it's the first week of work before any value comes out.

K.05/05

Which LLM for which task

At each step of the pipeline, the model that delivers best quality/cost. A technical decision that takes weeks of trials —and isn't always done well. Years of work with different models, already consolidated.

K.05/06

Years of work with the profession

Knowing what's relevant in the technical code for each case, what each council asks for and in what format, how to validate a geotechnical borehole… domain knowledge no LLM provides on its own.

Honesty

DO IT YOURSELF IF…
  • · You're passionate about learning the tool in depth.
  • · You have 4-6 months to dedicate without urgency on results.
  • · You want to understand deeply what's underneath.
  • · The result doesn't have to be immediately professional-grade.

Go for it. We won't sell you something you can do yourself if you can do it yourself.

LEAVE IT TO US IF…
  • · Your clients already expect results now.
  • · Your time is worth more than the indirect saving of learning the tool.
  • · Rigour is a promise to your client (not an experiment).
  • · You want to focus on what you do know.

We leave it done for you, we teach you to use it, and we're here to help it grow.

If you want to know how the two formats relate (One-Shot vs AI Department), see the collaboration formats →

CTA

Want to see it with a job of yours?