At a mid-volume operating shape (data-volume tier 2, processing complexity 1.5, $120/hour), the FTC vs NLT Regulatory Cost tool returns a US-FTC all-in annual cost of $42,360 against an EU (MiCA + DORA) cost of $179,600, a 4.2× gap dominated by the EU's heavier setup (200 vs 40 hours) and ongoing compliance (30 vs 8 monthly hours). The UK-FCA option sits between at $67,740. On top of the engine's data-regulatory model, an EU finance publisher targeting German-language readers also carries BaFin supervisory exposure, MAR investment-recommendation rules, and EU AI Act deployer obligations: regulatory layers the engine does not price but that a German-targeted operation must budget for separately.

TL;DR

  • US-FTC cost (tier 2, complexity 1.5, $120/hr): $42,360/year all-in (setup $7,200, monthly $3,530).
  • EU MiCA + DORA equivalent (same inputs): $179,600/year, a 4.2× gap driven by setup and ongoing hours.
  • UK-FCA sits between at $67,740/year.
  • The engine prices the data-regulatory burden; it does NOT price BaFin/MAR/AI-Act publishing layers. Those are additional EU obligations covered below.
  • For a publisher targeting EU (and especially German-language) readers, the binding cost is the EU one.

The three jurisdictions the engine prices

The FTC vs NLT Regulatory Cost tool models three jurisdictions on a data-volume × processing-complexity × hourly-rate cost formula. At tier 2, complexity 1.5, $120/hour:

Jurisdiction Setup hours Monthly hours Annual fees Setup cost Annual all-in
US — FTC 40 8 $0 $7,200 $42,360
UK — FCA 60 12 $1,200 $10,800 $67,740
EU — MiCA + DORA 200 30 $8,500 $36,000 $179,600

The FTC framework is enforcement-by-litigation: no registration, no ongoing supervisory engagement, but the substantiation and disclosure rules bind every published claim1. The EU MiCA + DORA framework is registration-heavy: CASP licensing, an ICT third-party register, threat-led penetration testing, and 24-hour incident reporting all load the setup and monthly-hours columns. That structural difference, not a publishing-specific surcharge, is what produces the 4.2× gap in the engine.

The BaFin / MAR / AI Act layers the engine does not price

The engine's EU jurisdiction is MiCA + DORA, which captures the data and ICT-resilience burden. A German-targeted finance publisher faces three additional obligations on top of that, which the engine does not quantify but which push a German-targeted EU operation further above the US line:

1. Active supervision

The FTC is reactive: enforcement happens after a complaint or audit. BaFin maintains the Verbraucherschutzforum and the Fachartikel publication track, both of which monitor finfluencer and finance content actively. The 2026 finfluencer factsheet2 documents the heightened scrutiny on social-media finance content. A German-targeted publisher has to budget for the realistic probability of a BaFin inquiry: not catastrophic, but recurring documentation work.

2. MAR investment-recommendation regime

Market Abuse Regulation Article 20 requires that any publication that "explicitly or implicitly recommends or suggests an investment strategy concerning one or several financial instruments" carry disclosed methodology, identified persons responsible, and a clear separation between fact and opinion3. The substantive bar is not different from FTC substantiation, but the procedural overhead (documented methodology files, disclosed conflicts, pre-publication review timeline) is heavier.

3. EU AI Act deployer obligations

The AI Act applies to publishers using LLMs to generate finance content. The deployer obligations under Article 50 include transparency disclosures, human-oversight documentation, and an AI-risk assessment that must be updated annually4. The cost is modest (€500-2,000/year) but is additive on top of the BaFin / MAR baseline.

The shared baseline

Several costs are common to both jurisdictions:

  • Errors-and-omissions insurance. Typical €1,500-3,000/year for retail finance content.
  • Substantiation documentation. Every performance claim, every backtest, every recommendation needs a documented evidence trail. The work is the same; only the audit-frequency expectation differs.
  • Conflict-of-interest disclosure. Both regimes require disclosure of paid endorsements, holdings in covered securities, and affiliate compensation.
  • Record retention. US substantiation typically requires 3-5 years; EU under MAR / WpHG typically 5-7 years.

When to operate under each regime

The choice is partly geographic. A US-resident publisher targeting US readers operates under FTC; an EU-resident publisher targeting EU readers operates under BaFin / ESMA. Cross-border operations have to honour the stricter rule applicable to each market they publish into:

  • US-resident publishing English content read by EU readers: not BaFin-binding unless actively marketed to EU.
  • EU-resident publishing English content for global audience: BaFin-binding for German readers by residence, but light-touch if no specific marketing to Germany.
  • EU-resident publishing in German: full BaFin / MAR / WpHG framework.

For a publisher choosing where to incorporate, the engine's cost gap (US-FTC $42,360/year vs EU MiCA+DORA $179,600/year at the same operating shape) is one of several factors, and the BaFin/MAR/AI-Act publishing layers widen the EU side further. Tax structure, banking convenience, and audience reach typically dominate the decision.

What changes at scale

In the engine, raising the data-volume tier and processing complexity scales the monthly-hours line for every jurisdiction, so the absolute gap widens with volume while several real-world overheads stay fixed:

  • The active-supervision premium for BaFin is largely fixed (it does not scale with revenue).
  • AI Act disclosure overhead is roughly fixed.
  • The legal-review hour count grows slowly relative to revenue.

So as a fraction of revenue the regulatory cost falls at scale even though the absolute EU-vs-US gap from the engine grows. The practical implication: the EU regulatory load bites hardest on a small operation, where the fixed setup and supervisory overhead are a large share of a modest budget.

What the AI Act adds quantitatively

The AI Act's deployer obligations on a finance publisher using LLMs:

  • Transparency disclosure on AI-generated content: editorial-process change, low cost (€500-1,000/year in documentation time).
  • Annual risk-assessment update: 4-8 hours of structured documentation, €500-1,000/year.
  • Human-oversight documentation: the editorial workflow already produces this; the obligation is to make it auditable, €200-500/year in tooling.

Total AI Act overhead for a small publisher: €1,200-2,500/year. Material but not deal-breaking. For a publisher already running disciplined editorial workflow, much of the documentation cost overlaps with what BaFin / MAR already require.

Jurisdiction selection in practice

For a German-resident publisher targeting EU readers, the jurisdiction is fixed by residence. The choice is operational: register voluntarily with BaFin if scaling beyond general-information content; remain under the unregulated-publisher posture if staying in the general-information lane.

For a US-resident publisher with global readership, the choice is whether to actively market to EU readers. Active marketing to German-language audiences triggers BaFin jurisdiction; English-only content with passive EU readership generally does not. The multiple-times-higher EU regulatory load in the engine, plus the BaFin/MAR/AI-Act publishing layers, may justify limiting marketing to US-English-only.

For an EU-resident publisher considering incorporation in a non-EU jurisdiction, the BaFin / MAR / MiCA framework still applies to content targeting German readers regardless of the entity's domicile. The incorporation move shifts tax framework, not regulatory framework.

Failure modes

  • Picking jurisdiction on cost alone. Tax, banking, and audience reach typically dominate. The cost gap is one input.
  • Treating "I'm US-based" as a defence against BaFin. Active marketing to German readers in German triggers BaFin jurisdiction regardless of publisher residence. The standard is audience, not address.
  • Skipping the AI Act overlay. The Act is in force as of 2024-2025; deployer obligations are not optional for LLM-using publishers.
  • Operating without insurance. A single defended claim under either regime exceeds the annual compliance budget; insurance is the load-bearing line.

FAQ

Is BaFin enforcement against small finance publishers actually likely?

For German-language content from non-registered publishers, BaFin's 2024 finfluencer survey and follow-up factsheet2 explicitly target this segment. Enforcement is typically warning-based on first contact; repeated violations escalate to fines and publication bans. The realistic risk for a small operation following documented procedures is modest; for one operating informally, it is real.

Can I publish from outside the EU and avoid BaFin?

For German-language content actively targeted at German readers, no. For English content with passive readership, generally yes. The active-marketing line is the binding one: German keyword targeting, German social-media buys, or German-language landing pages crosses it.

Does the AI Act apply if I use LLMs only for ideation, not for published prose?

The deployer obligations focus on published outputs. Internal ideation use is lighter; the obligation surface is on what reaches the reader. That said, "deployer" is defined broadly enough that any structured LLM use in the editorial pipeline likely qualifies. Document the use.

Connects to

References

Footnotes

  1. FTC (2023). "Endorsement Guides: What People Are Asking." ftc.gov

  2. BaFin (2024). "Generation Y und Z setzen auf Finfluencer." Fachartikel. bafin.de 2

  3. EU (2014). "Market Abuse Regulation (MAR), Regulation (EU) No 596/2014, Article 20." eur-lex.europa.eu

  4. EU (2024). "Artificial Intelligence Act, Regulation (EU) 2024/1689, Article 50." eur-lex.europa.eu

Verified engine output

Show the recompute-verified inputs and outputs
US — FTC oversight (tier 2, complexity 1.5, $120/hr)
Inputs
jurisdictionus-ftc
data_volume_tier2
processing_complexity1.5
hourly_rate120
Result
jurisdiction › idus-ftc
jurisdiction › nameUnited States — FTC oversight
jurisdiction › shortUS (FTC)
jurisdiction › setup hours40
jurisdiction › monthly hours8
jurisdiction › annual fees usd0
jurisdiction › legal hours per year12
jurisdiction › legal hourly usd650
jurisdiction › gotchas › row 1FTC enforcement is reactive, not registration-based — but settlements (like the 2024 Rite Aid algorithmic-bias order) bite hard.
jurisdiction › gotchas › row 2State-level rules (CA, NY) layer on top — biggest cost driver if you serve those markets.
jurisdiction › gotchas › row 3Disclosure and substantiation rules apply to performance claims; backtests need disclaimers.
jurisdiction › friction tier1
setup cost usd7200
monthly cost usd3530
annual cost usd42360

Computed live at build time.

UK — FCA principles-based (same operating shape)
Inputs
jurisdictionuk-fca
data_volume_tier2
processing_complexity1.5
hourly_rate120
Result
jurisdiction › iduk-fca
jurisdiction › nameUnited Kingdom — FCA principles-based
jurisdiction › shortUK (FCA)
jurisdiction › setup hours60
jurisdiction › monthly hours12
jurisdiction › annual fees usd1200
jurisdiction › legal hours per year18
jurisdiction › legal hourly usd750
jurisdiction › gotchas › row 1Consumer Duty (in force 2023) requires demonstrable consumer-good outcomes — keep evidence.
jurisdiction › gotchas › row 2FCA's 2024 AI report is technology-neutral but explicitly applies operational-resilience rules.
jurisdiction › gotchas › row 3Financial Promotions regime applies if you market to UK retail — separate gateway approval needed.
jurisdiction › friction tier2
setup cost usd10800
monthly cost usd5545
annual cost usd67740

Computed live at build time.

EU — MiCA + DORA (same operating shape)
Inputs
jurisdictioneu-mica-dora
data_volume_tier2
processing_complexity1.5
hourly_rate120
Result
jurisdiction › ideu-mica-dora
jurisdiction › nameEuropean Union — MiCA + DORA
jurisdiction › shortEU (MiCA + DORA)
jurisdiction › setup hours200
jurisdiction › monthly hours30
jurisdiction › annual fees usd8500
jurisdiction › legal hours per year60
jurisdiction › legal hourly usd550
jurisdiction › gotchas › row 1MiCA: CASP licensing required for crypto/asset-related products (≥6-month process, capital requirements).
jurisdiction › gotchas › row 2DORA: ICT-third-party register, threat-led penetration testing every 3 years, incident reporting in 24h.
jurisdiction › gotchas › row 3AI Act (2026): high-risk uses (credit scoring, insurance pricing) need conformity assessment.
jurisdiction › friction tier3
setup cost usd36000
monthly cost usd14258.333333333334
annual cost usd179600

Computed live at build time.