About Avelin

We read what arrives

Avelin started in a finance team that spent two days a month retyping invoices. It now reads intake for logistics, healthcare, legal and research teams.

About
A shared work table with blue chairs, monitors and clear desk screens in a bright office.

How it started

Our founders worked in the finance team of a property company. Every month they copied around nine hundred invoices into the accounting system by hand, then spent another day finding the mistakes. The first version of Avelin did one thing: it read an invoice, marked where each value came from and asked a person about anything it was unsure of.

Where we are now

Twenty-two people in two offices. Avelin reads about four million documents a month for teams in logistics, healthcare, legal services, housing and research. We are funded by our customers.

Working with us

We publish every release in the changelog and answer support questions from the same team that builds the product. If you want to talk about a role, write to hello@avelin.example.com.

About Avelin
  1. Every value has a source

    If a person cannot see where a value came from in one click, we have not finished the feature.

  2. People decide, rules check

    Software should do the arithmetic and the comparisons. Judgement belongs to the people who know the work.

  3. One input at a time

    We would rather a team sends one kind of input well than five kinds badly.

  4. Plain pricing

    Plans are priced by the document, with the allowance and the extra rate written on the pricing page.