What You're Actually Building

Description: We raised a million dollars on a simple pitch, built the app, launched it in Atlanta, and then found out we were building something completely different. The P2P model worked fine. The enterprise backbone was the actual product. This is about following what's real instead of defending the story you started with, and why that same honesty has to extend all the way down to your UX.

The pitch for Kanga was simple. You're at IKEA. You just bought bunk beds. They won't fit in your car. Somewhere in that same parking lot is a person with a truck who would happily run them to your house for forty bucks, and there's no way to find each other. That's the product. Uber for moving stuff.

We raised a million dollars on that pitch. We built the app. We launched in Atlanta.

And then we found out what we were actually building.

The P2P side worked fine, but the thing that kept lighting up was something else. Every time an enterprise client touched the platform, the scale of the problem changed entirely. It wasn't about connecting two strangers with a couch to move. It was about giving companies a real-time nervous system for local logistics, something that could coordinate just-in-time delivery across hundreds of jobs, multiple providers, and live route changes. The backbone problem. That was the actual product.

We didn't abandon the P2P model. Kanga Delivery kept running. But the company's center of gravity shifted because we followed what was real instead of defending what we had pitched.

I think about that a lot when I watch products drift in directions their founders didn't choose. The original intent stays intact. The mission statement stays on the website. And somewhere in between, the product quietly starts serving a different master.

Here's the thing nobody talks about honestly enough: you don't have to have bad intentions to build something that manipulates people. The design does it for you, one small decision at a time, usually because a metric somewhere said to.

The free trial that makes cancellation a six-step process through a retention flow. The inbox that marks messages as unread after you've read them because re-engagement numbers were soft. The checkout that pre-populates the more expensive option. The settings screen buried so deep it functions as a penalty for wanting control. The default notification cadence calibrated not to be useful but to keep the app in your head. The interface that shows you what 47 other people are doing right now because ambient social pressure is a retention mechanism.

None of these originate from someone deciding to be predatory. They come from a product team that needed better numbers, a designer who was handed a metric to move, and a roadmap that rewarded engagement over experience. Individually, each decision has a reasonable-sounding justification. Collectively, they add up to a product that treats the person using it as a resource to extract from.

The insidious part is that it works, in the short term, on the metrics that get reported. Dark patterns improve conversion rates. Friction reduces cancellation. Defaults drive upgrades. The dashboard looks great right up until the point where trust erodes and the churn that was being artificially suppressed catches up all at once.

I run everything through one question now: does the product get better for the business when it's genuinely better for the person using it?

Not "does the person feel engaged." Not "is their session time up." Does the actual experience the product delivers make the business stronger because it's producing something real?

If yes, we build aggressively. The incentives are pointed in the same direction and the flywheel is clean.

If no, you've got a structural problem, and your UX team is about to paper over it with patterns that make the metrics look fine while the foundation gets worse.

Kanga taught me that the thing worth building is rarely the thing you pitched. But more than that, it taught me that finding the real thing only happens if you're willing to look honestly at what's working instead of defending the story you started with.

That same willingness has to extend all the way down to the product experience, and most founders stop short of it. They'll pivot the business model when the data demands it. They'll change pricing, reposition the brand, kill a feature that isn't landing. But they won't audit the UX with the same honesty because the UX doesn't feel like a strategic decision. It feels like execution. It's someone else's job. It happened gradually, in a hundred small choices that individually made sense.

That's exactly how it gets you. Nobody makes a decision to become manipulative. The product just drifts there, one A/B test at a time, while the founder is still operating as if the original intentions are in control. They're not. Intentions set the direction at the start. After that, the design is in charge, and the design goes wherever the metrics point it.

So the audit has to be intentional and it has to be ruthless. Sit in your own product like a stranger. Try to cancel. Try to change your defaults. Try to find the information you'd need to make a real decision about whether to stay. If that experience doesn't match the company you think you're building, you've already drifted, and good intentions aren't going to fix it.