What is Lexr?

We are a network of law firms with three offices in Switzerland and one office in Berlin. Our main clientele are tech startups, scale-ups and all companies in the tech industry. This includes fintech and the crypto industry where we have a big reputation as a law firm. Lexr Finance is also a financial intermediary for niche financial services.

What were some of the challenges you were facing before using Archbee?

We use Archbee for a public-facing repository of our know-how. This is part of the Lexr standard which we are promoting as a standardized knowledge for our clients and future clients, for any startup that needs information in the jurisdictions where we practice.

With Archbee we found a software solution where we can conveniently fill the data base with our know-how. We can work on it collaboratively, which was an important aspect for choosing Archbee. The easiness of having a good-looking, public-facing website that we can publish on a subdomain was also one of the most important criteria for us. We looked at self-hosted services for example, at names like Notion, but they were mostly for internal knowledge management. We have a tool for that. Some were just too complicated for our everyday users to manage. We chose to use Archbee and from the feedback from our employees and all the collaborators on the page, everybody is satisfied with the capabilities and the way they were able to fill the database. As we speak, we are a few days before the launch of the repository. We are already spreading the news. In the coming month we'll see how our clients and the public will receive it.

Where there any features or functions that you found particularly useful?

I can speak from the role of the internal administrator and to some degree summarize the experience of our collaborators. I've seen them working very swiftly. It's rare that with a software solution I don't get questions or problems with things that are not working. It seems that our collaborators have been able to find their way and navigate through the different options. I think they've used it very elegantly. From my side I think what stands out is the integration into the subdomain, adding the brand assets and making the publishing of the website very easy as the administrator of the project. This was an experience that I enjoyed.

The nice thing about Archbee is that you work directly in the repository. A lot of editing tools are kind of annoying to work with. They're just not intuitive or you're always stuck with some formatting problem and distracted. From the texts that I wrote myself in Archbee I think it is a very convenient experience. You can basically focus on writing with shortcuts that you can use to build this page as you write.

Any advice for other companies considering Archbee?

Building the page has been a good experience and now we're looking forward to see how the public will navigate it. What our marketing team appreciated is that we can also implement the Google tracking script to see how much traffic we will receive on the pages. Don't forget to measure the visit on our pages as well.

‍