We detected 716 companies using Pylon, 12 companies that churned, and 7 customers with upcoming renewal in the next 3 months. The most common industry is Software Development (54%) and the most common company size is 11-50 employees (48%). We find new customers by discovering internal subdomains and certificate transparency logs.
Note: We only detect companies that use the customer portal or a chat widget
Source: Analysis of job postings that mention Pylon (using the Bloomberry Jobs API)
Job titles that mention Pylon
i
Based on an analysis of job titles from postings that mention Pylon.
Job Title
Share
Director of Customer Success
17%
Head of Customer Support
14%
Technical Support Engineer
11%
Customer Success Manager
9%
I noticed that Pylon buyers are predominantly customer-facing leaders, with Directors of Customer Success and Heads of Customer Support making up 31% of leadership roles. These executives are hiring across post-sales functions and prioritizing scalability, as evidenced by roles seeking to build support operations from scratch or transform customer care into a strategic advantage. The pattern suggests Pylon appeals to fast-growing B2B SaaS companies where customer experience leaders need unified platforms to manage tickets, knowledge bases, and team performance at scale.
Day-to-day users are technical support engineers and customer success specialists who handle frontline customer interactions. I found they spend significant time responding to tickets through multiple channels, troubleshooting technical issues, and maintaining documentation. Several postings mention using Pylon alongside tools like Linear, Datadog, and Slack, indicating it serves as the central hub for routing customer requests and managing support workflows across distributed teams.
The core pain points center on operational efficiency and scaling challenges. Companies repeatedly describe needing to handle growing ticket volumes while maintaining quality, with phrases like "clearing queues" and "manage multiple active transactions at once" appearing frequently. One posting explicitly stated the goal of building "automations and tooling that will let us scale without drowning in tickets," while another emphasized "eliminating manual work" and ensuring "no ticket goes dark." These companies want to professionalize chaotic support operations without adding headcount proportionally.
👥 What types of companies use Pylon?
Source: Analysis of Linkedin bios of 716 companies that use Pylon
I noticed that Pylon's customers are overwhelmingly developer-focused B2B software companies building infrastructure, tools, and platforms for other businesses. These aren't consumer apps or services. They're creating APIs, integration platforms, AI models, authentication systems, data pipelines, and developer tools. Many are building "platforms" or "infrastructure" that other companies build on top of. Even when they touch end-user experiences, like Superwall's paywall tools or Clueso's video creation, they're selling to other businesses who serve the end users.
These are definitively early-stage companies. Of the 28, most are seed stage or pre-seed, with a handful at Series A and only two at Series B or C. Employee counts cluster between 2-50 people. Funding rounds are modest, typically $2-8M. Several have YC backing. These companies are post-product-market fit enough to have customers but still figuring out scale. They're venture-backed, growth-focused, and likely burning through their runway while racing to prove their model.
🔧 What other technologies do Pylon customers also use?
Source: Analysis of tech stacks from 716 companies that use Pylon
Commonly Paired Technologies
i
Shows how much more likely Pylon customers are to use each tool compared to the general population. For example, 287x means customers are 287 times more likely to use that tool.
I noticed that Pylon users are predominantly B2B SaaS companies in the product-led growth stage who are building sophisticated operational infrastructure while scaling rapidly. The combination of tools like Ashby, Vanta, and Incident.io tells me these companies are past the scrappy startup phase and investing heavily in compliance, hiring, and reliability as they move upmarket or prepare for enterprise customers.
The pairing with Ashby is particularly revealing. Companies using advanced recruiting software alongside Pylon are clearly in active growth mode, likely scaling their teams rapidly while trying to maintain company culture and operational excellence. The strong correlation with Thena and UnifyGTM suggests these companies are thinking deeply about customer-facing workflows and go-to-market efficiency. They're not just answering customer questions, they're treating customer interactions as a strategic function that needs specialized tooling. The Incident.io connection makes perfect sense too. Companies that invest in formal incident management are running production systems that matter to paying customers and need to maintain high reliability standards.
The full stack reveals companies that are product-led but maturing into more structured organizations. They're past the "move fast and break things" stage and entering the "move fast with guardrails" phase. The emphasis on compliance tools like Vanta, incident management, and sophisticated recruiting suggests Series B or C companies that are professionalizing their operations while maintaining growth velocity. These aren't sales-led organizations with massive SDR teams. They're building products that customers discover and adopt, then using tools like Pylon to support and retain those customers effectively.
Alternatives and Competitors to Pylon
Explore vendors that are alternatives in this category