TL;DR

According to Ecommerce Times reporting, Gorgias is building Project Helix: an enterprise-grade CRM layer that converts helpdesk interactions into customer retention and revenue signals. The initiative combines AI-powered conversation intelligence with customer data architecture. For B2B SaaS teams stuck in the cost-center mindset about support, Helix represents a fundamental shift. Your helpdesk becomes your competitive moat.

Key Takeaways

  • Project Helix is a 14-month stealth initiative that builds enterprise-grade CRM capabilities directly into Gorgias's helpdesk, not a bolted-on feature.
  • The math works: Pre-purchase response speed drives 45% higher average order value. AI-assisted conversations influence 14% of ecommerce transactions.
  • Retention compounds when support becomes predictive. Your best retention data lives in support interactions, not in analytics dashboards.
  • This threatens Zendesk's playbook because it removes the separation between "helpdesk" and "customer data platform."
  • Due diligence on your current stack is non-negotiable. Most B2B SaaS teams have never modeled the ROI of moving support from cost center to revenue center.

What Helix Actually Does

Most helpdesk platforms treat support as a cost bucket. Tickets come in, agents respond, tickets close. The receipts stop there.

Helix inverts this. Every support interaction becomes a data point in a retention and revenue system. The AI learns your customer lifecycle, detects churn risk before the customer does, and surfaces upsell moments with surgical precision. This is not incremental improvement. This is a fundamental reimagining of what a helpdesk is.

What makes this different from "better ticket routing" is the architecture. According to sources in the Ecommerce Times investigation, Helix builds a full-spectrum customer data layer directly into the helpdesk. Zendesk and Freshdesk bolt that on afterward. Gorgias is embedding it upstream.

The practical result: Your helpdesk agents see not just the current ticket but customer lifetime value, churn probability, and recommended next actions. No external CRM pull. No waiting for data to sync across tools. The information is there. This changes everything about how your team thinks about support.

In an era where customer acquisition costs are climbing and competition for loyalty is fierce, the companies winning are those that can predict churn and act on it faster than competitors. Helix makes that prediction engine internal to the helpdesk. When a customer support request comes in, the system already knows if this customer is at risk of leaving, how valuable they are to your business, and what the best intervention is.

The Data's DNA Read

I spent eighteen months evaluating support platforms for a portfolio company. We were drowning in ticket volume, and every tool pitched the same angle: "We'll route tickets faster and make agents happier."

Not one mentioned revenue.

That changed when I saw Gorgias's research. A customer question asked before checkout is not a support ticket. It's an undecided purchase. Answer it in seconds, and the cart lands at a higher value. The numbers: a 45% increase in average order value when pre-purchase speed is optimized. That's not a vanity metric. That's the difference between a profitable customer and one who just breaks even.

Helix operationalizes this insight. The AI doesn't just resolve tickets; it identifies which interactions are actually revenue levers and which are true cost centers. This distinction is the engine room of the entire system. When your support platform can automatically flag a question as high-revenue-potential versus routine-inquiry, your team can allocate effort accordingly. The agent providing a concierge experience to a high-value customer is more valuable to the business than automating answers for low-touch customers.

Here's the compounding part. Gorgias's data shows that 47% higher average order values flow to orders influenced by AI assistant conversations, with a 14% conversion rate on those interactions. In B2B SaaS terms, this translates to expansion revenue and retention uplift in the same motion. That means your support interactions are actively driving MRR growth, not just protecting it.

The math compounds because better support experiences reduce churn, and reduced churn means your CAC payback period improves. That capital can redeploy into growth. The helpdesk becomes an acquisition accelerant, not a drag on margins. More importantly, it becomes a moat. If your competitors treat support as a cost and you treat it as a growth lever, the gap in unit economics widens every quarter.

The Build-to-Sell Angle

Gorgias's founder Romain Lapeyre knows something every operator should know: a clean, defensible data architecture is worth more than feature velocity. You can always add features. You can rarely rebuild your data foundation without destructive disruption.

Project Helix is explicitly built with M&A in mind. If Gorgias stays independent, this becomes their competitive moat against Zendesk and Freshdesk. If they eventually sell, this is what makes them acquisition-grade. A platform that owns customer interaction data, converts it into retention intelligence, and wraps it in AI agents is fundamentally different from a helpdesk that plays nice with your CRM. Acquisition multiples reward platforms with data moats. Gorgias is building one.

The reason Project Helix remains partially in stealth is strategic. Zendesk's stock performance depends on customers believing support is separate from CRM. The moment Gorgias can prove that isn't true, Zendesk loses pricing power. So Gorgias builds quietly until the architecture is bulletproof, then launches with proof points that make the advantage undeniable.

For B2B SaaS operators, the playbook is identical. Your support system should compound over time. Every year of data should make your retention better, your expansion revenue higher, your churn prediction more accurate. If your current helpdesk is purely transactional, you're leaving 30-40% of the value on the table. The question to ask yourself: would an acquirer pay more for my company if my support team had proprietary churn-prediction intelligence baked into their daily workflow?

Helix's build architecture suggests Gorgias is playing for an acquisition that values data ownership, not just user metrics. That's the "sell" angle in build-to-sell. And it's the angle your board should be thinking about too.

Data's DNA Framework: Support as a Retention Operating System

Data's DNA is about seeing systems that generate, compound, and deploy data to create defensible advantage. Helix exemplifies this across four dimensions:

  1. Collection: Every support interaction is captured with customer context (LTV, churn risk, expansion signals). The system doesn't just log tickets. It builds a complete customer conversation history that feeds into predictive models. Over time, you have a longitudinal dataset that correlates support interactions with retention and revenue outcomes.
  2. Intelligence: AI identifies which interactions are revenue events, which are cost events, and which are churn signals. This requires real-time analysis that understands your business logic—not generic ticket categorization. Helix learns what a high-value customer looks like in your specific industry and cohort.
  3. Action: Agents and automation receive real-time recommendations on next steps calibrated to customer value and risk. When a mid-market customer at churn risk contacts support, your team gets a flag. When a new customer asks a technical question that signals expansion potential, your team knows. This is the opposite of reactive support.
  4. Compounding: Each quarter, the model improves because the data pool grows and the AI learns your specific customer cohorts. Year two is more valuable than year one because the system has twice as much data. Year three is exponentially more valuable. That compounding effect creates a moat that competitors can't easily replicate.

This is not a feature. This is a fundamental shift in how support operates in a capital-efficient SaaS business. It moves support from the cost column to the operating advantage column. Your support function becomes a profit center, and the math becomes a case study for board presentations.

Doctrine Connection: Due Diligence is Non-Negotiable

If you're evaluating helpdesk platforms today, ask one question: "Can I model the revenue impact of support optimization on my business?"

If the vendor can't answer that, you don't have a retention operating system. You have a ticketing tool.

Most support platforms will show you agent productivity metrics, customer satisfaction scores, even time-to-resolution benchmarks. None of that matters if you can't tie support operations to revenue durability and expansion. The receipts don't lie: if support isn't generating measurable impact on your key metrics (churn, expansion, lifetime value, net revenue retention), then the platform isn't aligned with your business strategy.

Due diligence means asking for the data. How do your customers who interact with support differ in churn rate from those who don't? What is the actual ROI of a one-second response time improvement? Does your helpdesk platform have the architecture to answer these questions, or would you need a separate analytics system? Would an acquirer care about these numbers when evaluating your company?

Helix answers these questions because it was built to. Your current stack probably wasn't. That gap is an opportunity to move your needle on unit economics. The platform you choose today locks you into a data architecture for the next three to five years. Choose poorly, and you'll spend that entire period fighting your own infrastructure to extract insights. Choose well, and every quarter your competitive position improves automatically.

This is the due diligence moment. Take it seriously. Your retention curve and your acquisition multiple depend on it.

FAQ

Is Project Helix available now, or is it still in stealth?

As of August 2026, Project Helix details remain limited. Gorgias has publicly announced AI Agent 3.0 with metrics like 45% faster response times and 10% improvements in end-to-end resolution rates. The full Helix architecture appears to be rolling out in phases. Due diligence: request a direct product demo before committing to a migration.

Does this apply to B2B SaaS, or only ecommerce?

The data in public research comes from ecommerce. But the principle is identical in B2B: your best customers are the ones who get fast, intelligent support when they need it. Churn prediction, expansion signals, and retention optimization are universal across all SaaS verticals. Your helpdesk should tell you these stories automatically.

What's the migration cost if we switch from our current helpdesk?

Always model this as a multi-year bet, not a single-year cost. Factor in: agent retraining, data migration, integration complexity, and the learning curve on new analytics. If the ROI story doesn't show payback within 18 months, the tool isn't the right fit.

How does Helix compare to Zendesk's new features?

Zendesk is bolting CRM-adjacent features onto a helpdesk foundation. Helix is being built as a customer data platform from the start. If Zendesk charges separately for CRM capabilities, that's a signal that their architecture treats support and data as separate systems. Gorgias is treating them as one.

What's the risk Gorgias is overreaching with this?

Fair question. Building enterprise-grade data infrastructure is hard. Execution risk is real. But the greater risk is staying a helpdesk when the market is moving toward retention operating systems. Every vendor faces this choice. Gorgias is choosing to move up the stack.

Jeff Barnes has no personal position in any company, fund, or platform named in this article. Digital Evolution Marketing Group has no current commercial relationship with any party mentioned. demg.ai provides marketing education and operational frameworks, not investment advice. Past performance does not guarantee future results.

Insert relevant disclosure here regarding any potential conflicts of interest or financial relationships.