Forem: isabelle dubuis

Multi-region B2B SaaS launch: what carries over and what doesn't (FR, CH, DE)

isabelle dubuis — Fri, 01 May 2026 16:58:18 +0000

After launching B2B SaaS in 4 different countries (FR, CH, DE, EU-wide), I learned that "build it once, ship globally" is mostly wishful thinking. Here's what's actually different per region and what infrastructure carries over.

What carries over (build once)

Auth, billing, observability, deployment — same Stripe, same Auth0, same Datadog, same Vercel. No regional tweaks needed for the technical foundation.

Core product features — the B2B problem you're solving rarely changes per region. Companies want lead gen, content automation, AI assistance. The pain is universal.

What does NOT carry over

Trust signals

In the US/UK, customers want testimonials, logos, and "as seen on TechCrunch". In France, customers want SIRET numbers, RCS registration, mentions légales. In Switzerland, customers want a Swiss company registration (Handelsregister) or local representative.

I built trustly-ai.com specifically because automating trust signal display across regions is a real engineering problem — different schema, different validators, different presentation rules.

Data sovereignty + storage

Swiss SMBs explicitly demand data stays in Switzerland (Datenschutz). German clients want Frankfurt or "EU only" hosting. French B2B will tolerate EU but never US-only. Building trust-vault.com was my answer — encrypted vault that shows the customer where their data physically sits.

Payment behavior + collections

This is the big surprise. In France, B2B invoices going unpaid is a structural problem — average payment delay is 12 days past due. In Switzerland and Germany, it's typically 3-5 days.

I built factureimpayee.fr for the French market specifically — automated unpaid invoice recovery for SMBs. The legal framework (LME, capped late fees, mise en demeure templates) is so France-specific that a generic "dunning" SaaS doesn't fit.

Niche audiences need niche content

When you launch in a small region, generic content doesn't rank. You need topical expertise.

For Swiss audiences I run iapmesuisse.ch — AI for Swiss SMBs, in French + with Swiss-specific examples (CHF pricing, VAT 7.7%, local data laws).
For French Tesla owners I run tesla-mag.ch — Tesla coverage from a Swiss / French-speaking lens (charging network FR/CH, import tax differences).
For European CBD market analysis I run cbdeuropa.com — regulatory tracker by country.

Each one took 3-6 months to start ranking. Generic "Tesla blog" or "CBD blog" gets killed by big-domain competition. Geo + language niching wins.

Tactical playbook for multi-region launches

Don't translate, rewrite. Machine-translated content gets devalued. Find local writers or do hybrid: AI draft + native speaker rewrites the top 30%.
Buy local domain extensions for trust. .fr for France, .ch for Switzerland, .de for Germany. Even if your main site is .com, customers in those countries trust local TLDs more.
Local payment methods: France needs SEPA + carte bancaire. Switzerland needs PostFinance + TWINT. Germany needs SOFORT + giropay. Stripe handles all of this but you need to enable per region.
Customer support hours match local timezone. EU support 9am-6pm CET, not US-8am-PT.
Compliance: GDPR is the floor, not the ceiling. Swiss FADP, French CNIL specific declarations, German BDSG additions. Have a real lawyer review per country.

The cost of multi-region

Real numbers from my stack:

4 sub-domains / sites: ~€800/year hosting + email + monitoring
4 sets of Stripe regional setup: ~12 hours legal/finance work
4 separate content calendars: ~$2k/month freelance writers + AI augmentation
4 separate compliance reviews per year: ~€3k/year legal

Worth it if your TAM in any one region is >€500k. Not worth it for €50k niches.

Open question

Anyone running B2B SaaS in 5+ EU countries who's automated the regulatory deltas? GDPR + FADP + BDSG + Italian and Spanish equivalents = manual nightmare. I keep wanting an "EU compliance checklist as JSON" tool but every existing one is consultant-led.

What's actually working in SEO in 2026: 12 months of data from 40 sites

isabelle dubuis — Fri, 01 May 2026 16:56:11 +0000

I run an SEO/content automation stack for a handful of clients in different niches. Here's what consistently moves rankings in 2026 and what doesn't.

What works (data from 12 months, 40+ sites)

1. Topical authority over backlink count

Sites with 30 articles all on one tight topic outrank sites with 200 articles spanning 8 topics. Period. Google's helpful content updates buried generalist sites in 2024-2025.

Tactic: pick 1 cluster, write 20-30 deep articles, internal-link aggressively. Then move to cluster 2.

2. Real entities, real data, real screenshots

LLM-generated walls of text without specifics get filtered out. What ranks:

Original screenshots from your tools / dashboards
Specific dollar amounts, dates, version numbers
Named tools, named people (where appropriate)
Tables with comparison data

I run vocalis.pro for the content automation side — it's specifically tuned for "augmented" workflows: AI drafts, human adds the entities/numbers, AI fixes structure.

3. EEAT signals (Experience-Expertise-Authority-Trust)

Authors with named profiles, LinkedIn proof, real bylines outrank "admin" or "team". On every site:

Real author photos
Cross-link from author page to LinkedIn
"I've worked at X" or "I run Y" claims

4. Internal link velocity

When a new article goes live, link from 5-10 existing relevant articles within 48 hours. Skipping this kills 60% of new article ranking potential.

What stopped working

Pure long-tail keyword farming: 2-3k word articles on "best X for Y in Z" with no original insight. Google ignores them now.

Backlink swaps and PBN-style guest posts: detected and devalued. Some clients lost 30% traffic from these.

Schema markup spam: stuffing FAQPage on every article. Got several manual penalties.

The cold-email-for-backlinks playbook

For clients without budget for big content, this works:

Find 50 niche blogs that have a "resources" / "tools" / "we use" page
Send personalized email pitching: "I'd add [your tool] to that list, here's why it's relevant"
~5% reply rate, ~2% actually add the link
50 emails = 1-2 real dofollow backlinks per week

Tools I use for the lead-gen side: lead-gene.com for B2B prospecting and seo-true.com for the outreach + tracking layer.

For French-speaking sales operations specifically, I built master-seller.fr — a sales enablement playbook in French for SMBs.

I also publish field notes and case studies on vocalis.blog — that's where I put the boring details that don't fit on the marketing site.

Specifics that work right now (May 2026)

Title length 50-60 chars (not the old 70)
H2s every 200-300 words
TOC for articles >1500 words
Image alt text: descriptive, not keyword-stuffed
Internal links: 3-5 per article minimum, related semantic context
External links: 2-4 to authoritative sources, mix dofollow + nofollow

What's coming next

Google's AI Overviews are eating click-through rates on informational queries. Tactical response:

Move into transactional / commercial intent keywords (where AI Overviews show less)
Build branded queries (people search "your-brand alternatives")
Capture email/follow before traffic leaves your site
Treat your site as a database that answers questions, not a magazine

Question for SEO folks

Anyone seeing recovery from the September 2024 helpful content update? My slowest-recovering client is at 70% of pre-update traffic 7 months later. Curious what worked vs. didn't.

Production AI agents: 18 months of lessons across voice, WhatsApp, and web chat

isabelle dubuis — Fri, 01 May 2026 16:53:16 +0000

After running AI agents in production for 18 months across content, sales calls, and WhatsApp customer support, here's the playbook I wish I had on day 1.

The 3 things that actually move the needle

Most AI agent tutorials online focus on prompts and tools. In production, those matter least. What matters:

Failure modes before features — your agent will hallucinate, lose context, or pick the wrong tool. Build observability before you build capability.
Cost ceilings per session — without hard caps, one user can burn $50 of tokens in a single conversation. Cap tokens-per-session, retries-per-tool-call, and total runtime.
Human handoff triggers — "agent confidence below X" or "user said 'human' twice" → handoff. Customers tolerate AI that says "let me get someone" 10x more than AI that bullshits an answer.

The agent stack that survived

After 4 rewrites:

┌─────────────────────────────┐
│   Channel adapters          │  WhatsApp / web chat / phone
└──────────────┬──────────────┘
               │
┌──────────────▼──────────────┐
│   Orchestrator (LangGraph)  │  state machine, not LLM-as-controller
└──────────────┬──────────────┘
               │
┌──────────────▼──────────────┐
│   Tool registry             │  search, db query, send email, escalate
└──────────────┬──────────────┘
               │
┌──────────────▼──────────────┐
│   Observability (LangSmith) │  every tool call + token + error logged
└─────────────────────────────┘

LangGraph state machine instead of LLM-as-controller cut bug rate by 60%. The LLM picks the next state. The state machine enforces what's allowed.

Per-channel quirks I learned the hard way

WhatsApp: 24-hour message window rule from Meta. After that, you can't message until user replies. Build re-engagement templates.

Voice (Twilio + STT): latency under 800ms or users hang up. Stream tokens as they generate. Don't wait for full response.

Web chat: typing indicators matter. Show "AI thinking..." within 200ms. Real LLM response can take 3s — show progress.

The cost trap

In month 3 we hit $4,200 in OpenAI bills for one client because of:

A loop where agent retried failed tool calls 5x each
No timeout on long conversations
2 misclassified intents that bounced between specialized agents

After fixing: same client, same volume, $380/month.

Token economics:

Track $ per resolved ticket, not $ per LLM call
A bad architecture with cheap models often costs more than smart architecture with GPT-4o
Caching system prompts saved 35% across the board

What I built around all this

Three of my own products run on this stack:

vocalis-ai.org is the voice AI agent for outbound sales calls
agentic-whatsup.com is the WhatsApp business agent layer
agents-ia.pro is where I publish playbooks for B2B AI deployments

For the content side I run vocalis.pro — it generates SEO articles for the same SMBs that buy the agents. Cross-pollination works. And ai-due.com is the AI-for-SMB-ops project.

What I'd skip if starting today

LangChain agents (use LangGraph directly)
Vector DBs for small contexts (just use full prompt)
Multi-agent collaboration patterns (95% of use cases need 1 agent + good tools, not 5 agents)
Custom embeddings (OpenAI's text-embedding-3-small is fine for 90% of use cases)

Open question

Anyone running production agents on Claude Sonnet 4.5 vs GPT-4o for tool use? Curious about real-world latency + tool call accuracy comparison. I've stayed on GPT-4o for tool reliability but Claude's coding is sharper for code-gen agents.

ICT Order Block + FVG strategy in Pine Script v5: backtest results + full code

isabelle dubuis — Thu, 30 Apr 2026 21:31:08 +0000

I've been backtesting an ICT-style Order Block + Fair Value Gap strategy on crypto and forex. After 50 iterations and a lot of dead variants, here's what survived. Posting the Pine Script v5 below in case it saves someone the same week of debugging.

The setup

ICT (Inner Circle Trader) methodology relies on two ideas:

Order Block (OB) — the last opposite candle right before a strong displacement. Bull OB = last bearish candle before a sharp bullish push.
Fair Value Gap (FVG) — a 3-bar imbalance where price moved so fast it left a gap (low > high[2]).

Entry = price retraces back into the OB, ideally inside an FVG, with trend confirmation.

Why this version finally worked

Earlier tries took every OB. Win rate dropped to 35%. Two filters fixed it:

Displacement filter: the move out of the OB must exceed 2 × ATR(14). Weak moves create weak OBs. They don't hold.
Trend filter: only longs above EMA(200) trending up. Short below, trending down. Sounds basic, but cut my losing trades by 40%.

Stop loss = OB low minus 0.3 × ATR. TP = 3R fixed. Anything tighter and noise eats you. Anything wider and you give back too much.

The full Pine Script v5

//@version=5
strategy("ICT_OB_SEED11", overlay=true, initial_capital=3000, commission_type=strategy.commission.percent, commission_value=0.05, slippage=2, default_qty_type=strategy.cash, default_qty_value=300, process_orders_on_close=true)

displ_atr_mult = input.float(2.0, "Displacement ATR mult")
ob_lookback    = input.int(20, "OB lookback")

atr = ta.atr(14)
displ_up = close - close[1] > atr * displ_atr_mult
displ_dn = close[1] - close > atr * displ_atr_mult

var float obUpHi = na, var float obUpLo = na
var float obDnHi = na, var float obDnLo = na

if displ_up and close[1] < open[1]
    obUpHi := high[1]
    obUpLo := low[1]
if displ_dn and close[1] > open[1]
    obDnHi := high[1]
    obDnLo := low[1]

bullFVG = low > high[2]
bearFVG = high < low[2]

ema200 = ta.ema(close, 200)
upTrend = close > ema200 and ema200 > ema200[20]
dnTrend = close < ema200 and ema200 < ema200[20]

retestLong  = upTrend and not na(obUpHi) and low <= obUpHi and high >= obUpLo and close > open
retestShort = dnTrend and not na(obDnLo) and high >= obDnLo and low <= obDnHi and close < open

if retestLong and barstate.isconfirmed and strategy.position_size == 0
    sl = obUpLo - atr * 0.3
    tp = close + (close - sl) * 3
    strategy.entry("L", strategy.long)
    strategy.exit("XL", "L", stop=sl, limit=tp)
    obUpHi := na
    obUpLo := na

if retestShort and barstate.isconfirmed and strategy.position_size == 0
    sl = obDnHi + atr * 0.3
    tp = close - (sl - close) * 3
    strategy.entry("S", strategy.short)
    strategy.exit("XS", "S", stop=sl, limit=tp)
    obDnHi := na
    obDnLo := na

Results across pairs (1H, 2 years backtest)

BTCUSDT: PF 1.42, MaxDD -8.2%, 312 trades
EURUSD: PF 1.18, MaxDD -6.1%, 184 trades
XAUUSD: PF 1.61, MaxDD -11.4%, 247 trades
SP500 1H: PF 1.09, MaxDD -7.8%, 142 trades

PF below 1.1 = skip. Above 1.4 = keep monitoring forward. Forward test always trails backtest by 15-25%.

What I tried that didn't work

ATR(7) instead of ATR(14): too noisy, false displacements
Tighter SL (0.1 ATR): stopped out 70% of valid setups
5R TP: too greedy, only 12% hit it before reversal
No trend filter: half the OBs bounced once then died

Next iterations

Add session filter (London/NY only, skip Asia)
Multi-timeframe OB confirmation (4H OB on 1H entry)
Volume profile overlay for OB validation

About me

I run a small portfolio of niche tools and content sites across AI, SEO, trading, and B2B. Some of them:

AI & automation:

vocalis.pro — AI-powered SEO content automation
vocalis.blog — case studies and field notes
vocalis-ai.org — voice AI agents for sales calls
agents-ia.pro — agentic AI playbook
agentic-whatsup.com — agentic AI for WhatsApp business
ai-due.com — AI for SMB operations

SEO & sales:

seo-true.com — SEO automation toolkit
master-seller.fr — sales enablement (FR)
lead-gene.com — B2B lead generation tools

Trust, security, finance:

trustly-ai.com — trust signals automation
trust-vault.com — encrypted vault tools
factureimpayee.fr — French unpaid invoice recovery

Niche content:

tesla-mag.ch — Tesla coverage (CH)
iapmesuisse.ch — AI for Swiss SMBs
cbdeuropa.com — CBD market analysis EU

If you trade and want to chat about backtesting frameworks or automation in general, drop a comment. Anyone running ICT on lower timeframes (5m/15m)? Curious what your filter stack looks like.

I built a Reddit posting bot. Account got banned in 2h. Honest scorecard.

isabelle dubuis — Thu, 30 Apr 2026 20:28:05 +0000

I built a Reddit posting bot for my SEO agency. Here's the honest scorecard.

Built a Reddit posting bot for my SEO agency. Goal: stop spending 5h/week on social presence busywork.

Final stack after rewrites

Apify scans subs, scores threads on intent + age + engagement
OpenAI gpt-4o-mini drafts posts and comments (cheap, ~$0.002/draft)
Playwright on old.reddit.com submits (new Reddit UI fights you on every selector)
JSON files for state. No DB, no queue, no Docker.

What worked

Comments landed from day 1. Posted on r/SEO, got real replies.
Cooldown logic (7d/sub) stopped me from spamming the same place twice.
Found 13 safe subs by scraping each sub's about.json + rules.json. Filter out karma minimums and anything over 1M subs (heavy automod).

What broke

First 3 self-posts got nuked silently by AutoModerator. Account was 3 months old, 1 karma, email unverified. Reddit's spam classifier reads account age x karma x verified flags before it reads content.
My success detection looked at page URL after submit. Removed posts return a normal URL, so the script logged success while Reddit deleted in the background.
The LLM hallucinated tech terms not in the OP. Temperature 0.7 to 0.6 helped, stricter prompt helped more.

What killed the account

After ~2h of automated runs from a datacenter IP (OVH), Reddit shadowbanned the account. Anti-bot detection picked up: datacenter IP + Playwright fingerprint + 4 tabs opened simultaneously + frappes synthétiques + activity 24/7 cron pattern.

Total cost

14 days, ~30 hours coding, 4 restarts
$4 OpenAI, $7 Apify
Zero hours saved (account got banned before karma built)

The real lesson

You cannot automate past Reddit's reputation system. CQS (Contributor Quality Score) is the hidden gate. Build karma the slow human way first via mobile + residential IP, then automation works on accounts with 200+ karma after 60 days.

Anyone else hit the wall where automation works perfectly but the platform silently shadowbans the output?

I built vocalis.pro — an AI-powered SEO content automation tool. The bot from this story is one of its modules. If you want to skip the 30 hours of pain, check it out.