Bz Info · technical partner
Website, chatbot and technical platform for Luchtreiniger Pro Horeca.
This page explains compactly what technically sits behind the platform: not as decoration, but as proof that the public website, backend, admin, data, chat, AI assistance, SEO and production environment form one workable system.
Have an idea, a project or a business goal? I can help turn it into a real digital product: structured, usable, measurable and ready to generate value — not just a nice interface, but a platform that can grow with your activity.
The approach follows the Bz Info logic: understand the product first, define system boundaries, make backend and data reliable, keep interfaces usable, connect communication to real follow-up and prepare the foundation for maintenance and growth.
Technical transparency
A professional website must also be technically operable.
For a B2B company like Luchtreiniger Pro Horeca, a website is not an isolated page. It is an acquisition channel, a trust layer, an information source, a contact point, a quote system, a communication channel and an internal follow-up tool. That is why the technical foundation must not only look good, but remain understandable, indexable, maintainable and transferable.
System overview
Six layers that together form one platform.
Public website, SEO and acquisition
Luchtreiniger Pro Horeca uses a public website that goes beyond a classic showcase. Pages are built around services, sectors, local intent, quote requests, proof and trust. The goal is for a hospitality business owner to quickly understand what is cleaned, why it matters and how to make contact without friction.
The technical layer supports multilingual routes, metadata, sitemap, JSON-LD, internal links, conversion blocks and content pages for extraction hood cleaning, grease duct cleaning, fire safety, certificate, inspection, photo proof, knowledge base and sectors.
- Next.js NL/EN routes
- SEO metadata and JSON-LD
- Service, sector and knowledge pages
- Quote and contact flows
Backend API, data and business rules
Behind the visible website there is a backend that structures forms, conversations, leads, reviews, prospects, admin actions and technical events. The backend is the layer where data is validated, payloads remain controlled and business logic does not disappear into isolated frontend components.
This approach makes the platform more maintainable: forms remain predictable, admin flows can grow, chat and notifications can be connected to real records and future features do not have to start again from scratch.
- NestJS API structure
- DTO validation
- Prisma and PostgreSQL
- Controlled business records
Back office, follow-up and daily operations
A business does not only need visitors; it needs visibility. The admin environment helps track contact requests, quote requests, chat conversations, prospects, reviews and campaigns. This turns the platform into an operating system instead of only a presentation page.
The goal is for an administrator to see what came in, what was handled, which conversations need attention and which commercial signals can be reused later.
- Admin dashboard
- Requests and conversations
- Prospect follow-up
- Operational visibility
Realtime chat, AI and human handoff
The chat is part of the product architecture. Visitors can ask questions, the chatbot can help with first information and an administrator can take over when human follow-up is needed. This prevents communication from being disconnected from the platform.
Realtime events, visitor sessions, admin alerts and AI assistance remain technically separated from sensitive configuration. The public experience remains useful without exposing backend logic or secrets.
- Public chat widget
- WebSocket events
- AI-assisted first answers
- Human handoff
Mobile follow-up and extensible product foundation
Not all follow-up happens behind a desktop dashboard. The platform is prepared for mobile admin flows, notifications and quick actions. This makes it possible to connect a future mobile workflow to the same backend, data and rules.
The mobile layer is therefore not a second isolated product, but a future extension of the same product foundation: visitors, requests, conversations, prospects and administration remain connected.
- Mobile admin workflow
- Notifications
- Shared backend logic
- Future field operations
Quality, security, production and transferability
The technical value is also in what visitors do not see: safe configuration, separated frontend/backend settings, type checking, build checks, Docker/VPS production environment, documentation, technical SEO and maintainable modules.
A professional platform must remain understandable for the next developer, visible to Google, usable for the business and extensible without chaotic rewrites.
- Typecheck and build
- Docker/VPS production
- Security boundaries
- Documentation and maintainability
Applied to this project
From hospitality service to digital acquisition and follow-up system.
The public layer helps business owners search through concrete intent: extraction hood cleaning, grease duct cleaning, air duct cleaning, ventilation cleaning, fire safety, inspection, certificate, photo proof, costs, maintenance plan and sector-focused pages. This content is not random; it supports trust, SEO and conversion.
The internal layer helps prevent requests, conversations, prospects and follow-up from being lost. The technical choice is therefore not only visual: frontend, backend, database, admin and realtime communication must form one operable system.
Technical map
The responsibilities behind the platform.
Frontend and public experience
The visible layer where visitors build trust and are guided toward contact or quote requests.
Backend and data
The backbone for forms, records, validation, admin logic and extensible product rules.
Communication and operations
The layer that makes chat, prospects, notifications, campaigns and human follow-up usable.
Production and quality
The technical discipline that keeps the platform understandable, controlled and transferable.
Engineering proof
The value is in structure, not in huge titles or decorative blocks.
A professional product must be built, measured, indexed and transferable. The technical foundation must support the commercial flow without making the codebase unreadable.
Website, backend, admin, chat and data remain connected around the same business flow.
Public experience, admin features and backend configuration are not mixed together.
Structure, documentation and typed code help keep the platform understandable later.
Bz Info
Explore the technical partner behind this platform.
Portfolio, method, projects, stack, tech lab, experience and technical positioning of Bz Info.