Language
Book a discovery call
Methodology · Eat your own dog food

We don't build for otherswhat we don't use ourselves.

Digital Maker runs 54 AI agents in production internally — and the count grows daily. The same systems we build for clients are running in our own acquisition, project work and reporting.

Active agents
54+
↗ growing daily
Running since
v2025.01
14+ months live
Stack ownership
100%
code-first · versioned
Why this matters

We don't know AIfrom whitepapers.

We know it from daily operations — with everything that comes with it: the moments an agent works perfectly, and the moments it almost does. This knowledge flows directly into client projects. We've already made the mistakes ourselves. Not on your dime.

Sovereign AI

AI that belongs to you.Not AI that owns you.

You should use the best models — without chaining yourself to them. 2026 showed how fast that can flip: a top model was offline for 19 days by order, and one AI provider became its own partner's competitor within two months. Whoever hard-wires their business to an ecosystem gives up control. We build differently — so the model stays swappable and the code belongs to you. What that looks like in practice is in our Insights.

01 / Ownership

The code belongs to you

/ code · handover

Every agent, every workflow, every configuration lives in your accounts — documented and handed over. No vendor lock-in, no subscription on hope.

02 / Modelle

Models stay swappable

/ abstraction · swap

The model sits behind an abstraction layer. If a provider gets pricier, fails or becomes a competitor, the switch is a configuration — not a rebuild.

03 / Daten

Sensitive data stays in-house

/ local · open-weight

For privacy-critical workloads we use open models running locally or in EU cloud. What never leaves the building, no one can mine.

04 / Standards

No platform lock-in

/ open · no lock-in

We build business-critical processes on open standards, not on proprietary ecosystems whose rules can change at any time.

Three areas · One coherent stack

No full disclosure.But enough to show: this isn't a concept.

01 / Akquise

Before Gee has the first conversation.

/ inbound · qualification

Incoming requests get contextualized automatically — industry, company size, identifiable need, fit with our core services. No manual CRM entry. No lost information between first contact and first conversation.

Every conversation starts informed.
02 / Projektarbeit

While the work runs.

/ documentation · context

Project documentation emerges in parallel — not after the fact. Meeting transcripts get structured, decisions contextualized, open items land automatically where they belong. No "I'll write that down quickly." It's already written.

No knowledge loss. No double clarifications.
03 / Reporting

What the company knows about itself.

/ analytics · control

No manual collecting of numbers. The stack reports itself — project status, utilization, open items, next steps. Gee steers the company instead of managing it.

Decisions based on data, not memory.
What we've learned

What AI agents can do —and what they (still) can't.

"Our own agents have been running in production for over a year. The most important insight: AI agents are not autonomous employees. They are precise tools for clearly defined tasks — and exceptionally good at exactly those tasks."

Whoever thinks of agents as "digital employees" builds themselves disappointment. Whoever thinks of them as surgical tools builds themselves an advantage.

  • FEHLER 01
    Using agents for tasks that require judgment. AI is not good at recognizing context that wasn't made explicit. It is excellent at executing defined processes precisely.
  • FEHLER 02
    Running agents without sufficient context. An agent without the right data is a dangerous agent. More context = more precise results — usually.
  • FEHLER 03
    No human-in-the-loop for critical decisions. We build agents to pause at defined checkpoints and request confirmation — for money, contracts, client communication.

We've experienced both ourselves. That's why we know how to avoid them.

What we work with

No secret.Whoever hides their stack sells magic.

We exclusively use tools we can explain publicly — and everything we explain, we can also build. No no-code tools, no vendor lock-in. If you want to stop working with us tomorrow, the entire code, infrastructure and knowledge belong to you.

/01 · foundation

The Foundation

What everything runs on. Models, infrastructure, data stores.

Claude API Core model
Ollama Local models
Qdrant Vector store
Google Cloud Infrastructure
Docker Containers · deployment
Python Language · all agents
/02 · mcp servers

Connection to the world

What our agents can read, write and control — via Model Context Protocol.

notion Knowledge base
gmail Inbox · outreach
google-drive Documents · assets
asana Project tracking
fireflies Meeting transcripts
meta-ads Campaigns · analytics
google-ads Search · performance
/03 · clis & agents

In the terminal

Tools for code, deployment and our own agents — Hermes and Paperclip.

claude-code Agentic coding
gh GitHub · repos
gcloud Cloud · deployment
hermes internal Orchestration · routing
paperclip internal Document agent
git Versioning · audit
$ 54 agents orchestrate this stack daily — from lead qualification through code generation to reporting. Growing every day.

What this means for you.Operational experience, not theory.

When we build an AI agent for you, we don't just bring technical know-how. We bring operational experience — from a company that works with it daily. That's the difference between a system that can be demonstrated — and one that runs.

Book a discovery call See case studies