WeParse
A stack of policies becomes one click.
- Portfolio company
- UX and UI design, brand, website
- Software & AI
- since 2025
Result
- 80 % less time spent entering a policy
- 800,000 lines of code from first sketch to beta
- 3 founders, one of them from the industry the product is built for
Starting point
An insurance broker types data. Open the policy, find the client, premium, term, line of business, copy it into the next program. The idea for WeParse came to one of us at exactly that desk. The technology exists. The question was whether someone who earns a living with it would trust it.
Strategy
Trust comes from seeing what the machine has read. That is why WeParse never shows only a result, but always document and data side by side. The person checks, the software types. Every view is built so that a check takes seconds, not minutes.
What we built
Workflows in the broker's office
Workflows in the broker's office recorded before the first screen was drawn. What gets typed where, and when.
Components for every view
Type, colours and components as a system, so every new feature looks like the first.
Reading and checking a policy
Reading a policy, client and policy in detail, settings. As usable on a phone as on a desktop.
Brand and website
Name, logo and a website with waiting list, so the product has a face before the beta.
What changed
An idea at a desk became a product with three founders that transfers data from documents into any software. No typing, no copying.
What we take with us
The design system and the structure of the app are set up so that further products can be built on them.
Key facts
- Beta
- since 6 Oct 2026
- Services
- UX and UI design, brand, website
- Sector
- Software & AI
- Period
- since 2025
Price on request