Finance teams deserve a quieter close.
Month-end is the most important week in a finance team’s calendar, and most of it goes to matching numbers that already agree.
We built Tessel to do that part: every line, every day, with the evidence attached. The close becomes what it should have been all along, a review by the people who understand the business.
Tessel proposes. People approve. That order never changes.
Four rules we build by.
Evidence before automation
If Tessel can’t show why, it doesn’t act.
People approve
Thresholds are set by the team, and everything above them waits for a person.
Read-only by default
We never asked for permission to move money, and we never will.
Plain words
Flags speak in sentences a controller would write.
Open roles.
Close specialistCustomers · New York · Full-time
You’d run demos and pilots with finance teams, and turn what you hear into the next set of rules.
Product designerProduct · Remote · Full-time
You’d design the close workspace with the controllers who use it, from the checklist to the approval queue.
Reconciliation engineerEngine · London · Full-time
You’d work on the matching engine, from one-to-many splits to fee schedules, and on the evidence that explains every match it makes.
Senior frontend engineerProduct · Remote, Europe · Full-time
You’d build the ledger, the tables, matches and flags that controllers read all day. React, TypeScript and a lot of care about keyboard paths and figures that line up.