Skip to content
FORKOFF
GTM · Berlin · ETH + EU · By application

Germany AI, SaaS and Web3 entry thatwins ETH Berlin.

FORKOFF runs the 90-day Berlin playbook for tech, SaaS, deep tech and Web3/AI founders. BaFin sandbox, MiCA compliance, and eWpG routing locked in week one. A 19-operator Berlin and DACH roster pre-warmed before any drop sequence. ETH Berlin, Berlin Blockchain Week, and European Blockchain Convention anchored as the launch calendar. ETH dev hiring path through the TU Berlin and Humboldt alumni networks is one warm intro away when ICP fits.

engagement-fit by application · by applicationCapped at 4 Berlin engagements per quarterSelective on ICP · Web3 plus AI lane
3 / yrTier-1 launch windows on the Berlin calendar
19Berlin and DACH operators in active FORKOFF roster
90 daysMedian playbook commit to launch-day live
by applicationEngagement-fit band by ICP and stage
The short answer

What does a Berlin go-to-market launch take?

A Berlin go-to-market launch runs through the German and EU corridor across the BaFin regulatory surface and the ETH Berlin and Berlin Blockchain Week calendar. FORKOFF runs a 90-day phased sequence for tech, SaaS, deep tech and Web3/AI founders, locking narrative, KOL warm-up, event activation, compliance routing where it applies, and answer-engine visibility into one operating brief sized by application.

By the numbers

The Germany and Berlin opportunity, in numbers.

Every figure below is a published benchmark with a named source and a checkable link, the sourced picture behind the Berlin entry playbook on this page.

  • German startups raised about 7 billion euros in venture capital in 2024, up 17% year on year. (EY via GTAI, 2024)

  • The country added 2,766 new startups in 2024, up 11%, with software and AI the largest segment. (GTAI, 2024)

  • Germany's digital-asset penetration reached 35% in 2024, above the EU average of 32% and the global 12%. (GTAI, 2024)

  • Gartner projected that traditional search volume will fall 25% by 2026 as buyers move to AI chatbots and answer engines, reshaping how a launch gets discovered. (Gartner, 2024)

  • FORKOFF has processed more than 5 billion qualified views across its clipping network, the proof base behind the qualified-view reporting on this engagement. (FORKOFF, 2026)

Berlin and DACH surfaces and EU partners the playbook ships across
ETH BerlinBerlin Blockchain WeekBaFinBundesbankTU BerlinHumboldt UniversityHasso Plattner InstituteBitkomWeb3 BerlinPolkadot BerlinGnosisCentrifuge1inch BerlinSolaris BankDLT FinanceEuropean Blockchain ConventionETH BerlinBerlin Blockchain WeekBaFinBundesbankTU BerlinHumboldt UniversityHasso Plattner InstituteBitkomWeb3 BerlinPolkadot BerlinGnosisCentrifuge1inch BerlinSolaris BankDLT FinanceEuropean Blockchain Convention
BaFin sandbox + MiCA + eWpG fluentETH Berlin + Berlin Blockchain Week calendar19 Berlin + DACH operators · ETH dev hiring pathBy application
Pre-engagement diagnostic

Why most Berlin launches
stall before D-30.

Five patterns we see when a global brand tries to land in Berlin and the playbook stalls inside the first sixty days. Each row is the FORKOFF fix. Read it before you book the diagnostic call.

fk_audit · gtm_berlin_reject_log.csv
  • Row 01
    Reject reasonBaFin-blind tokenization launch
    Audit detail

    Token launch ships without BaFin sandbox routing or MiCA compliance mapping. Solaris Bank or DLT Finance custody is missing. The German press flags the gap inside seventy-two hours and the launch loses local institutional cover.

    FORKOFF fix

    BaFin tokenization sandbox routing memo locked in week one of D-90. MiCA compliance mapping for the actual product. Solaris Bank or DLT Finance custody routing introductions on fit. eWpG (German Electronic Securities Act) classification flagged where applicable.

  • Row 02
    Reject reasonNo ETH Berlin pre-broker
    Audit detail

    Founder buys an ETH Berlin or Berlin Blockchain Week ticket and walks the venue hoping to network. Hackathon partner slots are gone twelve weeks earlier. The DACH Web3 cluster ignores cold DMs because the founder has zero pre-warm signal in the local ecosystem.

    FORKOFF fix

    ETH Berlin or Berlin Blockchain Week side-event slot brokering queued by D-60 with three to five confirmed speaker or hackathon partner slots. Coordinated drop sequence across the 19-operator Berlin and DACH roster locked for the fourteen-day pre-event window. Gnosis, Polkadot Berlin, and Centrifuge ecosystem cross-promo plan published.

  • Row 03
    Reject reasonNo ETH dev hiring path
    Audit detail

    Brand lands in Berlin claiming to hire ETH developers and runs a generic LinkedIn job ad. The TU Berlin and Humboldt CS clusters never see the role. Senior protocol engineers with five-year track records ignore the listing because there is no signal it was tuned for them.

    FORKOFF fix

    ETH dev hiring path queued by D-60 with TU Berlin and Humboldt alumni network introductions. Three to five senior protocol-engineer warm intros routed per quarter on fit. Hackathon-sponsored bounty pathway flagged at ETH Berlin. Founder-to-engineer founder podcast guesting placements lined up.

  • Row 04
    Reject reasonEnglish-only launch in a German press market
    Audit detail

    Brand ships the same global launch tweet during Berlin Blockchain Week that ran for ETHDenver. Handelsblatt, FAZ, and the German tech press cluster ignore it. Half the local capital pool and the German-language KOL surface never see the launch.

    FORKOFF fix

    Bilingual canonical content (English plus German) on the top fifteen commercial pages by D-30. German alternate language tags shipped in schema. Press packet routed through Handelsblatt, FAZ, and t3n. Coordinated KOL drop sequence runs in both languages over the fourteen-day window.

  • Row 05
    Reject reasonNo EU regulatory bridge
    Audit detail

    Brand pitches Berlin as an EU launch market without MiCA mapping, no relationship with the German Bundesbank wholesale CBDC desk, and no understanding of the BaFin sandbox track. The pitch reads as wishful thinking to anyone reading from the EU regulatory community.

    FORKOFF fix

    MiCA mapping and BaFin sandbox routing locked in week one. Bundesbank wholesale CBDC sandbox path flagged where applicable. EU operator surface routed through twelve of the 19 active accounts on the FORKOFF roster. European Blockchain Convention positioning queued for the next-cycle event window.

5 / 5 patterns auditedSource: FORKOFF Berlin + DACH operator deskPre-application diagnostic
The wedge

Global agencies treat Berlin as an ETH Denver echo.
FORKOFF runs the 90-day BaFin-fluent playbook.

Most global agencies treat Berlin as a satellite stop and ship the same launch tweet they ran for ETHDenver. The German press cluster ignores it and the DACH KOL surface never lights up. FORKOFF runs the playbook from D-90 with the BaFin sandbox memo, MiCA compliance map, and side-event slots already booked. Sister page /gtm/dubai covers the home-market sister anchor; /gtm/london covers the EU-adjacent sister anchor.

90Day phased playbook from D-90 to D+90
3 / yrTier-1 launch windows on the Berlin calendar
19Berlin + DACH operators in active relationship management
Read the Dubai sister playbook
LIVEAudit ledger · Berlin bench

Three numbers that decideif Berlin is your launch market.

0 days
Median time-to-live
BaFin routing memo, MiCA mapping, bilingual corpus, and event activation in one operating system.
ETH Berlin (late summer), Berlin Blockchain Week (autumn), European Blockchain Convention.
Tier-1 launch windows
0 / yr
Plus the EU Web3 cluster of 12 inside the 19. Warm relationship management, not cold DMs.
Operators in active roster
0 DACH
Application-only · selective on ICPWeb3 plus AI lane · Seed to Series BQualified-view proof, audited every TuesdayCapped at 4 Berlin engagements per quarter
What the Berlin playbook ships

Spine, roster, side-event,
and ETH dev hiring path.

PHASE 01[WEEK ONE OF D-90]
01
Narrative spine

Locked story the operator desk and the Berlin and DACH roster can pre-clear.

Deliverables (5)

  • Narrative pillar lock + three launch tweets drafted
  • Founder bio rewritten for Berlin + DACH buyer language
  • Top fifteen commercial pages queued for bilingual rewrite
  • Pre-launch press packet for Handelsblatt + FAZ + t3n
  • Hero tier Berlin + DACH founder testimony slot pre-booked
PHASE 02[19-OPERATOR BERLIN + DACH ROSTER]
02
Operator coordinated drop

Seven to twelve accounts dropping over a fourteen-day window.

Deliverables (5)

  • 19 Berlin + DACH operators in active relationship management
  • 12 operators inside the EU Web3 cluster from the 19
  • Coordinated drop sequence (7-12 accounts × 14 days)
  • Three founder podcast guesting placements per quarter
  • X + LinkedIn + Farcaster cross-posting plan
PHASE 03[ETH BERLIN + BERLIN BLOCKCHAIN WEEK]
03
Side-event activation

Speaker slots, hackathon partners, and live clipping shipping.

Deliverables (5)

  • Side-event speaker slot booking (3-5 confirmed)
  • Hackathon partner brokering at ETH Berlin on fit
  • Live event clipping at 6-10 clips/day from on-stage moments
  • Five Gnosis + Polkadot Berlin + Centrifuge ecosystem cross-promos
  • Recap thread + post-event narrative lock by D+7
PHASE 04[D+30 TO D+90]
04
Post-event compounding

Sustained narrative + ETH dev hiring path queued.

Deliverables (5)

  • Weekly narrative beat sustained for 60 days post-event
  • Operator relationship deepening with 3 calls/quarter
  • ETH dev hiring intros via TU Berlin + Humboldt alumni networks
  • Solaris Bank or DLT Finance custody intros on fit
  • Quarterly qualified-view proof signed by operator
What counts on the Berlin playbook ledger

What countsas a Berlin-fit launch.

A Berlin launch is on track only when four signals hold every week. BaFin sandbox routing locked, ETH Berlin or Blockchain Week side-event slot booked, ETH dev hiring path queued, and German voice live on the hero tier. An English-only launch tweet during Berlin Blockchain Week never lands in the weekly report.

Active check · BAFIN
1 / 4Signals the Berlin verified proof checks every Monday. BaFin, ETH Berlin, ETH dev hire, German buyer.

01 BAFIN

BaFin sandbox + MiCA tokenization routing locked.

01

BAFIN

BaFin tokenization sandbox routing memo locked in week one of D-90. MiCA compliance mapping for the actual product. eWpG classification flagged where applicable. The framework is in writing before any launch tweet ships.

fk_audit · qv_check_01

rule · BaFin sandbox + MiCA tokenization routing locked.

02

ETH BERLIN

ETH Berlin or Berlin Blockchain Week anchored as the launch window. Three to five side-event speaker or hackathon partner slots booked by D-60. Coordinated drop sequence across seven to twelve Berlin and DACH accounts over the fourteen-day window.

fk_audit · qv_check_02

rule · ETH Berlin + Berlin Blockchain Week side-event slot booked.

03

ETH DEV HIRE

TU Berlin and Humboldt alumni network introductions queued by D-60. Three to five senior protocol-engineer warm intros routed per quarter on fit. Hackathon-sponsored bounty pathway flagged at ETH Berlin. Founder-to-engineer podcast guesting placements lined up.

fk_audit · qv_check_03

rule · ETH dev hiring path queued via TU Berlin and Humboldt.

04

GERMAN BUYER

Berlin and DACH founder testimony placed on the hero tier. Operator roster of 19 active accounts warmed across X, LinkedIn, and the German press surface. Bilingual canonical content live on the top fifteen commercial pages. Handelsblatt and FAZ press packet shipped.

fk_audit · qv_check_04

rule · German voice and DACH operator signal on the hero tier.

Counts as verified
  • BaFin sandbox + MiCA routing locked in week one
  • eWpG classification flagged where applicable
  • ETH Berlin or Berlin Blockchain Week side-event slot booked
  • Berlin + DACH operator drop sequence coordinated across the 14-day window
  • TU Berlin + Humboldt alumni hiring path queued
Does not count
  • ·Founder reads MiCA summaries on the flight to BER
  • ·Cold DM blast to DACH crypto Twitter the week before ETH Berlin
  • ·ETH Berlin attendance with no side-event slot or operator drops
  • ·English-only launch tweet during Berlin Blockchain Week
  • ·Generic LinkedIn job ad with no protocol-engineer signal tuning
Outcomes the Berlin playbook unlocks

DACH reach, BaFin-fluent routing,
and an ETH dev hiring path.

Three engagements across a Web3 protocol, a DePIN brand, and an AI infra hybrid. Berlin launches that locked the BaFin sandbox routing memo, activated ETH Berlin and Berlin Blockchain Week, and queued senior ETH developer warm intros via TU Berlin and Humboldt alumni networks. Pair the playbook with /events/devcon-2026 for the Devcon anchor or /events/ethcc-2026 for the European event circuit.

8-12

Cross-platform clips per ETH Berlin or Berlin Blockchain Week day from on-stage and side-event moments. Audit-ledger tracked.

2-4

Senior protocol-engineer warm intros per quarter routed via TU Berlin and Humboldt alumni networks on fit.

19

Berlin and DACH operators in active relationship management. 12 of them are inside the EU Web3 cluster.

OWNED

You keep the playbook, the BaFin routing memo, the bilingual corpus, the operator relationships, and the weekly report.

Comparison

FORKOFF Berlin 90-day playbook vs DIY launch vs generic global agency.

Three routes into the Berlin and DACH market. Match the playbook cadence to the BaFin and MiCA routing you actually need, the operator roster you can sustain, and the qualified-view proof you want shipped weekly.

← scroll horizontally to see more →

FeatureFORKOFF Berlin 90-day playbookOperator-led · BaFin + MiCA-fluent · weekly audit ledgerDIY Berlin launchFounder-led · no roster · ad-hoc ETH Berlin attendanceGeneric global agencyRetainer · English-only · ETH Berlin as a side note
Phase structure90-day phased playbook with named deliverables per phaseFounder writes a Notion doc the week before ETH BerlinGeneric three-phase deck reused from a 2024 SaaS engagement
Regulatory routingBaFin sandbox + MiCA + eWpG routing memo in week one of D-90Founder reads framework summaries late on Saturday. Often picks the wrong sandbox trackBoilerplate Web3 disclaimer copied from the Singapore engagement
Berlin + DACH operator roster19 Berlin and DACH operators in active relationship management plus EU cluster of 12Twitter DMs cold sent the week before ETH BerlinThree London or NYC operators reused for every market
Side-event activation3-5 speaker slots booked. Hackathon partner brokering. Live clipping at 6-10 per dayFounder buys a ticket and walks the venue. No slot. No clippingOne generic recap thread on day three of the event
ETH dev hiringTU Berlin + Humboldt alumni intros + 3-5 senior protocol-engineer warm intros per quarterGeneric LinkedIn job ad with no signal it was tuned for protocol engineersHiring is not a deliverable in the engagement scope
Qualified-view proofWeekly Monday scan plus citation count, drop reach, side-event RSVPs, signed proofAnecdotal screenshots when something happensQuarterly board deck with vanity reach numbers
Pricing modelengagement-fit by application by ICP and stage. Outcome-priced milestonesFounder time + opportunity cost. No ceiling on the burnHourly retainer regardless of result
Berlin fit diagnostic

Strong fit when 4+ are true.
Skip when any disqualifier fires.

Who you are
  • tech, SaaS, deep tech and Web3/AI founders launching into Germany and the EU inside Q1 to Q3 2026 with ETH Berlin or Berlin Blockchain Week timing
  • Pre-token, post-token, pre-ARR, or post-ARR teams pursuing BaFin sandbox, MiCA compliance, or eWpG security-token routing
  • Teams hiring senior protocol engineers from the TU Berlin and Humboldt alumni networks
  • Founders who can commit to a 90-day phased cadence with weekly proof
  • Brands building a real Berlin and DACH operator surface, not a one-week event activation
What FORKOFF delivers
  • 90-day phased playbook with named deliverables per phase (Pre-launch, Launch, Scale, Sustain)
  • BaFin sandbox + MiCA + eWpG routing memo in week one with ICP and stage mapping
  • Coordinated KOL drop sequence across the 19-operator Berlin and DACH roster (7 to 12 accounts × 14-day window)
  • ETH Berlin or Berlin Blockchain Week side-event slot booking with 3 to 5 confirmed speaker or hackathon partner slots
  • ETH dev hiring path with TU Berlin and Humboldt alumni intros and 3 to 5 senior protocol-engineer warm intros per quarter on fit
  • Weekly qualified-view proof with citation count, operator reach, side-event RSVPs, and clip cadence
Not the right fit
  • ×Pre-product brands shopping for a Berlin narrative with no real category to anchor on
  • ×US-only audiences with no EU exposure thesis (consider /gtm/new-york)
  • ×Founders who want hands-off execution; this is operator-led, not done-for-you
  • ×Token launches that conflict with MiCA classification or fail BaFin sandbox gating (we flag these)
  • ×Anyone expecting a viral hit in 30 days with no event-window anchoring
Apply for the Berlin sprint

entry diagnostic · engagement-fit by application

The entry diagnostic covers the BaFin sandbox routing memo and the MiCA compliance brief plus a 14-day positioning audit. Full engagement is by application by ICP and stage. ETH Berlin or Berlin Blockchain Week sponsor activation with side-event production lands at the upper end. KOL fees, sponsorship fees, and travel quoted separately. Capped at 4 Berlin engagements per quarter.

  1. 01Sandbox
  2. 02Engagement
  3. 03Compound
By application
Apply for the Berlin sprint
Inside the Berlin GTM market

BaFin sandbox routing, MiCA compliance posture, builder-skeptic founder cohort.

Berlin GTM engagements operate against the BaFin sandbox routing framework, the broader EU MiCA regulation alignment, and the Berlin builder-skeptic founder cohort communication norms. The Phase 1 GTM-playbook locks against BaFin sandbox availability for any fintech-adjacent brand, the broader EU MiCA token-classification language standards, the Bundestag policy proximity for crypto brand-communication norms, and the broader Berlin founder cohort's preference for technical-depth-first messaging. Brand positioning that fails the Berlin builder-skeptic filter reads as imported US growth-hack content.

The Berlin GTM guest pool runs through Factory Berlin, The Drivery, Silicon Allee community, the Berlin Web3 Founders network, BlueYard Capital community, Earlybird Venture Capital, Project A Ventures, Cherry Ventures Berlin office, Atlantic Labs, Speedinvest Berlin, Rocket Internet alumni network, and the broader Mitte plus Kreuzberg plus Prenzlauer Berg founder gathering circuit. Founder dinners at Cookies Cream, Pauly Saal, Crackers, and the Soho House Berlin private events route brand visibility against partner-dev attendance.

The 90-day phased Berlin GTM launch sequence runs against ETH Berlin (the Ethereum Foundation hackathon, summer), Berlin Blockchain Week (Sept-Oct), the broader Tech Open Air (TOA Berlin), and Bits and Pretzels Munich crossover from Berlin base. BaFin sandbox routing applies during the pre-launch D-90 to D-30 window where any token-listing or financial-services language gets pre-cleared. MiCA compliance mapping locks token-classification language per vehicle category. Solaris Bank custody routing applies on fit. Press wraparound runs through Handelsblatt Tech, WirtschaftsWoche Tech, Sifted Germany, Trending Topics, t3n.

Frequently asked questions

What is actually in the Berlin GTM playbook?

A 90-day phased launch sequence. Pre-launch (D-90 to D-30) locks the BaFin sandbox routing memo and the MiCA compliance mapping, queues the 19-operator Berlin and DACH roster, and books ETH Berlin or Berlin Blockchain Week side-event slots. Launch (D-30 to D plus 0) runs the coordinated KOL drop. Scale (D plus 0 to D plus 30) executes the event window with live clipping and DACH ecosystem cross-promo. Sustain (D plus 30 to D plus 90) compounds the narrative with ETH dev hiring intros and Solaris Bank custody routing on fit.

How is Berlin different from Zug for a Web3 launch?

Berlin runs on BaFin sandbox plus MiCA harmonization, has the largest ETH developer density in Europe, and anchors the launch window on ETH Berlin and Berlin Blockchain Week. Zug runs on the Swiss DLT Act and FINMA, sits next to the Ethereum Foundation, and anchors on CV Conf and Devcon. Pick Berlin first if EU passporting and senior ETH dev hiring matter; pick Zug first if Swiss tax-cert and FINMA letter routing matter. See /gtm/zug for the Crypto Valley sister page.

Do I need a German entity from day one?

Not for Phase 1. The pre-launch sprint can run while the German entity is being formed. Phases 2 and 3 expect either a UG, GmbH, or AG with a registered Berlin address, or a documented timeline to one. We work with two German counsel desks for the entity formation and the BaFin sandbox routing memo.

What is the entry diagnostic?

A 14-day positioning audit plus the BaFin sandbox routing memo and the MiCA compliance brief. Output covers token classification, eWpG flag where applicable, three operator partner introduction targets, and a flagged list of ETH dev hiring opportunities through the TU Berlin and Humboldt networks. The diagnostic doubles as the Phase 1 kickoff if the engagement converts.

How does FORKOFF charge for the Berlin playbook?

Engagement-fit by ICP and stage in the band by application. Lean entry covers the BaFin routing memo plus a Phase 1 prelaunch sprint. Full ETH Berlin or Berlin Blockchain Week sponsor activation with side-event production lands at the upper end. Outcome-priced milestones, not retainer hours. KOL fees, sponsorship fees, and travel are quoted separately.

Does the playbook help with hiring senior ETH developers?

Yes. The Sustain phase queues TU Berlin and Humboldt alumni network introductions plus three to five senior protocol-engineer warm intros per quarter on fit. Hackathon-sponsored bounty pathway is flagged at ETH Berlin. The hiring path is a deliverable, not a side promise. We do not run agency recruiting; we route relationship signal so your in-house lead recruiter can close.

What stage of company is this built for?

Post-product, pre-token or recent-token. You need a working product to anchor the narrative on. Pre-MVP narrative shopping does not survive the playbook's specificity gates. Mature post-token projects above $50M FDV get a custom variant.

How quickly can the playbook start once we engage?

Typically 7 to 14 days from contract to Phase 1 kickoff. We need to align on stage, ICP, launch window, and run the BaFin and MiCA routing pass with German counsel. For ETH Berlin timing, lock by Q1 for the late-summer window; for Berlin Blockchain Week, lock by Q2 for the autumn window.

Which BaFin route should my project take?

Three routes. Crypto-custody license under KWG section 1 if the project is operating custody as a regulated service. eWpG electronic-securities route if the project is tokenizing securities under German law. MiCA-passporting if the project is an authorized issuer or CASP in another EU member state passporting into Germany. The week-one routing memo names the right route for your design.

The brand line

Berlin is not improvised.
It is the 90-day playbook.

BaFin sandbox, MiCA, and eWpG fluency locked in week one. A 19-operator Berlin and DACH roster pre-warmed before any drop sequence. ETH Berlin, Berlin Blockchain Week, and European Blockchain Convention anchored as the launch calendar. ETH dev hiring path through TU Berlin and Humboldt alumni networks. Pair the playbook with /events/devcon-2026 for the Devcon anchor, /events/ethcc-2026 for the European event circuit, /gtm/london for the EU-adjacent sister anchor, /services/events for side-event production, /for/web3-protocols for the protocol-ICP wedge, or /gtm/dubai for the parallel-built sister GTM playbook.