Manicule’s CTO built AI marketing on context, not content

laptop screen displaying colorful code

Most AI marketing conversations start with the model. Shreyans Jain starts with the context. That difference, more than any tool choice, is what shaped how he built Manicule’s technical foundation and what pushed the company to roughly $53,000 in monthly revenue during Y Combinator.

Jain is Co-Founder and CTO at Manicule, a developer-focused marketing company. His argument is straightforward: a model can write fluent copy from weak context, but fluency and accuracy are not the same thing. For developer companies, where users can check technical claims almost immediately, that gap is expensive.

“People focus on the model, but the model only works with what you give it. If the system does not understand the company well enough, the output will still be generic.”

Where the Thinking Started

Jain’s background is in AI memory infrastructure. Before Manicule, he was employee No. 1 and founding engineer at Supermemory, a product that grew to more than 100,000 users and raised $3 million. The open-source project pulled more than 20,000 GitHub stars, and the memory system ranked first on LongMemEval, LoCoMo, and ConvoMem.

At Supermemory, Jain built the consumer app, MCP v2, Console, and SDK integrations for the Vercel AI SDK and OpenAI’s JavaScript and Python SDKs. Those integrations reduced memory setup to about two lines of code and contributed to annual contracts worth more than $50,000.

3D rendered ai text on dark digital background

The Platform He Built at Manicule

At Manicule, Jain applied the same core problem to a different domain. He built the shared platform that handles client context, content production, and publishing across all of Manicule’s client engagements.

Product specifications, code, and customer knowledge move through a structured workflow: research, drafting, human review, verification, and publication. Agents run in isolated sandboxes. Edits are versioned. Published material can serve both human developers and AI agents through company websites, llms.txt, and MCP.

The goal is to give agents a working understanding of a company before they produce anything. That shared foundation stays consistent even when the final deliverable changes from one client to another.

What the Numbers Show

Across its client work, Manicule has reported roughly 37 percent fewer support tickets and millions of impressions. For Supermemory specifically, a developer-relations campaign produced more than 1 million SEO impressions and 90 percent traffic growth over three months. A benchmark-led Reddit campaign generated more than 200,000 views. A documentation launch completed in 23 days was followed by a reported 30 percent improvement in answer success.

Jain credits those outcomes to the infrastructure beneath the campaigns, not the campaigns themselves.

“If the information is bad, scaling it does not fix the problem. You are just giving the system more bad information to work with.”

The Problem He’s Actually Solving

Developer marketing is shifting. Jain points to answer engine optimization, generative engine optimization, and the growing use of coding agents as evidence that AI now plays a meaningful role in how developers discover and implement products.

In that environment, publishing volume alone does not compensate for weak product context. An AI agent recommending a tool to a developer needs accurate, detailed information about what that tool actually does. Generic content does not survive that test.

“Companies want to know what they can publish to get recommended more often. The harder question is whether the agent actually has enough accurate context to understand what the product does.”

Jain’s answer is to work upstream, on the systems that determine what an agent knows before it writes anything. That is the lesson he carried from Supermemory, and it is the technical bet Manicule is built on.

Stay on top of AI & Automation with BizStack Newsletter
BizStack  —  Entrepreneur’s Business Stack
Logo