We Rebuilt Our Product Twice to Learn One Thing

During YC, OpenFunnel started exclusively within Slack, believing traditional UI wasn't ideal for surfacing intelligence. However, customer feedback revealed Slack had limitations—maintaining accuracy for alerts proved difficult, and their target market didn't think in alert-oriented terms.

The team pivoted to a full UI, which resonated during sales. Prospects appreciated seeing thousands of accounts with insights upfront, making purchasing decisions straightforward. Yet this approach created operational challenges. "Endless UI/UX optimization" diverted focus from core value delivery for a lean team.

A critical shift occurred when the company launched API and webhook integrations. With Claude Code gaining adoption and GTM teams increasingly favoring push-based actions over static dashboards, usage patterns evolved significantly.

The insight: customers preferred seeing UI with "big numbers" during presales evaluation, but post-purchase, they overwhelmingly chose MCP, APIs, webhooks, and Slack for actual operations—abandoning the complex interface they'd initially requested.