The verdict in three sentences
GDPR compliance for a business application usually costs 10 to 20% of the development budget, and two to three times more if it is bolted on after go-live. For a Berlin SME processing customer and employee data, the sensible baseline combines EU or German hosting, encryption at rest, a documented DPIA (Datenschutz-Folgenabschätzung) and configurable retention periods inside the software. A data protection officer who writes these four items into the specification removes most of the regulatory risk, where fines can reach 4% of worldwide annual turnover.
What the DPO must demand before signing
An application that handles customer records, contracts and employee data (absences, contact details, sometimes bank details) falls under the GDPR, which Germans know as the DSGVO, from the first line of code. Under the BDSG, Section 26 adds specific rules for employee data, and German works councils (Betriebsrat) often have a say when software can monitor staff behaviour. The DPO does not choose the framework, but needs written commitments on six points: legal basis for each processing activity, data minimisation, data location, technical security, data subject rights and automatic deletion.
The classic trap: a vendor delivers a working app with no access log, no per-person data export and backups kept forever with a US provider. Fixing those three gaps later typically costs 15 to 25 extra development days.
| Compliance item | 2026 ballpark (EUR, excl. VAT) | Best moment |
|---|---|---|
| Processing register and data mapping | 800 to 1,500 | Before the specification |
| DPIA (impact assessment) | 1,500 to 4,000 incl. register | During design |
| Encryption at rest and in transit | 2 to 5 development days | In the technical foundation |
| Access logging (timestamped audit trail) | 3 to 6 development days | In the technical foundation |
| Data subject rights module (access, export, erasure) | 4 to 8 development days | Before acceptance testing |
| Automatic deletion per retention period | 2 to 4 development days | Before acceptance testing |
| Security audit or penetration test | 3,000 to 8,000 | Before go-live |
These are 2026 ballpark figures for the German SME market. A DPIA is mandatory only for high-risk processing (health data, employee monitoring, profiling, data matching), but a careful DPO runs one whenever a system covers both customers and staff. In Berlin, the supervisory authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit.
EU hosting: options and budget
The GDPR does not require hosting in Germany, but it strictly regulates transfers outside the EU. Hosting with a German or European provider removes the transfer question and simplifies the DPIA. For an SME business app, three tiers stand out.
| Hosting option | Monthly cost 2026 (EUR, excl. VAT) | Strengths | Limits |
|---|---|---|---|
| VPS with a German provider | 80 to 150 | Simple, data in Germany | Monitoring is on you |
| Managed EU cloud (managed database, backups) | 150 to 300 | Backups and high availability | More technical setup |
| C5-attested or sovereign cloud | 250 to 400 and up | Reassures enterprise clients and public sector | Cost and onboarding time |
| US cloud, EU region | 100 to 300 | Rich ecosystem | Transfer assessment and clauses to document |
| On-premise server | 50 to 120 excl. hardware | Full control | Off-site backup and physical security to manage |
For a Berlin SME without health data, a managed EU cloud at 150 to 300 EUR per month covers most needs, encrypted backups included. Public-sector or healthcare clients will often ask for a BSI C5 attestation.
Compliance features built into the software
Compliance is not just a document; it must be visible inside the application. A well-built system offers an admin screen where the DPO sets retention per category: for example 3 years after last contact for a prospect, the end of the relationship plus the statutory period for a customer, and the legal retention period for payroll data, which in Germany often runs 6 to 10 years under the HGB and AO. A nightly job anonymises or deletes expired records and logs the action.
Other expected building blocks: role-based access (sales staff cannot see employee absences), strong authentication for admins, readable data export for access requests, and an internal incident alert so you can meet the 72-hour notification deadline.
At Kolonell, these blocks are part of the foundation of our custom applications, and compliance is scoped in the quote according to the processing involved.
Mini case study
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Sarah, DPO of a 90-person engineering SME in Berlin, must approve a project management application that centralises 4,000 customer contacts and team schedules. The development budget is 60,000 EUR.
Her calculation: compliance built in from the design stage at 15%, or 9,000 EUR, of which 3,000 EUR covers the register and DPIA and 6,000 EUR the development work (encryption, logging, deletion, data subject rights). Managed EU cloud hosting at 220 EUR per month, or 2,640 EUR per year.
The reverse scenario: compliance added after go-live, estimated at 2.5 times the initial cost of the technical features, or 15,000 EUR, plus an urgent audit at 5,000 EUR. That is 20,000 EUR versus 9,000 EUR, so 11,000 EUR saved by planning ahead. For a company turning over 12 million EUR, the theoretical ceiling of a 4% fine is 480,000 EUR.
FAQ
Is a DPIA mandatory for every business application?
No, only for high-risk processing such as employee monitoring or health data. It costs 1,500 to 4,000 EUR including the register, which is modest compared with the risk. German supervisory authorities publish a list of processing types that require one.
Must the data be hosted in Germany?
No, the EU is enough under the GDPR. Hosting in Germany or the EU for 80 to 400 EUR per month still avoids a transfer impact assessment and reassures enterprise clients.
How much time does compliance add to the project?
About 2 to 4 extra weeks on a 4-month project if planned from the start. Added afterwards, it can tie up the team for 6 to 8 weeks.
Do we need the works council's approval?
If the software can monitor employee performance or behaviour, the Betriebsrat has co-determination rights under Section 87 of the Works Constitution Act. Involving it early avoids 1 to 3 months of delay at rollout.
How should retention periods be configured?
Ideally through an admin screen per data category, for example 3 years for an inactive prospect. A daily automatic deletion job costs 2 to 4 development days and removes the risk of excessive retention.
Let's scope your project. Tell us which data you process and your hosting constraints, and we will define the scope, built-in compliance and delivery schedule. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.