The Tuesday started with an investor meeting at 10 a.m., but that wasn't what made it memorable. The call that mattered came the evening before, and it had nothing to do with a pitch deck.
A Lagos customer, one of our biggest in Nigeria, had a payment problem. The bank transfer workflow they used every week had stopped resolving. The money left their account, their supplier's account showed nothing, and the supplier was holding a shipment. Our support team did what support teams do, they escalated it to me. Because by then, the rule was simple: payment issues skip the queue.
The investor meeting was a Series A conversation we'd been chasing for three months. The Lagos customer was a contract worth a fraction of that number. The emails overlapped. The investor's associate wanted a response on a data room question by noon. The customer wanted to know whether to send the payment again, or call a lawyer.
I cancelled the investor meeting. Not dramatically, I just moved it. Tuesday was spent walking through the transfer lifecycle with the customer's finance team, line by line, until we found the specific step where the bank's confirmation message stopped updating. The money was fine. Their accounting system just needed a manual nudge, and someone to tell them it was safe to trust the transfer.
The decision looked wrong on every metric
You can argue the investor meeting was the better use of time. A Series A shapes the next two years. A single customer reconciliation shapes one Tuesday. By every conventional startup metric, I made the worse call.
But there's a historical pattern here worth holding up against your own roadmap. In April 1970, the Apollo 13 crew was three days into a routine mission to the moon when an oxygen tank exploded. The lunar landing was over, the goal became survival, specifically getting three astronauts home on the power and water left in the lunar module. What the crew and mission control actually did, hour by hour, was abandon every plan on the original schedule. They built adapters out of plastic bags and duct tape to fit square carbon dioxide scrubbers into round holes, because the round ones were running out. They cut power to nearly everything aboard to stretch the batteries. Every decision prioritized the immediate, verifiable constraint, the CO2 level, the power draw, the trajectory, over the mission's original objectives.
The Apollo 13 story works as an analogy because the outcome was genuinely in doubt, not because it was tidy. NASA's own post-mission report is unusually blunt about how close it came to not working. Every fix was improvised against a deadline nobody controlled. The crew made it home, but the record shows a team that kept choosing the concrete, solvable problem in front of them over the prestigious one they'd set out to solve.
Cancelling that investor meeting was my duct-tape moment. The roadmap that quarter had a new integration scheduled, an AI feature we'd promised in a sales deck, and a hiring decision. All of it slid. The customer's transfer got fixed and their business kept running, and that was the entire point.
The customer's workflow is your distribution
Here's the part that's easy to miss from the outside. Lagos businesses didn't adopt our product because of a feature page. They adopted it because the payment workflow, the bank transfer, the confirmation step, the reconciliation, already existed and was trusted. We built on top of an existing habit. When that habit broke, the trust broke with it, and fixing the trust was more important than any new feature we could ship.
This connects to something I wrote about with Nala's investor-focused module, how a feature built for a pitch can overshadow the urgent needs of the customers who actually pay. The Tuesday we took cards off the roadmap was the inverse: we chose the customer's live problem over the investor's potential check.
For a founder with limited runway, the temptation is always to optimize for the next raise. The data room question, the metrics slide, the demo for the associate. All of that is real work. But the customer who can't move money is a fire, and fires don't wait for the roadmap.
What the Tuesday actually bought
Moving that investor meeting cost us nothing in the end. The associate got their answer, by email, two days later. We closed the round anyway, a quarter after that. But the customer whose shipment was stuck, their business is still running, and they're still a customer. The trust from that Tuesday paid for itself many times over, not in a headline, but in the quiet retention numbers.
The lesson I keep coming back to isn't about investors or customers being more important. It's about which problem is real. An investor meeting is an option on the future. A broken transfer is the present, and the present always wins if you let it. Apollo 13's crew didn't reach the moon, they reached the ground, and that was the only outcome that counted.
The next time a roadmap item and a customer fire collide, ask which one you can actually verify is true on the ground. The answer might be the one that's inconvenient to your schedule.
Comments
No comments yet.