<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tapan Jain</title>
    <description>The latest articles on DEV Community by Tapan Jain (@jaint).</description>
    <link>https://dev.to/jaint</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3864771%2F10b1376d-035b-45c0-8fde-9cab821f0aa4.png</url>
      <title>DEV Community: Tapan Jain</title>
      <link>https://dev.to/jaint</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jaint"/>
    <language>en</language>
    <item>
      <title>We're an IT services company. We built a WhatsApp MCP server. Now we're trying to find who actually needs it.</title>
      <dc:creator>Tapan Jain</dc:creator>
      <pubDate>Tue, 07 Apr 2026 02:14:38 +0000</pubDate>
      <link>https://dev.to/jaint/were-an-it-services-company-we-built-a-whatsapp-mcp-server-now-were-trying-to-find-who-actually-25ab</link>
      <guid>https://dev.to/jaint/were-an-it-services-company-we-built-a-whatsapp-mcp-server-now-were-trying-to-find-who-actually-25ab</guid>
      <description>&lt;p&gt;I'll be honest — we didn't start as a product company.&lt;/p&gt;

&lt;p&gt;JCS has been doing IT services for 15+ years. &lt;br&gt;
Staff aug, custom dev, the usual. Good business. &lt;br&gt;
Predictable. Not particularly exciting.&lt;/p&gt;

&lt;p&gt;About 8 months ago we started noticing something. &lt;br&gt;
Every client we worked with — agencies, D2C brands, &lt;br&gt;
consultants — had the same problem. WhatsApp was &lt;br&gt;
their primary customer channel but their entire &lt;br&gt;
setup was manual. No automation. No unified inbox. &lt;br&gt;
No API layer that actually worked across providers.&lt;/p&gt;

&lt;p&gt;So we built one.&lt;/p&gt;

&lt;p&gt;We called it Jina Connect. A WhatsApp MCP server &lt;br&gt;
that unifies WATI, Gupshup, Twilio and Meta Direct &lt;br&gt;
into a single API. One integration. Switch providers &lt;br&gt;
without touching your backend code.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Where we are now&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The product works. We've tested it internally and &lt;br&gt;
with a handful of clients.&lt;/p&gt;

&lt;p&gt;But we're an IT services company trying to find &lt;br&gt;
PMF for a SaaS product. That's a different muscle &lt;br&gt;
entirely and we're feeling it.&lt;/p&gt;

&lt;p&gt;What we think we know:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Digital marketing agencies managing 10+ clients 
on WhatsApp are the most obvious fit&lt;/li&gt;
&lt;li&gt;D2C brands running Meta ads where leads land 
on WA with no follow-up are close second&lt;/li&gt;
&lt;li&gt;The "unified API" pitch resonates with developers 
but less so with agency owners who just want 
it to work&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What we're unsure about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Whether to go direct to brands or through agencies&lt;/li&gt;
&lt;li&gt;Whether the aggregator angle is the right hook 
or if we should lead with a specific use case&lt;/li&gt;
&lt;li&gt;How to sell this without a sales team&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;strong&gt;Why I'm posting this&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Not to pitch. Genuinely to think out loud and &lt;br&gt;
hear from people who've navigated this — &lt;br&gt;
especially the services-to-product transition.&lt;/p&gt;

&lt;p&gt;If you've built something in the WhatsApp / &lt;br&gt;
messaging API space, or if you're an agency &lt;br&gt;
that manages WhatsApp for clients, I'd love &lt;br&gt;
to hear what actually matters to you.&lt;/p&gt;

&lt;p&gt;Happy to share more as we go.&lt;/p&gt;

&lt;p&gt;— Tapan&lt;br&gt;
Co-founder&lt;br&gt;
JCS / Jina Connect&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>saas</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
