Offshore engineering quotes arrive in incompatible formats. One vendor quotes an hourly rate in USD, another a monthly rate per engineer in EUR, a third a fixed monthly fee for a team. Procurement then compares the headline numbers and selects the lowest. The result is frequently the most expensive option once delivery starts. The fix is a normalisation step: convert every quote into the total cost to your company per productive engineering day, including the effort your own team spends making the engagement work. This guide gives you the worksheet.

The market behind the quotes

The number of quotes a DACH buyer can collect keeps growing. NASSCOM estimates that India's technology industry reached revenue of USD 315 billion in fiscal year 2026, up 6.1 percent, with a workforce of about 5.95 million after 135,000 net additions. A NASSCOM and Zinnov study from 2024 counted more than 1,700 Global Capability Centres in India employing about 1.9 million people. The supply side is broad, and that breadth is exactly why offers differ so much in what they actually include.

On the buyer side, the reference point is moving. Destatis reported that nominal wages in Germany rose 4.2 percent in 2025, while consumer prices rose 2.2 percent. In Bitkom's 2025 survey, 63 percent of companies said applicants' salary expectations did not match their qualifications. When internal cost rises and hiring stays slow, a cheap headline rate becomes tempting, which makes a disciplined comparison more important, not less.

Why headline rates mislead

A rate describes what the vendor invoices for a unit of time. It does not describe what you receive. Five gaps explain most of the difference:

  • Scope of the rate. Does it cover only the developer, or also project management, QA, architecture review and DevOps?
  • Billing basis. Hours logged, days present, or a fixed monthly amount regardless of holidays and leave?
  • Seniority definitions. A senior engineer at one vendor may have four years of experience, at another ten.
  • Client-side effort. How much of your senior engineers' and product owners' time does the model consume?
  • Commercial terms. Currency, escalation clauses, minimum terms, notice periods and payment terms all change the effective price.

The normalisation worksheet

For each quote, fill in the same fields over a twelve-month horizon:

FieldWhat to capture
A. Vendor invoice totalAll fees for 12 months, including roles billed separately, travel, tooling and onboarding fees
B. Currency adjustmentIf not in EUR, apply your treasury's planning rate and a risk buffer for FX movement
C. Client-side management costHours per week of your staff spent on direction, review and coordination, multiplied by internal cost
D. Transition costKnowledge transfer in and out, access setup, security review
E. Contracted capacityNumber of engineers multiplied by working days per year in the vendor's location
F. Effectiveness factorShare of contracted time that produces accepted output, after ramp-up, rework and replacement gaps
Result(A + B + C + D) divided by (E multiplied by F)

Field F is the hardest and the most important. Do not let vendors fill it in. Set one conservative assumption for all bidders and adjust only where a vendor contractually commits to something better, for example a replacement guarantee within a defined number of days.

Illustrative calculation

The following example is an illustrative calculation with invented quotes for a team of three engineers over one month, using 21 billable days and an internal cost of EUR 518 per day for the client's senior staff (the steady-state figure from our separate analysis of a German senior hire).

ItemQuote AQuote B
OfferEUR 25 per hour per engineer, PM and QA billed at 15% surchargeEUR 4,800 per engineer per month, delivery lead and QA included
Vendor invoice14,49014,400
Client management time2 days per week: 4,5070.5 days per week: 1,140
Total monthly cost18,99715,540
Productive days (3 x 21 x 0.85)53.5553.55
Cost per productive dayEUR 355EUR 290

Quote A looks cheaper per hour and is nearly identical on invoice, yet it is about 22 percent more expensive per productive day because the client has to supply the coordination. The effect grows when the client's senior engineers are the bottleneck for the internal roadmap, since their time has an opportunity cost well above their salary.

Questions to send every bidder

  1. Which roles are included in the price, and what share of their time is allocated to us?
  2. How are public holidays, leave and sickness in the delivery location handled in billing?
  3. What are the minimum years of experience for each seniority level quoted?
  4. Who on your side is accountable for delivery results, and in which language do they communicate with us?
  5. What happens if an engineer leaves: notice to us, replacement time, and who pays for the overlap?
  6. In which currency is the contract, and under what conditions can the price change?
  7. What is the minimum term and notice period, and what exit support is included?
  8. Is the contract structured as Werkvertrag, Dienstvertrag or staff provision, and how is the instruction right handled?
  9. Are all prices net of foreign taxes, and is German VAT handled through the reverse charge mechanism of §13b UStG?

Set up the request properly

Comparability is created at the request stage, not at evaluation. Send every bidder the same short work package with acceptance criteria, require the quote in your format with separate lines for roles, expenses and transition, and ask how they would approach the package in the first two sprints. That answer reveals more about real working practice than any presentation. A bidder who replies only with developer CVs is usually selling capacity, not outcomes.

Contract model matters as much as price

Question 8 is not a formality. A low hourly rate in a staff augmentation arrangement where your managers direct the engineers daily carries a different legal profile from a fixed fee under a Werkvertrag (BGB §631) with Abnahme under BGB §640. If engineers are integrated into your organisation and subject to your instructions, the arrangement may fall under the Arbeitnehmerüberlassungsgesetz (§1 Abs. 1 Satz 2 AÜG). Without the required permission, §§9 and 10 AÜG can render the contract void and create a deemed employment relationship with the client. That risk should be priced into any comparison, even if only as a qualitative flag.

How to use the result

The worksheet does not replace judgement. A vendor with a higher cost per productive day may still win if it reduces risk you cannot otherwise mitigate, such as German-speaking delivery management or experience in a regulated domain. What the worksheet does is make that trade-off explicit, so the decision is about value rather than about the most visible number.

This article is general information, not legal or tax advice.

The worksheet works best when a quote already maps onto its fields. niogod™ prices a three-person pod (Projektleiter, Senior Consultant, Pilot Engineer) as one fixed monthly fee with delivery management included, so the coordination line in your comparison stays visible rather than hidden. If you are collecting offers for next year, it is worth including one structured this way.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights