// Not a freelancer marketplace
No browsing. No profile-shopping.
The Mandant does not curate individuals. niogod™ delivers a sealed unit configured for the Mandant's stack and Mandantenkontext.
One unit. Three roles.
One Werkvertrag.
The niogod™ pod is not a personnel selection — it is a sealed delivery architecture, governed under BGB §631, anchored in Stuttgart, accountable through a single Projektleiter.
Anatomy of the pod.
// Three roles · one Werkvertragsobjekt · one accountable interface
// Projektleiter — DACH Liaison
The single point of contact.
First and only interface to the Geschäftsführung des Mandanten. C1 German native or near-native. Owns sprint planning, risk reporting, escalation paths, and the legal interface between niogod™ and the Mandanten-Gesellschaft. Absorbs the operational complexity of the offshore layer.
// Qualifications
- C1 German, working English at C1+
- 5+ years in DACH engineering programme management
- Experience with deutsches Werkvertragsrecht and AÜG posture
// Operational mandate
- Sole instructional interface to the offshore layer
- Weekly Statusbericht to the Mandant CTO
- Owns Werkvertrag Abnahme criteria
// Senior Consultant — Architecture layer
10+ years of vertical seniority.
Architecture, technical reviews, and the bridge between the Mandant CTO and the Pilot Engineer. Selected per vertical: Robotics, ML/AI, AUTOSAR, SAP S/4HANA, IEC 62304-grade medtech, dual-use defense stacks.
// Qualifications
- 10+ years in production deep-tech systems within the assigned vertical
- Tier-1 institutional alumnus or equivalent
- Track record of architecture ownership at scale
// Operational mandate
- Architecture and design ownership within the Werk
- Direct technical supervision of the Pilot Engineer
- Quarterly architecture review with the Mandant CTO
// Pilot Engineer — Execution layer
The execution layer.
Highly specialized engineer drawn from India's Tier-1 institutional alumni network — IIT, BITS, IIIT, NIT, ISI, IISc. Pre-filtered through the five-stage niogod™ vetting funnel. Operates exclusively under direction of the Senior Consultant, under Werkvertragsmandate of the Projektleiter.
// Qualifications
- Tier-1 alumnus, 3–15 years production experience
- Written English at C1+; working German at A2+ a strong plus
- Five-stage vetting passed (sub-1% acceptance)
// Operational mandate
- Implementation under Senior Consultant supervision
- Daily async status to the Projektleiter
- No direct task-level Weisungen from the Mandant
Why three, not one.
// The standard objection — addressed
Cognitive load distribution. A single freelance senior engineer absorbs PM responsibilities, architecture decisions, and execution simultaneously. Each of those layers degrades under load. The pod separates them: the Projektleiter owns programme management, the Senior Consultant owns architecture, the Pilot Engineer owns execution. The same fully-loaded budget yields three differentiated outputs rather than one diluted one.
Compliance posture. A Werkvertrag under BGB §631 requires an identifiable, result-owing structure with defined Abnahme criteria and a hierarchical instruction chain that does not reach the Mandant. A single freelancer cannot, by structure, support that posture — the Mandant inevitably issues task-level Weisungen, which is the legal trip-wire for verdeckte Arbeitnehmerüberlassung. The three-role pod institutionalizes the protective hierarchy.
Continuity. A single contractor is a single point of failure. Illness, attrition, or scope drift collapses the engagement. The pod, with overlapping seniority and a documented internal handover protocol, sustains delivery across personal disruptions. The Mandant contracts with the institution, not the individual.
What the pod is not.
// Negative-space definition
// Not an EOR
Not an Employer-of-Record.
EOR is a payroll product. niogod™ is an engineering-delivery product with payroll absorbed inside a Werkvertrag.
// Not a body shop
Outcome owed, not effort.
No hourly billing toggles. No utilization quotas. The pod owes a Werk — defined deliverables under Abnahme.
// Not a captive GCC
No build-operate-transfer.
No €2M+ setup. No 12–24-week stand-up. No fixed headcount. The pod is operational in 72 hours and exitable in 30 days.
// Not a project agency
Not a fixed-bid agency.
Long-cycle deep-tech work, not transactional projects. Quarterly architecture review. Documented monthly Aufwandsbericht.
Engagement models.
// Investment ranges disclosed under NDA
// Pod (Standard)
Single pod · one vertical.
One Projektleiter, one Senior Consultant, two to three Pilot Engineers. Werkvertrag-led. Minimum term: 6 months. Exit clause: 30 days written notice post initial term.
// Monthly under Werkvertrag — discussed in consultation.
// Pod + Architect-on-Demand
Standard pod · second-vertical architecture.
Standard pod plus a second Senior Consultant retained on-call for cross-vertical architecture (e.g., Robotics primary, ML/AI on-demand). Minimum term: 9 months.
// Investment range disclosed under NDA.
// Multi-Pod Programme
Series B+ · programme-level.
Two to four pods under a programme-level Projektleiter, mapped across verticals. Quarterly steering committee with Mandant Geschäftsführung. Minimum term: 12 months.
// Programme economics under separate Werkvertrag.
No public pricing. Investment ranges are disclosed in consultation, indexed to vertical, pod composition, and term length.
Engage the pod.
A 30-minute strategy call with the DACH Liaison. Outcome: a tailored R&D Intelligence Report and a sample Statement of Work within 5 business days.