Linq
APIs and infrastructure for deploying AI agents into messaging channels and hosted computing environments.
Website: https://linqapp.com/
Cover Block
PUBLIC
| Field | Value |
|---|---|
| Name | Linq |
| Tagline | APIs and infrastructure for deploying AI agents into messaging channels and hosted computing environments. |
| Headquarters | Birmingham, United States [Crunchbase] |
| Founded | 2019 [Crunchbase] |
| Stage | Series B [PR Newswire, November 2026] |
| Business Model | API / Developer Platform |
| Industry | Other |
| Technology | AI / Machine Learning |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (3+), Elliott Potter, Patrick Sullivan, Jared Mattsson, Riley Davis [TechCrunch, February 2026] [LinkedIn] |
| Funding Label | $100M+ |
| Total Disclosed Funding | Approximately $120,000,000 [PR Newswire, November 2026] |
Links
From the public record
- Website: https://linqapp.com/
The Short Version
PUBLIC Linq sells APIs and communications infrastructure that let developers put AI agents into channels customers already use, a proposition that has become more investable now that the company has raised a $90 million Series B led by Andreessen Horowitz at a reported $1 billion valuation [linqapp.com] [PR Newswire, November 2026]. The public record indicates that Linq was founded in 2019 in Birmingham by Elliott Potter, Patrick Sullivan, Jared Mattsson, and Riley Davis, and that the company reached its current position after starting in digital business cards and later pivoting toward messaging infrastructure for AI agents [Crunchbase] [Apple Podcasts] [WOWTALE, November 2026] [LinkedIn].
The product thesis is straightforward: instead of forcing users into a new app, Linq gives companies a way to deploy AI assistants through existing messaging surfaces, with its website naming Apple Messages for Business, WhatsApp, SMS, RCS, voice, and compute among the product areas it supports [linqapp.com]. That distribution wedge appears to be the company’s main point of differentiation in public materials, along with its claim to handle channel access from one platform, though investors should separate that positioning from still-limited public evidence on retention, pricing durability, and channel-specific economics [linqapp.com] [Gunderson Dettmer, November 2026].
Founder-market fit is one of the cleaner parts of the story. Public reporting and profile data tie Potter, Sullivan, and Mattsson back to Shipt, where they held roles spanning marketing technology, frontend development, and partner success before leaving to build Linq, and Ben Horowitz joined the board after the Series B, giving the company a prominent governance signal even if it does not answer execution questions on its own [TechCrunch, February 2026] [LinkedIn] [The Org] [Techbuilders, March 2023] [PR Newswire, November 2026].
On financing, the disclosed record is concentrated but material: a $20 million Series A led by TQ Ventures in February 2026 and a $90 million Series B led by Andreessen Horowitz in November 2026, with the company stating it has raised more than $120 million in total [TechCrunch, February 2026] [PR Newswire, November 2026]. The business model is presented as an API and developer platform, and Linq’s own site shows self-serve pricing tiers alongside enterprise positioning, which suggests a land-and-expand motion is plausible but not yet fully documented in public filings or audited metrics [linqapp.com].
What merits attention over the next 12 to 18 months is whether Linq can convert message volume and customer growth into durable platform depth. Public sources cite more than 30 million messages processed each month, more than 1 billion messages processed across the customer base, 134,000 monthly active users for AI assistants, and 34% expansion in active accounts per customer after a strategy shift, but those figures come from a mix of company-linked and lightly corroborated coverage rather than a broad base of independent reporting [TechCrunch, February 2026] [The AI Journal] [Round].
Single-source, plausible -- This section relies on one independent outlet for the Series A, company announcement materials for the Series B and valuation, the company website for product positioning, and profile-based corroboration for founder backgrounds.
Taxonomy Snapshot
| Axis | Value |
|---|---|
| Stage | Series B |
| Business Model | API / Developer Platform |
| Industry / Vertical | Other |
| Technology Type | AI / Machine Learning |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (3+) |
| Funding | $100M+ total disclosed, approximately $120,000,000 |
The Company in Brief
PUBLIC
Linq presents today as an infrastructure company for putting AI agents into the communication channels people already use, and the public record places that business in Birmingham, Alabama, with a 2019 founding date [Crunchbase] [linqapp.com]. The company website describes Linq as "messaging infrastructure for AI agents," while its homepage points to a platform spanning messaging channels and compute surfaces rather than a single end-user application [linqapp.com].
The chronology matters because the current positioning is the product of a visible evolution. Elliott Potter has described himself publicly as co-founder and CEO of a digital business card company called Linq, which aligns with later investor commentary that Andreessen Horowitz first met him in 2020 when the company was building digital business cards [Apple Podcasts] [LinkedIn]. By November 2026, Linq was publicly announcing a $90 million Series B led by Andreessen Horowitz, with the company stating it had raised more than $120 million in total and that Ben Horowitz had joined its board [linqapp.com] [PR Newswire, November 2026].
That sequence leaves a company with a clearer recent identity than early one. Crunchbase lists Linq as founded in 2019, and the current website centers the infrastructure layer for AI agents rather than the earlier digital identity use case [Crunchbase] [linqapp.com]. Public materials do not establish the legal entity name in the source set used for this section, so the safer reading is simply that Linq has moved from an earlier digital business card product toward developer-facing communications infrastructure over time [Apple Podcasts] [linqapp.com].
Single-source, plausible -- Grounded primarily in Crunchbase and the company website, with chronology partially corroborated by founder and investor public profiles.
What They Have Built
Mixed sourcing
Linq’s product surface is easiest to understand as communications infrastructure for AI agents, not a consumer assistant in its own right. The company’s website describes a single platform that gives developers access to Apple Messages for Business, WhatsApp, SMS, RCS, Voice Agent Calling, and compute products including macOS cloud environments [linqapp.com]. TechCrunch’s February 2026 coverage aligns on the core use case, reporting that Linq helps companies place AI assistants inside messaging channels customers already use rather than pushing users into a separate app [TechCrunch, February 2026].
The more interesting technical point is where Linq appears to sit in the stack. Public materials frame the company as handling channel access and the operational layer around agent communication, including messaging delivery, identity, and scale across channels, according to Gunderson Dettmer’s November 2026 client note and the company site’s product taxonomy [Gunderson Dettmer, November 2026] [linqapp.com]. The same public materials also show product expansion beyond text messaging into voice and hosted compute, and PR around the Series B describes the company as building infrastructure for agents to use phones and computers, which is directionally broader than a pure messaging API [PR Newswire, November 2026] [Gunderson Dettmer, November 2026].
The available customer examples are still narrow, but they are concrete enough to show workflow depth. Public reporting says DoorDash uses Linq to let customers order, add items to carts, and complete checkout through Apple Messages for Business, which suggests the platform supports transactional flows rather than simple outbound notifications [TechCrunch, February 2026] [The AI Journal]. Other named users in public coverage include Town and Kernel, although the sources do not establish contract scope, deployment size, or whether those accounts also use the newer voice or compute products [The AI Journal] [PR Newswire, November 2026].
Single-source, plausible -- Product scope is corroborated by the company website and independent coverage from TechCrunch and Gunderson Dettmer, but several capability details and customer-use specifics remain partly company-attributed through financing and secondary coverage.
Market Size and Demand
From the public record
The market matters now because AI agents are moving from standalone apps into customer communication channels and operating environments that already have users, billing rails, and identity layers, which tends to pull infrastructure demand forward faster than end-user behavior changes [TechCrunch, February 2026] [Gunderson Dettmer, November 2026].
There is no cited third-party TAM, SAM, or SOM figure in the source set for Linq’s specific category, so the public record only supports an analogous-market framing rather than a formal market model. On the evidence available, Linq sits at the intersection of CPaaS-style messaging infrastructure and emerging agent infrastructure, with its public positioning centered on Apple Messages for Business, WhatsApp, SMS, RCS, voice, and hosted compute for agents [linqapp.com] [Gunderson Dettmer, November 2026]. That matters because the company is not selling a consumer AI app in isolation. It is attaching to existing enterprise communication workflows, where integration depth and channel coverage can matter more than raw model performance [TechCrunch, February 2026] [PR Newswire, November 2026].
Public demand signals in the source set point to distribution, not novelty, as the immediate tailwind. TechCrunch described Linq’s product as a way for companies to let AI assistants live within messaging apps rather than requiring a separate application, and Gunderson Dettmer similarly framed the platform around connecting AI agents to customers through established messaging channels [TechCrunch, February 2026] [Gunderson Dettmer, November 2026]. Linq’s own homepage extends that thesis to voice and compute surfaces, which suggests the adjacent market is broadening from message transport into agent execution infrastructure, although that expansion remains company-described in the public record [linqapp.com].
The operating metrics that have surfaced publicly are modest as market-sizing evidence but useful as directional proof of usage intensity. Coverage tied to the Series A reported 134,000 monthly active users for AI assistants, more than 30 million messages processed each month, 132% customer growth after a strategy shift, and 34% expansion in active accounts per customer [TechCrunch, February 2026]. Later coverage tied to the Series B said the platform had processed more than 1 billion messages across its customer base and described DoorDash, Town, and Kernel among the users of the infrastructure [PR Newswire, November 2026] [Citybiz, November 2026]. Those figures do not establish category size, but they do indicate that buyer interest is clustering around production-grade deployment and recurring message volume rather than experimentation alone.
Macro and regulatory conditions are supportive in a narrow sense and unresolved in a broader one. Supportive, because Apple Messages for Business, RCS, SMS, WhatsApp, and voice are all established communication surfaces with clear user habits, which lowers the friction of AI distribution if the infrastructure works reliably at scale [linqapp.com] [TechCrunch, February 2026]. Unresolved, because every step from identity to message routing to agent actions inside customer conversations can raise compliance, platform-dependence, and consent questions that are not addressed in detail in the public materials, especially as Linq expands from messaging into browser and macOS compute workflows described on its site [linqapp.com]. For investors, that means the market case likely rests less on a single headline TAM and more on whether agent deployment becomes a persistent infrastructure budget inside support, commerce, and customer engagement teams.
| Public market evidence | Figure | Framing |
|---|---|---|
| Monthly messages processed | 30 million+ | Early usage indicator for messaging-infrastructure demand [TechCrunch, February 2026] |
| Messages processed across customer base | 1 billion+ | Cumulative scale indicator for production deployment [PR Newswire, November 2026] |
| Monthly active users of AI assistants | 134,000 | Adoption indicator across deployed assistants [TechCrunch, February 2026] |
| Customer growth after strategy shift | 132% | Reported commercial acceleration after pivot [TechCrunch, February 2026] |
| Active accounts per customer growth | 34% | Reported expansion within existing customers [TechCrunch, February 2026] |
The table is useful less as market sizing and more as a read on where demand appears to be forming. The public evidence suggests a category that is still early, but already showing enough usage density to support infrastructure vendors that sit between AI agents and established communication channels.
Single-source, plausible -- This section relies on TechCrunch, PR Newswire, Gunderson Dettmer, Citybiz, and Linq’s website, but it does not have an independent third-party market sizing study for Linq’s exact category.
Who Else Is Fighting for This
MIXED Linq is positioning itself less as an end-user AI assistant and more as the plumbing that lets other companies place AI agents inside existing communication surfaces, a stance that puts it in a different lane from consumer agent apps but in direct tension with messaging platforms, CPaaS vendors, and any startup that tries to own the agent runtime end to end [TechCrunch, February 2026] [linqapp.com] [Gunderson Dettmer, November 2026].
The public record does not name a clean list of direct startup competitors, which is itself useful context. The company is described as providing access to Apple Messages for Business, WhatsApp, SMS, RCS, voice, and hosted compute from one platform, so the practical comparison set breaks into three groups: channel incumbents, application-layer agent builders, and infrastructure providers that could move down or up stack over time [linqapp.com] [Gunderson Dettmer, November 2026]. On the channel side, Apple Messages for Business and WhatsApp are not competitors in the usual venture sense, but they are gatekeepers because they control the user endpoints Linq depends on [linqapp.com] [TechCrunch, February 2026]. On the application side, the source material names DoorDash, Town, and Kernel as customers rather than rivals, which suggests Linq is trying to be the layer those companies build on rather than the branded assistant consumers interact with directly [PR Newswire, November 2026] [The AI Journal].
Linq's clearest edge today appears to be product scope across channels paired with a developer-oriented abstraction. Public materials describe one platform for Apple Messages for Business, WhatsApp, SMS, RCS, voice, and compute, and TechCrunch's February 2026 coverage framed the company around enabling AI assistants to live inside messaging apps users already open every day [linqapp.com] [TechCrunch, February 2026]. That is a meaningful distribution argument if it holds, because buyers may prefer one integration layer rather than stitching together separate channel vendors and agent tooling. The durability is less certain. A channel abstraction can be sticky once embedded in workflows, but it is also perishable if larger communications vendors or platform owners expose similar agent primitives natively.
The strongest public evidence for momentum is usage breadth rather than structural lock-in. Company-linked and press-release-adjacent sources say the platform processes more than 30 million messages each month and more than 1 billion messages across its customer base, and that DoorDash uses Linq to support ordering flows inside Apple Messages for Business [TechCrunch, February 2026] [The AI Journal]. Those figures, if sustained, matter because scale in messaging infrastructure can improve deliverability know-how, reliability, and implementation credibility with large customers. Still, most of the operational claims remain company-sourced or lightly corroborated, so the current edge looks more execution-based than regulatory or data-moat based.
The exposure is easier to define than the moat. Linq does not own the underlying channels, and the sources do not show exclusive rights to Apple, WhatsApp, SMS, RCS, or voice distribution [linqapp.com] [Gunderson Dettmer, November 2026]. That means any shift in platform rules, pricing, API access, or preferred partner structures could compress differentiation. It also means a better-capitalized communications platform could compete by bundling transport, compliance, and agent tooling together. Separately, if end customers decide they want a full-stack assistant vendor rather than infrastructure, Linq could be pushed into a lower-visibility supplier role even as adoption grows.
The most plausible 18-month scenario is that the category stratifies rather than consolidates. Apple Messages for Business is the winner if enterprise demand keeps moving toward native, in-channel transactions and service interactions, because control of the endpoint raises the value of every integration built around it [TechCrunch, February 2026] [linqapp.com]. Linq is a secondary winner in that case if it remains the simplest way to deploy across channels instead of forcing enterprises into one surface. The loser if platform owners or large communications vendors ship comparable cross-channel agent infrastructure is any independent layer whose differentiation rests mainly on aggregation. On the current evidence, that is the risk Linq has to outrun.
Opportunity
PUBLIC
The prize here is unusually large if Linq becomes the infrastructure layer that lets AI agents reach customers where they already spend time, rather than forcing every company to build its own messaging, voice, and compute stack from scratch [linqapp.com] [TechCrunch, February 2026] [PR Newswire, November 2026].
The headline opportunity is straightforward: Linq could become the default communications rail for customer-facing AI agents across messaging and adjacent execution environments. That is a bigger outcome than being a feature vendor inside one app, because the product is positioned at the infrastructure layer, spanning Apple Messages for Business, WhatsApp, SMS, RCS, voice, and hosted compute surfaces according to company materials and financing coverage [linqapp.com] [Gunderson Dettmer, November 2026] [PR Newswire, November 2026]. The path looks reachable, not merely aspirational, because public evidence already shows two things that matter at this stage: real volume, with more than 30 million messages per month and more than 1 billion messages processed across the customer base, and credible distribution proof, with DoorDash cited as a customer and Andreessen Horowitz leading the Series B while Ben Horowitz joined the board [TechCrunch, February 2026] [The AI Journal] [PR Newswire, November 2026].
The upside paths are still contingent, but they are legible enough to frame in concrete scenarios.
| Scenario | What happens | Catalyst | Why it's plausible |
|---|---|---|---|
| Messaging system of record for AI commerce | Linq becomes the standard API layer for brands that want AI agents to handle ordering, support, and transaction flows inside existing channels | A visible customer proving checkout and cart expansion inside Apple Messages for Business, as reported for DoorDash | DoorDash is already cited using Linq for ordering and checkout workflows, and messaging was Linq's first product, suggesting product focus rather than surface-level experimentation [The AI Journal] [TechCrunch, February 2026] |
| Multi-channel control plane for enterprise agents | Linq moves from messaging middleware to the orchestration layer across SMS, RCS, WhatsApp, voice, and hosted compute environments | Expansion of the current product set into calling and compute, as presented in company materials | The homepage already lists messaging channels, voice agent calling, and compute offerings, while the Series B announcement frames the company as building infrastructure for AI agents more broadly [linqapp.com] [PR Newswire, November 2026] |
| Picks-and-shovels provider for agent startups | Linq becomes a shared infrastructure vendor for a wide set of AI-native applications that need identity, delivery, and scale but do not want to build telecom-grade plumbing internally | Continued demand from AI companies following the company's pivot toward infrastructure | Coverage of the pivot says inbound demand increased when AI assistant use cases gained traction, and customer growth was reported at 132% after the strategy shift [WOWTALE, 2026-11-20] [Round] |
What compounding looks like is less about consumer network effects and more about infrastructure lock-in. If a customer launches one agent through Linq and sees adoption, the next logical step is to add more channels, more use cases, and more agent behaviors on the same backbone. Publicly cited traction points suggest that dynamic may already be starting: customer growth was reported at 132% after the company adopted its new strategy, active accounts per customer reportedly expanded 34%, and its AI assistants reached 134,000 monthly active users [Round]. Those figures do not prove durable retention on their own, but they do support the idea that one integration can widen into a broader account footprint.
There is also an operational flywheel embedded in the product mix. Messaging infrastructure is difficult to rebuild repeatedly inside each enterprise, especially when the requirement is to manage identity, delivery, and channel-specific behavior across several endpoints [TechCrunch, February 2026] [Gunderson Dettmer, November 2026]. If Linq can pair that connectivity layer with adjacent voice and hosted compute products, the company has a credible path to higher wallet share per customer and deeper switching costs over time [linqapp.com] [PR Newswire, November 2026]. Processed volume matters here: more than 1 billion messages across the customer base is not just a vanity number, it implies repeated real-world usage that can inform product reliability and account expansion if the company continues to execute [The AI Journal].
The size of the win is easiest to frame in private-market terms because the latest disclosed benchmark is already substantial. Linq said it was valued at $1 billion after its November 2026 Series B, which also brought total disclosed funding to more than $120 million [PR Newswire, November 2026]. If the company becomes the default infrastructure layer for enterprise AI agents across messaging and execution surfaces, a multi-billion-dollar outcome is plausible (scenario, not a forecast), because the market would be valuing not a single application but the communications substrate that many applications depend on. The public record here does not provide a clean listed comparable or a named third-party TAM estimate, so the more disciplined read is relative rather than absolute: the company has already crossed into unicorn territory on the strength of this infrastructure narrative, and the upside from here depends on proving that the current messaging wedge can broaden into a durable platform category [PR Newswire, November 2026] [TechCrunch, February 2026].
Single-source, plausible -- This section relies on a mix of independent reporting and company-announced claims, with strongest support from TechCrunch, PR Newswire, Gunderson Dettmer, and the company website; several traction metrics come from single-source coverage only.
Sources
From the public record
[Crunchbase] Linq | Crunchbase Company Profile & Funding | https://www.crunchbase.com/organization/linq-bd0c
[PR Newswire, November 2026] Linq Raises $90 Million in New Funding Led by Andreessen Horowitz to Build the Infrastructure Platform for AI Agents | https://www.prnewswire.com/news/linq/
[TechCrunch, February 2026] Linq raises $20M to enable AI assistants to live within messaging apps | https://techcrunch.com/2026/02/02/linq-raises-20m-to-enable-ai-assistants-to-live-within-messaging-apps/
[LinkedIn] Riley Davis | Linq | https://www.linkedin.com/in/riley-davis-600b10155/
[WOWTALE, November 2026] Linq Raises $90 Million Series B to Build Messaging Infrastructure for AI Agents | https://en.wowtale.net/2026/11/20/236104/
[Gunderson Dettmer, November 2026] Linq Announces $90 Million Series B | https://www.gunder.com/en/news-insights/client-news/linq-announces-dollar90-million-series-b
[Apple Podcasts] PR With The Pros: Elliott Potter | https://podcasts.apple.com/us/podcast/pr-with-the-pros-elliott-potter/id1400629358?i=1000552443839
[linqapp.com] Messaging infrastructure for AI agents | Linq | https://linqapp.com/
[The Org] Jared Mattsson | President & Co-founder at Linq | https://theorg.com/org/linqapp/org-chart/jared-mattsson
[Techbuilders, March 2023] Elliott Potter, Linq | https://techbirmingham.com/techbuilders-elliott-potter-linq/
[Citybiz, November 2026] Linq Raises $90M Led by a16z To Build the Infrastructure for Personal AI Assistants | https://www.citybiz.co/article/935989/linq-raises-90m-led-by-a16z-to-build-the-infrastructure-for-personal-ai-assistants/
Articles about Linq
- DoorDash's AI Ordering Runs on Linq's Billion-Message Platform — The ex-Shipt team's pivot to a communications layer for AI agents has landed Andreessen Horowitz and a unicorn valuation.