// /protocol
The niogod™ Einsatz-Protokoll is a documented four-phase deployment process anchored by a five-stage Pilot Engineer vetting algorithm. This is not marketing speed — it is operational rigor.
// 01
Each phase is governed by an explicit handover artifact. The clock starts at the signed NDA.
// T+0h · Konsultation & Scoping
A 30-minute structured consultation with the DACH Liaison. Mutual NDA executed via eIDAS QES. The problem statement, target stack, vertical, and team interface are captured in a structured Einsatzbriefing — a single artifact that the Senior Consultant works from.
Owner: DACH Liaison. Mandant input: 30 minutes.
// T+12h · Pod-Konfiguration
The Senior Consultant is matched against the Mandant's stack and Mandantenkontext from the niogod™ bench. The Projektleiter is assigned. The Pilot Engineer is selected from the active Tier-1 pool. Pod composition is delivered to the Mandant for review with role profiles, qualifications, and prior employer archetypes.
Owner: Projektleiter + Senior Consultant. Mandant input: profile review (~30 minutes).
// T+24h · Vertragswerk
The full Vertragswerk — Werkvertrag (BGB §631 ff.), Auftragsverarbeitungsvertrag (Art. 28 DSGVO), mutual NDA, IP-Assignment — is finalized and counter-signed via Qualified Electronic Signature (eIDAS). The Mandant's counsel may participate in a 30-minute counsel-to-counsel call before signature.
Owner: DACH Liaison + Mandant counsel. Mandant input: counsel review.
// T+48h · Onboarding
Repository, ticketing system (GitHub/GitLab/Linear/Jira), and communication channels are provisioned. The pod completes its security review against the Mandant's posture. A Kick-off-Meeting with the Geschäftsführung confirms deliverable scope and Abnahme criteria.
Owner: Projektleiter. Mandant input: provisioning + Kick-off attendance.
// T+72h · Operativer Einsatz
The pod begins delivery. Daily async status from the Projektleiter to the Mandant CTO. Weekly 30-minute steering call. Monthly written Statusbericht with KPIs, Risikoregister, and Aufwandsbericht. Quarterly Senior Consultant architecture review.
Owner: Projektleiter (delivery) + Senior Consultant (architecture).
// 02
Applied to every Pilot Engineer before placement. End-to-end acceptance ratio: <1%.
// Stage 1 · Sourcing pool
Profiles indexed across IIT, BITS, IIIT, NIT, ISI, IISc alumni networks and corporate alumni networks (ex-Bosch India, ex-Siemens India, ex-SAP Labs, ex-Mercedes Benz R&D India).
// Stage 2 · Algorithmic pre-filter
Filters by Mandant-required stack and seniority signals. C1+ written English mandatory. CET overlap window of 3.5–4.5 hours required. Working German (A2+) flagged as a strong plus.
// Stage 3 · Technical assessment
A 90-minute technical assessment with a senior niogod™ engineer: pair-coding on a representative production task, system-design interview against a deep-tech case study from the Mandant's vertical.
// Stage 4 · Senior Consultant review
The vertical-matched Senior Consultant assesses domain fit, prior production exposure, and engineering judgment under ambiguity. This stage is the highest filter rate.
// Stage 5 · Projektleiter culture-fit gate
Final gate: the Projektleiter assesses working style under DACH cadence, written-communication clarity, and escalation behavior. This is the gate that protects the Mandant from communication friction.
// 03
Every cadence is contractually defined in the Werkvertrag. No surprise rituals.
// Daily
From Projektleiter to Mandant CTO. Yesterday, today, blockers, Risikoregister updates.
// Weekly
Projektleiter + Senior Consultant + Mandant CTO. Sprint review, priorities, Eskalationspfade.
// Monthly
KPIs, Risikoregister, Aufwandsbericht, Abnahme of completed Werke.
// Quarterly
Senior Consultant-led architecture review with Mandant CTO. Refresh of vertical Mandantenkontext.
// 04
No proprietary niogod™ tooling required. The pod adopts your stack — not the other way around.
// Source & tickets
GitHub, GitLab, Linear, Jira, Notion. SSO via your IdP. Audit log access for the Mandant.
// Communication
Slack, Microsoft Teams, Mattermost. The Projektleiter is the single human you ping; the Pilot Engineer is reachable via the pod channel.
// Hosting & data
AWS Frankfurt (eu-central-1) by default. Hetzner, OVHcloud, IONOS, or Bring-Your-Own-Cloud. AVV per Art. 28 DSGVO signed before kickoff.
// Secure endpoints
Encrypted workstations with disabled USB write, MDM-managed, biometric access to the Bangalore execution center, enterprise VPN tunnels.
// 05
// Replacement
If the Pilot Engineer does not fit the Mandantenkontext, niogod™ replaces them within 60 days at no additional cost. Misfit at the Projektleiter layer is replaced within 30.
// Exit
30-day notice cancellation. Knowledge transfer included. No exit fees. No German Kündigungsfrist exposure. Werke completed during notice are subject to standard Abnahme.
A 30-minute consultation with the DACH Liaison is the first phase. Werkvertrag and AVV templates can be reviewed in advance.
Book Consultation