Kyo is the complete companyOS for agencies. Its tagline is simple: all your agency's tasks, sales, clients, and workflows in one workspace. For teams that already sell, support, and build relationships through DMs, Kyo turns those conversations into structured CRM context.
Anwar Lemu, co-founder of Kyo, found Context.dev on X/Twitter while looking for a way to build automatic CRM enrichment. The goal was to let Kyo read a conversation, understand where it was happening, identify the lead, and create a complete deal record without forcing the user to manually research every person or company.
Here is how Anwar put it:
"Context.dev is incredible. Very easy to use and plugin to Claude. Easy to navigate and understand. And most of all, powerful. We use it for our CRM scraping feature to automatically create enriched CRM deals with full information just from X/Twitter messages. Great product. Great founder."
What is Kyo?
Kyo is an operating system for agencies, combining CRM, projects, finances, knowledge base, HR, and client spaces in one workspace. Agencies can manage pipelines, client work, internal tasks, and team performance without stitching together a separate CRM, spreadsheet, project board, and wiki.
That makes context one of the most important pieces of the product. A DM is not just a message. It can be a lead, a company, a sales stage, a project opportunity, and a relationship history. Kyo's CRM needs to capture that context as soon as the conversation starts.
The use case
Kyo uses Context.dev to turn X/Twitter conversations into enriched CRM deals.
When a lead appears in a DM, Kyo can use the lead's username as the starting point. Context.dev helps gather the person and company details, identify the company behind the conversation, and source the company logo used inside the CRM. The result is a deal record that feels complete from the beginning instead of starting as a blank card with a name pasted in.
How they found Context.dev
Anwar was building Kyo's automatic enrichment feature and found Context.dev on X/Twitter. The product fit the job immediately: Kyo needed reliable web context and brand data from a lightweight integration, not another research workflow for users to maintain.
As Anwar described it, Context.dev did the CRM enrichment job "perfectly" and then helped with other features as well.
Integration experience
Kyo plugged Context.dev into its Claude-assisted development workflow and used it as the data layer for CRM scraping and enrichment. The API was easy to navigate, the behavior was straightforward to understand, and the output was strong enough to power a core product workflow.
The important part is that Context.dev sits behind the user experience. Kyo users can focus on their conversations while the product fills in the missing company context, contact details, and logos around each deal.
Key benefits
- DMs become deal records: X/Twitter conversations can become structured CRM opportunities without manual research.
- Lead context starts from the username: Kyo can use the place where the conversation happens as the seed for enrichment.
- Company details and logos are sourced automatically: Context.dev helps Kyo populate the company data and visual branding used in the CRM.
- Less blank-state CRM work: Sales teams get richer deal cards from the start, making pipeline review and follow-up easier.
By using Context.dev, Kyo can turn informal DM conversations into organized, enriched CRM deals. That gives agencies a cleaner pipeline without asking them to copy details across tools or manually hunt down every logo, website, and company profile.
Want to turn messy web context into structured product data? Context.dev gives your product the web scraping and brand data layer so your users can stay focused on the workflow, not the research.