MVPs and the Art of Good Enough
When fundraising, investors don't bet on perfect products—they bet on proof that your imperfect MVP actually works in the real world, right now.
When the investors walked into our Chairmanbari office in early 2016, I watched their faces. I was looking for the moment. The moment where they’d realize we were barely a company. That our “office” was a construction site with wi-fi. That the logo on the wall was held up with double-sided tape.
But the moment never came.
They sat in our bargained-for chairs, nodded at the plywood desks, and dove straight into questions about our model. About our delivery times. About our unit economics. They didn’t care that we looked broke. They cared that we had riders out there, right now, delivering packages across Dhaka.
We weren’t polished. We were operational.
That’s the thing about MVPs nobody tells you. The point isn’t to build something beautiful. It’s to build something that proves you can solve a problem, right now, with whatever you have. And sometimes, learning that lesson costs you five years and a regulatory shutdown.
The $200K That Saved Us
Pathao wasn’t sophisticated when we started taking courier orders. We had no dispatch system. No routing algorithm. No predictive anything. What we had was phones, bikes, Google Sheets, and riders willing to navigate Dhaka’s chaos for 60 taka per run.
Every delivery was manually coordinated. A rider would call saying he couldn’t find the address. We’d call the customer. The customer would describe landmarks. “You know the paan shop with the red awning? Turn left there.” We’d relay it back. The rider would find it. Or he wouldn’t, and we’d start over.
It was absurd. It was inefficient. And it worked.
Because the customers didn’t need perfection. They needed their packages delivered. The merchants didn’t need dashboards. They needed someone reliable to pick up their stock and get it to buyers. We gave them that. Just that. Nothing more.
When those first investors showed up, they didn’t invest in our tech stack or our UI. They invested in proof. We had forty deliveries a day happening in real time. We had merchants paying us. We had riders showing up every morning. That was worth $200,000. Not the potential version of Pathao, the one running on algorithms and venture scale. The actual version. The one held together with phone calls and prayer.
This is what founders miss about fundraising. Investors don’t fund perfect products. They fund evidence. Evidence that you understand a real problem. Evidence that people will pay for a solution. Evidence that you can execute under constraint.
Our plywood desks weren’t a bug. They were a feature. They proved we weren’t burning cash on appearances. Every taka went into riders, operations, and keeping the wheels turning. That told investors something no pitch deck could: we knew how to survive.
When Good Enough Kills You
Here’s where it gets tricky. Shipping fast doesn’t mean shipping recklessly. There’s a line between “embarrassingly incomplete” and “dangerously broken,” and that line isn’t always obvious until you’ve crossed it.
We learned this the expensive way with Pathao Pay.
By 2017, we were growing fast. Rides were working. Food delivery was taking off. And we kept hitting the same friction point: cash. Everything in Bangladesh ran on cash. Customers paid cash. Riders collected cash. Merchants settled in cash. We were basically a logistics company running a parallel banking operation, and it was a nightmare.
So we decided to launch Pathao Pay. A closed-loop wallet. Customers could load money into the app, pay for rides and food digitally, and riders wouldn’t have to carry cash anymore. It was elegant. It solved real problems. And we built it fast.
Too fast.
We launched in beta. Started onboarding users. Got traction. Then, three weeks in, we got a letter from Bangladesh Bank. Not a friendly inquiry. A notice. We were operating what they considered a financial instrument without the proper license.
Technically, Pathao Pay was a closed-loop system. You couldn’t transfer money out. You couldn’t use it anywhere except Pathao. It was more like a gift card than a wallet. But we called it “Pay.” We marketed it like a payment solution. And in a country where mobile financial services are tightly regulated, that was enough to raise every red flag.
We had to shut it down. Immediately. Not “let’s phase this out over a few months.” Not “let’s fix the regulatory issues and relaunch in six weeks.” Immediately. As in, users woke up the next day and couldn’t access their wallets.
The fallout was brutal. Customers were furious. Some had loaded significant amounts. We had to manually process refunds. The press tore into us. Competitors whispered that we didn’t know what we were doing. And investors, the ones we were pitching for our next round, started asking harder questions about our due diligence processes.
It took us five years to relaunch Pathao Pay. Five years of working with regulators, applying for licenses, building compliance infrastructure, and proving we could operate within the rules. Five years of watching competitors move into the space while we sat on the sidelines.
The MVP logic that worked for courier, launch fast, learn from users, iterate in public, failed catastrophically for payments. Because the cost of getting it wrong wasn’t a bad user experience or churn. It was regulatory shutdown. And in fintech, you don’t get do-overs.
Spotify could launch with an incomplete music library. Airbnb could launch with founders taking photos themselves. We could launch courier with manual dispatch. But we couldn’t launch payments without proper licensing. The line between fixable and fatal isn’t about product quality. It’s about irreversible consequences.
What You Can’t Learn From a Deck
Here’s what most fundraising advice gets wrong. It focuses on the pitch. The deck. The narrative. The vision.
But when we raised our Series A, the pitch mattered less than what we could prove in real time.
Our lead investor didn’t just review our deck and write a check. They sent analysts to Dhaka. For weeks. These weren’t courtesy visits. They embedded with our operations team. They rode with our drivers. They sat in our call center listening to customer complaints. They watched our ops managers manually assign deliveries at 7 AM.
And every day, they asked the same question: “Can this actually scale?”
Not “does the deck say it can scale.” Can it. Right now. With this team. In this market.
We couldn’t fake that. We couldn’t polish our way through it. Either the system worked or it didn’t.
This is where the MVP becomes your pitch. When you’re raising a seed round, investors bet on potential. But when you’re raising growth capital, they bet on proof. And proof isn’t a forecast. It’s not a TAM slide. It’s watching your product work, in the wild, under stress, today.
We had bugs. Our app crashed sometimes. Our routing was inefficient. But we had something more valuable: live operations. We could show an investor our courier dashboard at 3 PM on a Tuesday and say, “Right now, we have 142 active deliveries happening across Dhaka. Here’s the average delivery time. Here’s the rider utilization rate. Here’s yesterday’s cash reconciliation.”
That’s what closed the round. Not the perfect product we’d build someday. The imperfect one running right now.
And when we had to explain the Pathao Pay shutdown? We didn’t spin it. We said: “We moved too fast. We underestimated regulatory risk. Here’s what we learned. Here’s the process we built to prevent it from happening again.”
Investors don’t expect perfection. They expect honesty and learning velocity. Show them you can ship fast, fail smart, and adjust quickly, and they’ll fund the next iteration.
The Dhaka Advantage
Silicon Valley loves clean solutions. Elegant APIs. Seamless user experiences. Frictionless everything.
Dhaka doesn’t care about any of that.
In Dhaka, the internet is slow. Smartphones are cheap and underpowered. Data is expensive. Addresses don’t exist in half the city. Traffic is unpredictable. And cash is still king.
So when we built Pathao, we couldn’t just copy Uber’s playbook. Our MVP had to work in the reality on the ground. Our app had to function offline. Our dispatch had to account for traffic that could triple without warning. Our payment system had to handle cash, because cards weren’t an option. Our address input had to use landmarks, because street numbers were fiction.
These weren’t “features.” They were survival.
But here’s the thing: these constraints made our MVP stronger. Every compromise we made for Dhaka’s reality became a competitive advantage. Uber’s app assumed reliable connectivity. Ours didn’t. When network coverage dropped in Mirpur, our riders kept working. Uber’s didn’t.
The MVP isn’t about building less. It’s about building for the real world, not the ideal one. And the real world, especially in emerging markets, is messy. The startups that win are the ones who embrace that mess early.
We launched ugly. We launched incomplete. But we launched functional. And in a city where nothing works perfectly, functional was enough to win.