A small team that got tired of retyping invoices.
Tessera began in 2023, when two people who had run document operations at different companies realised they had built the same spreadsheet of exceptions twice.
Why a tessera?
A tessera is one small tile in a mosaic. Alone it says little. Placed carefully among others, it makes a picture. Documents work the same way: a supplier name, a date, a clause. Each piece is easy to read and easy to get wrong, and the value is in how they fit.
We build the part of the pipeline where a field is read, doubted and either trusted or sent to a person. Everything else, the ledger, the claims system, the contract repository, already exists and works. Our job is to hand it clean, checked data, and to be honest about the cases where we could not.
We are thirty-one people in Larkfield and a few time zones beyond. We are not trying to replace the person at the end of the queue. We are trying to make sure they only see the work that needs them.
How we work
- 01
Say what we do not know.
A product that hides its doubt is a product you cannot trust. We show scores, reasons and the page the answer came from.
- 02
People stay accountable.
Tessera proposes and routes. Decisions with money, coverage or legal weight stay with named people, and the record shows who.
- 03
Boring is a feature.
Idempotent endpoints, retried webhooks, calm dashboards. We would rather you forget we are there.
The people
-
Inès Varga
Co-founder, CEO
Spent nine years in accounts payable operations before writing the first Tessera prototype on a spare weekend.
-
Tomas Reiner
Co-founder, CTO
Built document pipelines for a logistics company. Owns the extraction runtime and the confidence model.
-
Amara Okafor
Head of Product
Designed the review lane. Believes the best interface is the one a tired reviewer can use at 5 pm.
-
Jun Takeda
Staff Engineer, Platform
Routing engine, webhooks and the audit log. Allergic to silent failures.
-
Lucía Brandt
Head of Security
Writes the controls, runs the exercises, answers the questionnaires so customers do not have to wait.
-
Oskar Lindqvist
Customer Engineer
Gets new document types from first sample to production routing, usually within two weeks.
Open roles
We hire slowly and write the job down before we post it. Salary ranges are in every listing, and the interview is a paid half day on a real problem.
- Apply by email
Senior Backend Engineer, Extraction Runtime
Own the queueing, retries and scoring path that every document passes through.
- Apply by email
Product Designer, Review Experience
Shape the review lane and the tools reviewers use for hours a day. Dense, calm, fast.
- Apply by email
Customer Engineer
Take new customers from sample documents to a routed production workflow.
- Apply by email
Security Engineer
Harden key management, tenant isolation and the evidence behind every control we publish.