AgentSDR

AgentSDR

09/10/2026
Sponsored Link

AgentSDR — Investment Research Report

Product Hunt launch date: 2026/10/09

Product Hunt listing: AgentSDR

Research date: 2026-10-12

Project owner: Kandid; Product Hunt maker Pulkit Garg

Category: Open-source sales engagement / AI-assisted SDR workspace

Final Decision: Pass

Executive Summary

AgentSDR is a free, MIT-licensed, self-hosted outbound sales workspace. It combines email sequences, LinkedIn outreach, WhatsApp messages and calls, lead enrichment, a CRM, and an inbox that classifies replies and drafts responses for human approval. Customers run the app and database on their own infrastructure and provide their own model and service keys.

The product addresses a real sales-stack pain point: leads, enrichment, sequences, channels, and replies are scattered across multiple tools. Its broad feature set, open code, and customer data control make it interesting to technical founders and small teams. But AgentSDR has no seat, contact, subscription, or usage revenue. MIT licensing permits third parties to self-host, modify, resell, and offer hosted versions. Kandid’s separate paid product, an AI sales assistant for Shopify and D2C brands, should not be counted as AgentSDR revenue.

The product also depends on LinkedIn automation, which LinkedIn’s current agreement prohibits when performed through unauthorized bots or automated methods. Its WhatsApp workflow relies on WhatsApp Web and external integrations, creating policy and account-continuity risk. Public adoption is unproven: the GitHub repository showed 28 stars and 8 forks at review time, while the demo’s campaign data is explicitly fictional.

Because there is no clear AgentSDR business model, commercial traction is minimal, and a core channel faces policy risk, the recommendation for AgentSDR as an investment target is Pass. Evaluate Kandid’s D2C sales product separately.

Investment Metrics

MetricAssessment
Product Hunt launch date2026/10/09, from the source sheet
StagePublic release 0.1.0 on October 6, 2026
License / priceMIT open source; free self-hosting
UsersFounders, agencies, and small or technical B2B sales teams
Revenue modelNo AgentSDR fee disclosed; users pay infrastructure and providers
Product signals28 GitHub stars, 8 forks at review time
Parent contextKandid markets a separate paid D2C AI salesperson
RecommendationPass for AgentSDR

Product and Value Proposition

AgentSDR centralizes a prospect record and its communication across email, LinkedIn, and WhatsApp. It supports spreadsheet imports, enrichment from 15 providers, AI/API columns, campaign sequences, and an AI CRM that classifies replies and prepares drafts for human approval. Analytics track replies, meetings, and customers by channel. The self-hosted product uses Docker, Next.js, and PostgreSQL, with customer-provided Google Workspace, Unipile, OpenRouter, storage, and enrichment accounts.

Its strongest appeal is consolidated workflow and data control. The project documents encrypted credentials, organization scoping, sending caps, unsubscribe handling, Do Not Contact controls, and human approval. These are useful design choices, though not an independent security audit.

The product has material gaps: no built-in lead database or data marketplace; email sends only through Google Workspace; no built-in email warm-up, HubSpot or Salesforce sync, or waterfall enrichment; and each campaign uses one channel rather than mixed-channel steps. Self-hosting also asks customers to own setup, maintenance, backups, and updates.

Company and Team

The repository and project site identify Kandid as the company leading AgentSDR and say it runs the product in production. Product Hunt lists Pulkit Garg as maker; public company material identifies Pulkit Garg and Bhavya Arora as Kandid co-founders. The first public AgentSDR release was October 6, 2026. No AgentSDR-specific funding, revenue, or valuation was found in reviewed sources.

Kandid’s main website sells a separate AI salesperson for Shopify and D2C brands, with advertised plans from $19 to $99 per month and usage charges. It publishes customer outcome claims, but these are vendor-reported and do not establish AgentSDR traction. Investors need to know whether AgentSDR is a separate product, a free growth channel, or an internal tool for the company’s sales efforts.

Market and Competition

Potential users include founders without an SDR team, agencies, and B2B sales groups that want lower software costs and a shared inbox. The broader sales engagement market is large, but crowded with mature tools. AgentSDR compares itself with Clay, lemlist, HeyReach, Instantly, Apollo, Smartlead, Salesloft, and Outreach.

Its distinction is self-hosting, MIT code, zero seat/contact fees, and a multi-channel CRM. These features suit technical buyers who can operate infrastructure. Hosted alternatives provide contact databases, email warm-up, easier setup, support, and mature integrations. AgentSDR’s own comparison page acknowledges several gaps.

The MIT license encourages adoption but weakens proprietary defensibility: others may modify and sell the code without publishing changes. Community contributions or a trusted hosted service could create an advantage, but current repository interest is too early to establish a network effect.

Traction and Commercialization

The project is only days old. GitHub’s 28 stars and 8 forks are early interest signals, not usage or customer evidence. Product Hunt rank and votes are temporary discovery metrics. The official demo uses fictional sample data; visible campaign totals and reply rates are not customer performance.

AgentSDR is free. Users pay for their own server, AI, Google Workspace, Unipile, enrichment, and storage. No paid hosted plan, support package, or usage pricing was found. Managed hosting, enterprise support, or implementation could become revenue paths, but are not disclosed today; third parties can also sell hosted versions under the MIT license.

Kandid’s separate D2C product may support the broader company, but no AgentSDR paid usage, retention, support cost, or revenue was reported. Those metrics should be tracked separately.

Business Model and Economics

There is no AgentSDR subscription model or published unit economics. The free self-hosted approach removes vendor fees and transfers infrastructure costs to customers. A hosted version could create recurring revenue, but would compete with self-hosting and MIT forks. Paid support and enterprise governance are possible hypotheses, not validated offerings.

Using customers’ own model and enrichment keys limits Kandid’s usage-cost exposure. Kandid still must fund development, security response, compatibility work, and community support. Revenue, margin, acquisition cost, and support load are unknown, so a product-level forecast would be speculative.

Unicorn Path and Valuation

A venture-scale path would require AgentSDR to become a trusted open-source entry point to a commercial sales platform with managed deployment, deliverability, integrations, governance, and analytics. It must also resolve the channel-policy risk and prove that customers will pay for a hosted or supported option. Alternatively, it may remain an internal tool or community project for Kandid, which would be strategically useful but not a separate venture asset.

No AgentSDR revenue, cap table, funding round, or valuation is public. Kandid’s separate product is insufficient to value AgentSDR; investors need company-level financials and clear product-line economics.

Risk Assessment

  1. LinkedIn policy: The agreement prohibits unauthorized automated contact and messaging; restrictions could remove a core feature.
  2. WhatsApp continuity: Use of WhatsApp Web and third-party integrations creates policy and account risks.
  3. Compliance: Cold email, contact data, and call recording carry jurisdiction-specific requirements.
  4. Monetization: No AgentSDR charge or proprietary hosted offer is disclosed.
  5. Competition: Missing contact data, warm-up, CRM sync, and cross-channel sequencing are notable gaps.
  6. Security operations: Self-hosting gives data control but leaves patching, backups, and key protection to customers.
  7. Maturity: Version 0.1.0 and small public code signals indicate an early product.
  8. Strategy: The link between AgentSDR and Kandid’s D2C business is not explained publicly.

Scorecard

DimensionScoreRationale
Problem and market12/15Clear sales-stack pain in a large market
Product and differentiation12/15Broad self-hosted workflow with important gaps
Team and execution9/15Kandid operates a related AI product; AgentSDR is new
Traction and validation4/15Small code signals; demo figures are fictional
Business model and economics2/15No direct fee or capture model
Defensibility4/10Open-source adoption helps; code is forkable
Distribution7/10Open source offers reach, adoption unproven
Compliance and operations2/5Key channels create policy and continuity risk
Total52/100Product promise exceeds investment readiness

Evidence Confidence

Moderate for features, license, ownership, and product gaps, based on the project site, repository, and Product Hunt. Low for external adoption, customer outcomes, financials, and future monetization. GitHub metrics are point-in-time counts; Kandid’s D2C performance claims are not AgentSDR results.

Final Decision and Change Conditions

Final Decision: Pass. AgentSDR has no disclosed revenue model, and its LinkedIn automation conflicts with LinkedIn’s published restrictions. Open code, self-hosting, and a unified CRM are useful, but do not offset the absence of commercial traction and channel continuity.

Reassess if Kandid launches a compliant managed offering, proves recurring paid deployments, and demonstrates reliable channel access. Evaluate Kandid’s D2C sales product separately through its own financials, retention, and attribution evidence.

Due Diligence Questions

  1. Is AgentSDR a standalone product, a growth channel, or an internal tool for Kandid?
  2. What paid offering is planned, and how will it compete with MIT forks?
  3. How many external deployments remain active after 30, 90, and 180 days?
  4. What will replace or redesign LinkedIn automation under LinkedIn’s restrictions?
  5. Does WhatsApp use approved business APIs, and how are opt-in and call-recording consent handled?
  6. What security testing covers Workspace access, integration credentials, and call recordings?
  7. How many users complete self-host setup without support, and what maintenance is required?
  8. How will the team address missing contact data, warm-up, CRM sync, and mixed-channel sequences?
  9. What are Kandid’s revenue, margin, retention, and funding status for its D2C product?
  10. What evidence supports Kandid’s sales-attribution claims, and does AgentSDR contribute?

Sources

Conclusion

AgentSDR consolidates outbound workflows and offers strong data ownership through self-hosting. Its investment case is limited by absent product revenue, early adoption, MIT resale rights, and a core LinkedIn feature that conflicts with platform rules. The decision for AgentSDR is Pass; Kandid’s paid D2C business requires separate underwriting.