/
.webp)
A company biography for the Stacksync content library
It's 11:14 on a Tuesday morning, three days after a long weekend. A DTC skincare brand just ran a flash sale. They moved 4,200 units in 36 hours. The inbox has 800 unread tickets. Half of them say some version of the same five words: where is my order.
The support agent — let's call her Sarah — opens the first ticket. She copies the customer's email address. Opens a new tab. Logs into Shopify. Searches for the customer. Finds the order. Copies the tracking number. Opens another tab. Pastes it into DHL's website. Confirms the status. Goes back to the helpdesk tab. Types a response that begins "Hi there! Thanks so much for your patience..." pastes in the tracking number, adds the estimated delivery date, adds a discount code for their next order. Hits send. That was four minutes. She has 799 more to go.
This is not a story about inefficiency. It is a story about a specific, localized pain that nobody in enterprise software had cared enough to fix — because it didn't affect their customers. It affected a different kind of customer entirely: the scrappy DTC brand on Shopify with eight SKUs and a founder who was also answering tickets at midnight. The kind of company that was invisible to Zendesk's enterprise sales team but was collectively moving billions of dollars through the internet.
Two French engineers in Paris saw it. They built something about it. And a decade later, 15,000 brands — including Steve Madden and Glossier — never let their support agents open a second tab.
Romain Lapeyre and Alex Plugaru were not building a helpdesk when they started Gorgias. That is the first thing you need to understand about this company. They were building a Chrome extension.
The year was 2015. Paris had a startup scene — small, scrappy, nothing like the Valley, but alive. Lapeyre had spent time at Scalr and Work4, product roles at startups early enough that you learn by breaking things. Plugaru was the technical half of the duo. Together they built a Chrome extension for email productivity: save response templates, fire them off faster, stop retyping the same answers to the same questions. It was a workflow tool. A small one. A useful one.
They shipped it. People started using it. And then they looked at their user data.
Seventy percent of their users were customer support agents at online stores.
Not executives. Not sales reps. Not productivity nerds who love keyboard shortcuts. Support agents. People sitting inside e-commerce companies, answering the same questions all day, desperate for any tool that would let them do it faster. The extension wasn't transformative for them — it just let them type less. But the signal was unmistakable: there was a group of people with a specific, structured, repetitive problem, and nobody was solving it properly.
Lapeyre and Plugaru pivoted. They abandoned the general-purpose productivity angle and went narrow: a helpdesk built specifically for e-commerce merchants. Not a Zendesk with an integration. Not a Freshdesk with a plugin. Something designed from the ground up for the context that mattered — Shopify stores, where every support ticket was a transaction, and every transaction had data attached to it that agents couldn't access without leaving the room.
They applied to Y Combinator for the Winter 2017 batch. Two French engineers with a pivot story and a product that could fill in order data automatically. YC took them. That San Francisco trip — the demo days, the investor conversations, the relentless founder-sparring that YC runs as a feature, not a bug — shaped how Gorgias thought about its market. It also put them in the right time zone for the customers they were trying to reach.
The irony was structural: a Paris-founded company running through San Francisco to serve American DTC brands who were themselves running through Shopify's Canadian infrastructure. The whole thing was an Atlantic crossing made possible by the fact that software doesn't care about geography.
The insight that drove Gorgias into Shopify territory was simpler than it sounds, and harder to execute than it looks.
When a customer emails a Shopify merchant with a support question, the answer almost always lives inside Shopify. Order number, shipping carrier, tracking link, delivery date, return status, refund history — all of it is in Shopify's database. But Shopify is not a helpdesk. It does not have a unified inbox. It does not thread email conversations. It does not auto-assign tickets or track response times. It does not let you send replies from inside it.
What merchants were doing was running two separate systems in parallel, manually bridging them with copy and paste. Open Zendesk. Read the ticket. Copy the email. Open Shopify. Search for the customer. Copy the order details. Go back to Zendesk. Type the response. This is not a corner case — this is the entire job description for a DTC support agent in 2017, 2018, 2019.
Gorgias collapsed the gap. They built deep into Shopify's API — not just a surface-level data fetch but bidirectional write access. An agent using Gorgias could see the customer's full order history inside the ticket view. They could create refunds from inside a ticket. They could edit orders, generate discount codes, modify shipping addresses — all without leaving the helpdesk. The support ticket and the transactional record lived in the same screen.
Then came macros.
Macros sound boring. They are template responses. But in the context of DTC support, they are the difference between 180 tickets a day and 40 tickets a day.
A Gorgias macro for a WISMO ticket — "where is my order" — doesn't just insert boilerplate text. It inserts the customer's name, pulled from Shopify. It inserts the order number. It inserts the current tracking status, fetched in real time. It inserts the estimated delivery date. It inserts the tracking link, the carrier name, the shipping address. An agent opens the ticket, reads the question, hits one button, and the response is already written — personalized, accurate, complete. They review it, maybe adjust a word, hit send. Twenty seconds. Not four minutes.
Multiply that across 800 tickets from a flash sale weekend, and you understand why brands were buying this with their credit card before anyone had pitched them.
The macro system looked simple from the outside. It was not. The technical challenge was maintaining accurate, real-time connections to Shopify's data layer — ensuring that when a macro pulled order status, it was pulling now, not from a cache that would tell a customer their package was "in transit" when it had already been delivered. This was the moat, built one API call at a time.
Gorgias charged by ticket, not by seat. This mattered. Zendesk charged per agent per month — a model designed for enterprise IT departments with stable headcount. DTC brands are volatile. They hire five temps for Q4. They have one person in January. Seat-based pricing punishes seasonal businesses. Ticket-based pricing scales with actual usage, and it made Gorgias dramatically easier to budget for a brand doing $2M in revenue.
By 2019, they had raised a $14M Series A. The DTC wave was already building. The Shopify ecosystem was growing by orders of magnitude. Every new Shopify brand was a potential Gorgias customer. The company was positioned at exactly the right intersection of a rising platform and an unsolved pain.
Then COVID happened.
March 2020 changed e-commerce permanently. Retail locked down. Consumers went online. DTC brands that had been growing steadily at 30% per year were suddenly growing at 300%. The brands that existed blew up. New ones launched by the week. Every single one of them needed customer support infrastructure, and they needed it immediately.
Gorgias's customer growth during 2020 and 2021 was, by any honest account, astronomical. The DTC boom was not a rising tide that lifted all boats — it was a targeted flood that hit exactly the segment Gorgias served. Shopify processed $61.1 billion in GMV in 2020 alone, up 96% from the year before. Every dollar of that GMV generated customer service tickets. A meaningful fraction of those tickets landed in Gorgias.
By December 2020, the company raised a $25M Series B at a $300M valuation. Sapphire Ventures led. The round was notable not just for the size but for the timing — this was a company that had been quietly compounding for five years, barely a household name outside the Shopify ecosystem, and suddenly it was valued at a third of a billion dollars.
Then came the move that confirmed Gorgias had become something more than a Shopify app.
In 2021, Shopify invested directly in Gorgias.
This requires a moment of explanation. Shopify's venture arm, Shopify Ventures, takes minority positions in companies that extend the utility of the Shopify platform for merchants. The logic is structural: every dollar of value that an ecosystem partner adds to the Shopify experience is a dollar of competitive moat against Amazon, WooCommerce, and every other commerce platform. Shopify investing in Gorgias was Shopify saying, explicitly, that customer support quality is part of why merchants stay on Shopify.
For Gorgias, the investment was more than capital. It was an endorsement baked into the platform's infrastructure. When Shopify's own evangelists and partner teams talk to merchants about setting up their stack, Gorgias is in the conversation. The investment turned a vendor relationship into something closer to an alliance.
The dynamics were not purely benign. Shopify had invested, but Shopify could also build. Or buy. Or designate. The dependency was now formal and visible. Gorgias's success was structurally tied to Shopify's success and to Shopify's continued willingness to let ecosystem partners do work that Shopify could, theoretically, absorb. This is the existential tension underneath all vertical SaaS plays: the platform is both your distribution channel and your biggest potential competitor.
In August 2022, Gorgias raised a $30M Series C at a $710M valuation, led by Sapphire Ventures. Near-unicorn. A French company, still partially headquartered in Paris, valued at more than most French startups ever dreamed of reaching.
The ARR trajectory told the story: $25M in 2022, $51M in 2023, $69M in 2024. 15,000 brands. 40% of Shopify's top 1,500 merchants. Premier Partner status in customer experience — a designation Shopify does not give lightly and gives to no one else in this category.
The question hanging over Gorgias in 2025 is not whether they built something real. They did. The question is what the next version of the company looks like — and whether the answer complicates the economics that got them here.
Gorgias has repositioned as a Conversational AI platform. Their AI agent now resolves, on average, 60% of support inquiries automatically. For some merchants, the number is higher — Orthofeet hit 56% automation in under two months. Pepper reached 54%. The promise is clear: you still need support infrastructure, but you need fewer human-hours to run it.
Here is the problem. Gorgias charges by ticket. If AI resolves 60% of tickets automatically, and merchants are paying per ticket, then Gorgias has built a product that shrinks the very revenue base it runs on. The more effective their AI, the fewer billable interactions their customers have. This is not a flaw in the product. It is a structural tension in the business model that every automation-first support company is now navigating — and most are navigating it by quietly raising prices for AI-resolved tickets while hoping merchants don't do the math too carefully.
The Zendesk comparison remains instructive. Zendesk went public in 2014 at a $1.7B valuation and spent a decade chasing enterprise. They built horizontally — every vertical, every use case, every industry. What they never quite solved was the context problem: a Zendesk ticket at a Shopify merchant is just a text field. It doesn't know the customer's order history. It doesn't know whether the package is late. It doesn't let you issue a refund. Zendesk became the system of record for enterprise support operations. Gorgias became the system of action for DTC operations. The distinction sounds subtle. In practice it meant Gorgias could charge $10/month for a starter plan and still win meaningful market share, because depth in one context beat breadth across all contexts.
The Shopify dependency is real and it is not going away. Gorgias has expanded to BigCommerce, Magento, and WooCommerce — but the overwhelmingly majority of their revenue, their partnerships, and their strategic positioning runs through Shopify's ecosystem. When Shopify launched their own AI tooling, every Gorgias investor held their breath briefly. When Shopify's GMV growth slowed in 2022 as pandemic e-commerce normalized, Gorgias's pipeline compression was immediate. The platform bet was correct. It also means that Gorgias is riding a wave that someone else is generating.
The European-founders-for-American-brands dynamic never fully resolved. Gorgias has a San Francisco headquarters, but a meaningful portion of its engineering and operational team is Paris-based. There is something clarifying about building American DTC infrastructure from a country where DTC barely exists at scale — you see the system from the outside, you are not socialized into its assumptions, and you are willing to ask questions that feel obvious to an outsider and feel dangerous to an insider. Why is everyone copying and pasting between tabs? Why does nobody automate this? The answer, often, is that insiders stopped noticing the problem.
Where Gorgias goes from here is an AI question disguised as a product question. If their AI can genuinely resolve 60% of tickets, the support center as a human operation changes fundamentally. Some merchants will need fewer agents. Others will redirect those agents toward proactive, revenue-generating conversations — the Shopping Assistant product that Gorgias launched alongside the AI Agent is a bet that CX teams become sales teams when they're not drowning in WISMO tickets. Arc'teryx reported a 23x ROI and a 75% increase in conversion rate from the shopping assistant. That is not a support metric. That is a revenue metric.
That reframing — from cost center to profit center — is the most interesting strategic bet Gorgias has made. It is also the answer to the pricing tension. If the new pitch is not "automate your tickets" but "turn your CX team into a revenue function," the economic model shifts. You're not charging for ticket deflection. You're charging for converted customers, increased AOV, reduced churn. The ticket price becomes a rounding error against the revenue impact.
Whether they can execute that reframe at 15,000 brands across every vertical of e-commerce is the open question. They have the distribution. They have the Shopify moat. They have the data. What they need now is the story — a story that takes them from "the most efficient way to handle where-is-my-order" to "the layer between your CX team and your revenue number."
That is not a small story to tell. But then again, it never was.
1. Shopify didn't just invest in Gorgias — Shopify is structurally dependent on Gorgias doing its job well.
The investment ran both directions in ways that aren't obvious from the outside. When a DTC merchant has a bad support experience, they blame the brand. When that happens at scale across thousands of Shopify stores, it erodes trust in the platform, not just the individual store. Shopify's investment in Gorgias was partly defensive: ensuring that CX quality across the Shopify ecosystem stays high enough that merchants don't leave and shoppers don't stop buying. Gorgias is, in a real sense, part of Shopify's infrastructure. It just happens to be owned by someone else.
2. The macro feature is not a template engine. It is an order management system wearing a templates costume.
When most people hear "macros," they picture mail merge. Fill in a name here, a date there. What Gorgias macros actually do is execute live API calls to Shopify at the moment an agent hits send — fetching real-time order status, current tracking data, updated delivery estimates. The response is accurate at the moment of sending, not at the moment the ticket arrived. This distinction is invisible to the merchant and invisible to the customer. It is entirely visible to the support agent who used to spend 90 seconds manually checking DHL, USPS, or FedEx before typing the answer, and who now sends an accurate answer in under five seconds.
3. Sixty percent automation is not a performance benchmark. It is a redistribution of labor.
When Gorgias says they automate 60% of support tickets, the implication is that 60% of work disappears. It does not. What happens is that 60% of tickets become non-events — they resolve without human attention. The remaining 40% are the hard ones: escalations, edge cases, angry customers, fraud disputes, complex returns. The automation removes the easy volume and concentrates human attention on exactly the cases where human attention matters most. For a support team, this is the difference between spending your day doing data lookups and spending your day doing actual problem-solving. The economics of support improve dramatically. The emotional weight of the job arguably increases.
4. The European founders didn't just build for American brands — they built a product that American founders wouldn't have built.
American SaaS founders in 2015 were focused on selling to enterprises. The DTC brand on Shopify doing $800K in revenue was below the radar of every major software company. French founders, running through YC, looking at user analytics on a Chrome extension, made the bet differently: go narrow, go deep, price to volume, win on specificity. The vertical SaaS playbook — go after one underserved industry and own it before expanding — is obvious in retrospect. At the time, the conventional wisdom was that horizontal tools scaled and vertical tools capped out. Gorgias proved the conventional wisdom wrong by doing something the conventional wisdom wouldn't have designed.
5. The pricing model is more radical than it appears.
SaaS charges per seat. Gorgias charges per ticket. This is not just a different price metric — it is a completely different relationship between the vendor and the customer. Per-seat pricing locks in revenue regardless of usage. Per-ticket pricing means Gorgias only gets paid when their customers are actually getting value. In the AI era, this matters enormously: if Gorgias's AI automates 60% of tickets, a per-seat model would charge the same amount for 40% of the work. A per-ticket model — properly structured to price AI-resolved tickets — creates a direct line between value delivered and revenue captured. The company that figured this out in 2017, before AI automation was a category, may be the company best positioned to navigate the economics of automated support in 2027.
Sources: TechCrunch funding coverage (2016, 2019, 2020, 2022), Sacra research, Gorgias product documentation, customer case studies, YC company profile, Crunchbase/PitchBook financial data. ARR figures: Sacra estimates.
