Hi,
I build production n8n workflows, AI integrations, telephony and automation systems.
Your requirement of exact catalog matching instead of LLM guessing is exactly how I would approach this problem.
I would implement a deterministic catalog lookup layer before quote generation, ensuring that only verified references and prices are used.
I’m open to building a small paid proof of concept and discussing the architecture before investing in a full prototype.
Regards,
Timur
Hi , I saw your AI automation/agent requirement. I build [n8n/Make/AI agents] with [OpenAI/Claude/Gemini], APIs and CRM integrations. I can start with a small paid milestone and deliver within time.. Are you availble for a short call
Built a working prototype against your exact spec before replying —
because “no prototype = no conversation” is the right filter.
End-to-end run today (screenshots + sample PDF attached):
About n8n: the prototype proves the core logic (extraction, strict
matching, pricing math) as a standalone script so you can see it
without infrastructure. In production it wraps into n8n: Webhook
(request in) → Claude node (extraction) → Code node (strict matcher)
→ PDF generation → Email/CRM node.
For production pricing I’d propose pulling live catalogs via the
industry channel your suppliers already publish to: Sanitas Troesch
and Nussbaum are IGH members (DataExpert® / DATANORM feeds), so the
agent quotes from your real net prices, not scraped data.
Background: 20+ years in ERP and cost estimation — I run a
building-services contracting company myself, so quoting against
supplier catalogs without inventing prices is literally my day job.
Fastest way to verify: send me ONE of your real intervention requests —
I’ll return a finished PDF devis within the hour. I work async and
document everything in writing (English or French — both fine), which
for a long-term build means you always have specs and decisions on
record. Also reached out on WhatsApp.
Bonjour Ali,
Je viens de voir ton annonce pour la création de l’agent de chiffrage HVAC/Plomberie. Étant parfaitement francophone et spécialisé dans la création d’automatisations complexes sur n8n, ce projet correspond exactement à ce que je construis au quotidien.
J’ai l’habitude de concevoir des workflows qui intègrent des agents IA capables de traiter de la donnée métier brute et de générer des documents PDF formatés. Le fait de devoir croiser des références exactes (catalogue Meier Tobler, Sanitas, etc.) sans aucune hallucination est un défi que je gère en ajustant strictement les paramètres des LLM et en structurant les données en amont.
Serait-il possible de s’organiser un appel rapide de 10 minutes pour discuter du périmètre de ton prototype et de la logique de calcul de tes marges ?
AD-1 — your exact-match/no-invented-price constraint is the part worth proving, so I built a small RomeoApps-owned test surface rather than sending a generic n8n portfolio:
It takes short French input, prices only matched synthetic catalog rows, leaves unknown lines unpriced, and applies the 15% margin / 95 CHF labour / 45 CHF travel / 8.1% VAT math only after the match. The rows and prices are fictional; the point is the fail-closed behavior and visible price provenance.
If that control path matches what you need, send the catalog format plus 5–10 anonymized requests and required quote fields. I’ll reply in writing with the smallest paid pilot, acceptance checks and open risks.
The non-negotiable in your post is the whole project, so let me answer that first.
Exact catalog matching is not something you ask a language model to respect. It breaks the moment a reference is close but not identical. The way I would build it, the model never chooses a reference: it only reads the French request and extracts intent, quantities and attributes. The lookup against Getaz Miauton, Sanitas Troesch and Nussbaum is a deterministic search over your own catalog data, keyed on the supplier reference. No exact hit means the line comes back flagged as missing, with the closest candidates shown for a human to confirm. The model writes sentences, never prices.
I learned this the expensive way. An agent I run in production once offered a discount that did not exist, because the price list lived in the prompt. Now prices live in a database and a validation node builds every figure before the model ever sees it.
The 15% margin, the 95 CHF/h labour, the 45 CHF travel and the 8.1% VAT belong in that same place, configuration rather than prompt, so you can change a rate without anyone touching a workflow.
On the prototype: tell me which of the three suppliers to start with, and send me a sample of that catalog (even 30 lines) plus two or three real requests in French. I will send back something you can run yourself, a French request in and a PDF quote out, with exact references matched and missing items flagged instead of invented. That is the part worth testing, and everything else depends on it.
Where I am honest with you: I work in English, Portuguese and Spanish, not French. The model handles French input fine, but I cannot judge whether the technical wording of a quote reads right to a Swiss plumber, so someone on your side should sign off on that. And I have never worked with these three catalogs before.
Background: 31 n8n workflows in production, self-hosted, Postgres for state, plus a watchdog workflow that checks the others every 15 minutes and alerts before the client notices anything.
Hi AD-1, the exact-catalog requirement is the important part here. I would keep the LLM limited to parsing the French request into structured line items. Supplier catalog lookup, price retrieval, margin, labor, travel, and VAT would remain deterministic. Any unmatched item would be flagged for review and excluded from the quote rather than guessed.
I would start with a small paid prototype using a sanitized catalog slice and five to ten sample requests, including PDF output and an explicit unmatched-item case. I do not speak French and I would not claim an existing production prototype, so I want to be clear about that.
If written English collaboration and a small paid prototype are acceptable, I can send a first-phase scope.
I built a working prototype for the exact-match and refusal path and sent it to you on WhatsApp.
French request in, controlled supplier validation, ambiguous or unpriced products held for review, deterministic quote calculations, PDF output, and an importable n8n workflow.
The prototype and tests are available here: GitHub - vjurcutiu/ai-hvac-quote-agent: Fail-closed AI quoting prototype with supplier validation, n8n orchestration, deterministic pricing and PDF generation. · GitHub
Hi AD-1 — I’m Jingxiong Xiao, leading Davi Studio, a China-based AI-native delivery team. Your exact-match constraint is the right design: parse the French request, match only against catalog references, flag missing items, then calculate margin/labor/travel/VAT and generate the PDF.
We can build a small paid proof against one catalog slice and 5–10 anonymized requests for US$200–300, with tests and handoff notes. For transparency, our public examples are self-initiated products, not paid client work, and we do not claim existing French-speaking client delivery. Is an English-language async team from China acceptable? If yes, which supplier source will you provide first (CSV, PDF, or API)?
Portfolio: https://studio.aibro.vip/
Hi, I’m interested in this opportunity.
I work with n8n and have built workflows involving lead processing, Gmail, Google Sheets, Calendar and routing logic.
Are you still looking for someone? If so, I’d be happy to hear what the first workflow you need built is.
The exact-catalog constraint is the right one. I’d make the prototype pass a small acceptance pack before discussing the full build: 20 French intervention requests, expected supplier SKU/reference, expected missing-item flag, and quote totals with margin/labor/travel/VAT shown separately. Unknown or ambiguous products should route to human approval rather than the LLM choosing a “close” item.
I build bounded agent workflows with approval gates and evidence receipts. I can deliver that first testable slice for CHF 750 fixed: one supplier catalog, one quote template, the acceptance pack, and a short failure report. If it passes, we scope the remaining catalogs and production hardening separately. If that matches how you want to select, send one sample catalog export plus 3 representative requests and I’ll confirm scope before any payment.
