From Salary to Hourly Rate: How Freelancers in DACH Calculate Their True 2026 Price
From Salary to Hourly Rate: How Freelancers in DACH Calculate Their True 2026 Price
Most IT professionals make the same mistake when going freelance: they take their gross salary, divide by 1,800 hours, add 20% — and end up underpriced by 30 to 50 percent. The result is a year of hard work, exhausted reserves, and the painful realization that "freelance" did not actually pay more than employment.
This guide walks through the full calculation — including everything employees rarely see on their payslip but freelancers absolutely must price in: social security, sick days, training, downtime, taxes, and a real profit margin.
Why "Salary × 1.2 ÷ 1,800" Is Wrong
The classic shortcut assumes a freelancer works 1,800 billable hours per year and only needs to cover the employer's share of social contributions. In reality, two numbers are off:
- Billable hours are closer to 1,400–1,500 per year, not 1,800. Acquisition, admin, training, vacation and downtime eat the rest.
- The cost gap to your old job is closer to 40–60%, not 20%. You now pay full health insurance, full pension contributions (or private retirement), liability insurance, accounting, software, hardware and office costs yourself.
A senior developer earning €85,000 gross who applies the naive formula lands at around €57/h. The honest number is closer to €95–€110/h — and that is before any profit margin or risk premium.
The Honest Formula
Use this step by step. It works for developers, project managers, SAP consultants, cloud architects and data engineers alike.
Step 1 — Target net income per year Decide what you want to keep after taxes. A reasonable benchmark is your previous net salary plus 20–30% (you carry more risk, so you deserve more reward).
Step 2 — Add taxes In Germany, plan for an effective tax burden of roughly 30–42% depending on income, family status and federal state. Austria and Switzerland differ — but the principle is the same: gross up your net target.
Step 3 — Add social security and insurance
- Statutory or private health insurance: €600–€1,000/month
- Pension or private retirement: at least 15% of gross
- Professional liability insurance: €300–€800/year
- Optional: disability insurance, legal protection
Step 4 — Add business costs Accounting (€80–€250/month), software licences, hardware depreciation, coworking or home office, training, conferences, marketing. Plan with €8,000–€15,000/year minimum.
Step 5 — Divide by realistic billable hours Use 1,400 hours as a conservative baseline (≈ 175 billable days × 8h, after vacation, sickness, acquisition and admin). Aggressive freelancers in long-term projects reach 1,600. Specialists in short engagements often stay below 1,200.
Step 6 — Add a profit margin 10–20% on top. This is what employees never get and what makes freelancing worthwhile in the long run. It also funds the next downturn.
A Worked Example
A backend developer with 8 years of experience, previously employed at €82,000 gross (≈ €4,000 net/month in Germany, tax class 1).
- Target net income: €60,000/year (50% above old net)
- Gross-up for taxes (~35%): €92,000
- Health, pension, insurance: €22,000
- Business costs: €10,000
- Total cost base: €124,000/year
- Billable hours: 1,400
- Cost-covering rate: €89/h
- Add 15% margin: €102/h
Anything below €90/h for this profile is a loss compared to the previous employment — even though it looks higher than the naive €57/h calculation.
Day Rate vs Hourly Rate
In DACH, mid- and large-cap clients usually procure on day rates (8h). Smaller agencies and direct clients prefer hourly billing.
- Day rate ≈ hourly rate × 8, but expect 5–10% discount for full-day commitments.
- Hourly billing protects you on short interventions (architecture review, incident support, code reviews).
- Day rates simplify procurement and are easier to compare in tenders.
A €102/h target translates to roughly €780–€820/day.
Common Pricing Mistakes
- Pricing against the cheapest competitor. There is always someone cheaper. Compete on outcomes, not on rate.
- Forgetting non-billable time. Acquisition, proposals, invoicing and learning are real work.
- No annual review. Inflation, certifications and seniority should push your rate up every 12–18 months.
- Discounting without a quid pro quo. If you discount, get something back: longer contract, faster payment terms, reference rights.
- Not separating travel and on-site days. On-site work justifies a 10–25% premium or full travel reimbursement.
When You Can Charge More
Some signals reliably justify a 15–40% premium:
- Compliance-heavy domains (NIS-2, DORA, KRITIS, GDPR audits)
- Scarce stack combinations (SAP BTP + S/4HANA, Snowflake + dbt, Azure + Databricks)
- Crisis interventions (production incident, audit support, project rescue)
- Documented references with measurable outcomes
- Niche certifications (AWS Specialty, Azure Solutions Architect Expert, CISSP, TOGAF)
How to Communicate Your Rate
Recruiters and procurement teams are used to negotiation. A few principles that work in DACH:
- Quote a range early, not a single number. "€95–€115 depending on scope and on-site share."
- Anchor on your value, not your cost base. Clients do not care about your insurance.
- Be ready to walk away. A no is better than a project that burns 6 months of your year below cost.
- Always have a written contract with clear scope, payment terms (net 14 or net 30), and a rate adjustment clause for extensions.
Bottom Line
A defensible 2026 rate is not "salary × 1.2". It is your target net income, grossed up for taxes, plus full social security, plus business costs, divided by realistic billable hours, plus margin.
Run this calculation once a year. Compare it to current market rates in your specialization (we publish role-specific rate reports for SAP, cloud architecture, project management and development). And never quote a rate you have not actually calculated.