About Gravitiy
Built by operators who ran the same close process.
We came from financial operations and enterprise data infrastructure. We started with the reconciliation problem because we spent years doing it manually.
The close used to be the worst week of our month
Before Gravitiy, our team spent the first two weeks of every month reconciling the prior month's transactions. We had spreadsheets for the spreadsheets, and the close was always a scramble.
We tried building internal tooling twice. Both times it worked for three months and then the data model changed and the tool stopped working. The third time, we decided to build the thing properly.
Gravitiy launched in early 2025 to a small group of design partners. Every feature we have built started from a real problem in a real finance team's close process. We are still in early access because we want to keep building that way.
If you are a controller or finance operator at a growing company, we are probably building for your problem right now. Apply for early access and tell us what your close looks like.
The team
Three people who have run finance-ops before
Riley Finch
CEO & Co-Founder
Spent years building transaction processing systems at payments and B2B SaaS companies. When running close cycles on those same systems, he saw how much of the work was matching transactions that a computer should be matching. He co-founded Gravitiy to rebuild that process from scratch.
Nadia Osei
Head of Finance and Product
Spent the early part of her career in controllership roles at companies going through rapid transaction volume growth. She joined Gravitiy to own the product roadmap and still personally onboards every design partner through their first month-end close.
Alex Moreau
Head of Engineering
Spent his early career building financial data pipelines at companies where transaction volumes made batch-job architectures untenable. Designed Gravitiy's matching engine and the real-time sync layer that keeps reconciliation state current without nightly jobs.
What we believe
How we build
Operators first
Every feature we ship has to solve a problem we have seen in a real close process. We do not build for the demo. We build for the controller at 9pm on the 3rd.
Trust is earned by accuracy
A reconciliation system that is wrong some of the time is worse than a slow manual process. We prioritize precision over coverage and flag uncertainty rather than hide it.
Small teams, serious problems
The finance team at a 100-person company has the same reconciliation volume as a 1,000-person company from five years ago. We build tools that give a team of two the infrastructure of a team of ten.
Work with us
We are hiring one senior engineer and one account lead
Both roles are hands-on. If you have run finance-ops or built data integration systems, we want to talk.
Get in touch