Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How a Rejected Invoice Built a 50M Payment Platform
Transcript
- Lucas: So you know how every once in a while, you hear about a startup that was born from a really specific, almost mundane frustration? Today's story is exactly that. It starts with a rejected invoice. Luna: A rejected invoice. That sounds like the least sexy origin story ever, but I have a feeling there's more to it. Lucas: There is. And before we get into it, I want to mention something. This show has been going for a hundred and fifty episodes now, and it exists because listeners like you chip in a couple of dollars a month — genuinely, that's what keeps it ad-free. If these conversations have moved your work forward in some small way, you can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, it really does make a difference. Every little bit helps keep the lights on here. Lucas: Okay, so back to the invoice. Priya Raman was working as an accounts payable clerk at a mid-sized manufacturing firm back in 2019. She saw hundreds of invoices a week, and one day she spot-checked a rejection that came back from a big client. The reason? A missing digit in the remittance address. The vendor had to wait an extra sixty days to get paid, and they nearly went under. Luna: Sixty days is brutal. So she saw this little typo cause a near-death experience for a small business. Lucas: Exactly. And her first thought was, how many other invoices are getting rejected for similarly dumb reasons? So she pulled the data from her own company: out of three hundred invoices a month, roughly eight percent failed validation on the first try. Eight percent. That's millions of dollars in delayed cash flow across the supply chain. Luna: That's a huge hidden tax on small suppliers. So what did she do? Built a spreadsheet? Lucas: She started with a macro in Excel, actually. It flagged common errors like mismatched purchase order numbers or wrong tax IDs. She shared it with a few vendors she'd gotten friendly with, and within a month, two of them asked if they could pay for it. Luna: That's the moment you realize you're onto something. People never pay for a spreadsheet macro unless it's saving them real money. Lucas: Right. So she quit her job in early 2020, incorporated ClearPay, and started selling a cloud-based version of that validation engine. The pitch was simple: we catch invoice errors before they reach your customer, so you get paid on time. Luna: But wasn't the timing terrible? I mean, early 2020, the pandemic hits, everyone's cutting costs. Lucas: You'd think so, but it actually helped. Because suddenly, cash flow was the number one concern for every small business. ClearPay's tool became a way to de-risk revenue. By mid-2021, they had four hundred paying customers, mostly manufacturers and logistics firms. Luna: Four hundred customers in eighteen months is pretty solid. What was the turning point? Lucas: The turning point was a network effect they didn't plan for. Once a supplier started using ClearPay, their customers — the big buyers — noticed that invoices arrived clean and on time. So the buyers started asking other suppliers to use it too. Luna: Ah, so it's like the buyer becomes the champion. That's a nice dynamic. Lucas: That's what pushed them past the early adopter phase. By early 2022, they had their first million-dollar month in annual recurring revenue. And that's when they raised a Series A — eighteen million dollars from a fintech-focused VC out of Boston. Luna: What did they do with the money? Obviously not just buy more coffee. Lucas: They invested in machine learning to predict which invoices are likely to be rejected, even before they're submitted. So instead of just catching errors, they're preventing them. They also built integrations with QuickBooks, NetSuite, and SAP. Luna: That's smart. You're not asking people to change their workflow; you're plugging into what they already use. Lucas: Exactly. And that integration strategy is a big reason they're now processing over a billion dollars in invoices annually. Luna: A billion dollars. Just from fixing typos. That's wild. But I'm curious — what was the biggest rejection she faced, other than that initial invoice? Lucas: Great question. When she first started pitching to VCs, she got turned down by, I think, twenty-three firms. The feedback was always the same: 'This is a feature, not a company.' Luna: Ouch. That's a classic dismissal. How did she keep going? Lucas: She told me that she kept a screenshot of one particularly condescending rejection email on her phone. She looked at it every time she felt discouraged. But more practically, she doubled down on customer feedback instead of chasing investor validation. Luna: That's the right move. Customers pay you; investors just hope you'll pay them eventually. Lucas: And the funny thing is, after she signed her first ten enterprise customers, the same VCs started calling back. One of them led her Series A. Luna: Ha. So the rejection wasn't about the idea, it was about the stage. They wanted proof she didn't have yet. Lucas: That's the lesson. Rejection often says more about the other person's risk tolerance than about your product. She had to find the right audience. Luna: And now she's got a forty-million-dollar company. What's the biggest challenge she's facing today? Lucas: Two things, really. First, competition — there are bigger players like Bill.com moving into her space. But she's staying ahead by focusing on verticals like logistics and healthcare, where the invoice complexity is higher. Luna: That makes sense. Deep focus beats generic features. Lucas: Second, she's dealing with the classic founder's dilemma: should she keep growing independently or take a buyout offer? She's had two acquisition approaches, both in the five-hundred-million range, but she's turned them down. Luna: Wow. That takes serious conviction. Do you think she made the right call? Lucas: Time will tell. But she's told me she's not done yet. She wants to build ClearPay into the default payment layer for the middle market. And with the network effects she's seeing, I wouldn't bet against her. Luna: So what's the one concrete thing our listeners should take away from this story? Lucas: I'd say this: pay attention to the annoyances in your own work life. Priya didn't invent some deep tech. She just automated a tedious manual check that was causing real financial pain. That's the seed of a forty-million-dollar company. Luna: And it's a reminder that rejection is just data. It tells you what to adjust, not whether to quit. Lucas: Exactly. So next time you get a rejected invoice — or a rejected pitch — ask yourself what it's telling you about your approach, not about your worth. Luna: Well said, Lucas. And on that note, we'll leave you with that thought. Until next time, keep building. Lucas: Thanks for listening, everyone.