He Killed a $100K Product & Pivoted to Raise $375M

What do you do when customers ignore your product and ask about the tech underneath it? Viraj Parekh answered that question by killing a working product and betting everything on open source. It took 18 months to hit $1M ARR—and then everything changed.

Key Facts

• Pre-pivot ARR: $100K–$400K from clickstream product (Viraj Parekh)
• Time to $1M ARR post-pivot: Over 18 months (Viraj Parekh)
• Total funding raised: Over $350M (Viraj Parekh)
• Airflow downloads: 300M+ in one year, 8,000+ companies using it (Viraj Parekh)
• First customer contract size: Under $20,000 (Viraj Parekh)

When Your Side Feature Is Actually Your Real Product

The signal is unmistakable: when paying prospects consistently ignore your product pitch and ask about something else, that something else is your real product. Viraj Parekh noticed customers kept asking about Apache Airflow—the backend powering his clickstream tool—more than the tool itself.

Astronomer started as a Segment competitor, a clickstream analytics product helping companies route user events to their data destinations. It was working. Revenue was somewhere between $100K and $400K ARR. But every sales conversation kept going sideways in the same direction.

As Viraj described it: 'I'd say, and we're powered by cool open source technology like Apache Airflow. And what we heard back was basically, oh, Airflow, that's really cool. Let's talk more about that.' Prospects kept mentioning that Airbnb was using it, that their data engineering teams were already talking about it, and that they wanted to learn more—not about the clickstream product, but about the technology underneath it.

The internal debate wasn't easy. The clickstream market was defined, budgets existed for it, and Segment was the clear benchmark. Airflow, by contrast, had no established commercial market yet. But the team had built deep expertise around it and, crucially, their engineering team was more energized by it. That combination of customer signal and internal conviction is what finally tipped the decision.

"This funny thing started to happen where we tell customers what our product was powered by and they'd be more interested in that than the product itself." — Viraj Parekh

"Segment was very good at what they did and we were always playing catch up. When your job is to play catch up, that doesn't really give you that much room to innovate." — Viraj Parekh

How to Validate Willingness to Pay Before You Build

Ask a direct question with a price attached: 'If we had an easy button for this, would you pay for it?' Then anchor the price to something concrete—like an engineer's salary. If the prospect hesitates, the problem isn't urgent enough. If they say yes without hesitation, you have your validation.

Viraj's approach to pivot validation was blunt and deliberate. Rather than running surveys or analyzing market reports, he went directly to potential customers and asked whether they'd pay for a managed Airflow service. The framing mattered.

'The questions that worked for us was like, hey, if we had an easy button for that, would you pay for this? It's kind of a direct question and it kind of can put people in an uncomfortable spot,' he explained. That discomfort was the point—a waffle meant low urgency. A firm yes meant a real problem worth solving.

He also anchored pricing to engineer salaries rather than arbitrary dollar figures. 'You can say, hey, was this going to be worth half an engineer salary to you? Or is this going to be worth a full engineer salary for you?' This framing removes founder anxiety about asking for 'too much' and grounds the conversation in value the customer already understands. The conclusion was clear: 'When people who are willing to pay say, I will pay you if you can give me an easy button for this thing—that's pretty much all the evidence you need.'

"When people who are willing to pay say, I will pay you if you can give me an easy button for this thing. That's pretty much all the evidence you need." — Viraj Parekh

"You could have every internal conversation that you want. You can look at studies about market size and so on and so forth. But when people who are willing to pay say yes—that's it." — Viraj Parekh

• Ask 'would you pay for this?' with a specific price—not just in theory
• Anchor price to engineer salaries to remove sticker shock
• A waffling response means low urgency—move on
• Immediate yes signals a design partner worth pursuing

Landing the First Customers: What Actually Worked

Cold email campaigns anchored to a top-of-mind technology—with a subject line like 'Don't open this unless you use Apache Airflow'—drove strong early response. Beyond acquisition, success came from obsessive customer support: Viraj talked to his first paying customer no fewer than four times a day for two months.

The first paying Astronomer customer was a data scientist at a media company in Ireland—a former Googler who simply needed his data loaded into BigQuery daily without managing infrastructure. The contract was under $20,000. What followed was anything but hands-off.

'I don't know of anyone whose first handful of customers hasn't been a bit of a knife fight,' Viraj said. 'You're just getting on the phone with them every day, trying to make sure what they're doing works.' He estimated he spoke to that first customer no fewer than four times a day for the first two months—via Intercom, Zoom, and whatever else worked.

For acquiring new customers, email campaigns with sharply targeted subject lines delivered results. The most successful: 'Don't open this email unless you use Apache Airflow.' Astronomer also launched an Airflow podcast to build community credibility. Being outside Silicon Valley meant the bar for proof was higher. 'We had to show more traction than I think our parallel sort of company would have,' Viraj noted. To compensate, they bundled in Airflow training and professional services with early contracts—adding value that offset their lack of brand recognition.

"I think I had talked to him no less than four times a day for the first two months. You just have to get maniacal about it and make sure that the second customer doesn't run into those same roadblocks." — Viraj Parekh

"Our most successful email campaign had the subject line: 'Don't open this email unless you use Apache Airflow.'" — Viraj Parekh

Building Outside Silicon Valley: The Higher Traction Bar

Founders outside major tech hubs need to show more concrete traction to raise equivalent rounds. Astronomer's answer was to recruit the most active Apache Airflow open source contributors, bundle professional services, and show up to customer meetings with a personal touch—a used book on the customer's college major—instead of branded swag.

Astronomer was built in Cincinnati. No Silicon Valley pedigree, no creator of the open source project on the founding team. According to Viraj, this meant the company had to earn legitimacy the hard way—through actions, not positioning.

The book story illustrates the mindset: 'We'd look up who we're visiting, find out what they majored in in college, and we'd go to the used bookstore and get a book about that topic. Because that was a whole lot cheaper than getting a bunch of shirts.' It wasn't just frugality—it was a deliberate signal about the kind of company Astronomer wanted to be.

For fundraising, Viraj's team recruited the most active Airflow open source contributors before their Series A to signal technical legitimacy. They raised their Seed round at roughly $500K–$1M ARR, noting that a comparable San Francisco startup might have raised at a lower traction threshold. Their Series A was approximately $13.5M in 2019. The lesson: geography isn't destiny, but it does change the rules of the game.

"We needed to show more traction than I think what our parallel sort of company would have—because of who we were and where we were." — Viraj Parekh

"We have to earn the right to be the Airflow company with our actions, not just words." — Viraj Parekh

• Recruit open source contributors to signal technical credibility
• Bundle training and services to compensate for low brand recognition
• Personal gestures outperform branded swag at zero-to-one stage
• Expect to show more traction than Silicon Valley equivalents

Why Slow Growth to $1M ARR Can Set You Up to Scale Faster

Taking 18+ months to reach $1M ARR forced Astronomer to earn every customer relationship, build real resilience, and deeply understand the product's value. That scar tissue became the foundation for faster, more durable growth after product-market fit clicked—and prevented the false confidence of early flukes.

Astronomer took over 18 months to reach $1M ARR. By most venture benchmarks, that's slow. But Viraj sees it differently: 'The lessons we learned in how hard it was to get to a million made it so that we could better serve our customers and build the company growing past that. Because that's when all the humbling happens, and that's when all of your resilience gets built.'

The risk of hitting $1M ARR too fast is mistaking early wins for product-market fit. 'What you don't want to happen is have a couple of early successes, and it turns out those were flashes in a pan,' he warned. True product-market fit arrived when customers started coming to Astronomer saying they'd already decided on Airflow—and heard Astronomer was the best way to run it. That inbound pull, not outbound grind, was the signal.

COVID accelerated things further. Data budgets exploded as companies raced to go digital-native, and Airflow's adoption grew with it. But the foundation—built through 18 slow months of knife-fight customer work—was what made scaling possible.

"Getting to the first million definitely took over eighteen months. After we got to that, it definitely went faster but it was a slog to get there." — Viraj Parekh

"Near the end of 2018 and early 2019, customers would say: 'We've decided on Airflow and we hear that you guys are the best way to do that.' That was product-market fit for us." — Viraj Parekh

Clickstream Product vs. Managed Airflow: Why Astronomer Pivoted