Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / How a Founder Used a 5-Dollar Typo to Save 50K
Transcript
- Lucas: So there's this founder named Jonathan Stark. He runs a small SaaS company called Blossom — project management for creative teams, nothing huge, maybe a couple hundred clients. In 2023, he sends an invoice to a long-term customer for five thousand dollars, which is the correct monthly retainer. But there's a typo. Luna: Oh no. The decimal point. Lucas: Exactly. He types '50,000' instead of '5,000'. So the invoice shows fifty thousand dollars, not five. The client receives it, and instead of paying or questioning it right away, they sit on it for a week. Jonathan notices the payment's late, follows up, and the client replies — I'm paraphrasing — 'We saw the invoice, we assumed it was a mistake, but we wanted to give you a chance to correct it before we said anything.' Luna: Wow. That's a test. The client is basically watching to see if the founder is honest. Lucas: Right. And Jonathan passes. He immediately apologizes, sends a corrected invoice for five thousand, and the client pays within hours. But here's the part that stuck with me. Jonathan told me he almost didn't catch it himself — his accounting software auto-calculates totals, and he'd typed the wrong number into the line item. So the software just multiplied and displayed fifty grand. If the client hadn't flagged it, he might have sent a second invoice with the same error. Luna: So the real mistake wasn't the typo. It was that he had no check in place. Lucas: Bingo. Jonathan now has a rule: he reads every invoice out loud before hitting send. Numbers, decimal places, the whole thing. He says it's the single cheapest quality-control process he's ever implemented. Takes thirty seconds, saves him from looking either incompetent or dishonest. And the client? They renewed for another year. Trust went up, not down. Luna: I love that. Because the natural instinct when you discover an error like that is to panic and cover it up — or blame the software. But he owned it immediately. Lucas: And that's the lesson. A five-dollar typo — or in this case, a forty-five-thousand-dollar typo — can either destroy trust or cement it, depending entirely on how you handle it. Jonathan chose the path that made him look human and honest. And the client rewarded that. Luna: There's actually a study on this. Harvard Business Review ran something in 2020 about how customers value honesty over perfection in service recovery. Something like 70 percent of customers who experienced a mistake that was handled well reported higher loyalty than customers who never experienced a mistake at all. Lucas: That's the service recovery paradox. A mistake handled brilliantly can actually strengthen the relationship. But most founders are so terrified of making errors that they hide them, which is exactly the wrong move. Luna: And Jonathan's example is so concrete. It's not abstract — it's 'read the invoice out loud.' I can do that. I can apply that to my own business today. Lucas: That's the kind of tactical takeaway I love. Let me give you another angle. Jonathan told me he also started sending a confirmation email — after the invoice but before payment is due — that says 'Hey, just checking: the amount on your invoice looks right, yes?' That way, the client has an explicit invite to catch errors. It turns the billing process into a collaborative check. Luna: That's brilliant. It also signals that you're not hiding anything. You're proactively inviting scrutiny, which builds massive trust. Lucas: And it costs nothing. A one-line email. But most founders skip it because they assume the software is right. The thing is, software is only as good as the data you put in. A typo is human. Trust is built in the response to that humanity. Luna: I want to go back to the client's reaction for a second. They waited a week. They didn't pay, they didn't complain, they just watched. What does that tell you about the state of business relationships? Lucas: It tells me that clients are constantly testing you, even if they don't realize it. They want to know if you're the kind of vendor who's honest when no one's watching. And waiting a week is a low-stakes way to find out. If Jonathan had sent a second incorrect invoice, they would have lost a customer. Instead, they gained a loyal one. Luna: So the key is to build systems that catch errors before they reach the client, but also to have a protocol for when they do slip through. Apologize fast, correct fast, and don't make excuses. Lucas: Exactly. And Jonathan's protocol is literally a five-second read-aloud. That's it. You don't need a compliance department. You need a mirror and your own voice. Luna: Okay, so let's talk about the flip side. What if the typo had gone the other way — he billed five thousand but meant fifty thousand? Would the client have said anything? Lucas: Probably not. And that's a darker lesson. Most clients will happily pay an undercharge and never mention it. So if you're the founder, you have to be extra vigilant on the low side too. Because undercharging might feel like a win for the client, but it's a leak in your revenue — and if it becomes a pattern, it's a serious problem. Luna: Right. And it's harder to fix later. 'Hey, I accidentally undercharged you for six months, can you pay the difference?' That's a much harder conversation. Lucas: Exactly. So the read-aloud rule catches both directions. Jonathan says he's caught four or five errors since implementing it — some in his favor, some in the client's. Each time, he corrected it immediately, and each time, the client appreciated the transparency. He estimates it's saved him about fifty thousand dollars in aggregate — either from not overcharging and losing trust, or from not undercharging and losing revenue. Luna: That's a huge return on a thirty-second habit. Lucas: And that's why I wanted to cover this story. It's not about a glamorous pivot or a viral marketing campaign. It's about a small, boring operational detail that can have outsize impact. Most founders focus on product and sales. But the back end — billing, communication, error handling — that's where relationships are truly built or broken. Luna: Speaking of building relationships — and this ties in directly — I want to mention something. We do this show ad-free, and it stays ad-free because a small group of listeners chips in monthly through buy me a coffee dot com slash fexingo. It's not a big ask, but it's what keeps us able to dig into stories like Jonathan's instead of chasing sponsorship dollars. Lucas: Yeah, and we appreciate that more than we say. It lets us stay focused on what's useful for founders. Jonathan's invoice story? That's exactly the kind of practical, real-world detail we can bring you because we don't have to fit ads in. So thank you to everyone who's part of that. Luna: Alright, back to Jonathan. One last thing — he told me that after he fixed the invoice, the client actually referred him to two other businesses. So the typo didn't just preserve trust, it generated new leads. Lucas: The service recovery paradox in action. A five-dollar typo — well, a five-thousand-dollar typo — turned into a growth engine. Because the client told other people, 'This founder is honest. When he made a mistake, he owned it immediately.' That's a marketing message money can't buy. Luna: So the lesson for founders: Don't fear mistakes. Fear how you handle them. Build a cheap system to catch them, and when they slip through, respond with speed and honesty. Lucas: And read your invoices out loud. It might be the most profitable habit you start this week.