Lexolve by Lawbotics
Legal automation platform
About the client
After working as a business lawyer for almost a decade in some of Norway's top tier law firms, Merete Nygaard was getting increasingly frustrated by the inadequate way legal knowledge was shared between lawyers and their clients, as well as between lawyers themselves. Lexolve's ultimate goal is to make legal work easier for businesses and the people working in them all over the world and is today enabling legal certainty for all.
The challenge
The solution
To make the most of this great concept, we went on a one-week wireframing sprint to get a prototype right from the start. Then we merged creative forces with the product owner to provide a sound business plan and top-notch branding. Then we did the coding bit, got some valuable user feedback, and adjusted the result until everyone was happy — both the users and the product owner!
The dynamic generation of Word documents using JSON templates was challenging.
Results
We designed the site to direct as much attention as possible to the easiness of using the service. With the superior, elegant interface, we could focus on presenting the content in a way that allows a visitor to easily understand every step of the process. Making the site clear-cut was one of our top priorities.
When working on the project we focused on using the most recent technology pieces.
Dynamic generation of Word documents based on schemes in JSON files may sound like a challenge, but our developers had accomplished that with ease. And they had done that while working on the project with some impressive technologies. The Lexolve technology stack is:
- Ruby on Rails
- Angular
- React.js
- PostgreSQL
- Mailchimp API
- Stripe API
- Kubernetes
- Rollbar (error tracking software)
- GitHub (code review)
- Cloudflare (protection)
- CircleCI (integration)
Conversation is one of our most important values and a habit we support at every stage of our development process. Conversation is executed through digital tooling so the context is never lost. We use Slack for chat, Jira for planning, and Github for code reviews and discussion.
Other case studies
