7 GTM Lessons From Building Illumex in a Crowded Data Observability Market

7 GTM Lessons From Building Illumex in a Crowded Data Observability Market

Product-led growth is supposed to be the holy grail for SaaS companies. Lower customer acquisition costs, faster sales cycles, and organic viral loops. Except when it doesn’t work at all.

In a recent episode of Category Visionaries, Ina Sella, CEO & Founder of Illumex, shared how her company discovered this the hard way—and what they did instead to build a data observability business that now serves enterprise customers. Her journey offers a masterclass in adapting GTM strategy when the conventional playbook fails.

Lesson 1: Your Sales Calls Are Your Best Product Research

Most technical founders dread their first sales calls. Ina turned hers into a competitive advantage. After an advisor reviewed her first call and told her, “you asked like maybe one question during the entire call. You just talked the entire time. You need to ask questions, you need to learn about them,” she completely reframed her approach.

Rather than viewing sales as pitching, Ina treats every call as customer discovery. “Even now when I go to sales calls, I always try to learn something from the customer that I didn’t know before the call,” she explains. This isn’t just good sales practice—it’s how Illumex has stayed ahead of larger competitors with more resources.

The implication for founders is profound: if you’re not learning something new on every sales call, you’re not asking the right questions. Your prospects know things about your market, your product, and your positioning that you don’t. The founders who win are the ones who figure out how to extract that knowledge systematically.

Lesson 2: PLG Works Until It Doesn’t—Know When to Pivot

Illumex initially tried to implement a product-led growth motion. The logic seemed sound: data teams are technical users who prefer self-service, and reducing friction should accelerate adoption. “We thought about doing like a free trial or freemium, but it didn’t really work,” Ina admits.

The problem wasn’t the concept—it was the implementation barrier. Getting value from a data observability platform requires connecting to data sources, configuring integrations, and understanding the insights. Prospects would sign up but wouldn’t complete setup without guidance.

The solution was counterintuitive: keep the self-serve option but immediately add high-touch support. “What we ended up doing is keeping the ability to self-serve and sign up, but we will contact you right away,” Ina explains. This hybrid model preserved the low-friction entry point while ensuring customers actually got to value.

The lesson isn’t that PLG doesn’t work—it’s that implementation complexity is the silent killer of self-serve motions. If your time-to-value requires more than 15 minutes of setup, you probably need sales involvement, regardless of what the GTM playbook says.

Lesson 3: In Crowded Markets, Responsiveness Is a Moat

Data observability is brutally competitive. Illumex competes against companies with significantly more funding, larger teams, and established brand recognition. Traditional advice would suggest focusing on product differentiation or finding a niche. Ina took a different approach.

“We try to be extremely responsive,” she says. “We try to be very hands-on with our customers. I’m very involved myself. I join sales calls, I join customer calls.” This isn’t a temporary founder-mode strategy—it’s a deliberate competitive positioning.

Larger competitors can’t match this level of engagement. Their processes, org structures, and scale prevent it. By being the company where prospects can talk directly to the CEO, where feature requests get immediate attention, and where implementation issues get resolved in hours instead of days, Illumex has carved out a sustainable advantage.

The broader principle: when you can’t outspend competitors, out-care them. Responsiveness scales poorly, which is exactly why it works as a moat for smaller companies.

Lesson 4: Solve Your Own Pain Point, But Validate the Market First

Illumex originated from Ina’s personal frustration managing data infrastructure at Meta. “I was building a lot of pipelines for business teams and data science teams,” she recalls. “And very often I would get paged in the middle of the night because something broke in production and I need to go and fix it.”

But personal pain points aren’t always market opportunities. Before committing fully, Ina validated that others experienced the same problems. “I felt like if I had this problem and I worked at one of the best companies in the world that built all of these technologies, I’m assuming that a lot of other data teams are also experiencing this.”

The distinction matters. Building from personal experience gives you authentic insight into the problem. But it can also create blind spots about whether the problem is widespread, whether people will pay to solve it, and whether your specific solution approach resonates. Validation bridges that gap.

Lesson 5: Enterprise Migration Requires More Than Product Changes

As Illumex evolved from mid-market to enterprise customers, Ina learned that the transition required changes across the entire company, not just the product. “In the beginning we had a lot of kind of like initial customers that were more like mid-market companies,” she notes. “Today a lot of our customers are enterprise.”

This shift demanded different sales processes, longer evaluation cycles, more sophisticated ROI frameworks, and new types of proof points. Enterprise buyers need case studies, security certifications, and references. They involve more stakeholders, have stricter procurement processes, and require different contract terms.

The mistake many startups make is treating enterprise expansion as purely a sales problem or a product problem. In reality, it touches everything: marketing messaging, customer success processes, pricing structure, and even technical architecture. Plan for this organizational transformation, not just product readiness.

Lesson 6: Differentiation Starts With Depth, Not Breadth

Rather than trying to match every feature of larger competitors, Illumex focused on doing specific things exceptionally well. “We started working on building our data observability solution that is more focused on helping data teams to troubleshoot and resolve issues as fast as possible,” Ina explains.

This meant building full column-level lineage and actionable recommendations—capabilities that competitors had deprioritized. Instead of just alerting that something broke, Illumex tells you why it broke and how to fix it.

This depth-first approach creates more defensible differentiation than breadth. Customers choose you because you’re dramatically better at solving their specific problem, not because you have 10% more features across the board. The companies that win crowded markets are usually the ones that go deeper on fewer things.

Lesson 7: Founder Involvement Scales Further Than You Think

Conventional wisdom says founders need to remove themselves from sales and customer interactions to scale. Ina’s experience suggests otherwise. Her continued involvement in customer calls and sales conversations isn’t a phase to grow out of—it’s a strategic asset.

This hands-on approach drives product decisions, informs positioning, maintains customer trust, and accelerates deal velocity. It’s also what prospects explicitly value when evaluating Illumex against larger competitors. The direct access matters.

The lesson for founders: don’t be too eager to remove yourself from customer-facing activities. The leverage you gain from staying close to customers often outweighs the time investment, especially in competitive markets where personal relationships and rapid iteration create meaningful advantages.

These lessons won’t guarantee success, but they represent hard-won insights from building in one of the most competitive categories in enterprise software. The companies that win aren’t always the ones with the most funding or the best pedigree—they’re the ones that adapt fastest when reality doesn’t match the playbook.