How The Connector Co. Runs Investor Outreach on Kantos, with Claude in the Pipeline
Kantos Team
A London firm that introduces companies raising capital to the right investors keeps every lead in Kantos and has Claude work the pipeline through MCP.
The Connector Co.connector-co.comThe Connector Co. introduces companies raising capital to the investors who can fund them. The team is based in London and works across Europe and beyond. They find family offices, private equity firms and real estate funds whose mandate fits the raise, start a personal conversation on LinkedIn, and hand their client only the investors who have already said they want to talk.
That work is a long run of small follow-ups across thousands of people, and they keep all of it in Kantos. In their own words: "Every lead lives in Kantos, an AI-native CRM. Claude is plugged straight into it, so your pipeline is watched, scanned and managed around the clock."
One record for every investor
Each investor they approach is a record in Kantos, with the details that decide whether a conversation is worth having:
- Who they are. Name, company, job title, country and LinkedIn profile.
- What they invest in. Asset class focus, geographic focus and decision timeframe.
- Where the conversation stands. Status, interest level, the date of the last reply, how many follow-ups have gone out, and the date of the next one.
- Who owns it. The person running that conversation, and the next action they have planned.
Because the fields are their own, the record says what a capital introduction needs, not what a generic sales CRM expects.
A list for each raise
Every client raise gets its own list in Kantos, with its own fields and statuses. On their site they describe two of them: a European property investment business put in front of family offices and real estate investment firms, and a modular construction company raising equity from family offices, private equity and real estate funds. Keeping each raise separate means each client's investors, notes and follow-ups stay together in one place.
Claude works the pipeline
The Connector Co. connects Claude to their Kantos workspace through the Kantos MCP server. MCP is the open standard that lets an AI assistant work inside your software rather than only talk about it. Their site puts it simply: "Kantos has it built in, so Claude can read, update and act on your leads directly."
In practice that means asking in plain English instead of building reports. Which investors replied this week? Who is due a follow-up? Which family offices in a given country have not heard from us in a month? Claude can search and filter the records to answer, then update a status, log a note or set the next follow-up date on the records it found.
Claude signs in with a person's own Kantos login and works only inside that person's organisation. As The Connector Co. tells its clients, "Claude works only inside your CRM workspace through a permissioned connection, and every action it takes is logged." If you want to try the same setup, our guide shows how to connect Claude to your CRM.
Their own enquiries land in Kantos too
The "Get a free outreach audit" form on connector-co.com sends each enquiry straight into Kantos through a form webhook. The record arrives with the company's goal and opportunity, the deal size, who they want to reach, their target regions and when they want to start, so the team can prepare before the first call.
What their clients see
The Connector Co. promises each client "live access to your CRM workspace, a weekly report and a named contact for your campaign." Because the pipeline lives in Kantos, the workspace a client looks at is the one the team and Claude update every day, not a copy made for reporting.
Getting started
If your team runs outreach and wants an AI assistant working inside the CRM instead of beside it, read about the CRM built for AI agents, or talk to us about setting it up for your team.