Internal Briefing · For Raffaello · Apr 17, 2026

Eurocomponents

New warm lead via Canta. 3 decisions for Friday. Follow-up call Monday Apr 20 PM.
Revenue 2024
€18M
Employees
39
Quotes / year
~150
Per quote
€M-scale
Recent loss
€6.5M
Budget anchor
€3–15K

1 The Warm Path (Why This Is Different)

Maurizio "Canta" Cantaboni is a senior consultant, not an employee. He works with Gianluca Zanoni (GM and owner) as external advisor. Known each other ~10 years. He is a close personal friend of mine.

He is the decision shaper. Zanoni signs. Trust level is extreme:

"se gli dico investiamo, investiamo"Canta on his relationship with Zanoni

He has been pushing AI and software automation to Zanoni for months. Already took 2 or 3 vendor calls with no one. "Non ho avuto un gran feeling con nessuno." We are near the front of the line by default.

He also manages a second external client, separate, flagged for a later play.

2 Company State (Urgent Context)

  • Eurocomponents SpA, Bedizzole (BS). Prefabricated bathroom pods since 1978. 60,000+ pods delivered across 20+ countries.
  • €18M revenue, 39 employees. Grew from €10M to €18M in recent years, rebuilt by Zanoni after losing the majority years ago.
  • Just lost a €6.5M project. Buyer pulled out after agreement signed. Production has been empty for 4 to 5 months.
  • Currently on cassa integrazione, 2 days per week reduced hours.
  • Zanoni quote: "le persone che li han lì non possiamo fare affidamento su quelle persone." He knows he cannot rely on current staff.
Read: this is a buying moment, not a research moment. Pain is acute. Budget will move if ROI is clear.

3 The Problem (Not Aronlight-Style)

  • 150 quotes per year (not per month). Low volume, very high value per quote. Each quote is a full project (hotel, hospital, residence, dorm) = 100 to 300 bathroom pods per project = €M-scale per offer.
  • Turnaround: 2 weeks standard (clients ask for 3 days, reality is 2 weeks). Time to prepare the "descrittivo" alone: 10 min simple to 4+ hours complex.
  • Inputs are chaos. Descriptive specs, CAD, email text, Excel, PDFs, JPEGs. Languages: Italian, German, French, English, Swedish, Norwegian. Often the bathroom info has to be dug out of general building capitolati (plumbing, electrical, structural plans), not bathroom-specific files.
  • They do not work from a catalog. Every bathroom is custom designed per project. This is the key architectural difference from Aronlight.
"Noi non lavoriamo a catalogo. È un prodotto creato su misura per il cliente."Canta, on why catalog-matching does not apply
"Se già solo la prima parte di analisi estrapolasse tutte le informazioni che servono a me e me le mettesse in un elenco fatto bene varrebbe già un sacco per me."Canta, de-prioritizing end-to-end in favor of Phase 1 extraction

4 MVP I Propose for Monday

Phase 1 only. No end-to-end. No catalog matching.

Scope: messy multi-format / multi-language input bundles go in, a clean standardized "descrittivo" per bathroom typology comes out. The preventivista takes the output and adds pricing manually (for now).

Architecture: LLM + rules + human-in-loop. Same pattern shape as Aronlight v6 (inputs to structured output with human review), different engine below (extraction and standardization, not SKU matching). We reference Aronlight as proof we have shipped this pattern, not as the template.

The one-line Monday pitch: turn 4 hours of manual descrittivo prep into minutes. Everything else (pricing, compliance, archive retrieval) waits for Phase 2+.

Why this: Canta explicitly de-prioritized email parsing and end-to-end auto-quoting. He wants the first block of the problem solved well. If we try to pitch the full stack Monday, we lose him.

5 Budget Math

  • Canta's comfort range: €3K to €15K implementation + usage-based ("pago per uso" / per proposal generated).
  • Zanoni's anchor: a back-office person costs ~€30K/yr. He is willing to spend €15K impl + €10K/yr maintenance if it replaces human effort. Not willing to pay €30K/yr just to keep the human.
  • Competitor: €200K to get started was rejected outright.
  • Our Aronlight v6 shape maps directly: low implementation + per-transaction. Different unit (descrittivo generated vs RFQ processed), same model.

6 Three Decisions I Need Friday

Decision 1 · Scope boundary
How tight is Phase 1?
My take: scope Phase 1 as pure extraction: inputs in, clean descrittivo out, nothing else. Keep feasibility analysis (phase before extraction) and pricing layer (phase after) explicitly as Phase 2. Risk if we widen: Canta said no to end-to-end, we lose trust.
Decision 2 · Pricing split
How do we split impl fee vs usage fee?
My take: €4–5K implementation (middle of Canta's range, leaves room to negotiate up or down), then per-descrittivo generated. Exact unit rate depends on the real work per descrittivo, which we can model against the 10 min – 4hr range. Need your gut check on the ratio: do we lean lower impl + higher usage, or the opposite?
Decision 3 · Demo posture
Do we show a live extraction demo Monday, or just architecture?
My take: no live demo Monday. We do not have sample RFQ inputs yet (Canta will send some). Show the Aronlight v6 pattern as proof, walk the architecture, and offer a paid pilot (small fee for first 5 descrittivi generated on their real inputs). Low-friction first yes.

7 Timeline

Fri Apr 18
You and me align on the 3 decisions above. ~30 min call.
Sun Apr 19
I finalize MVP scope one-pager + pricing proposal based on our Friday alignment.
Mon Apr 20 PM
Follow-up call with Canta. I present scope + pricing. Acknowledge "no catalog" explicitly as his insight.
Week of Apr 20
Canta sends sample RFQ inputs by email (from his external-client access, may be limited). We prototype extraction against real data.
Parallel
I introduce Canta to Manel (Aronlight). Canta wants lighting quotes for Eurocomponents pods. Warm loop both ways.

8 Monday Posture (For Reference)

  • Do NOT pitch end-to-end.
  • Do NOT reuse the Aronlight A2 slide deck as-is. The catalog-matching framing does not apply here.
  • Lead with business model: low impl (€3–5K) + usage fee per descrittivo generated. Same shape as Aronlight v6, different unit.
  • Reference Aronlight as pattern proof (email-to-structured-output + human-in-loop), not as direct template.
  • Acknowledge "no catalog" explicitly as Canta's insight. Shows we heard him.
"all'inizio sembra complesso ma se ci ragioni bene è solo una questione di far lavorare bene l'intelligenza."Canta's closing line. He wants a thoughtful system, not a magic AI demo.