← Back to Packages

Cooperation Models & Pricing

Below you will find typical cooperation models as they are practical in the technical SME sector (engineering/development/plant environment). The daily rates shown are starting prices ("from") net plus VAT and will be specified in the offer based on the specific project context.

1

Model 1 — Initial Development Phase: Full-time On-Site (Ramp-up)

Purpose: Maximum progress in short time (kick-off, system access, fast iterations, on-site tests/integration).
Use: PoC → Pilot, commissioning/troubleshooting phases, critical milestones.
Mode: Full-time, 5 days/week on-site.
Price: from €990/day
2

Model 2 — Hybrid Full-time: Mostly Remote + Scheduled On-Site Weeks

Purpose: High velocity with reduced on-site share; regular, predictable presence for reviews, tests, and acceptance.
Mode: ~80% remote, 1 week on-site every 5 weeks (full-time on-site).
Price: from €790/day
3

Model 3 — Long-term Part-time Support: Topic Ownership & Continuous Improvement

Purpose: Sustainable ownership without full-time headcount; stabilization, continuous improvement, knowledge transfer.
Mode: 20 hrs/week, ~80% remote, 1 full-time week on-site every 10 weeks (e.g., for reviews, tests, integration).
Contract: Open-ended B2B support contract with 3-month notice period.
Price: from €490/day

Agile Working Methods & Delivery Cycles (Standard)

Regardless of the billing model, development is agile:

  • 2-week cycle with result delivery (demo/review + next priorities)
  • Transparent progress (backlog, sprint goals, KPI tracking as needed)
  • Early feedback for risk reduction (technology, integration, acceptance)

Additional Models (optional, depending on scope)

Fixed Price / Milestone-based Payment (Work Contract Logic)

Suitable for: Clearly defined deliverables with defined acceptance (e.g., analysis package, model audit, MPC concept, prototype, optimization module).
Billing: Fixed price per milestone/package; acceptance based on clear criteria.
Advantage: Budget clarity and procurement-friendly structure.
Note: For unclear scope, a paid scoping sprint is recommended as a preliminary step.

Retainer / Service Contingent (optionally with response times)

Suitable for: Plannable capacity, regular reviews, quick support ("keep-the-lights-on" + minor enhancements).
Billing: Monthly contingent (e.g., X days/month), optionally with defined response times.

Scoping Sprint (Workshop → Reliable Offer)

Purpose: Quickly clarify scope, make risks/dependencies visible.
Result: KPI target picture, system boundaries, data/interface list, integration plan, effort estimate, and offer model (T&M or milestones).

Build–Operate–Transfer (Setup → Operation → Handover)

Purpose: Quick external start, then internal anchoring.
Service: Setup, stabilization, knowledge transfer, optionally recruiting support (role profile, interview support) and structured onboarding of internal owner.

A Quick Cost Comparison (Internal FTE vs. External)

An internal FTE with a €100,000 gross salary costs the company (roughly calculated) about ~€720 per productive day.

Internal FTE calculation example:

  • Employer costs (simplified): ~€120,000/year (salary + employer contributions)
  • + conservative overhead (IT/workplace/management/HR, tools, etc.): +20% ⇒ ~€144,000/year
  • Productive days (e.g.): ~200 days/year (working days minus vacation/sick leave/training/other absences)

→ Internal full cost per productive day: 144,000 / 200 = ~€720/day

Price Factors (why "from" pricing makes sense)

The specific conditions typically depend on:

  • Geography & travel: Travel, accommodation, expenses
  • Urgency / availability: Express start, downtime situations, weekend windows
  • Predictability & duration: Contingents/long-term enable better conditions
  • On-site share & rhythm: Predictable vs. ad-hoc
  • Complexity & criticality: Production risk, safety/quality constraints, commissioning
  • Scope clarity: Clearly defined deliverables vs. open R&D questions
  • Tooling & compliance: Access, data situation, IT/OT requirements, documentation scope
  • Response times / SLA: Agreed response times
  • IP/rights arrangements: License, source code, exclusivity

Contract & Compliance Components (typical)

  • NDA (confidentiality) as needed
  • DPA (Art. 28 GDPR), if personal data is processed
  • Clear arrangements for acceptance, change requests, payment terms, travel costs, liability framework (project-specific)

IP, Licensing & Exclusivity Options (on request)

Depending on the project, cooperation can also be structured as Solution-on-Demand:

  • Delivery of a ready-to-use solution (e.g., software module/algorithm component/toolchain).
  • Typical distinction between customer-specific results (for the customer) and reusable generic IP (methodology, libraries, building blocks).
  • Optional: License/usage rights model (e.g., per site/plant/module or enterprise license) incl. maintenance/updates via retainer.
Optional customer protection (competitor restriction):

It can be agreed that we will not sell or license the developed solution to direct competitors of the customer (e.g., as industry/competitor exclusivity for a defined period and/or market), with scope and limits to be precisely defined contractually.

Conclusion

The models above are proven standards — individual structures are also possible. Whether daily rate, milestones, retainer, license model, or exclusivity: We design the cooperation to fit scope, risk, budget, and your procurement/compliance process.

The cooperation possibilities are practically unlimited – we will find a clean, fair way.

Note: This page is for general information and does not constitute legal advice. The specific terms are bindingly regulated in the respective offer and contract.

Interested?

Tell us about your target system, timeline, and data/interface situation – we'll recommend the right model.

Get in touch