DualEntry

Get the latest jobs and industry news

It was incentivized dysfunction. Santiago Nestares believes that ERP vendors make the software hard to implement because it drives more revenue and billable hours for implementation partners. It was incentivized dysfunction, in his words. Santiago joins Glenn Hopper and me for another fascinating episode of Future Finance where he sahres why he started Dual Entry. At his previous company, Benito, Santiago scaled to $100M+ in revenue and watched his finance team grow to 12 people. Half of them? Doing repetitive work every single month—categorizing credit card transactions, processing invoices, copying old journal entries into ChatGPT to adjust allocations. That's when it clicked: "Why is this not already part of the software from the very beginning?" So he built DualEntry, which just announced a $90M Series A from Lightspeed, Khosla Ventures, and GV. He says they "broke all the rules of entrepreneurship" by starting with mid-market companies instead of SMBs. Why? Because that's where the real pain lives—multi-entity structures, audit requirements, and systems that feel 25 years old because they are. He shared the following analogy to explain how most people think about their ERP: ERPs are like chronic back pain. Everyone knows they have it, want to fix it, but fear the "surgery" (implementation) will be worse than the disease. DualEntry aims to make it feel like a massage instead. If you're evaluating systems, Santiago's advice is simple: insist on using the product yourself. If they won't let you click around freely during the demo, walk away. Listen to the full episode here to see how DualEntry things about the ERP space: https://lnkd.in/gdraaECB 🎓 Check out our sponsor QFlow.ai at https://lnkd.in/g2Vyc5J7 - GTM Finance CoPilot 🧔 Follow Co-Host and AI expert Glenn Hopper 📺 Check out the podcast on our YouTube Channel at https://lnkd.in/gaudpc_G

Running a $140M company with a single finance person sounds impossible, until you’re using DualEntry. Automation, workflows, and controls built to scale without adding headcount.

Graphite.io inherited a legacy ERP filled with manual steps, confusing rules, and workflows that slowed everyone down. They were ready for a change: something cleaner, clearer, and actually built for how teams work today.

Slash needed an ERP that could keep up with real transaction volume — not just the occasional batch here and there. Traditional tools weren’t built for the pace they operate at. With DualEntry, they finally have a platform designed for modern, high-activity finance teams.