Nederland.ai — Advice Tools
A suite of AI advice tools backed by a Flask service, FAISS vector search, and the ChatGPT API — embedded directly into the Nederland.ai website.
The challenge
What needed solving
Nederland.ai needed conversational advice tools embedded directly into their public website — not a generic chatbot widget, but domain-specific tools that answer questions grounded in their own content. The constraints were tight: cheap to run, fast first-response, and able to cite the source documents behind every answer instead of hallucinating.
The team had tried wiring up ChatGPT's API directly to a static system prompt and quickly hit the predictable failure modes — hallucinations on questions outside the training data, no ability to cite sources, no domain grounding. They needed a retrieval-augmented setup but didn't want to manage a full vector database.
The build
How we built it
We built a Python service on Flask that sits between the website and OpenAI. The website hits our endpoint; we resolve the question against a FAISS index built from Nederland.ai's source documents; we hand the relevant chunks plus the user's question to the ChatGPT API as a single retrieval-augmented prompt; we return the answer with source citations.
FAISS keeps the vector search in-memory and fast — no Postgres extension, no managed vector DB, no per-query fees. The index rebuilds on a schedule when source documents change. The Flask layer handles rate-limiting, prompt construction, caching of common questions, and serves a simple JSON API the website embeds via JavaScript.
Deployed as a self-contained Python process on Nederland.ai's existing infra. Total cost is dominated by ChatGPT API calls — the FAISS layer adds essentially nothing.
The result
What shipped
Multiple advice tools now embedded across the Nederland.ai website, each grounded in its own document corpus. Answers cite their sources. First-response time under 2 seconds. The team can add new advice tools by dropping a new document set into the indexer — no engineering work per tool.
Key design choice that paid off: keeping FAISS in-process instead of running a separate vector database. Lower latency, lower cost, simpler deployment, fewer moving parts to break.
Tech stack
What we built it with.
More work
Other projects worth a look.
Hewie — AI Health App
A consumer health app where users describe symptoms in their own words. The AI model runs on its own dedicated service; the mobile app talks to it through a safety-checked API.
Property Grip — Image Recognition for Real Estate
AI image recognition that classifies real estate listing photos automatically — rooms, features, quality. Model runs on its own dedicated service; the web app talks to it over a REST API.
Have a similar project in mind?
Let's build yours.
Send us a description. We'll respond within one business day with a clear next step.
Start the conversation