DACH market-entry GTM stack guide

Germany: UWG section 7 requires prior express consent for electronic post, including B2B advertising, and for automatic calling machines. The email customer exception requires all four conditions: address collected in a sale, the sender's own similar products or services, no objection, and a clear low-cost opt-out at collection and every use. A prospect database, generic business mailbox or relevant job title is not this exception.[1]

Germany: live advertising calls to consumers need prior express consent; calls to other market participants need at least presumed consent. The distinction concerns the recipient's capacity, not just company size. Our assessment is to document a specific reason counsel accepts for each business call, rather than infer permission from a published number. Do not extend the live-call standard to SMS or automated calls.[1]

Austria: the TKG 2021 section 174 channel regime is not Germany's presumed-consent business-calling model. RTR says advertising calls need prior consent and advertising electronic post, including SMS, needs prior consent. Its guidance describes an existing-customer exception for contact details obtained with a contract, similar products or services, and an opt-out in advance and with every message. Our assessment is to gate both corporate and sole-trader prospects on evidenced consent, and check the ECG list before relying on a customer exception. Direct retrieval of the consolidated section 174 text was blocked; the complete statutory exception needs counsel confirmation before activation.[2][3]

Switzerland: the UWG rule addressed by the commissioner concerns mass advertising sent by telecommunications. Its email guidance requires informed, voluntary prior opt-in. The customer exception needs an actual sale or use of a service, similar offerings from the same company, sender identification and a simple free opt-out. Creating an account is insufficient. Do not convert the mass-advertising scope into a claimed one-to-one cold-email exemption.[4]

Switzerland: UWG article 3(1)(u) prohibits advertising calls to starred directory numbers and numbers absent from the telephone directory, except in a business relationship. A vendor-supplied mobile is not evidence of an unstarred directory listing. Our assessment is to record the listing check or approved exception before manual dialing and keep automated calling and SMS outside this manual-call policy.[4]

LinkedIn in Germany, Austria and Switzerland: the checked channel sources do not establish a blanket permission for promotional DMs or InMail. Our assessment is to review those messages under each destination's electronic-marketing rules and not treat a connection acceptance as advertising consent. LinkedIn separately prohibits unauthorized bots that send messages and tools that scrape profiles. Start with manual research, public content and requested conversations, not a scraped-DM sequence.[1][2][4][5]

Germany and Austria: employee contact records are personal data even where the buyer is a corporation. GDPR Article 6 requires a processing basis; legitimate interests need a necessity and balancing assessment and are not UWG or TKG marketing consent. Article 14 generally requires source and processing information for indirectly collected data, normally within one month, earlier at first communication or disclosure, unless a specified exception applies. Article 21 requires direct-marketing processing to stop after objection. Our assessment is to sync suppression before any re-enrichment.[6][1][2]

For EU-origin CRM data, verify each vendor's role. GDPR Article 28 requires a contract for processing on your behalf and controls over subprocessors; a database seller is not automatically your processor. Switzerland is on the Commission's adequacy list, but Article 44 still covers onward transfers. Without applicable adequacy, use an Article 46 safeguard such as standard clauses unless a specific Article 49 derogation applies. Our assessment is not to use a derogation as the default for a recurring CRM or enrichment workflow. Choosing an EU hosting region does not replace a review of support access and enrichment destinations.[6][7]

Switzerland: FADP Articles 6, 19, 30 and 31 require lawful, proportionate, purpose-compatible processing, information for indirect collection, and attention to express objections and personality rights. This is not simply GDPR's Article 6 basis menu. Swiss transfers use adequate destinations or permitted guarantees and exceptions. The commissioner requires assessment of whether contractual protections work under recipient-country law, with technical measures when needed, and disclosure of the foreign destination and relevant guarantee. Our assessment is to maintain separate EU-export and Swiss-export entries for the same CRM vendor.[8][9]

Clay documents country, region and city filters, language filters and job-title modes that can include translated titles. Those are search controls, not German, Austrian or Swiss contact recall or email fill-rate guarantees. Cognism documents verification and do-not-call screening processes, but the checked data page does not establish independently audited country-specific recall for your DACH ICP. Do-not-call screening also does not supply Austria's affirmative calling consent.[10][11][2]

Our assessment is to compare providers against the same approved sample of German, Austrian and Swiss accounts. Separate company headquarters from contact location; test Geschäftsführer, Geschäftsführerin, Vertriebsleitung and English equivalents against the actual buying role. Record correct legal entity, current employer, valid work email, usable phone and lawful activation as different outcomes. Report misses by country and segment rather than use a global database size as the buying criterion.[10]

Our assessment is to launch German-language discovery, proposals and security answers with a named German-speaking seller and implementation owner. Use reviewed German consent and opt-out copy, a controlled title dictionary and customer-facing dates without ambiguous month/day formatting. Review Austrian wording separately and use Swiss standard German conventions for German-language Swiss assets instead of blindly copying a German landing page.

Switzerland has German, French, Italian and Romansh language communities; the FDFA distinguishes spoken Swiss German dialects from written standard German. Our assessment is to route by the account's chosen language, not its CH country code. For Romandie or Ticino accounts, qualify the language of the buying committee before offering a German-only demo. Hand off the buyer's language, approved contact channel, implementation constraints and invoice recipient with the opportunity. Require the AE to obtain CS acceptance of the support language, staffed hours and onboarding milestones before signature.[12]

Germany: the structured e-invoice rule concerns in-scope supplies between domestically established businesses, including a participating domestic fixed establishment, not every foreign SaaS sale to Germany. A PDF alone is not the structured format in UStG section 14. The general issuance transition ends 31 December 2026; issuers with prior-year turnover no more than EUR 800,000 may use the extended transition through 31 December 2027, and a separate qualifying EDI transition also runs through that date. These transitions also depend on when the underlying supply takes place; non-structured electronic invoices still need recipient agreement. Full in-scope issuance applies from 2028 after these transitions, subject to applicable exemptions. There is no matching blanket delay of recipient capability.[13][14]

Austria: USP allows ordinary electronic invoices, including PDFs, with recipient agreement and authenticity, integrity and readability controls. Federal government suppliers have needed structured invoices since 1 January 2014; foreign suppliers are obliged only to the extent technically possible, while a supplier established in Austria falls within the obligation. Do not apply the federal rule to every private buyer. Where Austrian reverse charge applies to a qualifying foreign service, USP requires a net invoice, the parties' UID numbers and a reverse-charge notice, issued by the 15th of the following month. Classify the supply and establishment before choosing the tax treatment.[15][16][17]

Switzerland: the CHF 100,000 worldwide turnover threshold is not an automatic VAT registration verdict for a foreign SaaS exporter. MWSTG Article 10 exempts certain foreign suppliers making only recipient-location services, but carves out telecommunications or electronic services to non-taxable recipients. Confirm buyer tax status and the service classification. Article 26 requires an invoice on request with identities, service period, scope, amount and applicable tax details; Article 27 forbids a non-registered person from showing Swiss VAT. German issuance deadlines do not govern this invoice.[18]

Our assessment is to offer EUR bank-payment and card workflows for German and Austrian customers, plus an agreed CHF invoice/payment route for Swiss buyers. Stripe documents SEPA Direct Debit Core, not the B2B scheme, mandates and delayed settlement; Core covers business as well as personal accounts. Buyers can dispute an authorized debit without question for eight weeks. Keep mandate, invoice delivery and payment success as separate states, and do not mark an initiated debit as settled revenue. Confirm merchant-country eligibility and currency support before promising a Swiss collection rail.[19]