Giroteam / Lösungen
§ Der Katalog

Sechs Disziplinen.
Eine Arbeitsweise.

Die meisten unserer Arbeiten fallen in eine von sechs Formen. Die Grenzen verschwimmen in der Praxis — ein maßgeschneiderter Aufbau kommt oft mit Integration, Automatisierung und einem Stück Strategie. Wählen Sie die, die Ihrem Problem am nächsten kommt, und wir kalibrieren von dort aus.

§ 01 / Der rote Faden

Sechs Labels.
Ein Betriebsprinzip —
senior Hände
bei der Arbeit.

Whichever discipline you start in, the engagement runs the same way. One senior architect owns the project end-to-end. Specialists from a trusted network join per phase, then step back when their craft isn't needed. No account managers, no junior teams hidden behind a logo, no bench cost passed through.

Always

Senior-led, named

The same person on day one as on day 180.

On demand

Specialists, per phase

Frontend, backend, DevOps, design, data, QA.

Structural

No middle layer

You talk to the builder. Always.

§ 02 / The six

The catalogue —
in detail.

Each card opens onto a longer page with engagement tiers, methods, and worked examples. Hover for the headline take.
§ 01 Build

Custom Software
Development

SaaS platforms, ERPs, CRMs, and bespoke systems — built around your operation, not a vendor's roadmap. The thing your business becomes.

From discovery brief to production hand-off
Two-week build cycles, demoable from week four
Code is yours · no licensing, no lock-in
Ebenen
Sprint · Bauen · Betreiben
Durchlaufzeit
2–24 Wo
§ 02 Automatisieren

Workflow
Automatisierung

Ersetzen Sie manuelle Schritte durch zuverlässige, lautlose Infrastruktur. Die Infrastruktur, die Ihr Team gestern gebraucht hat – robust genug, um sie zu vergessen.

End-to-End-Prozessgestaltung vor jeglichem Code
Ereignisgesteuerte Abläufe, überwacht, wiederholbar
Keine brüchigen No-Code-Spaghetti – produktionsbereit
Ebenen
Audit · Bauen · Betreiben
Durchlaufzeit
2–12 Wo
§ 03 Verbinden

System
Integration

Lassen Sie jedes Tool in Ihrem Stack die gleiche Sprache sprechen. APIs, ETL, Ereignisbussen, Datenverträge – der unsichtbare Kleber, der einen Betrieb zusammenhält.

Eindeutige Quelle der Wahrheit über CRM, ERP, Finanzen
Datenverträge & idempotente Pipelines
Replaces brittle webhooks with durable plumbing
Tiers
Map · Wire · Operate
Lead time
3–10 wk
§ 04 Scale

Cloud &
Infrastructure

Scalable foundations designed for predictable growth — chosen for fit, not fashion. AWS, GCP, Hetzner, Cloudflare — picked for the workload in front of us.

Infrastructure-as-code · Terraform / CDK
Observability, cost shape, recovery rehearsed
No vendor lock-in beyond what's necessary
Tiers
Audit · Migrate · Operate
Lead time
2–16 wk
§ 05 Decide

AI & Intelligent
Automation

Judgement-class automation for the work that actually moves the business — measured on the cost-of-being-wrong, not on demo theatre.

Honest readiness audit before any model spend
Right-sized models · DistilBERT to Claude
Guardrails, monitoring, fallback paths native
Tiers
Audit · Build · Steward
Lead time
3–14 wk
§ 06 Plan

IT Consulting &
Architecture

Strategic design before a single line of code is written. Often the most valuable work we do — and sometimes the only work you'll need.

Written brief · architecture · TCO model
Stress-tested by a second senior architect
~ 1/3 of clients stop here, brief in hand
Tiers
Brief · Architecture · CTO
Lead time
2–8 wk
§ 03 / Picking the right one

Not sure which
discipline fits your
problem?

Most engagements start with the wrong label and end up somewhere more useful. Here's a rough map — match the symptom on the left to the likely shape on the right.
"Our operation runs on Notion, Excel, and tribal knowledge — and it's starting to fail."
"Half my team's day is copy-pasting between systems that should talk."
"We have all the tools — none of them know about each other."
"Our cloud bill keeps growing and we're not sure why — or whether we'd survive an outage."
"I keep hearing 'AI'. What's actually worth building and what's noise?"
"We need to make a build-vs-buy call — and we want a senior view that isn't trying to sell us something."

↪ Still unsure? Send the brief. We'll suggest the shape on the first reply — and won't take an engagement that isn't the right fit.

§ 04 / Method

Whichever discipline,
the same four phases.

We run every engagement through the same arc. Tight at the start, careful in the middle, unhurried at the end.

Phase 01 — 2 weeks

Diagnose

We sit with the team, watch the work, and document what's really happening. Output: a written brief you keep.

Phase 02 — 2–4 weeks

Architect

Systems design, data model, integration map, build sequence. Decisions made on paper before they get expensive in code.

Phase 03 — 2–6 months

Build

Two-week cycles, demoable from week four. Senior hands only — no outsourced delivery.

Phase 04 — ongoing

Operate

We stay on as the system grows: tuning, evolving, transferring knowledge — until you no longer need us.

Currently accepting Q3 engagements

One brief.
We'll point you at
the right shape.

Send a few honest sentences about the work. We'll reply within a working day with the discipline we'd start in — and an honest read on whether we're the right team for it.