2025 · Website development

LexPro

LexPro is the Slovene HR and employment-law consultancy site that Niro Digital built for LexPro of Maribor in 2025, with a service catalogue, an AI legal assistant and an automated blog.

Client: LexPro
Industry: HR and labour-law consulting
Year: 2025
What we did: Website development

Visit lexpro.si

The constraint

LexPro is a two-person HR and labour-law consultancy in Maribor selling to Slovenian employers. Two consultants cannot answer every first question an employer has about contracts, notice periods or leave, and most of those questions never turn into a paid engagement anyway. So the site does the first pass. The service catalogue is written out in full, each service on its own page from one data file. "AI Pravnik" answers general employment-law questions in a streamed chat, calling tools over the firm's own services, articles and team, closing every answer with a disclaimer, and handing the visitor to a lead form after a set number of free questions. A durable pipeline researches official legal sources and publishes to the blog on a schedule. It runs on Next.js and Vercel, with the AI routed through a gateway so one unavailable model does not take the assistant down.

50+

organisations served, LexPro's own figure

15+

years of labour-law practice, LexPro's own figure

*Figures from the project's own accounts and dashboards at the time of writing.

The system

//01An editorial Slovene site for a two-person HR and labour-law consultancy

LexPro service catalogue — employment documentation, hiring, payroll and labour-inspection advice

//02A written service catalogue, each service rendered from one data file

AI Pravnik landing page — try the assistant, or read its limitations

//03The assistant sold as experimental, with its limitations one click away

AI Pravnik answering a question about Slovenian annual-leave entitlement, with the free-question counter visible

//04Free questions counted down, then the chat hands over to a form
//05Every answer closes with an informational disclaimer, and feedback controls

//06A blog kept current by a scheduled, durable publishing pipeline

//07An about page naming the two consultants behind the practice

//08A plain contact form, the page the assistant hands visitors to

//09Mobile layout with the assistant one tap away on every screen

What changed

//01Employers get a first answer on the site instead of waiting for a callback
//02The assistant reads the firm's own services and articles, so answers point back at LexPro
//03The free-question gate turns a chat session into a named lead for two consultants
//04The blog stays current without either consultant writing an article

What we'd do differently

The assistant is deliberately limited: it answers general Slovenian employment-law questions and says so, because a legal consultancy cannot ship a chatbot that sounds like advice. Routing it through a gateway with a fallback chain was a response to real downtime, not a design flourish. What we would do differently: we set the free-question limit generously at launch and it almost never fired, so the gate did nothing for months until we measured it and lowered it. That number should have been chosen from the first week's sessions, not guessed.

All projects