Your B2B or B2C business, or even harder: SaaS, has been in Germany for months (or you plan to enter the German market). The pipeline is thin, growth is behind plans, and uncomfortable questions arise. Here’s what could went wrong and how to know if it’s fixable.
About the Author
Stefan Golling, Cologne, Germany. Worked since 1998 as a Copywriter and Creative Director in (Network) Agencies and freelances since 2011 as German Freelance Copywriter, Marketing Freelancer, Creative Consultant etc., e.g., in international projects.
Request a meeting
Is this your GTM story?
This is a story that probably plays out dozens of times every year in B2B and B2C companys, especially in, but not limited to, SaaS:
A company decides „Germany is the next growth market“. The logic makes sense: 84 million people, largest economy in Europe, high (IT) budgets, businesses that pay for software, and individuals earning enough money to actually buy things beyond the bare necessities.
In the next step, website / app / product / anything GTM translation gets done (AI, good enough for those villagers, and as no one in your team speaks German, you assume your „German“ is A-W-E-S-O-M-E), a sales rep gets hired, maybe some Google Ads, Meta Ads and/or the Amazon Shop get turned on.
Six to twelve months later, the numbers can be disappointing. Pipeline is a fraction of what was projected. The sales rep can’t close deals and gets ghosted. Marketing spend isn’t converting. And the question that nobody wants to ask out loud starts echoing in leadership meetings: Should we even be in Germany? Are those villagers too stupid for our product?
If this sounds familiar: You’re probably not doing anything fundamentally wrong, but you’re running into structural realities of the German market that some companies discover too late and at great expense. It’s an issue that not only SaaS companies face.
Here’s what’s likely going wrong.
German B2B Buying Is Structurally Different
If your bsiness / SaaS grew through product-led growth, like free trial / credit card, expansion, the first thing to understand: that motion does exist in German B2B, but only limited. It starts with a general lack of company credit cards (freemium, of course, is a good thing). Yes, someone most likely has a access to the (single) company credit card, but that could be the finance pitbull no one dares to ask if you can have access to it.
The reality: German companies procure anything, also software, through processes.
Multiple decision-makers with veto power. A mid-market software purchase in Germany typically involves the Geschäftsführer (managing director), IT-Leiter, Datenschutzbeauftragter (data protection officer), and sometimes the Betriebsrat (works council). In larger companies, procurement (Einkauf) joins the conversation. Each can block the deal, and they often exercise that power. Basically, you will not know who has the final say (the company itself sometimes does not know who has the final final final say). And, as your product screams „change“, middle management and employees might hate it, as there’s change knocking on the door. Germany is a „formal education“ based society, so change in work processes is the horror, the horror, as people have never learned to be open for change.
Decision cycles of 3 to 12 months (or longer). Not because German buyers are slow, but because they are thorough. They check references. They read data processing agreements line by line. They involve legal early (of course not always real „legal“; the poor procurement guy has to read the paperwork). They may ask questions that most SaaS sales teams have never encountered. Still, there’s hope: If you find the right people in the company, and the need is strong, and your product solves a problem, adoption of new technologies can be quite quick.
A strong bias toward established vendors. „Nobody ever got fired for buying SAP“ is not a joke in Germany (the company still might collapse with an ERP project turning wild, but that’s not „getting fired“, the company will just disappear…). It reflects a preference for vendors with a track record, local presence (and local implementation partners), and long-term stability. A SaaS company with no German customers, no German-language case studies, and a .com domain starts at a significant trust deficit. But of course, that can be adressed, and you can always go for the innovators and first-movers.
Relationship-first, not product-first. Despite the formal processes, German B2B is mostly relationship-driven, so that basic sales rule is still valid. The first meeting might be a demo request, but it could es well be a chemistry check. German buyers often want to know who’s behind the product, how long the company has existed, and whether it will still be around in five years, Yet, they may proceed faster when your solution is really excellent and solves real-world problems. Think of ChatGPT: The product is so strong that it does not need sales reps.
Ta-da-da-TAM?
Make sure you know your market size. In case you are trying to win business with a certain industry, try to figure out the total adressable market (TAM). The market size may differ drastically to your home market, due to totally different history of the local industry. It might be larger or smaller than what you expect.
And knowing the TAM (and your potential future growth / market share) will impact your strategy: In case it’s like 100 companies, and with best effort you may win 20 of them, a „paid inbound marketing automation lead generation agentic AI lead generation MQL SQL machine“ will probably not work. It might be more smart to invest in thought leadership and (un-)virtually shaking hands with the interesting people from the small circle of interesting companies; think of congresses, trade shows, you know that.
Of course, that’s actually not really something new, but it’s just a hint that your domestic marketing toolbox will not work out of the box.
The Translation Trap
One pattern in German market entry follows a predictable arc:
Month 1–2: Translate the website. AI and/or a low-cost translator. Cost: € 500–2,000+. It looks German, more or less (it’s OK for launching early, but quality should be improved soon).
Month 3–4: Turn on Google Ads in German. € 2,000 per month. Some clicks, some form fills. Most leads go nowhere. Wrong ICP, wrong intent, or buyers who wanted a free trial and vanished. Or: No leads at all. And: Keywords got brutally expensive, and click rates sank drastically.
Month 5–6: Pipeline isn’t working. The response: „We need someone on the ground.“ A DACH sales rep gets hired from LinkedIn or via headhunter. Cost: € 70,000–100,000+ per year, fully loaded (that’s the money you can earn in Germany working for gov’t, without any sales pressure). Read: Rather more money is need, or you go fot the Junior route.
Month 7–9: The sales rep books (good) meetings / demos. But deals stall. Prospects ask for German-language case studies. There are none. They want to see DSGVO compliance documentation (hey, you always wanted to finish that), but the DPA is still a one-page English template. They need a proper Invoice (Rechnung) with E-Rechnung features, and an Auftragsbestätigung, and a Lieferschein, but you’re still in basic Stripe universe (for instance, HubSpot does it quite good, the send you German invoices in Euro with German VAT to your invoice@ email address, not Stripe invoices in USD to your Google account).
Month 10–12: The pipeline is thin and slow-moving. The few real opportunities have six-month timelines at best. Leadership gets impatient. The sales rep feels isolated and unsupported. Finger-pointing begins.
Month 13–15: The sales rep leaves or gets let go (anyway, that might be a good decision). The German experiment gets quietly wound down. Total investment: €150,000–250,000. Revenue: close to zero.
Pricing and Invoicing: Where Deals Die Quietly
A surprising number of deals in Germany might die not because of how it’s sold and billed. German B2B buyers have expectations that seem minor but are genuine deal-breakers:
Dollar pricing is disqualifying. A pricing page in USD signals that a company hasn’t seriously committed to the European market. You can get away with it when you’re an AI company that drowns in business, but in case you read that: you aren’t. Most companies have fixed that, and if have, you can cross that off the list, which feels good.
A German Rechnung is specific. German invoicing requires: company details with Steuernummer or USt-IdNr (VAT ID), the buyer’s address and VAT ID, a clear Leistungsbeschreibung (service description), net amount, applicable VAT, gross amount, and increasingly, compliance with GoBD standards for digital accounting, which means e invoice (Stripe + Billit work). If your billing system can’t produce this, some German companies cannot (or are too lazy) to process the payment at all. Still, in a first market entry phase, you can find buyers, among SMEs, highly innovative companies, start-ups, etc.
Bank transfer is standard. A significant portion of German Mittelstand companies do not (like to) use corporate credit cards for (software) purchases (still, sometimes they have to). They pay by Überweisung (bank transfer) against an invoice, net 30. Some larger companies pay net 45 or net 90… If Stripe credit card checkout is the only payment path, that portion of the market is inaccessible (I have that on my frontpage, but that’s just for fun).
Compliance Is Real
Most SaaS companies know they need to address GDPR or DSGVO, as it’s called in Germany. Most treat it as a one-time exercise: cookie banner, updated privacy policy, done.
In the German market, compliance expectations are substantially deeper:
Hosting location is scrutinized. German companies, particularly in finance, healthcare, and the public sector, strongly prefer EU-hosted data. Many require it contractually, and German data centers are preferred over other EU locations. „AWS us-east-1“ can be a quiet deal-killer for some companies (others don’t care). The prospect doesn’t argue, they simply move to a vendor who hosts in Frankfurt (that even works with Firebase).
The AVV gets read. The Auftragsverarbeitungsvertrag (data processing agreement under GDPR) most likely gets reviewed by the internal (or external) Datenschutzbeauftragter and often by external legal counsel. It needs to be thorough, specific, and ideally available in German. A generic English-language DPA from a legal page rarely survives this review. But, of course, if your product is ultra-outstanding, no one will care. It looks different, when you have well-established competitors that offer the full set of German data law compliance – then you might be screwed.
The Betriebsrat has co-determination rights. If the software touches employee data, e.g., time tracking, communication monitoring, productivity analytics, even certain HR workflows, or anything an American boss would think is totally normal, the Betriebsrat (works council, many companies have one) has legal rights to approve or block adoption. It’s German labor law (BetrVG § 87). When it comes to employee data / monitoring, you also face issues with data protection laws and EU AI act.
When you’re dealing with public service, it’s called „Personalrat“. Selling to gov’t is brutally hard, by the way.
Regulated industries add layers. Financial services, healthcare, energy, public sector… each has requirements that a general GDPR compliance statement might not address.
The Real Competition: Inertia
Most (SaaS) companies entering Germany research direct competitors: who sells a similar product globally and/or in DACH (only)? Who owns the market? Will we need to create the market, or will we need to make users switch from offer A to us? This matters, but it misses the most powerful opponent in the German market.
The primary competitor for any (SaaS) product in Germany is the way things are currently done.
Entrenched German ecosystems. Yes, there are German IT and software companies. Yes, they have loyal customers. Yes, the workflows are embedded in the companies. And yes, the employees know how to work with them (they hate change). Operational transformation can be accepted, if your product really offers a real advantage.
„Good enough“ manual processes. Many German companies manage with Excel, Word templates, shared drives, and established routines what a SaaS product could automate. The barrier is that changing requires approval from multiple stakeholders, training, risk of disruption, and the implicit message that the old way was wrong. Microsoft 365 is an easy sell, because otherwise you would take ppt and Excel away from the employees. And: As most companies are client of a „Systemhaus“ which sold them MS 365, upsell for them is a bit easier.
Switching cost is cultural. A Mittelstand company using the same process for 15 years won’t switch because a tool offers 30% more efficiency, if this can be measured. The real switching cost is the organizational disruption, the change management, the accountability if something goes wrong, and the cultural weight of „Das haben wir schon immer so gemacht“ (We’ve always done it this way).
Four Possible Diagnoses
When a German market entry isn’t working, the situation might fall into one of four categories:
Diagnosis A: The go-to-market was wrong, but the market fit exists. The product solves a real problem for German companies, but the channels, messaging, pricing, or compliance thingies are misaligned. This is fixable. A (pivotal) course correction can turn things around. Of course you will not know beforehand what was wrong and what will work.
Diagnosis B: The market fit isn’t there. The execution may have been reasonable, but German companies don’t need the product enough, or not at this price, not against this competition, not with this regulatory backdrop. This isn’t fixable with better marketing. The honest answer is to stop investing in DACH and redeploy the budget to a market with better odds. Or you improve your product.
Diagnosis C: The timing or readiness is wrong. The product could work in Germany, but the company expanded too early: insufficient resources, no local expertise, premature international push driven by investor expectations rather than market signals. The answer is not „never,“ but „not yet.“
Diagnosis D: Obsolete product. You product gained traction in your home market, some years ago. You have loyal customers. But: You can’t create growth at home, so you try your luck elsewhere. Probably today your APIs-glued-together product is not good enough for either your home market not for any new market, as either AI already does the job better, or new competitors have a better product. Probably it might be a good idea to sell your company (or pivot).
An honest assessment of which diagnosis applies to your specific situation is the most valuable (and most rare) thing you can get.
How to Figure Out Where You Stand
Whether you’re six months from a German market entry or into it eighteen months, the first step is the same: a look at what’s happening (and why).
A few questions worth answering honestly:
- Is there evidence that German companies spend money on the problem you solve, or is the assumed demand based on your experience in other markets?
- Do you have any organic signals from DACH, e.g., inbound website traffic, leads, sign-ups, inquiries, or is all interest generated through outbound?
- Can you handle German invoicing, data hosting, and compliance requirements today, or are these still on the to-do list?
- Does your team include anyone with firsthand experience in German B2B sales, or are you operating from assumptions about how it works?
- Are your leadership and board prepared for a 12–18 months timelines, or is the expectation „show ROI this quarter“?
If more than two of these answers make you uncomfortable, the discomfort is information. A clear-eyed diagnosis before you spend more money might help.
When to Get an Independent Diagnosis
A self-assessment gives you a directional signal. But if real money is at stake – a sales rep on payroll, a marketing budget running, a GmbH with fixed costs – the question of „is this fixable or should we stop?“ deserves a proper answer.
An independent DACH market diagnosis covers:
- Product-market fit analysis. Is there genuine demand from German companies for what you sell, or is this an assumed need from a different market?
- Competitive reality. Who are you actually competing against, including entrenched local tools and the powerful force of „how things are done here“?
- Pricing and packaging. Does your current model work for German procurement, or is it structurally misaligned?
- Compliance gaps. Where does your DSGVO, hosting, invoicing, and regulatory posture actually stand, and how much would it cost to fix?
- Go-to-market evaluation. What’s working, what isn’t, and what would need to change?
- Honest verdict. Is this Diagnosis A (fixable), B (stop), or C (not yet), or D (pivot)? No spin.