LIZAR Systems designs, manufactures and assembles identity document issuance systems in Europe, with headquarters in Lisbon and production in Pombal. Its customers are ministries, mints, civil registries, security printers, banks and fintechs. These buyers read the spec sheet before they read any marketing copy.
The old website did not reflect that. LIZAR had grown from one flagship machine into an ecosystem of hardware, software and AI modules. The website still presented it as a hardware supplier.
In September 2026 we launched the new platform in five languages. This article explains the decisions we made and what any B2B company with a technical product can apply to its own website.
What was wrong with the old website?
LIZAR’s brief was direct: a website that explains a complex product family without oversimplifying it, serves as a reference throughout a procurement process and turns anonymous visits into qualified technical conversations. Three problems stood in the way.
- The portfolio had outgrown the story. DRACO, VARAN and SMAUG handle card personalisation, passport personalisation and portable power for mobile issuance. Around them sit software modules for machine control, fleet management, AI quality control, chip encoding, immutable logging and field verification. Presented as a list, it looked like complexity.
- Technical information was locked inside sales conversations. Every question needed a person on the other side. That slowed early evaluation and put off buyers who prefer to research before talking to anyone.
- Incoming enquiries said very little. A name, an email and one sentence do not tell a sales engineer the volume, the document type or the deadline. Every lead started from zero.
How do you structure a B2B website for technical buyers?
The structural decision was to present document issuance as a complete chain instead of a catalogue.
What does the AI assistant do and not do?
The assistant, built on the Claude API, replaces the contact form. It answers from the platform’s own product documentation, so it handles specification questions without improvising. A visitor can ask whether a machine works with polycarbonate or how chip encoding fits into an existing PKI.
After answering, the assistant steers the conversation towards the parameters a sales engineer needs. An eight-field form asking for the same information would be abandoned. A conversation that gives something back with every answer is not.
| The assistant | Does | Does not |
|---|---|---|
| Specifications | Answers from published documentation | Speculate beyond what the documentation says |
| Commercial | Collects volume, deadline, geography and context | Quote prices or commit to delivery dates |
| Compliance | States the published certifications | Suggest certifications the company does not hold |
| Out of scope | Says it does not know and offers a demo | Invent an answer to keep the conversation going |
At the end of each qualified conversation, the extracted parameters, a summary and the full transcript go to LIZAR’s back office as a structured package, through an authenticated webhook. Nobody retypes anything. A ministry assessing a national programme and a student researching laser engraving are separated before anyone spends time on either.
Why do five languages need a single source of truth?
With teams in Europe, Latin America and Africa, language parity was an operational requirement. The known risk of a multilingual website is drift: a specification updated in one language and forgotten in the others.
The content model was built so that each specification lives in one place and appears on every page and in every language where it is used. When a machine’s capacity or a certification status changes, it changes once. In a public procurement process, a published figure that no longer matches the machine becomes a serious problem long before anyone notices it. The assistant replies in the language the visitor writes in.
What results did the new platform deliver?
The most visible change is in what reaches the sales team. Qualified leads rose by around 70 per cent. Qualification now happens before a person steps in. A conversation that ends at two in the morning in Bogotá is already structured in the back office when the Lisbon team starts work.
Filipe Castro, CEO of LIZAR Systems, describes the change from the sales team’s side. Before, every enquiry from the website had to be qualified by hand. Today leads arrive more complete and better qualified, with no extra work for the team. Follow-up also starts sooner.
There is a second, less obvious gain. The conversation logs show what buyers actually ask. Three patterns emerged in the first weeks.
None of this would have surfaced through a form. The logs now shape LIZAR’s content plan.
What can you apply to your own B2B website?
- Publish specifications as data. The same fields, in the same order, for every product. Technical buyers compare line by line.
- Organise by use context as well as by product. A bank and a ministry arrive with different problems. Give each one a way in.
- Replace the form only if the conversation knows what it is talking about. An assistant without grounding documentation invents. Connect it to published content and nothing else.
- Set boundaries before you set the tone. Prices, deadlines and certifications are the answers an assistant must never improvise.
- Read the conversations. Repeated questions show where the documentation falls short. It is the best content plan there is.
What makes this kind of project different from a corporate website?
A corporate website presents the company. A website for technical buyers has to work as reference documentation through months of evaluation. That changes how the project is planned.
| Aspect | Corporate website | Website for technical buyers |
|---|---|---|
| Content | Presentation copy written once | Structured specifications, kept as data and updated with the product |
| Validation | Marketing sign-off | Technical review of every published figure, because one error can exclude the company from a tender |
| Languages | Translation at the end of the project | A multilingual model from the start, with one source for each specification |
| Contact | Generic form | Structured qualification, connected to the sales team’s back office |
| Success | Visits and time on page | Qualified leads and technical conversations that move forward |
Which metrics should you track after launch?
On a B2B website with an assistant, the usual traffic metrics say little. These say more about whether the website is doing its job.
These metrics only exist because the conversation is structured. A form would never provide them. Reviewing them monthly with sales and product turns the website into a source of market insight, not just a channel.
Which materials should you gather before starting?
A website for technical buyers depends on information that is usually scattered across the company. Gathering it before the project saves weeks of back and forth.