Forem: SIKOUTRIS

Building a B2B Electronic Invoicing API for French PDP Compliance in 2026

SIKOUTRIS — Mon, 27 Apr 2026 09:24:25 +0000

The French e-Invoicing Mandate: A Developer Perspective

France is implementing one of the most ambitious B2B e-invoicing mandates in Europe. By September 2026, all businesses registered for VAT in France will be required to both receive electronic invoices and progressively transmit them through certified platforms known as PDPs (Plateformes de Dématérialisation Partenaires).

Architecture Overview

The French e-invoicing ecosystem has three key components:

1. PPF (Portail Public de Facturation) — the government-operated central hub managed by the DGFIP. All invoice flows pass through or are registered here.

2. PDPs (Plateformes de Dématérialisation Partenaires) — private certified operators that handle invoice transmission, validation and archiving. Companies can choose to use PDPs for full lifecycle management.

3. ODs (Opérateurs de Dématérialisation) — intermediaries that convert invoice data but route through either a PDP or the PPF.

Key Technical Requirements

Invoices must comply with one of three accepted structured formats:

Factur-X (hybrid PDF/XML, cross-border compatible)
UBL 2.1 (XML, widely used in European public procurement)
CII (UN/CEFACT Cross Industry Invoice, XML)

The mandatory data fields extend beyond standard invoice elements to include SIREN numbers, VAT identification, payment terms, and specific buyer routing codes.

Notification and Status Events

A critical difference from traditional invoicing: the e-invoicing platform must emit lifecycle status events (deposited, received, rejected, paid) that are registered with the PPF. Implementing an event listener and status update mechanism is therefore as important as the invoice generation itself.

# Example: listening to PDP webhook events
@app.route("/pdp-webhook", methods=["POST"])
def handle_invoice_status():
    event = request.json
    invoice_id = event["invoiceId"]
    status = event["lifecycleStatus"]  # DEPOSITED, RECEIVED, REJECTED, PAID
    update_invoice_status(invoice_id, status)
    return jsonify({"received": True}), 200

Testing Environment

The PPF provides a dedicated testing sandbox. Developers should validate:

Schema conformance for all three accepted formats
SIREN/SIRET validation against INSEE data
Status event round-trips in the sandbox
Archiving compliance (10-year retention required by French tax law)

Resources

For non-technical stakeholders and SMEs navigating the mandate, mafacturation-electronique.fr provides clear guides on platform selection, implementation timelines and frequently asked questions in French.

The September 2026 deadline is firm — organizations that have not yet begun their integration work should prioritize this now.

Kapitalmarkt 2026: Anlagestrategien für deutsche Investoren im Niedrigzinsumfeld

SIKOUTRIS — Mon, 27 Apr 2026 09:24:24 +0000

Der Kapitalmarkt 2026: Was Anleger wissen müssen

Nach Jahren volatiler Märkte und geldpolitischer Unsicherheit stellt sich für deutsche Privatanleger und institutionelle Investoren die zentrale Frage: Wie sieht eine zukunftsfähige Anlagestrategie in 2026 aus?

Zinsentwicklung und ihre Auswirkungen

Die Europäische Zentralbank (EZB) hat ihren Leitzins im Verlauf von 2025 schrittweise gesenkt. Für Anleger bedeutet dies:

Anleihen: Bestandsanleihen mit höheren Kupons gewinnen an Wert, Neuemissionen rentieren niedriger
Aktien: Dividendentitel und Wachstumsaktien profitieren von günstigeren Finanzierungsbedingungen
Immobilien: Die Finanzierungskosten sinken, was den Markt graduell entlastet

Diversifikation als Kernprinzip

Ein ausgewogenes Portfolio in 2026 kombiniert verschiedene Anlageklassen, um Risiken zu streuen. Empfohlene Allokationen variieren je nach Risikoprofil, umfassen jedoch typischerweise:

Aktien (30–60%): Globale ETFs auf MSCI World oder MSCI All Country World bieten breite Diversifikation bei niedrigen Kosten
Anleihen (20–40%): Staatsanleihen aus der Eurozone oder Investment-Grade-Unternehmensanleihen
Alternative Anlagen (10–20%): Rohstoffe, Infrastruktur oder REITs als Inflationsschutz
Liquiditätsreserve (5–10%): Tagesgeld oder kurzlaufende Geldmarktfonds

Steuerliche Aspekte nicht vergessen

Die Abgeltungsteuer von 25% (zzgl. Solidaritätszuschlag) bleibt für Kapitalerträge relevant. Der Sparer-Pauschbetrag wurde auf 1.000 Euro (Einzelperson) bzw. 2.000 Euro (Verheiratete) angehoben. Ausländische Quellensteuern können in vielen Fällen angerechnet werden.

Weiterführende Ressourcen

Für fundierte Analysen zu Märkten, Wirtschaftstrends und Anlagestrategien bietet Kapital-Spiegel.de regelmäßig aktualisierte Berichte und Marktkommentare — unabhängig und ohne Produktempfehlungen.

Eine gut informierte Anlagestrategie beginnt mit verlässlichen Daten und unabhängiger Analyse.

Detecting Greenwashing at Scale: Building an EU Green Claims Compliance Checker

SIKOUTRIS — Sat, 25 Apr 2026 14:06:49 +0000

Detecting Greenwashing at Scale: How We Built an Automated EU Green Claims Compliance Checker

The EU Green Claims Directive is coming into force progressively through 2026, and for the first time, companies making environmental claims face substantive legal liability if those claims aren't backed by verifiable evidence.

The Problem We Solved

When auditing marketing copy across dozens of websites, we kept encountering the same patterns: vague claims like "eco-friendly," "sustainable," or "carbon-neutral" with no supporting methodology. The EU's Green Claims Directive specifically targets these — Article 5 requires that claims be specific, accurate, and substantiated.

Our challenge: how do you scan hundreds of pages of marketing content and flag potential greenwashing violations programmatically?

Technical Architecture

We built a three-layer pipeline:

Layer 1: Claim Detection

Using a combination of regex patterns and a fine-tuned classification model, we detect phrases that trigger scrutiny under the Green Claims Directive:

Absolute claims ("100% sustainable," "zero emissions")
Vague positive claims ("eco-friendly," "green," "natural")
Future-tense claims without substantiation ("working toward carbon neutrality")
Comparative claims without a reference point ("greener than competitors")

Layer 2: Evidence Matching

For each detected claim, we attempt to find supporting evidence on the same page or domain:

Third-party certifications (ISO 14001, EU Ecolabel, Carbon Trust)
Lifecycle assessment references
Specific metrics (percentage reductions, absolute quantities)
Accredited methodology citations

Layer 3: Risk Scoring

Claims without matched evidence receive a risk score from 1-10 based on:

Claim specificity (absolute > comparative > vague)
Audience exposure (homepage > product page > blog)
Regulatory focus area (climate > biodiversity > circular economy)

What We Learned

The most common violation pattern? Scope conflation — companies claiming their product is "carbon neutral" when only their offices have a carbon offset scheme. The EU directive is particularly strict about this.

Tools like greenwashing-checker.com automate the first pass of this analysis, flagging claims that warrant deeper legal review. The human expert still needs to make the final call, but automated scanning reduces audit time by 70-80%.

The Regulatory Timeline

2026 Q1-Q2: Member states transposing the directive into national law
2026 Q4: First enforcement actions expected in France and Germany
2027: Full enforcement across all EU member states

Open Questions

The directive still leaves gray areas, particularly around:

What constitutes "equivalent prominence" when displaying claim limitations
How to handle claims inherited from supply chain certifications
The threshold for "significant" environmental benefit

If you're building compliance tooling in this space, the European Commission's implementation guidance is worth reading alongside the directive text.

Building something in the sustainability compliance space? Drop a comment — happy to compare notes on the technical challenges.

How I Built a Childcare Availability Platform for 38,000 French Nurseries

SIKOUTRIS — Fri, 24 Apr 2026 10:36:10 +0000

How I Built a Childcare Availability Platform for 38,000 French Nurseries

Finding childcare in France is famously difficult: 230,000 spots are missing nationwide, and the search process involves calls to mairies, waiting lists at crèches associatives, and forms sent by post to CAF. I built a platform to fix this — here is the technical story.

The Data Problem: 18 Different Source Formats

French childcare data comes from multiple public sources, each with its own format and update frequency:

Source	Format	Update	Scope
CAF (data.gouv.fr)	CSV	Monthly	Agrément PMI + PSU subvention
Mairie databases	No API	Variable	Municipal crèches
DREES SSAM	Excel	Annually	Capacity statistics
Monenfant.fr (CNAF)	HTML	Daily	Limited fields

The strategy: use the CAF CSV as the authoritative registry (38,427 établissements in the 2025 edition), then enrich with GPS coordinates from the government Base Adresse Nationale (BAN API), and supplement with phone/email via SIREN lookup on api.insee.fr.

Geocoding at Scale

The CAF CSV contains addresses but no GPS coordinates. Geocoding 38,000 addresses via the BAN API:

import asyncio
import aiohttp

async def geocode_batch(addresses: list[str], session: aiohttp.ClientSession) -> list[dict]:
    results = []
    for address in addresses:
        async with session.get(
            "https://api-adresse.data.gouv.fr/search/",
            params={"q": address, "limit": 1}
        ) as resp:
            data = await resp.json()
            if data["features"]:
                results.append(data["features"][0]["geometry"]["coordinates"])
            else:
                results.append(None)
    return results

With a concurrency limit of 10 requests/second (BAN API rate limit), geocoding 38,427 addresses takes ~64 minutes. We run this monthly after the CAF CSV refresh.

Proximity Search with PostGIS

The core search feature — "crèches near me" — uses PostGIS geography functions:

SELECT id, nom, adresse, type_etablissement,
       ST_Distance(
         location::geography,
         ST_SetSRID(ST_MakePoint($1, $2), 4326)::geography
       ) AS distance_m
FROM etablissements
WHERE ST_DWithin(
  location::geography,
  ST_SetSRID(ST_MakePoint($1, $2), 4326)::geography,
  $3  -- radius in meters
)
ORDER BY distance_m ASC
LIMIT 20;

With a GiST index on the location column, this query runs in ~8ms even with 38,000 rows.

Handling the Availability Problem

Crèches do not publish real-time availability (no API exists). The approach:

Contact form integration: Users submit interest, triggering an email to the crèche director with a structured inquiry
Response tracking: We track response rates per établissement — directors who respond within 48h get a "responsive" badge
User-reported availability: After a successful placement, users can mark a slot as "taken" — crowd-sourced freshness signal

This gives parents actionable information without requiring crèches to adopt new systems.

The Result

The platform trouver-creche.fr now covers 38,427 établissements across metropolitan France, with geocoded locations, contact details enriched from SIREN, and user-reported response time indicators. Monthly CAF data refresh keeps capacity figures current.

The biggest lesson: in public service data, freshness beats completeness. Parents need to know if information was updated last month, not last decade.

Building a Pet Insurance Comparison Engine: Handling Variable Premiums Across 15 French Insurers

SIKOUTRIS — Fri, 24 Apr 2026 10:36:09 +0000

Building a Pet Insurance Comparison Engine: Handling Variable Premiums Across 15 French Insurers

French pet insurance has grown 34% since 2022, driven by rising vet costs and increased pet ownership post-COVID. But comparing products programmatically is a nightmare: 15 major insurers, each with their own pricing grid based on species, breed, age, region, and deductible. Here is how I built a comparison engine that handles this complexity.

The Data Model Challenge

Each insurer publishes premiums differently:

Santévet : JSON API (unofficial, scraped from their quote widget)
Assurimo : PDF tariff grids updated quarterly
Groupama : Static tables by risk category
Dalma : Dynamic pricing engine (quote request required)

The core problem: how do you normalize wildly different data structures into a comparable output?

A Flexible Pricing Schema

{
  "insurer_id": "santevet",
  "product_id": "sv-excellence",
  "species": "cat",
  "breed_risk_group": 2,
  "age_min_months": 12,
  "age_max_months": 84,
  "region": "IDF",
  "deductible_pct": 20,
  "ceiling_annual_eur": 3000,
  "monthly_premium_eur": 38.50,
  "reimbursement_basis": "actual_costs",
  "waiting_period_days": 30
}

This schema handles ~80% of cases. The remaining 20% (hereditary conditions, breed exclusions, complementary modules) use an exclusions array and add_ons object.

Breed Risk Classification

The biggest normalization challenge is breed-to-risk mapping. French insurers use different classification systems:

Santévet: 4 risk groups (1=low, 4=high)
Assurimo: 7 categories by morphology
Allianz: breed whitelist / blacklist

I built a crosswalk table mapping 380 dog breeds and 90 cat breeds to a normalized 5-level risk scale using FCI (Fédération Cynologique Internationale) breed standards as the anchor.

Regional Pricing

Vet costs vary significantly by region: a consultation costs €28 in rural Creuse vs €68 in Paris 16th. Some insurers adjust premiums by department, others by zip code prefix, others by urban/rural flag only.

Solution: a geolocation lookup table mapping INSEE commune codes to risk tiers, updated annually from the DREES veterinary care cost survey.

Real-Time Quote Aggregation

For insurers with quote APIs, I use a queue-based system: user input triggers parallel quote requests across all insurers, with a 3-second timeout. Missing quotes fall back to cached tariff data (max 30 days old), flagged visually in the UI.

The result is a side-by-side comparison that actually reflects real prices. You can test the live engine at monassuranceanimal.fr, which covers 12 insurers with real-time quotes and 3 with cached grids.

Handling Annual Premium Updates

French law requires insurers to notify policyholders of premium changes 15 days before renewal. For comparison sites, this creates a "freshness" problem: prices quoted in November may differ by January.

My solution: a confidence score per premium record, calculated as 1 - (days_since_update / 90). Records older than 90 days are excluded from comparisons and flagged for manual refresh.

What I Would Do Differently

Start with the PDF parser first - most insurers still distribute tariffs as PDFs, and building a reliable extractor took 3x longer than expected
Document the exclusions schema early - adding hereditary conditions support retroactively broke 4 normalizers
Build the insurer change detection webhook - instead of polling, subscribe to insurer sitemap changes

Have you built comparison engines in regulated industries? The insurance sector has unique challenges around accuracy obligations (ACPR regulations) that add compliance overhead. Happy to discuss in the comments.

Building a Digital Agency Hub: How METIS Digital Manages 40+ Web Properties

SIKOUTRIS — Sat, 18 Apr 2026 14:09:21 +0000

Managing one website is straightforward. Managing five gets interesting. Managing forty-three across four business entities, multiple tech stacks, and different markets? That requires a system.

I run METIS Digital, a digital agency that operates a portfolio of web properties spanning real estate diagnostics, professional training, senior services, AI comparison tools, online calculators, and sustainability compliance. Each site has its own audience, monetization model, and technical requirements. Here is how we keep it all running without losing our minds.

Why 43 Sites?

The obvious question: why not just build one big site? The answer is strategic.

Each site targets a specific niche with laser-focused SEO. A domain like "greenwashing-checker.com" immediately communicates its purpose to both users and search engines. A generic "metis-digital.click/tools/greenwashing" does not carry the same weight.

The multi-site approach also provides risk isolation. If one site gets hit by a Google algorithm update, the rest of the portfolio is unaffected. If a particular niche declines, our revenue is diversified across many others.

And frankly, exact-match domains still carry SEO value in certain niches — particularly for comparison sites, calculators, and tools where user intent is crystal clear.

The trade-off is operational complexity. Which is where the interesting engineering challenges live.

The Architecture

Our portfolio runs on three main stacks:

WordPress — about 60% of sites. Used for content-heavy sites where we need flexible publishing, plugin ecosystems, and easy content management. Our diagnostic immobilier sites, training platforms, and content portals run on WordPress.

Pure PHP — about 30% of sites. Used for tool-focused sites (calculators, comparators, checkers) where we need maximum control over performance and do not need a CMS. These sites are lightweight, fast, and cheap to host.

Cloudflare Pages — about 10% of sites. Used for static or semi-static sites where we want edge deployment and zero server management.

All 43 sites are hosted on a single o2switch shared hosting plan (for the WordPress and PHP sites), with Cloudflare in front of everything for CDN, SSL, and basic WAF protection. Total hosting cost: under 10 euros per month.

The Central Nervous System: Supabase

The key to managing this many sites is centralized data. We use Supabase (managed PostgreSQL) as our single source of truth for everything:

Site registry — all 43 sites with their domains, tech stack, current status, deployment phase, and configuration
Content pipeline — articles, keywords, semantic clusters, and publishing schedules
Performance tracking — keyword rankings, traffic data, and revenue metrics
Health monitoring — automated checks for uptime, SSL expiration, and SEO health
Credential management — API keys, app passwords, and service accounts (encrypted)

Every tool, script, and automation workflow in our stack reads from and writes to Supabase. There is no spreadsheet, no local file, no "I think it was on the other computer" situation. One database, one truth.

Automation: n8n as the Backbone

Manual management of 43 sites would require a team of 10. Instead, we run a small team augmented by heavy automation.

n8n (self-hosted workflow automation) is our automation backbone. Here are some of the workflows running daily:

Health Monitor — runs every 6 hours, checks all 40 active sites for:

HTTP status (is the site returning 200?)
SSL certificate validity
DNS resolution
Response time
Critical page availability

If anything fails, we get an immediate alert. Sites that were fine yesterday but return 500 errors today get flagged before any user reports it.

Content Pipeline — automated workflows that:

Identify keyword opportunities from Google Search Console data
Prioritize content creation based on search volume and competition
Draft articles using AI (Claude API), which then go into a human review queue
Publish approved content to the correct WordPress site via REST API
Submit new URLs to Google for indexing

SEO Monitoring — daily checks that:

Pull ranking data from DataForSEO
Compare positions against previous periods
Identify quick wins (keywords ranking 11-20 with decent volume)
Flag significant ranking drops for investigation

The Deployment Pipeline

Deploying changes across 43 sites requires discipline. Our process:

Snapshot — before any change, we capture the current state (file backup, database export for WordPress sites)
Deploy — changes go out via WordPress REST API (for content and snippets) or FTP (for PHP files)
Verify — automated health check confirms the site still returns 200 OK
Rollback — if verification fails, the snapshot is restored immediately

We never deploy to all sites simultaneously. Changes roll out in tiers: first to a test site, then to a small batch, then to the full portfolio. This limits blast radius when something goes wrong — and something always eventually goes wrong.

SEO at Scale

Running 43 sites gives us interesting SEO insights that you do not get from managing one or two:

Internal linking across sites. Where it makes sense editorially, our sites link to each other. A calculator site might link to a comparison site for deeper analysis. A training platform might link to a diagnostic service site for practical context. This is not a link network — the links are genuinely useful to users — but the cross-pollination of authority helps.

Content velocity matters. Google rewards consistent publishing. Across 43 sites, we publish 100+ articles per month. Each individual site might only get 2-3 articles, but the portfolio-level velocity means we are constantly feeding the indexing pipeline.

Technical SEO is multiplicative. A Core Web Vitals improvement that saves 200ms per page load, applied across 43 sites, is a portfolio-wide performance upgrade. We invest in reusable optimizations: shared CSS frameworks, optimized image pipelines, and standardized structured data templates.

Keyword research scales. Understanding one niche deeply helps with adjacent niches. Our AI comparison sites share keyword research patterns. Our calculator sites share user intent models. Knowledge compounds across the portfolio.

Cost Structure

People are surprised by how cheaply this runs:

Item	Monthly Cost
o2switch hosting (all sites)	~8 euros
Cloudflare (37 zones, free plan)	0 euros
Supabase (Pro plan)	~25 USD
n8n Cloud	~20 euros
DataForSEO API	~50 USD
Domain renewals (amortized)	~50 euros
AI APIs (Claude, OpenAI)	~40 USD
Total	~200 euros/month

That is under 5 euros per site per month for hosting, monitoring, automation, and AI-powered content assistance. The marginal cost of adding a new site to the portfolio is essentially zero — just the domain registration.

Mistakes We Made

Lest this sound too smooth, here are things that went wrong:

Over-engineering early. We spent weeks building a custom deployment system before realizing that WordPress REST API + a simple backup script covered 90% of our needs. Start simple.

Ignoring monitoring initially. We lost a site to an SSL expiration because nobody noticed the certificate had not auto-renewed. Now everything is monitored automatically.

Too many plugins. Early WordPress sites had 20+ plugins each. Performance suffered, updates broke things, and security surface area was enormous. We now run a minimal plugin set and use Code Snippets for custom functionality.

Not centralizing data sooner. For the first year, site information lived in spreadsheets, local files, and peoples heads. Migrating to Supabase as a single source of truth was the single biggest operational improvement we made.

What We Would Do Differently

If starting from scratch today:

Supabase from day one. Central data from the start, not retrofitted.
Fewer WordPress sites. More PHP-pure for tool sites, reserving WordPress for content-heavy sites only.
Automated testing earlier. We now have health checks, but automated content quality checks and SEO validation would have caught issues sooner.
Standardized templates. We built too many one-off designs early on. A small library of proven templates would have saved months.

The Takeaway

Managing a large portfolio of web properties is less about technical brilliance and more about operational discipline. Centralize your data. Automate your monitoring. Standardize your deployments. And invest in the boring infrastructure that keeps everything running reliably.

The exciting part is not any single site — it is the system that makes all of them work together.

METIS Digital operates 43 web properties across multiple verticals. Learn more at metis-digital.click.

How to Evaluate Software Tools Without Getting Misled by Vendor Marketing

SIKOUTRIS — Tue, 14 Apr 2026 13:10:26 +0000

How to Evaluate Software Tools Without Getting Misled by Vendor Marketing

Software tools define how modern teams work. But with thousands of options in every category, choosing the right stack is increasingly difficult.

The problem with vendor-driven software reviews

Most software review sites earn revenue from the vendors they review. This creates obvious incentive problems: paid placements appear as "Editor Choice," review criteria are shaped by what vendors want highlighted, and genuine weaknesses get buried.

What makes an objective comparison?

A trustworthy software review process typically includes: testing by actual practitioners, transparent scoring rubrics published before testing, long-term testing across multiple use cases, and no revenue dependency on the vendors reviewed.

Key categories in 2026

Project Management: The gap between tools like Linear, Jira, and Basecamp is not just UX - it is philosophy. Linear optimizes for speed, Jira for enterprise customizability, Basecamp for simplicity.

Developer Tools: IDE plugins, CI/CD pipelines, observability stacks - each category has matured. Benchmarks under realistic workloads reveal differences that marketing copy never would.

Business Intelligence: From self-hosted Metabase to enterprise Tableau, the cost/complexity tradeoff has never been more pronounced. Open-source options have closed the feature gap significantly.

For independent software reviews across 30+ categories with transparent scoring, visit softwarerundown.com.

AI Coding Assistants in 2026: A Practical Comparison for Developers

SIKOUTRIS — Mon, 13 Apr 2026 09:27:11 +0000

The AI coding assistant space has consolidated significantly. Where dozens of tools competed in 2023, a handful of serious contenders now dominate daily developer workflows. But choosing between them is still surprisingly non-obvious — the differences that matter most are rarely highlighted in marketing materials.

What Actually Differentiates AI Coding Tools

Context window size gets the headlines, but the real differentiator is code understanding depth. Can the tool reason about your entire project architecture, not just the file currently open? Can it understand undeclared variables from project-wide context? This matters for refactoring and debugging far more than raw token limits.

Speed vs accuracy tradeoffs are real. Faster models generate suggestions quickly but make more logic errors. Slower models with better reasoning catch edge cases that faster alternatives miss. For boilerplate, speed wins. For complex logic, accuracy matters more.

The Integration Factor

The best standalone AI coding tool becomes mediocre if the IDE integration is poor. Look for:

Inline suggestions that don't interrupt flow
Multi-file context without manual selection
Test generation that understands your testing framework
Git-aware suggestions (not ignoring recently changed code)

Language and Framework Support Varies More Than Expected

Most tools excel at Python, JavaScript, and TypeScript. Support for Go, Rust, Kotlin, and Swift varies considerably. If you work in less common languages, run your own benchmarks — marketing claims and real-world performance diverge significantly.

Cost Structures in 2026

Per-seat pricing has become the norm for teams. Individual pricing ranges from free tiers with limited completions to $20-$40/month for unrestricted usage. Team plans often include admin controls and audit logs that matter for enterprise security requirements.

For a detailed feature-by-feature breakdown of the leading AI coding assistants — including context handling, language support, IDE compatibility, and pricing — aicodingcompare.com provides regularly updated comparison tables based on hands-on testing.

Making the Choice

The most practical approach: trial the top 2-3 tools for one week each on real work tasks, not toy examples. The tool that reduces your actual friction wins, regardless of benchmark scores.

Building a Pet Insurance Comparison Engine: Data Normalization in the French Market

SIKOUTRIS — Tue, 07 Apr 2026 13:10:49 +0000

This post is based on our experience building monassuranceanimal.fr, a pet insurance comparison platform for French pet owners.

How We Built srat.fr: Digitizing Real Estate Diagnostics for French Homeowners

SIKOUTRIS — Sat, 14 Mar 2026 16:49:28 +0000

Real estate diagnostics in France are mandatory — no exceptions. Before selling or renting any property, homeowners must produce a Dossier de Diagnostic Technique (DDT) covering everything from energy performance (DPE) to asbestos, lead paint, termites, and more. Yet for years, the process remained stuck in the analog era: phone calls to local diagnosticians, paper reports, and zero transparency on pricing.

That is exactly the problem we set out to solve with srat.fr.

The Problem: A Fragmented Market

France has roughly 8,000 certified diagnostic professionals (diagnostiqueurs immobiliers). They operate independently or in small firms, each with their own pricing, availability, and booking process. For a homeowner in Lyon or Marseille trying to schedule a DPE before listing their apartment, the experience was painful:

Call 3-4 companies to compare prices
Wait for callbacks
Hope the diagnostician shows up on time
Receive a PDF report days later

Meanwhile, regulations kept tightening. The 2021 Climate Law made DPE results legally binding and introduced rental bans for the worst-rated properties (class G by 2025, class F by 2028). Suddenly, millions of landlords needed diagnostics — fast.

Why We Built SRAT

SRAT (Société de Recherche et dAssistance Technique) was founded to bridge this gap. The idea was straightforward: build a digital platform that connects property owners with certified diagnosticians, streamlining the entire chain from quote request to report delivery.

Our goals were:

Instant quoting — homeowners describe their property and get a price estimate in under 2 minutes
Certified network — every diagnostician on the platform holds valid certifications (COFRAC-accredited)
Digital reports — results delivered electronically with proper ADEME registration
Coverage across France — not just Paris, but secondary cities and rural areas too

The Technical Stack

We went with a WordPress-based architecture for several practical reasons. The French real estate market is local and search-driven — people google "diagnostic immobilier + ville" thousands of times per month. WordPress gave us the SEO flexibility we needed without over-engineering the initial product.

Key components:

WordPress + custom theme for the public-facing site
WooCommerce adapted for service booking (not physical products)
Custom PHP modules for quote calculation based on property type, surface area, and location
Supabase as a backend database for diagnostician availability and report tracking
n8n workflows for automated dispatching and follow-up emails

The quote engine deserves a mention. French diagnostic pricing depends on multiple factors: property size, number of required diagnostics (DPE alone vs. full DDT), property age (pre-1949 buildings need lead testing), and geographic zone. We built a rule engine that weights all these parameters and returns a competitive quote instantly.

Understanding French Diagnostic Requirements

For those unfamiliar with the French system, here is what a complete DDT typically includes:

Diagnostic	When Required	Validity
DPE (energy performance)	All sales and rentals	10 years
Amiante (asbestos)	Buildings pre-July 1997	Unlimited if negative
Plomb (lead paint)	Buildings pre-January 1949	1 year (sale) / 6 years (rental)
Termites	Designated zones (prefectural decree)	6 months
Gaz (gas installation)	Installations > 15 years	3 years (sale) / 6 years (rental)
Électricité (electrical)	Installations > 15 years	3 years (sale) / 6 years (rental)
ERP (natural/tech risks)	All transactions	6 months
Assainissement	Non-collective sanitation	3 years

Getting this right matters. An incomplete or expired DDT can void a real estate transaction or expose the seller to legal liability.

Challenges We Faced

The biggest challenge was not technical — it was trust. French homeowners are cautious about online services, especially for something legally sensitive. We invested heavily in:

Displaying certification numbers prominently
Publishing real customer reviews
Offering phone support (yes, actual humans picking up)
Transparent pricing with no hidden fees

Another challenge was geographic coverage. Unlike delivery services where you can start in one city and expand, diagnostic coverage needs to be broad from day one. Nobody wants to enter their address and see "no diagnostician available in your area." We spent months onboarding diagnosticians across major metropolitan areas before launching publicly.

Results and Lessons Learned

Since launch, srat.fr has processed thousands of diagnostic requests across multiple French regions. A few things we learned along the way:

SEO is king in local services. Over 70% of our traffic comes from organic search. People search for exactly what they need: "diagnostic immobilier Toulouse prix" or "DPE obligatoire location 2026." Building content around these queries drove growth more than any paid channel.

Simplicity converts. Our first version had too many form fields. When we cut the quote form down to 4 essential questions (property type, surface, location, diagnostic type), conversion doubled.

Regulation changes create demand spikes. Every new government announcement about DPE thresholds or rental bans sends a wave of traffic. Being ready with updated content and available diagnosticians during these spikes is critical.

What is Next

We are working on several improvements: a real-time availability calendar so homeowners can book specific time slots, automated report analysis that flags energy renovation priorities, and expanded coverage into overseas territories (DOM-TOM).

The French real estate diagnostic market is worth over €1.5 billion annually and still largely offline. There is plenty of room for digital platforms that make the process faster, cheaper, and more transparent.

If you are building in a regulated, fragmented market — real estate or otherwise — feel free to reach out. We have learned a lot about navigating French bureaucracy, certification requirements, and the particular challenge of digitizing services that people only need once every few years.

SRAT provides certified real estate diagnostics across France. Learn more at srat.fr.

Greenwashing Checker vs Scanner: Two Approaches to EU Green Claims Compliance

SIKOUTRIS — Sat, 14 Mar 2026 16:49:19 +0000

The EU Green Claims Directive is coming, and most companies are not ready. Starting in 2026, businesses making environmental claims in the European market must substantiate those claims with verifiable evidence — or face significant penalties. Phrases like "eco-friendly," "sustainable," or "carbon neutral" without proper backing will become regulatory liabilities.

This regulatory shift has created a new category of tools: greenwashing detection and compliance platforms. We have built two of them — greenwashing-checker.com and greenclaims-scanner.com — each taking a different approach to the same fundamental problem.

Here is what we learned about the challenge and why we think both approaches have merit.

The Regulatory Landscape

The EU Green Claims Directive (proposed March 2023, expected enforcement from 2026) requires that:

Environmental claims must be based on recognized scientific evidence
Claims must specify whether they apply to the entire product, part of it, or certain life cycle stages
Companies must identify if there are significant trade-offs between environmental impacts
Third-party verification may be required for certain claim types
Penalties for non-compliance include fines and potential market access restrictions

This builds on existing regulations like the Unfair Commercial Practices Directive and supplements sector-specific rules (EU Taxonomy, CSRD reporting, etc.).

For companies marketing in the EU — which includes non-EU companies selling to EU consumers — this is not optional. It is a compliance requirement with teeth.

The Two Approaches

Greenwashing Checker: The Quick Assessment

Greenwashing Checker is designed for speed and accessibility. Think of it as a first-pass screening tool. You input a green claim — from a product page, marketing material, annual report, or ad — and the tool evaluates it against a framework of common greenwashing patterns.

How it works:

Input — paste the text of an environmental claim (or a URL containing claims)
Analysis — the tool checks for vague language, unsubstantiated superlatives, irrelevant claims, hidden trade-offs, and misleading imagery cues
Score — returns a risk score from low to high, with specific explanations for each flagged issue
Recommendations — suggests how to rephrase or substantiate the claim to reduce greenwashing risk

Best for:

Marketing teams reviewing copy before publication
Compliance officers doing initial screening
Journalists investigating corporate environmental claims
Consumers who want a quick reality check

Limitations:

Cannot verify the underlying data behind a claim (it analyzes the language, not the science)
Works best with explicit textual claims rather than visual/contextual greenwashing
Provides guidance, not legal compliance certification

Green Claims Scanner: The Deep Audit

Green Claims Scanner takes a more comprehensive approach. Instead of checking individual claims, it scans an entire web presence — website pages, product descriptions, marketing materials — and produces a full audit report.

How it works:

Crawl — the scanner crawls the target website (or a specified section) identifying all environmental and sustainability-related claims
Classify — each claim is categorized by type (carbon claims, recyclability, biodegradability, energy efficiency, etc.)
Assess — claims are evaluated against EU regulatory frameworks and common greenwashing indicators
Report — generates a comprehensive report with risk levels, specific citations, and remediation priorities

Best for:

Companies preparing for Green Claims Directive compliance
Legal teams conducting pre-audit assessments
Consultancies advising clients on sustainability communications
Competitors benchmarking industry claims

Limitations:

Slower (a full site scan takes time)
More complex to interpret — requires some regulatory knowledge
Higher cost for comprehensive scans

Why Two Tools?

The honest answer: because the market needs both, and they serve different stages of the compliance journey.

A marketing manager writing a product description needs a quick check: "Is this claim okay?" That is the Checker use case. Five seconds, immediate feedback, iterate.

A head of compliance preparing for the Green Claims Directive needs a systematic audit: "What claims are we making across our entire web presence, and which ones are at risk?" That is the Scanner use case. Thorough, documented, actionable.

We could have built one tool that tries to do both, but in practice, the UX requirements are fundamentally different. Quick checks need to be fast and simple. Comprehensive audits need to be thorough and detailed. Trying to combine both typically results in a tool that does neither well.

Common Greenwashing Patterns We Detect

After analyzing thousands of environmental claims, patterns emerge clearly:

Vague claims without specifics. "Eco-friendly packaging" means nothing without specifying what makes it eco-friendly (recyclable? made from recycled content? biodegradable? all of these? under what conditions?).

Irrelevant claims. Advertising a product as "CFC-free" when CFCs have been banned for decades. Technically true, practically meaningless, and designed to create a green impression.

Hidden trade-offs. "Our electric vehicle produces zero emissions" — at the tailpipe, yes. But manufacturing the battery has significant environmental impact. Omitting material trade-offs is a form of greenwashing.

Unsubstantiated superlatives. "The most sustainable option available" requires comparative evidence across all competitors — which rarely exists.

Misleading imagery. Green colors, nature imagery, and leaf icons on products that have no particular environmental benefit. Our text-analysis tools cannot fully catch this, but we flag common textual correlates.

False certifications. Referencing certifications that do not exist, are expired, or do not apply to the specific product being marketed.

The Technical Side

Both tools share a common analysis engine but differ in their input/output pipelines.

Analysis engine:

NLP-based claim extraction (identifying what constitutes an environmental claim in free text)
Pattern matching against a database of known greenwashing patterns
Regulatory mapping (which EU directives apply to which claim types)
Risk scoring algorithm combining multiple signals

Checker-specific:

Simple REST API for single-claim analysis
Sub-second response time for pre-analyzed patterns
Widget-friendly output for integration into CMS tools

Scanner-specific:

Web crawler with configurable depth and scope
Batch processing pipeline for large sites
PDF report generation with executive summary and detailed findings
Scheduled re-scanning to track compliance improvements over time

Both are built on a PHP/WordPress stack for the frontend (SEO matters in this space) with Python services handling the NLP and analysis workload.

Market Reality

The greenwashing detection market is early. Most companies are still in the awareness phase — they know the Green Claims Directive is coming but have not started compliance work. We expect demand to increase sharply as enforcement deadlines approach.

The interesting dynamic is that this is not just a compliance tool — it is also a competitive intelligence tool. Understanding how your competitors make environmental claims, and where those claims are vulnerable, is valuable strategic information.

Where This Is Heading

As the regulatory framework solidifies, we expect several developments:

Standardized claim formats that make automated verification easier
Integration with supply chain data to verify claims against actual production data
Real-time monitoring as companies update marketing materials
Cross-jurisdiction coverage as other regions follow the EUs lead

The companies that start compliance work now will have a significant advantage. Retrofitting sustainability communications across an entire web presence is much harder than getting it right from the start.

Check your green claims for compliance risk at greenwashing-checker.com. For comprehensive website audits, try greenclaims-scanner.com.

Crypto Comparison Tools: Building Trust Through Transparent Data

SIKOUTRIS — Sat, 14 Mar 2026 16:49:18 +0000

The cryptocurrency space has a trust problem. Not just with the technology itself — most people have moved past the "is Bitcoin real" phase — but with the tools and platforms that surround it. Exchange comparison sites, portfolio trackers, and data aggregators often have opaque methodologies, undisclosed affiliate relationships, and data that does not match what users see on actual exchanges.

Building a crypto comparison platform that people actually trust is harder than it sounds. Here is what we learned building compararcripto.com.

The Problem with Existing Crypto Data

When we started researching the crypto comparison space, we found several systemic issues:

Wash trading inflation. Many exchanges report inflated trading volumes through wash trading — simultaneously buying and selling to create the appearance of liquidity. Some data aggregators display these numbers without correction, making certain exchanges look more active than they actually are.

Stale pricing. Crypto prices move fast. A comparison showing prices that are even 30 seconds old can be misleading, especially during volatile periods. Many sites update prices on long intervals and do not clearly communicate their data freshness.

Hidden affiliate bias. This is the elephant in the room. Most crypto comparison sites earn revenue through affiliate relationships with exchanges. There is nothing inherently wrong with this — it is a legitimate business model. The problem is when affiliate relationships influence rankings without disclosure. When an exchange paying 50% revenue share consistently appears at the top of "best exchanges" lists, users should know why.

Incomplete fee data. Exchange fee structures are notoriously complex. Maker vs. taker fees, tiered pricing based on volume, withdrawal fees that vary by cryptocurrency, hidden spread markups — presenting this accurately in a comparison format is genuinely difficult.

Our Approach: Transparency as a Feature

We decided that transparency itself would be our differentiator. Not faster data or more features — just honesty about what the numbers mean and where they come from.

Data sourcing. We pull data from multiple independent sources and cross-reference them. When sources disagree (which happens regularly), we show the range rather than picking one number. Users can see that Exchange X reports $500M daily volume, but independent estimates suggest $200-300M.

Methodology documentation. Every ranking, score, and comparison on the site has a documented methodology page. How do we calculate trust scores? What factors go into our security ratings? How do we handle exchanges that do not disclose certain data? All of this is public.

Affiliate transparency. If we have an affiliate relationship with an exchange, it is labeled. We maintain a public page listing all our commercial relationships. Our ranking algorithm does not factor in affiliate status — and we explain why users should verify this themselves.

Real-time data where it matters. Prices and basic metrics update in near-real-time via WebSocket connections. Historical data and analytical metrics update daily. We clearly label the timestamp on every data point.

Technical Challenges

Building a reliable crypto data aggregation platform involves several non-obvious challenges.

API Reliability

Crypto exchange APIs are... inconsistent. Some are well-documented and reliable. Others go down during high-volatility periods — exactly when users need data most. Rate limits vary wildly. Some exchanges change their API structure without warning.

Our solution: we maintain connections to every exchange we cover and have fallback data sources for each. When a primary API fails, we switch to backup sources and clearly indicate reduced data freshness to users.

Multi-Currency Complexity

Crypto pricing is not straightforward. Bitcoin/USD on Exchange A and Bitcoin/USD on Exchange B are not the same price. Arbitrage opportunities exist precisely because of these differences. Our comparison needs to show these differences accurately without implying that the "lowest price" is always the best deal (it might be on an illiquid exchange where you cannot actually execute at that price).

We solve this by showing effective prices — accounting for fees, spread, and estimated slippage based on order book depth. This gives users a more realistic picture of what they would actually pay.

Regulatory Landscape

Cryptocurrency regulation varies dramatically by country. An exchange that is fully licensed in one jurisdiction might be banned in another. Comparison data needs to be context-aware — showing a user in France exchanges that are not available in the EU is worse than useless.

We use geolocation (with user consent) to filter results by availability. Each exchange listing includes its regulatory status across major jurisdictions.

The Tech Stack

For those interested in the technical implementation:

Data ingestion layer — Python services connecting to exchange APIs, with queue-based processing for reliability
Database — Supabase (PostgreSQL) for structured data, with time-series extensions for historical pricing
Frontend — PHP-based site optimized for SEO (comparison sites live and die by organic search)
Caching — Cloudflare CDN with intelligent cache invalidation for dynamic data
Monitoring — Custom health checks that verify data freshness and API connectivity across all sources

The architecture prioritizes data reliability over raw speed. We would rather show slightly delayed data that we know is accurate than real-time data that might be wrong.

What Users Actually Want

After launching and iterating based on user feedback, we learned that what users want from a crypto comparison tool is simpler than we initially assumed:

Honest fee comparisons — "If I buy $1,000 of Bitcoin on Exchange X, what will it actually cost me including all fees?"
Security track record — "Has this exchange been hacked? Have users reported withdrawal problems?"
Regulatory status — "Is this exchange legal in my country?"
User experience quality — "Is the platform easy to use for a beginner?"
Customer support — "If something goes wrong, can I reach a human?"

Notice that "lowest fees" is only one factor. Trust, security, and usability matter as much or more to most users — especially those new to crypto.

Lessons for Building Trust in Comparison Platforms

These lessons apply beyond crypto to any comparison or review platform:

Show your work. If you rank things, explain how the ranking works. If you score things, publish the scoring methodology. Users are sophisticated enough to evaluate your methodology — hiding it only breeds suspicion.

Disclose commercial relationships. Every comparison site needs to make money somehow. Being upfront about how you make money actually increases trust rather than decreasing it.

Present data honestly. When data is uncertain, say so. When sources disagree, show the disagreement. Users respect honesty more than false precision.

Update regularly. The crypto space changes fast. An exchange that was excellent six months ago might have new management, different fees, or regulatory problems today. Stale data is misleading data.

Let users verify. Link to primary sources. Let users check your claims independently. The goal is not to be the final word — it is to be a useful starting point for informed decisions.

The Road Ahead

We are working on several improvements: DeFi protocol comparisons (yield farming, lending, DEX aggregation), portfolio tracking with tax estimation, and expanded coverage of crypto derivatives platforms.

The crypto market is maturing, and with that maturity comes higher expectations for the tools surrounding it. Users deserve comparison platforms that treat them as intelligent adults capable of making their own decisions — not as conversion funnels to be optimized.

For transparent, data-driven cryptocurrency comparisons, visit compararcripto.com.